Release ASUS RT-AX88U Pro Firmware version 3.0.0.6.102_33308

[shaft]

Guest network will not save my 63 character ASCII printable network keys after a reboot. This did work properly in the previous Asus firmware branch 3.0.0.4_388_***** and Merlin's current branch. After a reboot my Guest network network keys become truncated and no longer work until I reenter them. In addition Guest Network Pro has a 32 character limit to network key length that requires me to access a hidden page in the GUI at http://192.168.50.1/Guest_network.asp to enter the network keys. I have submitted a bug report to Asus.

 

[dave14305]

Guest network will not save my 63 character ASCII printable network keys

Your guests must hate you if they need to enter that key by hand. Torture.

 

[shaft]

Your guests must hate you if they need to enter that key by hand. Torture.

I use the keys for my robot vacuums, mower, and security cameras. They are all copy pasted.

 

[shaft]

Guest network will not save my 63 character ASCII printable network keys after a reboot. This did work properly in the previous Asus firmware branch 3.0.0.4_388_***** and Merlin's current branch. After a reboot my Guest network network keys become truncated and no longer work until I reenter them. In addition Guest Network Pro has a 32 character limit to network key length that requires me to access a hidden page in the GUI at http://192.168.50.1/Guest_network.asp to enter the network keys. I have submitted a bug report to Asus.

One other thing I noticed is that I can see the same truncated network key (3 characters) if I view it through the Guest Network Pro page even when it is working correctly (with a 63 character key) from the hidden Guest network page. Perhaps the Guest Network Pro information is the one saved to nvram on reboot? "nvram show" shows the correct key though until reboot.

 

[shaft]

lol, Asus replied to my bug report with this:

I knew they would be no help...

 

[OzarkEdge]

I tried the GNP Guest Portal... seems to work as intended except I don't understand the landing page response on my Android devices... after agreeing to the Terms of Service, the landing page flashes briefly and then the browser closes. Appears to work properly on Win10... the browser opens and stays... if the ToS change while connected, Win10 Wireless notifies of action required; you select the notification and the browser opens again with revised ToS.

Also, once any WiFi credential and/or passcode are entered, the portal no longer presents the ToS... until they are revised. Except I think I'd like an option to display the ToS everytime a client connects so the visitor can review important information (not typical ToS) at any time by simply reconnecting.

And what DNS would you recommend to keep Guest Portal access to the Internet only as kid-safe as possible? I'm currently trying CleanBrowsing 185.228.168.168, 185.228.169.168... seems to block porn, an easy test.

OE

 

[OzarkEdge]

Bug! Changing GNP Pro Guest Portal settings pertaining to ToS totally blew away my custom Guest and IoT VLANS and WLANs. LAN\VLAN profiles is empty except for the guest portal VLAN. And now the remaining guest portal VLAN profile is a Custom Network with no portal option. Not good... firmware got confused and borked itself.

Update: Performed a full Hard Reset etc. and similar happened again... the AiMesh topology page went blank and the GNP page reset to no entries/scratch... and would not recover. But I notice the WLANs still broadcasting so I logged out and back into the webUI to find all returned to normal. So, perhaps a webUI issue here on Win10 Edge.

Example of webUI corruption... even my main SSID is not displayed:

The GNP page also went back to its default state... no VLANs displayed. When it happens, logout and log back in to clear the condition.

OE

 

[OzarkEdge]

Some more findings with GNP...

GNP VLAN profiles are offering me a 6GHz selection! I don't have a 6GHz radio, so that's not right.

Now for the main issue...

Given two custom VLAN profiles:
2.4/5.0 custom WLANs, all nodes (for guests)
2.4 custom WLANs, all nodes (for IoT)

When I add a third predefined VLAN profile:
2.4/5.0 predefined Guest Portal WLANs, all nodes

... the remote 86U Pro node stops broadcasting all VLAN WLANs... only the main WLANs are broadcast... no VLAN WLANs on the remote 86U node.

To get back to something half usable, if I disable the Guest Portal VLAN on the remote 86U Pro node, that node resumes broadcasting the given VLAN WLANs correctly. The 2.4/5.0 Guest Portal WLANs are then only broadcast from the 88U Pro router/root node... half usable.

In other words, when I apply this 2.4/5.0 Guest Portal VLAN to my 86U Pro node, that node stops broadcasting all VLAN WLANs. So, I won't do this until something gets fixed.

This issue could just be related to using the pre-defined Guest Portal on a node, or on a mismatched node like mine, and may have nothing to do with my given VLAN profiles.

I would like to know if a 2x AX88U Pro AiMesh exhibits the same issue. And no, I am not going to replace my 86U Pro with an 88U Pro.

Update: Guest Portal WLAN on root node follows schedule... shut down last night and fired up this morning on schedule.

OE

 

[OzarkEdge]

Administration\Privacy\ASUS Privacy Notice *link in blue* comes up blank here on Win10 Edge:

Regarding Security upgrades...

"Security upgrade incorporates security measures that continuously update its security file and scans to protect against malware, malicious scripts, and emerging threats in order to secure the router and ensure system stability. Some upgrades addressing important security issues or meeting legal/regulatory requirements will still be downloaded and installed automatically, even if “Security Upgrade” is turned off."

This seems to be new or newly revealed, and separate from the Trend Micro stuff... has it been discussed here... what is the router doing?... running anti-malware on the router fulltime?... all routers or just the stronger ones?

OE

 

[OzarkEdge]

Had some more wonkiness with GNP WLANs... OE Guest signal seemed less stable on node and would exhibit name * on a WiFi analyzer app which I use for relative comparisons, so did not look/feel normal. Tried soft system reboot and node reboot... not much change and noticed the router Log indicating 'skip event reboot'. This after some text edits to a test Guest Portal on router only. So, I removed the node to reset it, power cycled the router to reboot it, added the node, and added GNP WLANs OE Guest and OE IoT back to the node. Seems back to working normally now.

It would be handy to have some way to instruct the firmware to rebuild a node fully upon adding it so as to not have to revisit up to five GNP WLANs to configure their AiMesh Mode... i.e., make the Mode setting stick through removing/adding back nodes for the typical maintenance reasons.

OE

 

[OzarkEdge]

More trivia...

Noticed this in the Log... a Linux mechanism to prevent run-away processing(?):

Jul 2 10:49:49 kernel: sched: RT throttling activated

And this... the GNP Guest Portal open source code https://coova.github.io/CoovaChilli/ :

coova-chilli

And these... a little humorous:

Jun 30 20:19:57 coova-chilli[13234]: ssl.c: 384: Spurious SSL handshake interrupt [Hint: Usually just one of those OpenSSL confusions!?]
Jun 30 20:19:59 coova-chilli[13236]: ssl.c: 384: Spurious SSL handshake interrupt [Hint: Usually just one of those OpenSSL confusions!?]
Jun 30 20:20:00 coova-chilli[13237]: ssl.c: 384: Spurious SSL handshake interrupt [Hint: Usually just one of those OpenSSL confusions!?]
Jun 30 20:20:09 coova-chilli[13250]: ssl.c: 384: Spurious SSL handshake interrupt [Hint: Usually just one of those OpenSSL confusions!?]
Jun 30 20:20:20 coova-chilli[13253]: ssl.c: 384: Spurious SSL handshake interrupt [Hint: Usually just one of those OpenSSL confusions!?]
Jun 30 20:20:22 wlceventd: wlceventd_proc_event(722): wl0.3: Assoc 26:353:02:4B5, status: Successful (0), rssi:-81
Jun 30 20:20:24 coova-chilli[13257]: ssl.c: 384: Spurious SSL handshake interrupt [Hint: Usually just one of those OpenSSL confusions!?]
Jun 30 20:20:30 coova-chilli[13260]: ssl.c: 384: Spurious SSL handshake interrupt [Hint: Usually just one of those OpenSSL confusions!?]
Jun 30 20:20:41 coova-chilli[13265]: ssl.c: 384: Spurious SSL handshake interrupt [Hint: Usually just one of those OpenSSL confusions!?]
Jun 30 20:20:51 coova-chilli[13270]: ssl.c: 384: Spurious SSL handshake interrupt [Hint: Usually just one of those OpenSSL confusions!?]

OE

 

[OzarkEdge]

Just stumbled across this more current firmware for a different model...

ASUS GT-BE98 Pro Firmware version 3.0.0.6.102_34491

Version 3.0.0.6.102_34491
66.99 MB 2024/05/07
New Features:
Introduced AURA Night Mode.
Added Multi-link Operation (MLO) network in Guest Network Pro.
Added automatic WAN/LAN detection feature.
* Please note: After updating to this version, main WiFi encrytpion will be upgraded to GCMP-256 for higher security, please refer to https://www.asus.com/support/faq/1053342/ for more information and setup suggestions.

Bug Fixes and Performance Enhancements:
Enhanced connectivity for WiFi 7 devices.
Fixed client binding issues on AiMesh nodes.
Resolved AiMesh node broadcast issues in Guest Network Pro.
Corrected Link Aggregation UI errors.
Fixed Guest Portal bugs.
Improved AiMesh system stability.
Addressed DNS errors affecting internet access for Guest Network Pro and VPN connections.
Resolved the issues of WireGuard client profile names.
Fixed dual WAN and VLAN 4094 IoT issues.

OE

 

[vit5421]

The ax88u Pro works great, fast and very stable here for all networks including IoT devices with only one strange wifi issue.
The 2.4ghz and 5ghz channels are hard to switch to fixed channels with many attempts and tricks. As long as i able to switch any of them to fixed channel the other is switching to Auto. Its very unusual and i don't know how to fix it if even possible?
Any advice?

 

[Justinh]

The ax88u Pro works great, fast and very stable here for all networks including IoT devices with only one strange wifi issue.
The 2.4ghz and 5ghz channels are hard to switch to fixed channels with many attempts and tricks. As long as i able to switch any of them to fixed channel the other is switching to Auto. Its very unusual and i don't know how to fix it if even possible?
Any advice?

It is a bug in the firmware webpage rendering. If you set a channel and Apply for each band, the channel will be set. When the channel shows Auto, refresh the page (sometimes a hard refresh) and it will show the channel as you set it. You can confirm your settings in System Log > Wireless Log.

Please report this bug to ASUS. If enough users report it maybe they'll fix it.

 

[vit5421]

It is a bug in the firmware webpage rendering. If you set a channel and Apply for each band, the channel will be set. When the channel shows Auto, refresh the page (sometimes a hard refresh) and it will show the channel as you set it. You can confirm your settings in System Log > Wireless Log.

Please report this bug to ASUS. If enough users report it maybe they'll fix it.

Thank you. Refreshing webpage is not helping here but I will report the bug.

 

[Justinh]

Refreshing webpage is not helping here

Do a forced refresh (Shift+refresh button, or Shift+F5/Ctrl+F5).

I will report the bug

Thanks!

 

[vit5421]

Do a forced refresh

It helps for one of wifi band but switching other to Auto. In any case fixed channels are working. Bug report was submitted.
Thanks

 

[bluegrass]

The drop down is present in 388.6_2, and works as advertised. Flash back to stock. full reset, and no drop down.
Am I missing something on the AI Mesh and guest networks? It works on my RT-AX88U running either version of the latest firmware. On the PRO version, network says it is there, active on the node, but will not assign an IP. I turn off guest network to the node in AI Mesh, and it works fine on the primary router.

Well lo and behold the AI Mesh issue was an unfriendly Trendnet 2.5gb switch. Swapped in a TP-Link 2.5gb, everything works. (Outside of manually inputting the dns-over-tls settings. )