I've been fighting this for a few days and it's driving me nuts
I've got a client configured to be the router for a remote subnet, the main network is based around 192.168.x.x ... the openvpn server is configured to be 10.200.x.x and the remote network is 10.75.x.x
I can access any of the 192.168.x.x machines from the openvpn client, ssh and ping work fine ... but any of the workstations on the far side of openvpn client can't get there
Monitoring both ends of the tunnel with "tcpdump -i tun0 dst port 22" which shows when I am ssh'ing from the client it's coming from 10.200.0.2 going to 192.168.1.20, I see packets on both side of the tunnel
When I try and ssh to 192.168.1.20 from 10.75.0.2 I see the packet coming in on tun0 on 10.200.0.2 but I don't see the packet coming out on 10.200.0.1
Client routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.1.0 10.200.0.1 255.255.255.0 UG 0 0 0 tun0
10.200.0.0 0.0.0.0 255.255.255.0 U 0 0 0 tun0
10.75.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1
0.0.0.0 x.x.x.x 0.0.0.0 UG 100 0 0 eth0
Server routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
10.200.0.0 0.0.0.0 255.255.255.0 U 0 0 0 tun0
10.75.0.0 10.200.0.2 255.255.255.0 UG 0 0 0 tun0
0.0.0.0 x.x.x.x 0.0.0.0 UG 100 0 0 eth0
I've never heard of the tunnel dropping packets ... anyone have an idea I can pursue?
