Beta Asuswrt-Merlin 3006.102.6 Beta is now available

[nagyimre1980]

@RMerlin

I think this change entry is wrong. This affects the BCM4912 too! Not only the BCM4916 devices.

- FIXED: OpenSSL 1.1.1 would prioritize CHACHA20 over AES
on BCM4916 devices

 

[X3wKNkGk]

I just encountered the wifi disconnect after upgraded to this beta version on be86, and I find out it printed these logs around that moment:

Nov 13 17:59:49 acsd: acsd_main_loop(1285): sync_id: 22152, status:4, misc.error/abort
Nov 13 17:59:53 kernel: WLC_SCB_DEAUTHORIZE error (-30)
Nov 13 17:59:53 kernel: WLC_SCB_DEAUTHORIZE error (-30)
Nov 13 17:59:53 kernel: WLC_SCB_DEAUTHORIZE error (-30)
Nov 13 17:59:53 kernel: WLC_SCB_DEAUTHENTICATE_FOR_REASON err -30
Nov 13 17:59:53 kernel: WLC_SCB_DEAUTHENTICATE_FOR_REASON err -30
Nov 13 17:59:53 kernel: WLC_SCB_DEAUTHENTICATE_FOR_REASON err -30
Nov 13 17:59:54 kernel: WLC_SCB_DEAUTHORIZE error (-30)
Nov 13 17:59:54 kernel: WLC_SCB_DEAUTHENTICATE_FOR_REASON err -30

not sure if anyone who also has ever encountered similar issue before?

 

[Chestertheman]

I own the rt-ax86u pro and the one problem I noticed is MU-MIMO is missing on both frequencies.

 

[steamidwudichao]

hi @RMerlin reporting the same thing on my AX6000, updated from alpha 1 to beta 1.
Logo lights stays off but LAN, WAN and Wifi lights stays on despite "enable leds" to off

 

[RMerlin]

@RMerlin

I think this change entry is wrong. This affects the BCM4912 too! Not only the BCM4916 devices.

- FIXED: OpenSSL 1.1.1 would prioritize CHACHA20 over AES
on BCM4916 devices

View attachment 68896

The bug was that it only checked for 4908 and 4912, and didn't check for 4916. If you look at the new first line, it now checks for all three CPU models that shouldn't prioritize CHACHA.

 

[MDM]

But seriously Asus - successed instead of succeeded...
“successed” is not a proper word in the English language I know, and I am not native either. Or is it a misspelling from linux?

 

[heysoundude]

There must have been over 20+ SSIDs all starting with "skyrealm" visible at that time.

If you REALLY want to have some fun, make that the default SSID for any router flashed with your firmware.

 

[John Adler]

Dirty flash from alfa to beta1 on RT-AX86U Pro
so far everything works fine
thxs Merlin

 

[Poul Bak]

I'm not sure if the stock firmware even expects logging to happen over IPv6, as they automatically redirect you to www.asusrouter.com, which probably resolves only as an IPv4. Asuswrt-Merlin does not enforce that redirection, so it might be causing this issue.

That means I will probably have to see if I can fix that myself. At least part of that log code is open source, no idea if enough of it is accessible for me to fix it. I suspect I might be able to fix the syslog portion, but not the Security Log portion.

You're right, 'www.asusrouter.com' resolves to an ipv4 address only. People using that won't see this bug.
The reason I use custom urls like 'https://myrouter.home' is that I can now connect to both routers' GUI (I have always hated ip addresses in browser).
The only problem is that you need custom certificates for each router (not trivial but a one time job). My own certificates use the host name and domain with no browser warning.

My BT10 (stock as access point)) does not redirect to 'asusrouter.com' - it uses custom urls with the host name and domain (but as I said: No ipv6 on access point so no wrong addresses).
I tried to enable 'Redirect webui access to www.asusrouter.com' in 'Tweaks'. However I don't see ANY change at all - it doesn't redirect (just a test - I really don't care about that).

Well, the good news are that it doesn't break anything in router, it just makes the 'Security Update Notification' useless, I will not notice if I'm actually being hacked.

 

[Poul Bak]

On my AX86-Pro these correctly show logins to the router. Not sure why this would be called "Security Update Notivication" or noted as "successed".

If you're using 'www.asusrouter.com' or ipv4 address in browser, you won't see this - it's an ipv6 thing. Or do you actually see ipv6 addresses in log?

 

[RMerlin]

But seriously Asus - successed instead of succeeded...
“successed” is not a proper word in the English language I know, and I am not native either. Or is it a misspelling from linux?

That string isn`t part of the webui, so it was written by an engineer who probably has very limited English skills. The webui uses language catalogs that do get handled by a translation team.

For years, they would spell "stoped" throughout the rc code when logging that a service had been stopped, for example.

If you're using 'www.asusrouter.com' or ipv4 address in browser, you won't see this - it's an ipv6 thing. Or do you actually see ipv6 addresses in log?

When using a hostname on an IPv6-enabled network, your browser might resolve to an IPv6. In my case for example, https://stargate/ resolves to an IPv6.

 

[RMerlin]

Fixing the IPv6 logging won't be doable on my end. Internally, that function does not receive the whole IPv6, it only receives a small subset of it.

Fixing it will require more low-level changes, which falls in Asus' courtyard.

 

[Poul Bak]

Fixing the IPv6 logging won't be doable on my end. Internally, that function does not receive the whole IPv6, it only receives a small subset of it.

Fixing it will require more low-level changes, which falls in Asus' courtyard.

''BUMMER'' - but I kind of expected that. Thanks for investigating. Still embarrassing for Asus IMHO, ipv6 is almost 30 years old and still "Oops, we didn't expect ipv6".

 

[SomeWhereOverTheRainBow]

Known issues:

• ZenWifi Pro XT12 missing (GPL wasn't ready in time for beta 1, should be available in beta 2)
• GT-AX60000 LEDs not properly disabled at boot time (Fixed for beta 2)
• Cannot backup JFFS2 on GT-BE19000AI (Fixed for beta 2)

Great work here! One has to wonder how soon after release did you get your GT-BE19000AI.

 

[SomeWhereOverTheRainBow]

Fixing it will require more low-level changes, which falls in Asus' courtyard.

''BUMMER'' - but I kind of expected that. Thanks for investigating. Still embarrassing for Asus IMHO, ipv6 is almost 30 years old and still "Oops, we didn't expect ipv6".

Yep, only low-level skilled labor can make these changes-- afterall, ipv6 is such a niche concept. @RMerlin is after tackling the more challenging top tier stuffs.

 

[Poul Bak]

Yep, only low-level skilled labor can make these changes-- afterall, ipv6 is such a niche concept. @RMerlin is after tackling the more challenging top tier stuffs.

Niche concept????????
Have you been in coma the last 10 years?
At least Google thinks it important enough to make statistics: Ipv6 statistics.
Half the world have ipv6 now!

...and I'm not blaming Merlin at all, this is on Asus.

 

[Chestertheman]

Dirty flash from alfa to beta1 on RT-AX86U Pro
so far everything works fine
thxs Merlin

Check to see if mu-Mimo is still showing up for you under both bands. I reset my settings after I updated so idk if that makes a difference.

 

[RMerlin]

Great work here! One has to wonder how soon after release did you get your GT-BE19000AI.

I got it before launch, in early October.

 

[#TY]

Does this mean that WISP will also be available on the ASUS RT-BE92U?

 

[FLA_NL]

Dirty upgrade RT-AX86U Pro from 3006.102.5 to 3006.102.6_beta1 (running almost 2 days). Statistics page is working. Still cannot connect the Awair Element sensor as in previous 3006.102.x versions, still working around that with connecting it to the Access Point RT-AX86U (Non Pro). No other noticeable issues.