"Initials" by "Florian Körner", licensed under "CC0 1.0". / Remix of the original. - Created with dicebear.comInitialsFlorian Körnerhttps://github.com/dicebear/dicebearMA
Self-Hosted Main 54lzy 11mo ago 80%

Accessing home network remotely over WireGuard when the other network is on same subnet

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 think via a static route?). I also use my home networks dns server (AdGuard home on 192.168.1.121) which then has a wildcard redirect for my domain to my Unraid 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).

I imagine my methodology is not best practice. 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.

3
3
Comments 3