Wouldn’t this tunnel everything? I just want 10.10.10.0/24 and 10.0.0.0/24 (VPN and LAN IP range to get tunneled). I also don’t know how this would mitigate this issue
Comment on WireGuard VPN IP Issue
stown@sedd.it 1 year ago
Change your allowed IPs config to 0.0.0.0/0
Smash@lemmy.self-hosted.site 1 year ago
Smash@lemmy.self-hosted.site 1 year ago
Thanks for the pointer, it seems it’s an DNS issue after all (IT’S ALWAYS DNS). Routing all traffic through the tunnel forces the Clients to use the DNS server of the LAN. Without, my internal websites (which use a public domain namespace) are sometimes resolved with a public DNS. So the browser doesn’t request test.home.network (10.0.0.100) but test.home.network (1.19.72.59).
stown@sedd.it 1 year ago
Glad you figured it out. I’ve also run into issues with Firefox using the wrong DNS.