Beta Asuswrt-Merlin 3006.102.4 Beta is now available

dave14305 said:

So I see both DNAT and REDIRECT. REDIRECT for a client, and DNAT for the Global mode. Intended?

Code:

-A DNSFILTER -m mac --mac-source 4C:03:DE:AD:BE:EF -j REDIRECT
-A DNSFILTER -j DNAT --to-destination 192.168.1.1

Click to expand...

I hope to try out the beta2 tomorrow, but when I manually implemented the guest clients in beta1, I needed the router ip of the other subnets to implement the DNSFILTER_DOT icmp-port-unreachable rules in addition to the dnat rules. Any idea how those are handled now?

bennor said:

Thanks for the explanation. Did read the 3006 change log but just wasn't clicking for some reason why Pi-Hole users may want to change Global Redirection from Router to User Defined DNS 1.

Click to expand...

Same here, but it appears to work once reconfigured.

As previous beta IoT schedule still not working. IoT off by schedule, IoT devices remain connected and accessible.
Also, as previous beta, IoT devices don't show on Client List at all (they show on 2,4Ghz network) but show correctly on System Log - Wireless Log.
Router was set up multiple times after Factory restore, settings by hand, different browsers tested.







The other way around, despite Guest Network Pro indicates 0 devices, IoT devices are connected and accessible.

Hi, I upgraded to beta2, when having the DNS Director Enabled and set the Global Redirection to User defined DNS 1, which has a IP from my Adguard Home instance, it seems like DNS Redirection doesn't work. I can configure my tablet to use a static IP with Google DNS configured, and doing so, the google DNS servers are queried and not redirected to my Adguard Home instance. LAN DHCP is also configured to use Adguard Home. Tablet is on the main LAN and not on a Guest Network. Adguard home is not running on the Router itself.

Concerning this problem I had with Beta 1:

The VPN page seems to be messed up for me. Have a RT-AX86U Pro. On the VPN Director Page I can select a client and/or rule hit Apply and it shows that nothing is selected even though it may be or I can deselect something and refresh page and it will show as still selected even though it isn't . The VPN may be working but it doesn't show it is. Went back to last Release firmware and all is fine. I tried clearing Browser cache and all that. I did not try deleting all VPN and re-adding them or setting router backs to defaults and starting over, as that would have been more work that I want to do right now.

I tried Beta 2, still same problem. However, I found out that the VPN is working and on even if it's not showing correctly on the VPN Status or VPN Director Page. But if I Clear the Browser Cache then refresh the webpage it shows correctly. Problem is, on the VPN page every time I make a change and save it, I have to clear the browser cache for it to show correctly. This does not happen with any other pages in Beta 2, just the VPN page. Also, I don't have this problem with the pervious release version of the firmware. The only time I might have to clear the browser cache is after flashing the firmware.

Using Windows 11 Pro all updates and Edge browser with latest updates. Didn't see anything in log that looked wrong.

Thanks

zenmota said:

Concerning this problem I had with Beta 1:

The VPN page seems to be messed up for me. Have a RT-AX86U Pro. On the VPN Director Page I can select a client and/or rule hit Apply and it shows that nothing is selected even though it may be or I can deselect something and refresh page and it will show as still selected even though it isn't . The VPN may be working but it doesn't show it is. Went back to last Release firmware and all is fine. I tried clearing Browser cache and all that. I did not try deleting all VPN and re-adding them or setting router backs to defaults and starting over, as that would have been more work that I want to do right now.

I tried Beta 2, still same problem. However, I found out that the VPN is working and on even if it's not showing correctly on the VPN Status or VPN Director Page. But if I Clear the Browser Cache then refresh the webpage it shows correctly. Problem is, on the VPN page every time I make a change and save it, I have to clear the browser cache for it to show correctly. This does not happen with any other pages in Beta 2, just the VPN page. Also, I don't have this problem with the pervious release version of the firmware. The only time I might have to clear the browser cache is after flashing the firmware.

Using Windows 11 Pro all updates and Edge browser with latest updates. Didn't see anything in log that looked wrong.

Thanks

Click to expand...

I already answered you before.

1) The Apply button is only of use when editing the rules, it has nothing to do with enabling/disabling a client
2) If the client does not start then look at your system log for the reason why it's failing.

FLA_NL said:

Hi, I upgraded to beta2, when having the DNS Director Enabled and set the Global Redirection to User defined DNS 1, which has a IP from my Adguard Home instance, it seems like DNS Redirection doesn't work. I can configure my tablet to use a static IP with Google DNS configured, and doing so, the google DNS servers are queried and not redirected to my Adguard Home instance. LAN DHCP is also configured to use Adguard Home. Tablet is on the main LAN and not on a Guest Network. Adguard home is not running on the Router itself.

Click to expand...

Make sure your tablet isn't set to use DoH. DNS Director cannot do anything about it since DoH uses port 443. The main reason why I've always been saying that DoH is a stupid idea.

RMerlin said:

I already answered you before.

1) The Apply button is only of use when editing the rules, it has nothing to do with enabling/disabling a client
2) If the client does not start then look at your system log for the reason why it's failing.

Click to expand...

Ok, understand. Let me see if I can explain it better. I enable a client on the VPN Director Page (don't click apply) then go over to the VPN Status page it will not show the VPN as being enabled or go back to VPN Director Page it will not show as enabled. If I clear the browser cache and refresh the page, then it will show the VPN as being enabled on the VPN Status page and VPN Director Page. It's not that the VPN isn't being enabled, it just doesn't show being enabled until I clear the browser cache and refresh the page. Same thing if I disable the VPN. Would have to clear browser cache and refresh page for it to show it was disabled (even though it is). I looked at log and saw nothing wrong, because the VPN is starting just got to clear cache and refresh page for it to show that. I don't have to do this on any other pages.

Thanks, hope that explains better....

For RT-AX68U Pro,
Ingress wireless 5G band speeds, traversing over the Internet, is quite good. I've noted this starting with B1 in comparison with stock (latest and second to latest).
On stock, testing with mobile, Ingress would trail behind, by about 50-75% against Egress, or thereabouts, on the Internet. I am on symmetrical 300 MBPs. Now on here, it near matches and could exceed it, akin to wired. I did make some slight adjustments to the band settings (UI configuration), which I found in another thread here. While this helped on stock, it didn't really sort out the issue as much as I would like in a near consistent manner. Same settings as stock here (no reset just flashed over starting with B1 from latest 3006).

I can't seem to find the thread at the moment but will take note and edit this post and add it once / if found, in case if it may help others.

Good stuff!

RMerlin said:

Make sure your tablet isn't set to use DoH. DNS Director cannot do anything about it since DoH uses port 443. The main reason why I've always been saying that DoH is a stupid idea.

Click to expand...

Thanks that was it. Private DNS was set to Auto, when disabled DNS Director was working correctly. I am using a Samsung S9 Tab, I thought android uses DoT instead of DoH. I have port 853 TCP/UDP blocked in Network Services Filter and a blocklist for DNS domains in Adguard Home. But that is still not enough it seems. Probably when using 8.8.8.8 and 8.8.4.4, DNS domain and IP is being hardcoded somewhere without the use of a bootstrap DNS as how they call it in Adguard Home. I do see blocked DNS requests for "dns.google" in Adguard Home.

RMerlin said:

Make sure your tablet isn't set to use DoH. DNS Director cannot do anything about it since DoH uses port 443. The main reason why I've always been saying that DoH is a stupid idea.

Click to expand...

Slightly related, but is there a way to "tell" DNS Director not to block port 853? I delegate DoT/DoH blocking to an external DNS block list through ControlD but at the same time I'd like to use ControlD DoT on my Android phone (and DNS Director blocks it). In short, I'd like to have DNS Director active but outgoing port 853 open as well. Is this feasible, somehow, even using some iptables rule? Id6be grateful if you could suggest some workaround.

Thanks a lot in advance.

Firstly thanks Merlin for your efforts.

BE92u updated to beta2. PPTP error still happened. I haven't enabled DNS director and only IPSec VPN is enabled.

Apr 20 14:49:05 pptp[6874]: Call manager exited with error 1
Apr 20 14:49:08 rc_service: dns_dpi_check 4662:notify_rc start_dnsqd
Apr 20 14:49:15 pptp[9331]: connect: Connection refused
Apr 20 14:49:15 pptp[9331]: Could not open control connection to 192.168.2.1
Apr 20 14:49:15 pptp[6874]: Call manager exited with error 1
Apr 20 14:49:25 pptp[9414]: connect: Connection refused
Apr 20 14:49:25 pptp[9414]: Could not open control connection to 192.168.2.1
Apr 20 14:49:25 pptp[6874]: Call manager exited with error 1
Apr 20 14:49:35 pptp[9732]: connect: Connection refused
Apr 20 14:49:35 pptp[9732]: Could not open control connection to 192.168.2.1
Apr 20 14:49:35 pptp[6874]: Call manager exited with error 1
Apr 20 14:49:45 pptp[9878]: connect: Connection refused
Apr 20 14:49:45 pptp[9878]: Could not open control connection to 192.168.2.1
Apr 20 14:49:45 pptp[6874]: Call manager exited with error 1
Apr 20 14:49:55 pptp[10033]: connect: Connection refused
Apr 20 14:49:55 pptp[10033]: Could not open control connection to 192.168.2.1
Apr 20 14:49:55 pptp[6874]: Call manager exited with error 1
Apr 20 14:50:05 pptp[10112]: connect: Connection refused

Apr 20 14:47:22 kernel: 0000: 04 00 00 00 00 00 00 00
Apr 20 14:47:22 kernel: 0000: 04 00 00 00 00 00 00 00
Apr 20 14:47:22 kernel: 0000: 04 00 00 00 00 00 00 00
Apr 20 14:47:23 kernel: fifo_bitmap_by_startidx:
Apr 20 14:47:23 kernel: fifo_bitmap_by_startidx:
Apr 20 14:47:23 kernel: 0000: 04 00 00 00 00 00 00 00
Apr 20 14:47:23 kernel: fifo_bitmap_by_startidx:
Apr 20 14:47:23 kernel: 0000: 04 00 00 00 00 00 00 00
Apr 20 14:47:23 kernel: 0000: 04 00 00 00 00 00 00 00

Secondly for the CPU issues and no response to WEBUI while login need time to see if these issues are fixed. Beta1 happened many times and I need to force back to the original firmware.

Many thanks and will report later.

Has anyone else lost wifi calling with either of the betas after a full manual rebuild? I saw this this morning, but after restoring the backup from this morning it's back and running fine. If I have to do a full manual rebuild to create the error again I'm willing.

Beta 1 and beta 2 both freeze my AX88U pro as soon as I install Entware.
I have tried clean install as well. The router keeps freezing and Internet as well as router ui becomes unresponsive

Beta 2 loaded here this morning on top of Beta 1... no issues to report other than a mild grumble from my wife for a surprise outage. Heh.

irfan44 said:

Beta 1 and beta 2 both freeze my AX88U pro as soon as I install Entware.
I have tried clean install as well. The router keeps freezing and Internet as well as router ui becomes unresponsive

Click to expand...

Possible issue with USB drive?

visortgw said:

Possible issue with USB drive?

Click to expand...

Unmounting usb does nothing. Had to remove all scripts (was using only FlexQOS) and turn off JFFS, then finally a manual reboot does the trick
BTW was using using same usb drive with Alpha builds and it ran good.
Nothing related to freezing shows up in the log. CPU and RAM usage also remains normal

Ripshod said:

Has anyone else lost wifi calling with either of the betas after a full manual rebuild? I saw this this morning, but after restoring the backup from this morning it's back and running fine. If I have to do a full manual rebuild to create the error again I'm willing.

Click to expand...

Even after a full manual rebuild wifi calling is working as expected.

Dedel66 said:

Even after a full manual rebuild wifi calling is working as expected.

Click to expand...

Depends on who your service provider is. T-Mobile Wifi calling only is able to serve one device at a time and you have to manually open the ports when UPNP is off. Which for me UPNP is always off.

As for my setup, running beta 2 with no issues, although still had to turn off BSD because all the Apple devices don't like it and it spams my logs. Still also seeing better throughput with it off but you have to do it through SSH or the router will also turn off MIMO if you try to use the GUI.

Installed beta2 and everything works as expected. The only new message in the log is about removal of a VLAN that was not successful. I don't know what VLAN devices it tries to delete, but I'll ignore it for now since it doesn't seem to affect anything.