Accessing home network remotely over WireGuard when the other network is on same subnet reddit / selfhosted ---------------------------------------------------------------------- 54lzy · 2023-12-03 22:22 My home network uses the incredibly common 192.168.1.0/24. I have WireGuard setup where I can connect to WireGuard and access my home network. I also use my home networks dns server which then has a wildcard redirect to my server. When I connect to WireGuard remotely on someone else’s WiFi that uses the same 192.168.1.0/24 subnet, I can’t access dns or my local network (I assume because of ip conflicts). Can someone recommend how I should go about fixing this? Should I change my home subnet to something less common? Should I setup a dns server that lives on my WireGuard network (10.253.0.0/24) that wildcard redirects my domain to the servers WireGuard ip? Something else? Thank you for taking the time to read this. ---------------------------------------------------------------------- Swedophone · 2023-12-03 22:57 >Should I change my home subnet to something less common? Yes, that's a good idea. ---------------------------------------------------------------------- positivesnow11 · 2023-12-03 23:06 Make two routes that split your /24 into two /25s. The client device will look at the longest prefix match and prefer the tunnel rather than directly connected next hop. ---------------------------------------------------------------------- Majiir · 2023-12-04 04:22 You can create an IPv6 ULA prefix (assuming your ISP doesn't assign you a static global prefix) and address your hosts with it. This practically guarantees you won't have any IP address conflicts with other networks, assuming you create the ULA correctly. Wireguard can carry IPv6 traffic over an IPv4 tunnel if you only have IPv4 connectivity. ---------------------------------------------------------------------- dually · 2023-12-04 04:41 Wireguard client for Android allows you to specify a dns server. Just run dnsmasq at the gateway address peer of the vpn network. That is what I do. As I bonus this also gives me dns-based adblocking everywhere. ---------------------------------------------------------------------- DaFyre2010 · 2023-12-04 15:56 Change it up... Pretty much anything in the [192.168.X.0/24](https://192.168.125.0/24) should work for your home network. Make it an oddball number like... 43... or 237... Just don't forget to update your router's ip & dhcp first. :-D ---------------------------------------------------------------------- AllTheModzAreCancer · 2023-12-05 06:07 https://i.imgur.com/JCSxrZU.jpeg