Beta Asuswrt-Merlin 3006.102.3 beta is now available for Wifi 7 devices

[RMerlin]

Thanks for checking. The issue persists after reboots so if there is any data I can gather to help solve the mystery please let me know what you need. I should have time to try a factory reset this weekend if needed. As of now I have 4 connected clients to 5GHz and only one showing. I have not seen any issues with actual connectivity so just a cosmetic anomaly. 2.4, 6-1 and 6-2 are still showing everything just fine.

View attachment 63317
View attachment 63319

How many guest networks do you have? According to the list, you seem to have at least 5 separate networks on that 5 GHz band, with three of these four clients connected to the 5th network. Are they all enabled, or are some disabled?

EDIT: the problem is indeed caused when you have multiple guest networks on a single interface - guest subunits are not always sequential. I'll need to see if I can get more info from Asus on how to better determine which interfaces to query.

 

[RMerlin]

How many guest networks do you have? According to the list, you seem to have at least 5 separate networks on that 5 GHz band, with three of these four clients connected to the 5th network. Are they all enabled, or are some disabled?

EDIT: the problem is indeed caused when you have multiple guest networks on a single interface - guest subunits are not always sequential. I'll need to see if I can get more info from Asus on how to better determine which interfaces to query.

Fixed with commit.

 

[emwgee]

After updated to beta_1 on my GT-BE98 PRO from 3006_102.2_2, wireless log shows only two of my three 2.4GHz guest networks, even though the unshown network is there and working fine with clients connected to it.

I tried refreshing wireless log, cleared browser cache, disabled and re-enable the unshown network and reboot the router. None of that helps.

Another thing that I've noticed is that with the beta_1 firmware the 6GHz signal seemed not to be as far reaching as the 3006_102.2_2 release. Where inside my home I used to have one bar of signal on 6GHz network 1 on 3006_102.2_2 firmware now has none.

 

[junior120872]

Another thing that I've noticed is that with the beta_1 firmware the 6GHz signal seemed not to be as far reaching as the 3006_102.2_2 release. Where inside my home I used to have one bar of signal on 6GHz network 1 on 3006_102.2_2 firmware now has none.

I'm also noticing reduced reach on the 6ghz signal from locations in the house that were able to get it on the be96u.

 

[Geraner]

I have an interesting DNS problem with the RT-BE86U.

Running NextDNS via CLI installation on Merlin's latest beta firmware. Using NextDNS with my own config.
All networks, Main Network LAN + Wifi, and the IoT Wifiis using NextDNS as DNS server, which is the default on my router. I didn't configure the WAN GUI DNS to anything, as this is handled by NextDNS CLI in the router.
But, the Guest_Wifi network connected clients are not using the default NextDNS configuration. Those are using the DNS server from my ISP.
Was previously running the RT-AX86U, with the same config (but no IoT Wifi), and the main LAN + Wifi incl GuestWifi devices all used the NextDNS CLI configuration.

The only solution for me, to get the GuestWifi devices to use my NextDNS config as well on the RT-BE86U, was to enable the DNS Privacy Protocol on the WAN GUI config, to DNS-over-TLS (DOT), Profile = Strict, and configuring the DNS-over-TLS Server List, with the NextDNS configurations (DNS IP + TLS Hostname) for my own NextDNS config. After that I have done this, also the Guest Wifi connected devices are using the NextDNS configuration.
The only difference now, compared to my previous RT-AX86U is, that the GuestWifi devices are not sending the local client name to NextDNS. Their requests are just shown as DNS requests from my public IP address.

This is maybe not any fault in the Merlin firmware, but more a general setup change done in the RT-BE86U compared to the RT-AX86U.
Anyway, I wanted to address this here, to get some comments from you or from RMerlin on this.

Thanks in advance!

 

[nomadneo]

Makes no difference. If the file fails to transfers properly, then it won't flash at all - the image is validated before being written to flash.

My point was: I once tried to install a merlin firmware over a native asus firmware and it failed with an error. Was doing it over wifi. So, thought that I should do it a cable.

 

[silen7fury]

I can confirm that the new 102.3_beta1 using the 37xxx GPL codebase fixes the WAN speed issue for those with >2Gbit connections on the upstream, on an RT-BE88u using the 10G copper port, using a bridged ONT CPE.

I sometimes am bitten by the "Your ISP's DHCP does not Function Properly" but it seems to resolve itself after a reboot, or two. Anything I can provide to help fix this, happy to do so.

to RMerlin and his team as always.

 

[MDM]

I'm also noticing reduced reach on the 6ghz signal from locations in the house that were able to get it on the be96u.

Also @emwgee
And you are certain it is on the same manually selected channel?!
If not, not comparable, and nothing to do with FW version...

 

[BlueFrog]

I keep getting this error in my general log, including the ^M at the end.

Jan 9 18:32:33 kernel: Failed delete entry 0000:0000:0000:0000:0000:0000:0000:0000 ^M
Jan 9 18:32:33 kernel: Failed delete entry 0000:0000:0000:0000:0000:0000:0000:0000 ^M
Jan 9 18:33:16 kernel: Failed delete entry fe80:0000:0000:0000:a426:11ff:fed2:1810 ^M
Jan 9 18:33:16 kernel: Failed delete entry fe80:0000:0000:0000:a426:11ff:fed2:1810 ^M
Jan 9 18:42:20 kernel: Failed delete entry fe80:0000:0000:0000:3050:cc52:2f52:08ea ^M
Jan 9 18:42:20 kernel: Failed delete entry fe80:0000:0000:0000:3050:cc52:2f52:08ea ^M
Jan 9 18:42:23 kernel: Failed delete entry fe80:0000:0000:0000:3050:cc52:2f52:08ea ^M
Jan 9 18:42:23 kernel: Failed delete entry fe80:0000:0000:0000:3050:cc52:2f52:08ea ^M
Jan 9 18:42:35 kernel: Failed delete entry fe80:0000:0000:0000:3050:cc52:2f52:08ea ^M
Jan 9 18:42:35 kernel: Failed delete entry fe80:0000:0000:0000:3050:cc52:2f52:08ea ^M
Jan 9 18:42:35 kernel: Failed delete entry 0000:0000:0000:0000:0000:0000:0000:0000 ^M
Jan 9 18:42:35 kernel: Failed delete entry 0000:0000:0000:0000:0000:0000:0000:0000 ^M

 

[emwgee]

Also @emwgee
And you are certain it is on the same manually selected channel?!
If not, not comparable, and nothing to do with FW version...

Both Control and Extended channel setting for all bands are on "Auto" setting, as they were prior updating to 3006.102.3 beta_1.
Actually ever since the router was set up initially on GT-BE98_PRO_3006_102.2_0 firmware, nothing had been changed.

 

[MDM]

Both Control and Extended channel setting for all bands are on "Auto" setting, as they were prior updating to 3006.102.3 beta_1.
Actually ever since the router was set up initially on GT-BE98_PRO_3006_102.2_0 firmware, nothing had been changed.

And that is the issue!

Signal strength (and noise on given channel) change is just from the channel change after reboot from FW update.
And thus like I said not comparable. Only on same channel and settings before and after update can you compare.
And it is always better to select and set channel manually. You can easily educate yourself about it on this forum, just use search...

 

[emwgee]

And that is the issue!

Signal strength (and noise on given channel) change is just from the channel change after reboot from FW update.
And thus like I said not comparable. Only on same channel and settings before and after update can you compare.
And it is always better to select and set channel manually. You can easily educate yourself about it on this forum, just use search...

1. There wasn't any other 6GHz band routers in my neigbourhood. I scanned using Site Survey and also WifiAnalyzer on my Android phone.
2. The router was flashed with Asuswrt Merlin GT-BE98_PRO_3006_102.2_0 firmware when I first got it in Nov, 2024, and then GT-BE98_PRO_3006_102.2_2, and now GT-BE98_PRO_3006_102.3_beta1.
3. My router was scheduled to an automatic reboot every Sunday early in the morning.
4. The 6GHz channels selected automatically each time after router reboot remained the same so far, channel 37 for 6GHz-1 and 133 for 6GHz-2, as it is now.

I am simply reporting my own observations, not a complaint

 

[MDM]

I am not saying you are complaining.

Just that if at the observation times, you are not 100% sure the channels vere indeed the same, you can not compare. (they tend to stay the same after reboot but can easily change after a FW reboot)
Lower and upper channels do not transmit with same strength, and you even being solo on a mountain does not affect that fact...

Now, if you manually fix the channels and mesure, then go back to previous FW and measure again, then you have a meaningful comparaison to report. Auto does not count.