Beta Asuswrt-Merlin 3006.102.6 Beta is now available

[dave14305]

BTW the image you posted isn't relevant

Actually it is exactly relevant to the original question. There is a Wireless and Status tab on the older routers in the System Status pane. Now it’s apparently just the Status pane with no tabs.

 

[Ripshod]

Actually it is exactly relevant to the original question. There is a Wireless and Status tab on the older routers in the System Status pane. Now it’s apparently just the Status pane with no tabs.

We seem to be seeing something different here.
@SANdood posted a question about missing tabs in the Client Status sidebar (a sub section of network map), whereas @scootertramp replied referencing the main network map page and posted an image of the same.
This is what was asked about

 

[dave14305]

posted a question about missing tabs in the Client Status sidebar

Here was his question:

On the RT-BE92U Network Map page, I notice that the tabs are missing under the System Status segment on the right - it only shows what is on the "Status" page.

No mention of Client Status, only System Status. And we’ve learned that it changed recently.

 

[Ripshod]

Here was his question:

No mention of Client Status, only System Status. And we’ve learned that it changed recently.

I stand corrected. It's something I never saw/noticed/needed.

 

[David Cavalli]

I'm trying to use the System Log to find any anomalies that lead up to the router crash. Skipping the Link DOWN items, I see many sets of {Disassoc, Deauth_ind, Auth, Assoc} sets in the log when some IoT devices, tablets, etc. lose/reset connectivity. The only item that stands out other than those is the above "SIG_UPDATE" entries, which don't seem to change the value. Anything important?

Another night, another crash. About 30 minutes ago. Tonight, however, the log has some new entries. There's one kernel error @ 20:25 which I've never seen before. (I edited out two hours of random wlcevend on/off pairs.) My wife used her Apple iPad (the renamed BB:BB:BB:BB:BB:BB entry, which goes on/off all day for HayDay and other games) at 22:13:58, and had a strange status at that point. I think this triggered the main kernel error which came @ 22:14:10. This has a whole bunch of "things" that might be of use to someone who knows in resolving this. It's the most data I've seen ever at the point of a system crash and it was seconds after the iPad tried to connect.

Nov 22 20:25:04 kernel: NOHZ: local_softirq_pending 2ce
Nov 22 22:13:58 wlceventd: wlceventd_proc_event(645): eth7: Deauth_ind BB:BB:BB:BB:BB:BB, status: 0, reason: Unspecified reason (1), rssi:0
Nov 22 22:13:58 wlceventd: wlceventd_proc_event(685): eth7: Auth BB:BB:BB:BB:BB:BB, status: Successful (0), rssi:-57
Nov 22 22:14:10 kernel: rcu: INFO: rcu_preempt detected stalls on CPUs/tasks:
Nov 22 22:14:10 kernel: rcu:     Tasks blocked on level-0 rcu_node (CPUs 0-3): P9291
Nov 22 22:14:10 kernel: rcu:     (detected by 2, t=60011 jiffies, g=32887013, q=138558)
Nov 22 22:14:10 kernel: Call trace:
Nov 22 22:14:10 kernel:  __switch_to+0xe0/0x160
Nov 22 22:14:10 kernel:  0xffffff801ee4bc18
Nov 22 22:14:10 kernel: Call trace:
Nov 22 22:14:10 kernel:  __switch_to+0xe0/0x160
Nov 22 22:14:10 kernel:  0xffffff801ee4bc18
Nov 22 22:14:15 wlceventd: wlceventd_proc_event(722): eth7: Assoc BB:BB:BB:BB:BB:BB, status: Successful (0), rssi:0
Dec 31 16:00:32 kernel: klogd started: BusyBox v1.25.1 (2025-11-19 11:36:49 EST)
Dec 31 16:00:32 kernel: Linux version 4.19.183 (merlin@ubuntu-dev) (gcc version 9.2.0 (Buildroot 2019.11.1)) #1 SMP PREEMPT Wed Nov 19 11:37:06 EST 2025

Any insight appreciated. Can do anything on this end to help debug. Thanks!

 

[Tadas]

Hi, I would like to ask if version 3006.102.6-beta 2 includes fixes from version 3.0.0.6.102_38980?

 

[bennor]

Hi, I would like to ask if version 3006.102.6-beta 2 includes fixes from version 3.0.0.6.102_38980?

Note the change log in the very first post of the thread. It lists the GPL's included in the beta release.

- UPDATED: Merged GPL 38978 (RT-BE58_GO only)
- UPDATED: Merged GPL 40103 (GT-BE19000AI only)
- UPDATED: Merged GPL 39099 (other Wifi 7 models)
- UPDATED: Merged GPL 37351 (Wifi 6 models)

Further RMerlin indicates the code he receives from Asus is unrelated to what Asus releases on their website.

I get code directly from Asus, it's unrelated to what's released on their website. I have particular requirements that their developers need to meet when preparing the archives, like having the same code base for all models, which is rarely the case with their own firmware releases.

PS: And more explanation from RMerlin.

It depends. If you ask them for a GPL drop for a particular model, it will be for the same version that was used for that model's released firmware - which is what the GPL licensing requires them to do. The difference in my case is they build the tarballs for all models within a branch but all on the same version, so I don't need to maintain 20 parallel branches to handle 20 devices on 20 different codebase versions. Sometimes, that version will match a released firmware. Sometimes it will be a newer snapshot, depending on the point in time where they prepare those archives. But in terms of content, yes, that is the same code that is available in regular GPL drops. Just it might be from a more recent git point.

 

[SANdood]

On the RT-BE92U Network Map page, I notice that the tabs are missing under the System Status segment on the right - it only shows what is on the "Status" page. Shouldn't there be a page for "Wireless"?

TBH, I don't remember if it was there on the stock firmware before I upgraded this new router to Merlin...

It seems maybe this is related to the BE models:

Note also the absence of the SSID list on the BE92U

 

[bpsmicro]

It seems maybe this is related to the BE models:

View attachment 69135

View attachment 69136

View attachment 69137

Note also the absence of the SSID list on the BE92U

I have the BE92 still on 3006.102.5. When I first click on "Network Map", I see the "System Status" screen as you show.
If I click on the Clients box, the screen changes to show "Client Status", with the Online, Wired & Wireless tabs.
I don't recall seeing it behave any other way.

 

[lgkahn]

I have the BE92 still on 3006.102.5. When I first click on "Network Map", I see the "System Status" screen as you show.
If I click on the Clients box, the screen changes to show "Client Status", with the Online, Wired & Wireless tabs.
I don't recall seeing it behave any other way.
View attachment 69140

same on be88u

 

[GWTechTalk]

Using this on BE96U and so far, it is working well. While this version didn't introduce the bug this version still has the issue where 6Ghz devices are not shown in the main network map. The only place you can see those devices is in the System Log > Wireless Log. Either way just a minor UI issue functionally I haven't had any problems. Like everyone else reported the SSID is no longer seen on the main page but it doesn't bother me as I know where to get that information anyways. In the right side wireless menu after selecting the computer icon on the main screen you can select 6Ghz but it enters a search loop that doesn't end or find the devices. To me this just seems like a data pointer issue in the UI. It's not pointed to the proper location for the UI to show.

 

[RMerlin]

6Ghz devices are not shown in the main network map

Works for me. My tablet currently appears on the Client List when sorted by Network, same with the Client Status when displaying just the 6 GHz tab. Open your browser console and look for JS errors.

 

[Blkpanthr]

Using this on BE96U and so far, it is working well. While this version didn't introduce the bug this version still has the issue where 6Ghz devices are not shown in the main network map. The only place you can see those devices is in the System Log > Wireless Log. Either way just a minor UI issue functionally I haven't had any problems. Like everyone else reported the SSID is no longer seen on the main page but it doesn't bother me as I know where to get that information anyways. In the right side wireless menu after selecting the computer icon on the main screen you can select 6Ghz but it enters a search loop that doesn't end or find the devices. To me this just seems like a data pointer issue in the UI. It's not pointed to the proper location for the UI to show.

View attachment 69143

Same on my BE92U. Not in network map, but shown on wireless log.

wireless log says its connected multiteam (2) AX spec.

only error in the console (chrome) is "clients.asp:1 Uncaught (in promise) Error: Could not establish connection. Receiving end does not exist."

pops up when i click on clients bubble. nothing additional when i select 6ghz on the side panel.

Same behavior on Chrome, Edge, and Firefox.

 

[Blacklistedcard]

My BE98Pro has the tabs on the system status?

 

[Blacklistedcard]

Using this on BE96U and so far, it is working well. While this version didn't introduce the bug this version still has the issue where 6Ghz devices are not shown in the main network map. The only place you can see those devices is in the System Log > Wireless Log. Either way just a minor UI issue functionally I haven't had any problems. Like everyone else reported the SSID is no longer seen on the main page but it doesn't bother me as I know where to get that information anyways. In the right side wireless menu after selecting the computer icon on the main screen you can select 6Ghz but it enters a search loop that doesn't end or find the devices. To me this just seems like a data pointer issue in the UI. It's not pointed to the proper location for the UI to show.

View attachment 69143

I just checked my BE98Pro. There is no problem with the listing of 6Ghz connected devices. Both 6Ghz channels are displaying connected devices fine.

 

[Blkpanthr]

turns out i was on beta1. the 92U was not in the initial batch of beta2 releases. it was uploaded 3 days ago and i never went back to check.

dirty upgrade to beta2 fixed the 6hz not showing on the network map page.

 

[Poul Bak]

Using this on BE96U and so far, it is working well. While this version didn't introduce the bug this version still has the issue where 6Ghz devices are not shown in the main network map. The only place you can see those devices is in the System Log > Wireless Log. Either way just a minor UI issue functionally I haven't had any problems. Like everyone else reported the SSID is no longer seen on the main page but it doesn't bother me as I know where to get that information anyways. In the right side wireless menu after selecting the computer icon on the main screen you can select 6Ghz but it enters a search loop that doesn't end or find the devices. To me this just seems like a data pointer issue in the UI. It's not pointed to the proper location for the UI to show.

View attachment 69143

I had this bug on my BT10 (stock - as access point), which takes care of my wifi.
I found that enabling MLO on the 'Wireless' tab, 'MLO' made them show correct.
Don't know if it's related at all, but you could try that.

 

[GWTechTalk]

Works for me. My tablet currently appears on the Client List when sorted by Network, same with the Client Status when displaying just the 6 GHz tab. Open your browser console and look for JS errors.

I stand corrected. It is now seeing my 6Hz devices in the wireless menus on the main screen. I did have one error but I'm not sure what it means. Sorry for the false alarm. I swear it was not working for quite a long time. Why it's working now, donno, must be layer 8 issues.

 

[RMerlin]

I stand corrected. It is now seeing my 6Hz devices in the wireless menus on the main screen. I did have one error but I'm not sure what it means. Sorry for the false alarm. I swear it was not working for quite a long time. Why it's working now, donno, must be layer 8 issues.


View attachment 69149

That file is not part of the firmware, so it must be coming from a browser addon.

 

[penguin22]

Not sure if related or arbitrary, however with my BE86U AiMesh node running beta 2, one of my IoT networks stopped functioning. All other networks worked fine and I only had to restart wireless from SSH on the node to restore connectivity.

Digging through the logs with some Copilot help, since I haven't done a restart of the node, only the wireless driver, I get the following:

From the earlier logs:

Repeated GTK handshake failures and WLC_SCB_DEAUTHORIZE error (-30) indicate the driver couldn’t complete key updates or clean up stale station entries.
MLO association failures (status 31) suggest the radio was in a transitional state (possibly DFS or resource contention).
Combined, this points to a wireless subsystem bug or resource exhaustion, not a config or firewall issue.

The SSID didn’t disappear from config; the VAP was either:

Not properly initialized, or
Hostapd couldn’t manage it due to driver state corruption.

Restarting wireless flushed the driver and hostapd state, recreated VAPs, and fixed the issue.