Wireguard client to server and cascading to Nordvpn

I have a Flint 3 setup as my wireguard server and Slate AX as my travel router.

Currently when I connect to the Flint 3 remotely is still exposes my home external ip rather than the dedicated Nordvpn IP.

I am usinfg the glinet ddns as my endpoint.

My question, is there a way to have the travel router not expose the home ip while using wireguard?

Note everything works fine currently. I just want a way to prevent the DNS leaking from the travel end

Wireguard config

[Interface]
Address = 10.1.0.2/24
PrivateKey = hidden
DNS = 10.1.0.1
MTU = 1420
Jc = 11
Jmin = 75
Jmax = 1153
S1 = 99
S2 = 74
S3 = 17
S4 = 31
H1 = 762300480-762300897
H2 = 1480476958-1480477367
H3 = 957391932-957392003
H4 = 483031282-760645253


[Peer]
AllowedIPs = 0.0.0.0/0
Endpoint = xxxxx.glddns.com:51820
PersistentKeepalive = 25
PublicKey = hidden

Hello,

I assume you have the WG server enabled on your Flint 3, and you have also enabled the VPN client and connected it to NordVPN with a dedicated IP.

In this case, go to Flint3's NordVPN tunnel -> 'From-Specified Connection Types', and check 'WireGuard Server'.
Once applied, your Slate AX traffic will be routed: Slate AX WG client -> Flint 3 WG server -> Flint 3 NordVPN.

With the default settings, there won't be any DNS leaks. You can verify this using various DNS leak test websites.

Thank you Bruce, thats exactly what I wanted to achieve.

Edit

I can get this to work at both ends now by tagging the Wireguard and local network tabs however when I implement a client exclusion it turns of the function.

Added the NoVPN solution to exclude specific devices

1 Like