This seems to be fixed on the latest snapshot on the MT3000, with the option Allow Custom DNS to Override VPN DNS disabled now the MT3000 shows the VPN DNS instead of the custom DNS, using VPN based on domain name.
However, when Allow Custom DNS to Override VPN DNS is disabled, as soon as I enable AdGuard Home Handle Client Requests the router starts using the custom DNS on the VPN Client based on domain name, and when I reboot it still stops working, and I see my ISP IP and my custom DNS instead of the VPN IP, AND VPN DNS, so that one is likely not resolved
I see that in the Repeater section you have added MAC address randomization options for this network and these are the options
Factory
Clone
Random
The only thing I'm missing is the Custom option, which was useful here.
Another thing that would be useful is to go to the WIRELESS section (Wifi networks of the GL-iNet router) and be able to change the MAC of these networks (Normal and Guests).
It could look like this: after clicking "Modify", you could choose the options for the MAC address you want this network to use, and these could be:
You can choose to clone and manually enter the MAC address of your client device.
This input box + down list UI component is really not intuitive enough, we will optimize it later.
We have seen a similar need and are discussing it.
After upgrading my Beryl AX from yesterday's snapshot (0520) to today's (0521), Repeater mode fails to connect to both existing and new WiFi networks. (I'm testing this at home.)
The Logs show:
Mon May 20 20:06:53 2024 daemon.err gl-repeater[2836]: (repeater.lua:287) connect timeout
Mon May 20 20:06:53 2024 daemon.info gl-repeater[2836]: (repeater-mtk.lua:468) remove "apclix0" from wwan
Mon May 20 20:06:53 2024 daemon.notice netifd: Interface 'wwan' is disabled
Mon May 20 20:06:53 2024 kern.debug kernel: [ 751.300369] SetApCliEnableByWdev: I/F(apcli1) (enable = 0)
Mon May 20 20:06:53 2024 daemon.info gl-repeater[2836]: (repeater.lua:955) switch in 30 seconds...
Mon May 20 20:06:53 2024 daemon.info gl-repeater[2836]: (repeater.lua:364) check status exited
Mon May 20 20:06:53 2024 daemon.info gl-repeater[2836]: (repeater-mtk.lua:365) listen event exited
I'll try to downgrade. Let me know if more logs would be helpful, and how I can filter the relevant ones.
I tested the repeater mode and it connected and worked for me, did you keep settings? I didn’t, never keep settings while testing snapshots, even betas
Thank you -- I had indeed kept my settings, I'll remember that for the future. I've now successfully downgraded to the previous snapshot and the repeater is working again. I'll stay there for the moment -- I'll need the improved captive portal support on my upcoming trip.
unfortunately it is not stable as I would like, when I was testing it there were several high latency/ping spikes in online games, soon after returning to 4.5.8 the problem was resolved.