[ 3006.102.6 alpha Build(s) ] available build(s)

[AceSpace]

BE92U - 3006.102.6_alpha2-g683db26d11
2.4ghz WLC_SCB_DEAUTHORIZE error (-30)
After half an hour, an error appears in the logs and the devices begin to reconnect.

 

[penguin22]

I sometimes see similar in the logs:

Nov 7 15:25:49 RT-BE88U kernel: CFG80211-ERROR) wl_cfg80211_change_station :
Nov 7 15:25:49 RT-BE88U kernel: WLC_SCB_DEAUTHORIZE error (-30)
Nov 7 15:25:49 RT-BE88U kernel: CFG80211-ERROR) wl_cfg80211_del_station :
Nov 7 15:25:49 RT-BE88U kernel: WLC_SCB_DEAUTHENTICATE_FOR_REASON err -30
Nov 7 15:25:49 RT-BE88U kernel: CFG80211-ERROR) wl_cfg80211_change_station :
Nov 7 15:25:49 RT-BE88U kernel: WLC_SCB_DEAUTHORIZE error (-30)

 

[Ripshod]

I've been seeing those too. For quite a while now - certainly in the last release too.
Nothing's actually broken so I don't worry.

 

[penguin22]

I've been seeing those too. For quite a while now - certainly in the last release too.
Nothing's actually broken so I don't worry.

It appears to be primarily IoT clients that don't properly disassociate and lose connection in a non-clean manner.

 

[AceSpace]

It appears to be primarily IoT clients that don't properly disassociate and lose connection in a non-clean manner.

The problem is that after such messages, IoT devices start to constantly lose connection in my case.

 

[CaptainLockness]

I had tried using the stock on my nodes, BE86U and BE82U wired backhaul respectively. I found that the BE82U is fully stable and works well with the current stock firmware (3.0.0.6.102_39099), though the BE86U on current stock (3.0.0.6_102_39112) was unstable with continuous reboots throughout the day, which persisted even after a full reset.

I am now running Alpha 2 on the main BE88U router and Merlin 3006_102.5_0 on the BE86U Mesh node with full stability for what it's worth.

What ive done is downgrade back to Alpha 1 from the old broken version of Alpha 2 and just upgraded to the fixed version of Alpha 2 and everything works again.

Keep in mind the only i have changed is normal network settings and only MerlinAU installed recently for my RT-BE88U.

 

[Asım Demir]

What ive done is downgrade back to Alpha 1 from the old broken version of Alpha 2 and just upgraded to the fixed version of Alpha 2 and everything works again.

This didn't work for me. The version isn't changing. (BE86U)

 

[penguin22]

What ive done is downgrade back to Alpha 1 from the old broken version of Alpha 2 and just upgraded to the fixed version of Alpha 2 and everything works again.

This worked fine for the BE88U, though not for the BE86U, which doesn't like Alpha 2 for some reason.

 

[Geraner]

Tried to upgrade from ASUS stock firmware 3.0.0.6.102_39112 to Alpha2. After a reboot, the RT-BE86U still runs on stock firmware 3.0.0.6.102_39112.

 

[bennor]

Tried to upgrade from ASUS stock firmware 3.0.0.6.102_39112 to Alpha2. After a reboot, the RT-BE86U still runs on stock firmware 3.0.0.6.102_39112.

May or may not apply but since you were coming from stock Asus 3.0.0.6.102_39112 firmware to Asus-Merlin firmware you may need to perform the following (if you haven't previously done so) that is mentioned in the Asus-Merlin change log in order to successfully flash Asus-Merlin firmware to the router:

3006.102.3 (11-Jan-2025)
- NOTE: If flashing on top of Asus stock firmware 3006.102_37000
or greater, then you first need to enable downgrade
capabilities before flashing Asuswrt-Merlin on top
of it. Connect Over SSH, and run the following command:

nvram set DOWNGRADE_CHECK_PASS=1

After that, you can upload Asuswrt-Merlin through
the webui like any regular firmware upgrade.

This is only required when flashing Asuswrt-Merlin
for the first time.

 

[X3wKNkGk]

May or may not apply but since you were coming from stock Asus 3.0.0.6.102_39112 firmware to Asus-Merlin firmware you may need to perform the following (if you haven't previously done so) that is mentioned in the Asus-Merlin change log in order to successfully flash Asus-Merlin firmware to the router:

3006.102.3 (11-Jan-2025)
- NOTE: If flashing on top of Asus stock firmware 3006.102_37000
or greater, then you first need to enable downgrade
capabilities before flashing Asuswrt-Merlin on top
of it. Connect Over SSH, and run the following command:

nvram set DOWNGRADE_CHECK_PASS=1

After that, you can upload Asuswrt-Merlin through
the webui like any regular firmware upgrade.

This is only required when flashing Asuswrt-Merlin
for the first time.

I guess this is not the cause of not having a successful upgrade to alpha2, and it seems like there's something wrong with this version.
As I notice more people trying to update to alpha2 on be86 all hit the same problem as reported in this thread... no matter which version where they were trying to upgrade from

 

[Dedel66]

Maybe they all did not perform the procedure bennor told?

So you may try and tell all if it worked for you.

 

[KevTech]

nvram set DOWNGRADE_CHECK_PASS=1

Tried and did not work.
I add nvram commit to that command to make sure it sticks even if I reboot the router.
Something wrong with alpha2 that the router does not like so refuses to upgrade to it.
Tried from stock, alpha 1 and even from 3006_102.5_0
Reset to defaults after changing to each of these but still refuses to update.

 

[Geraner]

As I notice more people trying to update to alpha2 on be86 all hit the same problem as reported in this thread... no matter which version where they were trying to upgrade from

Missed that part. Thanks for the hint. I will stay on stock firmware 3.0.0.6.102_39112 for the time being. Until Merlin might has answered on this post, and until the Beta is starting.
stock firmware 3.0.0.6.102_39112 works just fine for me. I'm just missing a few of the Merlin features.

 

[RMerlin]

GPL merge issue with the RT-BE86U with the rdp component of the SDK, possibly conflicting with other models. I have removed the test build for now. It seems Asus has compiled GPLs from two different SDK versions. It seems the RT-BE86U has some unique code not present in other models in one of the binary SDK components, and it was working in 3006.102.5 by pure luck.

 

[RMerlin]

For those wondering what is actually happening - these routers have two boot/rootfs partitions. If one fails to boot, then the router reboots on the other partition. This is why for instance I always said to avoid using hnd-write unless you really, REALLY must use it. Flashing a non-working image with hnd-write means your router will keep boot looping on that image, requiring the use of recovery mode. The web-based firmware upgrade takes care of switching partition, so flashing a non-working firmware will usually just switch back to the previous firmware.

In this case, the RT-BE86U fails to boot, so the router reboots on its other partition, containing the previous firmware.

 

[CaptnDanLKW]

I sometimes see similar in the logs:

Nov 7 15:25:49 RT-BE88U kernel: CFG80211-ERROR) wl_cfg80211_change_station :
Nov 7 15:25:49 RT-BE88U kernel: WLC_SCB_DEAUTHORIZE error (-30)
Nov 7 15:25:49 RT-BE88U kernel: CFG80211-ERROR) wl_cfg80211_del_station :
Nov 7 15:25:49 RT-BE88U kernel: WLC_SCB_DEAUTHENTICATE_FOR_REASON err -30
Nov 7 15:25:49 RT-BE88U kernel: CFG80211-ERROR) wl_cfg80211_change_station :
Nov 7 15:25:49 RT-BE88U kernel: WLC_SCB_DEAUTHORIZE error (-30)

Same here. I have an old Surface Pro 4 with the Marvell AVASTAR WLAN adapter. From what I read this error is due to incomplete implementation of certain capabilities within the driver.

 

[salieri]

I noticed that for the BE86U, the official ASUS firmware version 3.0.0.6.102_38984 came out after the current Merlin stable release (3006.102.5).

In the official ASUS notes, it says:

“Important: After installing this firmware, we strongly recommend performing a factory-default reset to activate every new security adjustment.”

Does this mean we’ll need to do a full factory reset again once Merlin 3006.102.6 stable is released to accommodate for this?

 

[ryosuke]

3.0.0.6.102_38984
this is no longer the latest one.

 

[penguin22]

3.0.0.6.102_38984
this is no longer the latest one.

Note, there is a stability issue with 3.0.0.6.102_39112 for the BE86U, which I reported to ASUS support. Downgrading to 3.0.0.6.102_38984 resolved the issue for me. Merlin GPL shouldn't be directly compared to stock firmware as they are provided directly and the numbering is not directly comparable.