I need a site-to-site OpenVPN connection between two LANs in different locations. I have managed to get the OpenVPN connection running but there seems to be a problem with client-side routing.
The OpenVPN server is on Asuswrt-Merlin (Asus RT-AC68U). That machine is the gateway, 192.168.0.1, on the server-side LAN (192.168.0.0 / 255.255.255.0). On OpenVPN it is 192.168.5.1.
The OpenVPN client is on FreshTomato. It is running on a Linksys WRT54GL (192.168.34.202), which is *not* the gateway, on the client-side LAN (192.168.34.0 / 255.255.255.0). The client’s user name is "vpn4" and IP address on the OpenVPN is 192.168.5.2.
The gateway of the client-side LAN is a Huawei modem router with very little configurable options (192.168.34.1), and there are some more devices on the client-side LAN that I need to access from the server-side LAN.
At the moment I can ping the Linksys device (192.168.34.202) and access FreshTomato on that device over OpenVPN from the server-side LAN.
THE PROBLEM: I cannot ping or access any other devices on client-side LAN over OpenVPN from the server-side LAN. I suppose that the problem is somewhere in the client-side LAN and related to client-side routing.
VPN Client:
and
Current routes on VPN Client machine:
I have not manually added any static routes to either the VPN server or the VPN client. (I tried though but none of my ideas solved the problem.)
VPN Server configuration:
TUN
UDP
VPN subnet 192.168.5.0 / 255.255.255.0
Push LAN to clients: Yes
Direct clients to redirect Internet traffic: No
Manage Client-Specific Options: Yes
Allow Client<-> Client: Yes
Allow only specified clients: No
Custom:
client-config-dir /jffs/configs/openvpn/ccd2
script-security 3
reneg-sec 0
route 192.168.34.0 255.255.255.0
push "route 192.168.34.0 255.255.255.0"
In the folder ccd2 I have a file named "vpn4" containing this:
iroute 192.168.34.0 255.255.255.0
I noticed that when I remove the route, push "route" and iroute directives from the OpenVPN server, then machines in the server-side LAN can ping (but not access) 192.168.34.1. When I add those directives to the OpenVPN server, 192.168.34.1 becomes unpingable and 192.168.34.202 (the OpenVPN client machine) becomes pingable and accessible.
Tracert from a machine on server-side LAN shows (Doomsville.KCN is the VPN server machine, which is also the gateway on the server side):
None of the numerous options I could think of during a number of hours gave me access to the client-side LAN. Any ideas how to make other devices (like 192.168.34.1 or 192.168.34.102) on the client-side LAN accessible from the server-side LAN?
The OpenVPN server is on Asuswrt-Merlin (Asus RT-AC68U). That machine is the gateway, 192.168.0.1, on the server-side LAN (192.168.0.0 / 255.255.255.0). On OpenVPN it is 192.168.5.1.
The OpenVPN client is on FreshTomato. It is running on a Linksys WRT54GL (192.168.34.202), which is *not* the gateway, on the client-side LAN (192.168.34.0 / 255.255.255.0). The client’s user name is "vpn4" and IP address on the OpenVPN is 192.168.5.2.
The gateway of the client-side LAN is a Huawei modem router with very little configurable options (192.168.34.1), and there are some more devices on the client-side LAN that I need to access from the server-side LAN.
At the moment I can ping the Linksys device (192.168.34.202) and access FreshTomato on that device over OpenVPN from the server-side LAN.
THE PROBLEM: I cannot ping or access any other devices on client-side LAN over OpenVPN from the server-side LAN. I suppose that the problem is somewhere in the client-side LAN and related to client-side routing.
VPN Client:
and
Current routes on VPN Client machine:
I have not manually added any static routes to either the VPN server or the VPN client. (I tried though but none of my ideas solved the problem.)
VPN Server configuration:
TUN
UDP
VPN subnet 192.168.5.0 / 255.255.255.0
Push LAN to clients: Yes
Direct clients to redirect Internet traffic: No
Manage Client-Specific Options: Yes
Allow Client<-> Client: Yes
Allow only specified clients: No
Custom:
client-config-dir /jffs/configs/openvpn/ccd2
script-security 3
reneg-sec 0
route 192.168.34.0 255.255.255.0
push "route 192.168.34.0 255.255.255.0"
In the folder ccd2 I have a file named "vpn4" containing this:
iroute 192.168.34.0 255.255.255.0
I noticed that when I remove the route, push "route" and iroute directives from the OpenVPN server, then machines in the server-side LAN can ping (but not access) 192.168.34.1. When I add those directives to the OpenVPN server, 192.168.34.1 becomes unpingable and 192.168.34.202 (the OpenVPN client machine) becomes pingable and accessible.
Tracert from a machine on server-side LAN shows (Doomsville.KCN is the VPN server machine, which is also the gateway on the server side):
None of the numerous options I could think of during a number of hours gave me access to the client-side LAN. Any ideas how to make other devices (like 192.168.34.1 or 192.168.34.102) on the client-side LAN accessible from the server-side LAN?
Last edited: