How to Fix IP Conflicts with OpenVPN Full Tunnel?

Switching to a full tunnel won’t really fix your IP conflict issue. The routing won't work the same way for both networks since they share the 192.168.1.0 range. In my experience, what helps is configuring NAT with a different IP range on both sides, especially since re-IPing isn’t possible right now. You should definitely discuss this with your network team before proceeding.

How many remote users are we talking about? And what kind of traffic do they generate? If it’s just a handful of people, a full tunnel might not be the best fix for the core issue at hand. Re-IPing isn’t too complicated unless you have a very large network, which it sounds like you don’t since you’re working with 192.168.1.

One simple but not very graceful solution could be to use NAT for the addresses. In the past, we had a similar issue and routed everything through the VPN server on different ports. While it required some user training and documentation maintenance, it worked without major issues. Alternatively, setting up a second VLAN on a different subnet might also be a viable route.

Have you thought about looking into a SASE or Zero Trust platform? Using static IPs with IPSEC tunnels can really sidestep many of these issues. In my company, we utilized Timus, allowing us to adjust the protocol subnet so we don’t run into common home network conflicts like 192.168.1.0/24.

Honestly, you're better off giving the servers a different subnet entirely. You could technically add static routes after the VPN connections, but they will likely still prioritize the local network over the VPN traffic. So, a subnet change seems like a more reliable solution.