[Riscol]

Hi everyone,

I have moved from my previous appartment to a new one - and of course now have a new networking setup with issues:

Setup:

* Nighthawk R7000P as DD-WRT router behind ISP modem
* R7000P setup as local DNS server (in parallel to ISP modem as DNS Server - both with the same static routes defined) //disabling DNS server in my DD-WRT always breaks the network (?)
* DD-WRT setup as VPN Server and VPN Client
* VPN Client (NordVPN) defined for few devices with policy based routing (ip based)

Issues:

(a) I had many DNS leak problems, primanrily resulting in Netflix blocking my streaming.
(b) I have/had regular connection drops in meetings while PBR still worked (see below), i.e. video call dropped for 5-10 seconds every couple of minutes (and then it was okay again for some time)

Based on Issues (a) + (b) I initiated some trouble shooting and tried to fix it (see these guides in top post by egc): https://forum.dd-wrt.com/phpBB2/viewtopic.php?t=321686

(c) With the applied fixes my PBR routed devices now use the VPN's DNS (VPN client is connected), but the devices still go via regular WAN suddenly. I have no idea why and how to fix this
(d) Also, my VPN server is not reachable anymore (I portforwarded in the ISP modem of course)
(e) Also, looking at the syslog I now regularly see warnings of possible rebind attacks (previously rather seldom) and ERROR that the time server is not reachable (network down)

Could you please help me?

I'd like to share logs/settings but Admin > Commands > Run (see commands below) do not return any output.

"ip route show
ip route show table 10
ip rule show"

Happy to supply logs if you tell me how (via GUI?).

Key issue for me is currently (c)

Thank you!


Firmware: DD-WRT v3.0-r47117 std (08/01/21)
Time: 14:38:47 up 29 min, load average: 0.02, 0.03, 0.00
WAN: Disabled

[eibgrad]

TIP: Avoid using the Administration->Commands input field to run arbitrary commands. I have no idea how that's implemented, but it's notorious for being VERY finicky about syntax and formatting. Instead, use telnet or ssh. You'll have a lot less problems.

In the case of (c), since I don't know specifically what you did, it's hard to critique it and explain the behavior. The fact you say the PBR devices now use the VPN'd DNS, but are routed over the WAN, is particularly confusing. How did you verify this? It's not always that easy to know for sure. Not unless you use a traceroute, or perhaps dump connection tracking on the router (cat /proc/net/nf_conntrack).

[Riscol]

Thanks eibgrad - good point regarding commands.

So I did some testing.

I realized the VPN Client was not connected successfully at all (?!).

To fix issues (a) and (b) as described above I (among others) added the following two codes to the VPN client additional config field (as described in trouble shooting guides linked in original post).

Code 1

[eibgrad]

[Riscol]

Ah - this is really embarrassing. I must have mixed up the syntax myself.

I'll adapt and get back to you with feedback.

In any case: many thanks eibgrad!