Release ASUS RT-AX86 Series (RT-AX86U/RT-AX86S) Firmware version 3.0.0.4.388_24338 (2025/03/25)

[Tech9]

However the traffic itself to the WPA3 clients should be executed differently in mixed-mode.

In theory - yes. In reality - it creates issues quite often. Not only in Asus world, but with other equipment as well. Ubiquiti Community Forum is also full of transitional/mixed mode negative experience. Good idea, bit doesn't work as intended with currently existing and popular clients. Issues with a single client ruin the experience. I don't use it for another reason - my network-wide single SSID carries few different VLANs with private pre-shared keys. This works with WPA2 only.

 

[ho_kuku]

Updated mine (via dirty online update) - ax86u main and mesh node - wired backhaul. Mesh node started having problems 2 days later. Connection to node will drop randomly and after that - degrade to 100mbps. Factory resetted both main router and node - works ok now.

 

[iFrogMac]

@Tech9 got my RT-AX86U update, didn't have to take the network down, or change anything. I just disabled the iMac's built in Ethernet, connected a USB to Ethernet dongle and then connected to a LAN port of the 86U (after downloading the firmware first). Flashed router, saw it was up to date, disconnected everything and re-enabled built in Ethernet. Now computer is back online, and RT-AX86U is up to date and ready to be used in case of a backup situation.

 

[Tech9]

I just disabled the iMac's built in Ethernet, connected a USB to Ethernet dongle

You could use the built-in NIC. Additional USB-to-Ethernet dongle is not needed.

 

[iFrogMac]

You could use the built-in NIC. Additional USB-to-Ethernet dongle is not needed.

I should have mentioned that, I could have used the built in, but it's a pain to get behind the iMac in this cubby stye setup, so I made it easier and just disabled the built in port in the OS and connect the dongle to the hub. So, in this case this was just the easier way to do it, not that I had to do it this way.

 

[Dick_W]

Edit to update: Scratch this--the third browser page refresh seems to have made the UI return to normal. Go figure.

It's still not working with some clients but working with others. Back to work I go…

Version 3.0.0.4.388_24338
71.55 MB
2025/03/25

Is it just me? Post this install, here's the UI the router presents for VPN Server:

That just doesn't seem right.

The underlying VPN Server is still working for some of my platforms. At the moment, it's not working for others. I think that might because both Windows and ChromeOS somehow don't like that I'm testing the VPN connection from LAN side not WAN. But tethering through my phone to come in on the WAN side didn't work either. I'd check to make sure the VPS Server is setup the way I think it is, but, well, see above.

 

[jksmurf]

Is it just me? Post this install, here's the UI the router presents for VPN Server:
View attachment 65096

That just doesn't seem right.

The underlying VPN Server is still working for some of my platforms. At the moment, it's not working for others. I think that might because both Windows and ChromeOS somehow don't like that I'm testing the VPN connection from LAN side not WAN. But tethering through my phone to come in on the WAN side didn't work either. I'd check to make sure the VPS Server is setup the way I think it is, but, well, see above.

This might be way off base, but are sure that's not just an issue with the Browser that can be remedied by flushing the browser cache / a browser refresh ?
It looks like what I saw sometimes after a new FW flash. Perhaps try that first?

 

[RMerlin]

Edit to update: Scratch this--the third browser page refresh seems to have made the UI return to normal. Go figure.

It's an old Chrome bug where Chrome will randomly fail to load various components of a webpage when using a self-signed certificate. Accessing over HTTP, or using a different browser is the only known workaround.