You don't have to use Nord's DNS servers, not even the Smart DNS ones. I had Nord's servers originally for my WAN and it still didn't work.@iTyPsIDg
If you force all WAN traffic through the VPN w/ the Router rule set to the WAN ip, that also includes the remote connection to the VPN server, which *must* use the WAN, so it makes no sense.
If, as @L&LD suggests, you need to force NordVPN's DNS servers over the VPN, then that shouldn't be a problem provided they are scoped within the same *private* IP network as the tunnel. That's the *only* viable route to those DNS servers, despite however Routing Policy is configured.
OTOH, if the NordVPN DNS servers are using *public* IPs, and the router is bound to the WAN due to PBR, you can create policy rules that bind those IPs to the VPN. You just have to place those IPs in the destination IP of the rule, NOT the source IP.
#!/bin/sh
swapon /tmp/mnt/WRT-Merlin/myswap.swp # Skynet
/jffs/scripts/scmerlin startup "$@" & # scMerlin
. /jffs/addons/diversion/mount-entware.div # Added by Diversion
/jffs/scripts/ntpmerlin startup "$@" & # ntpMerlin
/jffs/scripts/connmon startup "$@" & # connmon
/jffs/scripts/uiDivStats startup "$@" & # uiDivStats
cru a logrotate "5 0 * * * /opt/sbin/logrotate /opt/etc/logrotate.conf >> /opt/tmp/logrotate.daily 2>&1" # added by scribe
/jffs/scripts/uiScribe startup "$@" & # uiScribe
/jffs/scripts/spdmerlin startup "$@" & # spdMerlin
/jffs/scripts/vpnmgr startup "$@" & # vpnmgr_startup
We use essential cookies to make this site work, and optional cookies to enhance your experience.