Release Asuswrt-Merlin 3004.388.9 is now available

[aex.perez]

I have exactly the same problem. Anyway to fix it?

View attachment 64939

Shorten the names as mentioned, but the ones that are already short and still show up incorrectly, the one before/above needs to be shortend to fix it, even if it loooks fine.
Get a little creative, before "Kids Bed Room", after "KBR" - maybe in your case "AC" instead of "AR Condicionado"

 

[aex.perez]

I have exactly the same problem. Anyway to fix it?

View attachment 64939

I think I responded to this in another post. Shorten the name of the impacted ones and the ones above/below the ones that aren't as that will fix the ones that all ready have short names but are messed up because of the long name of the device before it. Get creative, I did "KBR" for "Kids Bedroom" maybe "AC" instead of "Ar Condicionado" will work for you and may reduce the name enough for some of the others

 

[aex.perez]

So some issues with WiFi clients, AiMesh node disappearing, WPA2/WPA3-Personal vs WPA2-Personal, and roaming assistant personal and a lot of client reconfiguring (not reconfigure, same settings) but pretty much have it figured out now, and for now stable.

If you'd like in on the fun and see what we did and went through to avoid going through it yourself or try and look for a bug, we couldn't find one that was overt.
Read through the long set of posts starting here with the one that opened the flood gates on getting everything working: https://www.snbforums.com/threads/m...auto-updater-gnuton-support.91326/post-951078

@RMerlin, probably not the right place for it but we were on a roll.
Sorry!

So, for giggles and to confirm behavior. Switched back to WPA2/WPA3-Personal, all three SSID's but one at a time. And sure enough the problems we, @ExtremeFiretop and I were having with WiFi devices connecting immediately happend, mostly impacting the devices trying to connect to the nodes, but had a couple that didn't connect to the router either, the same ones I had issues with before, that I need to setup again, but with all the smae settings.

Well, at least it's consistent in that respect. As soon as I changed everything back to WPA2-Personal, and waited a bit for things to settle, everything connected back up.
Might try a couple of other things, I just need to reconfigure things to use them ,maybe even the other Authentication Methods to see if those cause the issue as well.

But I still wonder, after I reverted the previous FW, I still had the same issue. I actually had to WPS reset and restore the Router and each node to get it working again when I rolled back. I did compare all the NVRAM settings and logs and didn't see anything different or out of place. I have to think this is at low level to affect that, something that can likey only be addressed by ASUS, more so as it has a greater impact (but not exclusively) on AiMesh which is closed source and completely invisible to @RMerlin

For now with WPA2-Personal and everything connected on the Router and nodes, all on 388.9 - All good!

 

[ExtremeFiretop]

So, for giggles and to confirm behavior. Switched back to WPA2/WPA3-Personal, all three SSID's but one at a time. And sure enough the problems we, @ExtremeFiretop and I were having with WiFi devices connecting immediately happend, mostly impacting the devices trying to connect to the nodes, but had a couple that didn't connect to the router either, the same ones I had issues with before, that I need to setup again, but with all the smae settings.

Well, at least it's consistent in that respect. As soon as I changed everything back to WPA2-Personal, and waited a bit for things to settle, everything connected back up.
Might try a couple of other things, I just need to reconfigure things to use them ,maybe even the other Authentication Methods to see if those cause the issue as well.

View attachment 64946

But I still wonder, after I reverted the previous FW, I still had the same issue. I actually had to WPS reset and restore the Router and each node to get it working again when I rolled back. I did compare all the NVRAM settings and logs and didn't see anything different or out of place. I have to think this is at low level to affect that, something that can likey only be addressed by ASUS, more so as it has a greater impact (but not exclusively) on AiMesh which is closed source and completely invisible to @RMerlin

For now with WPA2-Personal and everything connected on the Router and nodes, all on 388.9 - All good!

I noticed that while I don't have a single network set was WPA2/WPA3-Personal since the discovery of issues; it still says that's the security on the home page:

A little confusing and maybe a clue of some kind.

 

[AlbumMan]

Dirty update yesterday from 388.8_4 directly to 388.9 on RT-AX3000 node. All good so far.
Am holding out until 3006.102.4 is released for main router, RT-AX86U Pro.

 

[aex.perez]

I noticed that while I don't have a single network set was WPA2/WPA3-Personal since the discovery of issues; it still says that's the security on the home page:

View attachment 64947

A little confusing and maybe a clue of some kind.

I checked mine as well, but it's showing correctly.

So maybe it is a clue

Clicking on the circle, brings up the config for the my Dual Band and Smart Connect SSID

 

[dave14305]

A little confusing and maybe a clue of some kind.

That could come from either variables:

• wl0_auth_mode_x
• sdn_rl for MAINFH network

 

[magwa_sc]

I was switching my wireless security level from WPA2 Personal to WPA2/WPA3 via the wireless tab and then switched it back to only WPA2 and when the page auto reloaded I got this screenshot below. I was able to just refresh the page again and everything was fine but I thought I would report my findings. I tried to reproduce the issue but I wasn't able to.

 

[ExtremeFiretop]

I checked mine as well, but it's showing correctly.

View attachment 64948
So maybe it is a clue

Clicking on the circle, brings up the config for the my Dual Band and Smart Connect SSID

View attachment 64949

Clicking on the circle for me refreshes and does absolutely nothing! Lol Brings me back to the "status" page showing my CPU usage.

That could come from either variables:

• wl0_auth_mode_x
• sdn_rl for MAINFH network

I appreciate your analyses! Here are my results:

Admin@GT-BE98_Pro:/tmp/home/root# nvram get wl0_auth_mode_x
psk2sae

 

[dave14305]

Here are my results

Actually, you probably want something like:

nvram show 2>/dev/null | grep apm[0-9]_security=.

 

[DrTurk]

Dirty update yesterday from 388.8_4 directly to 388.9 on RT-AX86U. All good so far.

 

[RMerlin]

I have exactly the same problem. Anyway to fix it?

View attachment 64939

My guess is that the name is too long to fit within the field, and there`s no vertical space to add a second line, so it wraps on top of itself.

 

[tallytr]

My guess is that the name is too long to fit within the field, and there`s no vertical space to add a second line, so it wraps on top of itself.

Its a detail but no clue why, not a long name...you can put in only one letter and it still shows wrapped...

 

[dave14305]

Its a detail but no clue why, not a long name...you can put in only one letter and it still shows wrapped...

View attachment 64958

Is that first one supposed to read “Christoph’s iPhone Home” but the “me” is what wraps to overlay the following entry? It’s difficult to read the overlapping text to understand where it really belongs.

 

[aex.perez]

Its a detail but no clue why, not a long name...you can put in only one letter and it still shows wrapped...

View attachment 64958

Even a shorter name will be wonky if the one above or below is. I just shortend them all (using abbreviations like "KBR" for "Kids Bedroom") and now all look fine. What I didn't do is look to see what I could get away with before the name in the field (character length) wraps around.

 

[yxo-6o6uka]

I greatly appreciate the continuing development and support of this fw line, thank you!
Upgraded RT-AX88U from 3004.388.8_4 to 3004.388.9. Lost ability to SSH into the router using key pair. PUTTY gets "server unexpectedly closed connection". The key pair is correct, triple rechecked with other router and a linux server.
Still able to SSH into the router with a password.

Downgraded to 3004.388.8_4 and SSH works with same key pair and/or password.

The issue appears to be 3004.388.9 specific. If I missed some documented change pls point. TIA!

 

[RMerlin]

I greatly appreciate the continuing development and support of this fw line, thank you!
Upgraded RT-AX88U from 3004.388.8_4 to 3004.388.9. Lost ability to SSH into the router using key pair. PUTTY gets "server unexpectedly closed connection". The key pair is correct, triple rechecked with other router and a linux server.
Still able to SSH into the router with a password.

Downgraded to 3004.388.8_4 and SSH works with same key pair and/or password.

The issue appears to be 3004.388.9 specific. If I missed some documented change pls point. TIA!

Check the system log. Dropbear was upgraded, it`s possible that you key is too weak and gets rejected by the updated Dropbear.

 

[ivannn]

Its a detail but no clue why, not a long name...you can put in only one letter and it still shows wrapped...

View attachment 64958

dirty upgrade on ax86u
I have the same issue. Browser cache was cleared. It's cosmetic, but nevertheless unexpected.

 

[Igor]

ASUS RT-AX68U fw 3004.388.9

Does the new dropbear have limitations?
I'm seeing an access problem from the Home Assistant integration:

Apr 12 09:04:13 dropbear[5255]: Child connection from 192.168.2.225:44326
Apr 12 09:04:13 dropbear[5255]: Exit before auth from <192.168.2.225:44326>: No matching algo hostkey

 

[Reef2009]

Dirty upgraden o 2*AX88u (route + node) with lost of amtm and customizations.
No issues so far. Running for 48 hours