Beta Asuswrt-Merlin 3006.102.5 Beta is now available

[oldgringo]

It looks like some issue here.

I see in mozilla docs also this:
Elements that can be associated with a label element include button, input (except for type="hidden"), meter, output, progress, select and textarea. So no radio type is allowed.

In brave browser I cannot change it at all, only CTRL+F5 helps.

 

[Poul Bak]

I see in mozilla docs also this:
Elements that can be associated with a label element include button, input (except for type="hidden"), meter, output, progress, select and textarea. So no radio type is allowed.

In brave browser I cannot change it at all, only CTRL+F5 helps.

Radio buttons are: <input type="radio" /> so they ARE allowed!

 

[RMerlin]

In brave browser I cannot change it at all, only CTRL+F5 helps.

Just tested it in Brave, and it works fine for me.

 

[RMerlin]

Radio buttons are: <input type="radio" /> so they ARE allowed!

And in fact the W3Schools website example for the LABEL tag actually uses... radio buttons.

There is one error in that code tho - the duplicate "for" value. I just replaced that whole block with the more up-to-date block from upstream, which also uses localized labels in addition to fixing that duplicate value. I replaced the duplicate value (the rest of the upstream code does not apply because they handle that value differently from me).

 

[atkinsom]

Just tested it in Brave, and it works fine for me.

I'm assuming the original poster has tried this on different computers? Perhaps a plain setup PC/Mac without any 3rd party add-ons/software or AV/firewall software other than the built-in Windows/Mac av stuff. This would help establish a baseline to work backwards if the issue still exists in that environment. Hard to fix if you can't replicate I would imagine.

 

[welim]

Dear Sir/Mdm,

My AIMESH main router is AX88U. I went to Wireless-> General and would like to change the 5GHz control channel from current 149 to 100. When I make changes and hit "Apply", it is not working. The "Apply button seems not functioning. Is this a known issue for Beta ?

Best Regards,
Wee-How

 

[dave14305]

The "Apply button seems not functioning. Is this a known issue for Beta ?

Review post #2 in this thread.

 

[welim]

Review post #2 in this thread.

Thank you. So its known issue and plan to fix it in the beta2. Much appreciated Dave

 

[RMerlin]

I'm assuming the original poster has tried this on different computers? Perhaps a plain setup PC/Mac without any 3rd party add-ons/software or AV/firewall software other than the built-in Windows/Mac av stuff. This would help establish a baseline to work backwards if the issue still exists in that environment. Hard to fix if you can't replicate I would imagine.

I always ask people to try a different browser whenever reporting these types of issues, but people don't always listen to me. <shrug>

 

[GWTechTalk]

Not sure what ASUS did in this release, but I ended up having to wipe the whole router and start fresh. It was causing an issue with older devices that use WPA2 to only be connected for like 15 min then they would all freeze up. They would show connected still but with no RX network stats. Externally those devices would then show offline on their respective apps. After a full wipe and rebuild everything is back to normal. Just a warning for those like me on the BE96U or possibly the BE98 that this update might need a clean install.

 

[oldgringo]

I'm assuming the original poster has tried this on different computers? Perhaps a plain setup PC/Mac without any 3rd party add-ons/software or AV/firewall software other than the built-in Windows/Mac av stuff. This would help establish a baseline to work backwards if the issue still exists in that environment. Hard to fix if you can't replicate I would imagine.

I have created new VM with nothing but 3 different browsers installed (mozilla, chrome and brave) just for testing. I know something about SW development, especially GUIs. Anyway, downgrade fw to the previous final version solved the issue on all browsers. That's my basic check.

 

[GaselK]

Same behavior for IoT scheduling remains in beta
as here https://www.snbforums.com/threads/3006-102-5-alpha-build-s-available-build-s.95014/post-959663

 

[nzwayne]

Beta1 installed ok on 5Jul'25. The two AiMesh units operational on existing code levels of GT-BE98Pro - 3006_10237839 & RT-BE96U - 3006_102.4_0. My early appends on 3006_102.5 noted that RT-BE96U 2.4 & 5GHz radios & panel LEDs would not enable on code levels of 3006_102.5 (Alpha or Beta), Stock - 300610237839, but was all ok on earlier level of 3006_102.4_0.
Yesterday after the ASUS release of level 300610237849 on Thr/Fri to fix a 5GHz Broadcom issue on various units, installed this ASUS code on the RT-BE96U AiMesh unit. All radios enabled, leds on, clients connecting to 2.4GHz & 5.0GHz bands. yippee!!! On that success, converted the other AiMesh unit GT-BE98 Pro to this newly released level too.
All going will with our 50 odd home clients, smartconnect enabled (as always), add-on's all behaving, family (the true testers...) flogging the network.

 

[RMerlin]

July 20th: Beta 2 is now available. Changes since beta 1:

d8fdc1840d Updated documentation
a037fbdfab webui: removed unused Email code from OVPN server page; minor cleanups
696eb4b955 webui: fix duplicate label value on OVPN server page
8e55cf4acd webui: Rework the QIS Wizard page shown if a new firmware is available
79e7d0ef48 httpd: check that we have a potential IP before calling ParseIPv4OrIPv6()
1df7906db3 Harmonize target profiles with Asus
d17547441d webui: don't link to the whole networkMap.css on Sysinfo, just include the classes we need
155ad587bf webui: workaround for Wireless settings page not scrolling to the top when applying
c45f6e8d0a webui: fix invalid dwb_mode on some models (patch from Asus)
fec8643b8c Updated documentation
94497b5595 webui: Do not enumerate SDNs that use the default LAN for DNSDirector; table layout fix
bb0b9e6867 rc: filter out any SDN that uses network 0 (LAN) instead of just back/fronthaul networks when setting up DNSDirector iptables
292ecacadc webui: properly fix Makefile recipes; remove unused dns_db.json
22b2406ba4 rc: skip fronthaul/backhaul SDNs when creating DNSDirector iptables rules
0b8cbcc23c rom: update CA bundle
aab06d3dd2 rom: update mk-ca-bundle script from Curl
b1da4aec20 networkmap: webui: update databases
709b5a783e webui: fix install recipe following last GPL merge
bcc40abf75 httpd: optimize performance for conn.active sysinfo queries
a971907427 Bump to beta 2

 

[NiklasO]

Is this my server (Unraid/Docker/VM) doing something strange or has something changed between .4 stable and this beta affecting this?
Both numbers keep "counting" up every 1-2 sec but drops down to sane numbers after it counts up to 200-250 "clients".
Sane is like Clients: 30-40 and the "x clients are connecting to..." goes away but it starts counting up again and repeats.
Docker is using macvlan so the containers shows up as individual clients/devices and that's fine but I don't understand the ~200 ghost clients that mysterious goes away and comes back.

View attachment 66524

View attachment 66525

Edit: Ok. So dirty downgrade to 3006.102.4 stopped this behavior.

This is still happening in beta2.

52 devices connected via my server (0 with .4). And rising.
100+ "clients" in total... and rising (stable at 20-30 with .4).

I don't see these "clients" anywhere. Just the numbers increasing until they drop and start counting up again.
Maybe just visual but it does not feel right.

Edit 164-128=36 is probably near the right number of real clients. Dropped to 0 connected through and now counting up again, and repeats indefinitely.

 

[Ripshod]

Beta 2 is now available.

Killed my wifi
nvm, reset brought it back.

 

[MDM]

No problem detected at first glance, all seems OK and working as supposed.

 

[XIII]

Trying to upgrade my GT-AX6000 from 3006.102.5_beta1 to 3006.102.5_beta2.

For more than 15 minutes it displays "Please wait, Applying Settings..." and when I ssh into the router it still reports 3006.102.5_beta1.

How long should I wait before taking any actions? (Which?)

 

[MarkusI]

@RMerlin just updated to beta2 and I still can ping all my internal IPs except the router itself when connected via OpenVPN and server is set to 'internet only'...

 

[Samuel_1975]

Trying to upgrade my GT-AX6000 from 3006.102.5_beta1 to 3006.102.5_beta2.

For more than 15 minutes it displays "Please wait, Applying Settings..." and when I ssh into the router it still reports 3006.102.5_beta1.

How long should I wait before taking any actions? (Which?)

You can probably turn off the router and turn it on again after a few seconds if that helps as I myself had to turn off the router and turn it on again