I’ve recently found the ability to configure Wireguard with the function to only be utilized by my cellphone when away from home Wi-Fi, and only when accessing local network private IP addresses in the 192.168.1.xxx range.
This is awesome, because i don’t need to worry about constantly turning on and off the VPN, or exposing services to the public, so i can access them while away from home. More importantly, i can set my wife’s phone up so it is seamless when accessing something on the home network without exposing it to the public internet.
This is all great, however, when on Wi-Fi somewhere other then at home, if that network shares the same subnet, nothing will work, because it will be searching the local Wi-Fi network, instead of routing through the VPN.
I’ve been reading up on this, and one solution is to change my home network from the 192.168.1.x subnet, to a non conflicting subnet, however residential networks commonly use the 192.168.x.x range, and commercial networks commonly use the 10.x.x.x range. So it seems, it could be difficult to find a subnet that wouldn’t have a conflict.
I also saw people using 1:1 NAT to somehow change the IP across the VPN which somehow aids in avoiding conflict.
What would be the easiest way to avoid private IP conflicts while connected to outside the home Wi-Fi?
Current setup is PFSense for routing, One wireguard tunnel, and three peers (my cell, wife’s cell, and my laptop). Behind PFsense, i have a server that i host various entertainment applications, none of which are exposed to the public internet, other then through wireguard VPN.