Quote History Quoted:
What's happening is a routing problem on the work desktop. It knows what the local home network because it's a local network. The work VPN is routing all other subnets down it's VPN tunnel. Since your openvpn is a different subnet handled by the default gateway the work computer is routing upir openvpn packets to your work VPN as it takes the default gateway position.
You need to add a static route on the work computer to say 192.168.2.0/24 goes to 192.168.1.1 and hope the work VPN doesn't override it.
Alternatively, and maybe a better idea if you can do it, is to tell your router to NAT your openvpn traffic into your internal network. Then the connection to the desktop would look lik its coming from the router (192.168.1.1) and no routing changes to the desktop are required.
View Quote
@Foxxz
NAT is accomplished using the "static route" configuration in my router, correct?
I'm home now and can experiment with this without affecting my work. I've changed my internal IP addresses in my router so I'm not likely to have conflicting IPs with any remote network I may be on.
My new home LAN IPs are 192.168.87.*, and my gateway is 192.168.87.1.
My VPN, when I connect from another network, now assigns my laptop an IP address of 192.168.88.*.
Since my router is acting as my OpenVPN "server," I really can't configure the VPN server in any meaningful way.
I am able to add static routes on my router, the screen is asking for Destination IP Address, IP Subnet Mask, Gateway IP Address, and Metric.
Is this likely to help? If so, what values would I be entering there?