Have switched from a bridged to routed VPN. Using Shibby's VPN 1.28 097 build (good job fixing the 32k NVRAM limit on the N66U BTW!)
Having some trouble routing to machines on the client side of the VPN tunnel from the server side. Of course being bridged in the past this was not an issue.
Routing is not my strong suit, so am sure this is PEBCAK; but everywhere I search it just keeps telling me how to let the client side see the server. That's working fine right out of the box. Am trying to do the reverse.
I do see the VPN server pushing it's LAN subnet to the client router upon connection. Have tried manually adding a static route for the client's subnet on the server side (via SSH, not the GUI), but that didn't seem to do any good. Didn't really see anything in iptables on either side so wasn't thinking it was a firewall issue.
Let's go with these subnets (not the production ones, just for example):
Server LAN: 10.0.0.0/24
Client LAN: 10.0.1.0/24
Server's PTP IP: 10.200.0.1, with .2 as the other side
Client's PTP IP: 10.200.0.4, with .3 as the other side
Any machine on the server side LAN (10.0.0.x) can ping and ssh to 10.200.0.4, though I can't get the admin GUI to come up. Not sure why.
The manual route addition made on the server/router:
route add -net 10.0.1.0 netmask 255.255.255.0 gw 10.200.0.2
This seems to be the reverse of what is being pushed to the client, adjusting addresses as necessary.
I figured once the static route was in place on the server, packets would flow from the 10.0.0 subnet across the vpn and find the 10.0.1 subnet. But no such luck. Since a route from the client is already in place back to the server's LAN, didn't think I'd have to touch anything on the client side.
Fingers getting blurry from searching.
Any ideas how to get machines on the server side's LAN to access machines on the client's LAN?
Am sure there's something simple I'm just not getting, but an actual example would be great, not a link to routing 101. Once the cobwebs clear…