beroduar I believe this problem should be considered as a bug in the OpenVPN client under Windows. I have already asked the Forum how to solve the problem of losing access to the local LAN resources after connecting to the OpenVPN server. In response I got a bunch of "wise-people-good-advice" stuff to "read this friendly manual" and not to spam the forum. I believe there is a lot of newbies , not necessarily IT gurus, who DO want to use OpenVPN software, but are overwhelmed by the technicalities involved. I know the exact answer to my problem IS NOT directly related to the OpenVPN client, however I believe the way how the client changes Windows routing table MAY be considered as a bug - at least as unwanted behaviour. I explain the problem in details here. Let's assume my LTE router address is 192.168.1.1, my PC address is 192.168.1.2, my LAN printer address is 192.168.1.3, my remote (site1) OpenVPN server address is 10.8.0.1, my local OpenVPN client address is 10.8.0.2, my remote(site2) PostgreSQL server is an OpenVPN client with address 10.8.0.3. There is a routed client-to-client config. After launching OpenVPN client I can ping 10.8.0.1(openVPN server) and 10.8.0.3 (site2 PostgreSQL server), but I cannot print on my LAN printer and I cannot access my LTE modem/router. After disconnecting OpenVPN everything gets back to "normal". This is an unexpected and UNWANTED behaviour. The solution is quite simple - add permanent routes to the Windows routing table: route -p add 192.168.1.1/32 192.1.168.2 route -p add 192.168.1.0/24 192.1.168.1 (add a route to the modem through the PC LAN address + add a route to the LAN resources through the router) I cannot see this particular problem explaned in the HowTo and I cannot see this simple solution around the internet, even my IT guy did not know how to solve that (or was too relaxed to bother with too simplistic problems of an IT pariah, namely me). I believe this should be addressed to the OpenVpn Windows client maintainers , as the generic expected behaviour after connecting to the OpenVPN server would be not losing access to the LAN resources (e.g printers, modems, home automation/telemetry etc.)
TinCanTech beroduar wrote expected behaviour after connecting to the OpenVPN server would be not losing access to the LAN resources That is the default behaviour.
300000 there is nothing wrong with openvpn but the way config is wrong . you dont need to add permanent routes to the Windows routing table but only need one line into your client config so it can access every device at your lan when you connect to openvpn server the line to add is route 192.168.1.0 255.255.255.0 net_gateway
