I would like to be able to access the server network from the client with an establishedVPN connection on tun0. I've got the following setup:
- Client (10.8.0.6 on tun0 and 172.28.220.95 on wlan)
- VPN server (10.8.0.1 on tun0 and 192.168.178.32 on eth)
- Server-side network (192.168.178.0/24)
Routing on the client side:
client$ ip route show 10.8.0.0/24 dev tun0 scope link src 10.8.0.6 client$ ip route show table local local 10.8.0.6 dev tun0 proto kernel scope host src 10.8.0.6 local 172.28.220.95 dev wlp2s0 proto kernel scope host src 172.28.220.95
And on the server side:
server$ ip route show default via 192.168.178.1 dev eth0 10.8.0.0/24 dev tun0 scope link 192.168.178.0/24 dev eth0 proto kernel scope link src 192.168.178.32 server$ ip route show table local local 10.8.0.1 dev tun0 proto kernel scope host src 10.8.0.1 local 192.168.178.32 dev eth0 proto kernel scope host src 192.168.178.32
Irrelevant routes and broadcast routes left out for clarity.
The server can ping itself at 10.8.0.1. The client can ping itself at 10.8.0.6. However, when I try to ping the client from the server or vice versa I get no response (but no error either, besides the 100% packet loss).
Any ideas on what goes wrong here? I also don't quite understand the meaning of the peer addresses with ip addr.
# server 4: tun0: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN qlen 100 link/none inet 10.8.0.1 peer 10.8.0.2/32 scope global tun0 # client 8: tun0: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN qlen 100 link/none inet 10.8.0.6 peer 10.8.0.5/32 brd 10.8.0.6 scope global tun0