The last step, and one that is often forgotten

The last step, and one that is often forgotten, is to add a route to the server’s LAN gateway which directs to the OpenVPN server box (you won’t need this if the OpenVPN server box is the gateway for the server LAN). Suppose you were missing this step and you tried to ping a machine (not the OpenVPN server itself) on the server LAN from The outgoing ping would probably reach the machine, but then it wouldn’t know how to route the ping reply, because it would have no idea how to reach The rule of thumb to use is that when routing entire LANs through the VPN (when the VPN server is not the same machine as the LAN gateway), make sure that the gateway for the LAN routes all VPN subnets to the VPN server machine.

Similarly, if the client machine running OpenVPN is not also the gateway for the client LAN, then the gateway for the client LAN must have a route which directs all subnets which should be reachable through the VPN to the OpenVPN client machine.

OpenVPN HowTo

In meinem Fall hat die Route in der Fritzbox gefehlt, die Pakete an das 10er VPN über den Raspberry routet, der ja im 192er und dem 10er-Netz sitzt. Nun erreiche ich auch die lokalen Rechner über den VPN-Server.

Eine Antwort auf &‌#8222;The last step, and one that is often forgotten&‌#8220;

Kommentare sind geschlossen.