I have a multi-WAN setup, where repeater has the highest priority.
The secondary connection is trough PPPoE, in failover mode.
Well, this is the problem: The Slate AX is in fact using DNS from repeater AND PPPoE connection at the same time, mixing them.
Also, I don’t have any indication of the DNS that are used on the UI:
Browserleaks.com, dnsleaktest.com, ipleak.net are all reporting multiple dns hosts from both WWAN and WAN.
Also when Slate AX mix the DNS, streaming services like Prime Video stop working.
The Slate AX is repeating from a Beryl AX wich is running Wireguard Client (ProtonVPN).
I tried to uncheck “Use DNS servers advertised by peer” on the WAN PPPoe interface and using custom DNS but it’s stil mixing them, so I ended up setting simply 127.0.0.1 and I enabled Adguard Home as a temporary solution.
No, if I set DNS manually all is fine, but it’s problematic because I am using a Wireguard client from Beryl AX WWAN, so I should manually set 10.2.0.1 wich of course doesnt work with PPPoE conection. Using a 3rd party DNS also works but it breaks too many thing with ProtonVPN Wireguard (e.g. streaming services, security cameras playback…).
When you upgraded did you keep setting or load a config file in LuCi?
Check edit host in DNS settings?
Was Uboot Updated?
The VPN Config file could have DNS servers it using
If you installed a VPN APP on a device it might have had DNS Servers hardcoded.
In Multi-WAN is forced refresh streams enabled?
Is the Beryl AX up to date on firmware and packages(34 for upgrade usually)?
No, I did not keep settings.
All I did (after firmware upgrade without keeping settings) is giving the repeater the highest priority in Multi-WAN settings, then connect to to the repeater and to PPPoE. That’s it.
I noticed the problem since beta1.
Refresh streams in Multi-WAN is disabled and Beryl AX is running the latest firmware.
Wireguard is not the problem, even if Beryl AX is not running WG client, I still have mixed DNS between the 2 sources (WAN & WWAN).
Thanks, I already tried playing with failure conditions and priorities with no luck.
Enabling strict order makes thing worse, with that option enabled the Slate AX is only using DNS from PPPoE ignoring the repeater.
Here’s the content of the resolv.conf.auto file:
# Interface wan
# Interface wwan