Routes vanishing
-
Hi, I currently have a pfSense setup with one pfsense box in a datacenter and one pfsense box at home. Both are connected with an openvpn tunnel. To allow access to the home subnet from the pfsense box in the datacenter, I added a static route for the subnet, pointing to the openvpn address of the pfsense box at home (The pfsense box in the datacenter serves as the main openvpn box).
Unfortunately, it seems that the route unsets itself each time the connection between the pfsense box in the datacenter and at home drop.
Is there any way to fix this?
-
Never add static routes manually for OpenVPN connections, just put it in the OpenVPN client or server (whichever side that has) as the "remote network" and let OpenVPN handle the routing.
-
@cmb:
Never add static routes manually for OpenVPN connections, just put it in the OpenVPN client or server (whichever side that has) as the "remote network" and let OpenVPN handle the routing.
I added the network (192.168.2.0/24) to the section named "IPv4 Remote Network/s" on the OpenVPN Client which is on the LAN side. No route is added on the OpenVPN Server. Is this only supported under tun? I am using tap.
-
The routes are handled by each side on its own with shared key, fill in the "remote network" on each end accordingly. With SSL/TLS, the server side can push route(s) to the client but they're still required on the server side.
-
@cmb:
The routes are handled by each side on its own with shared key, fill in the "remote network" on each end accordingly. With SSL/TLS, the server side can push route(s) to the client but they're still required on the server side.
Ah, I see.
All working now.
Thanks!