Release Asus RT-AX86 Series Firmware version 3.0.0.4.388_24231 (11/07/2023)

[kev2022]

Hi all,
I have a RT-AX86U and I'm considering updating to latest firmware but I also have some of the Kasa/TP link smart plugs and I'm wondering if these are still causing a issue after updating? I only have the RT-AX86U, no AIMesh etc and I have them all on a separate guest network with no access to main network, been setup this way for a while. Been waiting on a update to this for a while but not heard anything and this is only think holding me back on doing the update.
Thanks for any update.
Kev

 

[ryan806]

Hi all,
I have a RT-AX86U and I'm considering updating to latest firmware but I also have some of the Kasa/TP link smart plugs and I'm wondering if these are still causing a issue after updating? I only have the RT-AX86U, no AIMesh etc and I have them all on a separate guest network with no access to main network, been setup this way for a while. Been waiting on a update to this for a while but not heard anything and this is only think holding me back on doing the update.
Thanks for any update.
Kev

I would like to know this also

 

[Tech9]

I would like to know this also

Save your configuration, upgrade the firmware - test. If not good - downgrade the firmware, reset, upload your saved configuration, wait for a new firmware.

 

[dgt02]

You didn't specify if you were also using AIMesh vs a single router with this issue. In the past I've had quite a bit of trouble with my Wiz bulbs disconnecting on any router. The fix for me was to put the bulbs on their own 2.4GHZ guest with intranet access disabled so there was no interaction between the guest and main network(s). Maybe try that with your plugs, if you haven't already. Also I have a couple of amazon smart plugs, and they function normally on the main 2.4ghz network. It was only the bulbs which seem to need their own network.

I haven't tried any Kasa products, just TP-Link routers.

Thank you iFrogMac. This occurred before I recently added a node and started using aimesh. I reported this problem to ASUS this morning using the Feedback tab in the Administration function of the RT-AX86U as I did not see any new firmware since November which introduced the bug. In the past, I have waited for new firmware and it always fixed bugs that were introduced by new versions. I hope others are reporting this problem so ASUS fixes this bug.

 

[dgt02]

Save your configuration, upgrade the firmware - test. If not good - downgrade the firmware, reset, upload your saved configuration, wait for a new firmware.

Thanks - that's what I did and have done for years when finding bugs. I usually don't have to re-apply or restore settings, even when downgrading

 

[RSengine]

Something extremely strange has happened while on this firmware. I upgraded probably a month ago and reset my all my VPN keys a month ago.

Today, all of a sudden, I find myself unable to connect via VPN and my router-side OpenVPN keys and Wireguard keys have been completely reset and the Port Forwarding settings were completely wiped out. Everything else remains the same (SSID, Wifi passwords, admin password) as far as I can tell. Router is still locked from WAN side.

I live alone so it’s not someone else in the household.

I have no idea what caused this, but I’m thinking
- Hackers? But it would be strange for them to remove my port forwarding settings. If anything, they would want to open more floodgates
- Cosmic rays? But again, strange that my SSID and Wifi passwords and admin password are unaffected
- A rather unpleasant bug in this firmware?

I have never seen this type of behavior before on Asus stock firmware. Not sure if anyone else has experienced this. Maybe I need to wipe the NVRAM and start fresh.

 

[iFrogMac]

Something extremely strange has happened while on this firmware. I upgraded probably a month ago and reset my all my VPN keys a month ago.

Today, all of a sudden, I find myself unable to connect via VPN and my router-side OpenVPN keys and Wireguard keys have been completely reset and the Port Forwarding settings were completely wiped out. Everything else remains the same (SSID, Wifi passwords, admin password) as far as I can tell. Router is still locked from WAN side.

I live alone so it’s not someone else in the household.

I have no idea what caused this, but I’m thinking
- Hackers? But it would be strange for them to remove my port forwarding settings. If anything, they would want to open more floodgates
- Cosmic rays? But again, strange that my SSID and Wifi passwords and admin password are unaffected
- A rather unpleasant bug in this firmware?

I have never seen this type of behavior before on Asus stock firmware. Not sure if anyone else has experienced this. Maybe I need to wipe the NVRAM and start fresh.

I was going to mention the possibility of corrupt storage / ram. Maybe the router's storage needs to be cleaned, or you had some corruption. Maybe try a factory reset, and clean setup.

 

[RSengine]

I was going to mention the possibility of corrupt storage / ram. Maybe the router's storage needs to be cleaned, or you had some corruption. Maybe try a factory reset, and clean setup.

Yea. I think I'll just wipe it and start fresh. Hopefully, that solves it. Very strange

 

[John Fitzgerald]

Yea. I think I'll just wipe it and start fresh. Hopefully, that solves it. Very strange

Before you wipe and reset,
Pull the power while it is on, wait 1 minute, and put the barrel plug end back in for a clean boot.
Also see here:

CVE-2024-31497: PuTTY vulnerability vuln-p521-bias

Every version of the PuTTY tools from 0.68 to 0.80 inclusive has a critical vulnerability in the code that generates signatures from ECDSA private keys which use the NIST P521 curve. (PuTTY, or Pageant, generates a signature from a key when using it to authenticate you to an SSH server.)...

www.snbforums.com

 

[Wayne]

I will skip this and wait for the newer one.

 

[Tech9]

will skip this and wait for the newer one.

You are skipping this for >5 months already, no?

 

[Wayne]

You are skipping this for >5 months already, no?

Yes, the recent release for the AX88 and AC68 firmware is good! I’m waiting for the AX86 version.

 

[Jbennett360]

Yes, the recent release for the AX88 and AC68 firmware is good! I’m waiting for the AX86 version.

Eh?

Totally different routers

 

[Wayne]

Eh?

Totally different routers

Similar bersion of firmware though.

 

[iFrogMac]

Similar bersion of firmware though.

A few weeks ago I read through this thread: https://www.snbforums.com/threads/rt-ac68u-end-of-life-announced-by-asus.89314/
People seemed to be suggesting the RT-AX86U was end of life there. I checked the list from Asus myself, and that particular model isn't listed as EOL, I haven't heard anything officially specific to the model. So, hopefully there will be more updates for it. It has been a while though.

 

[Tech9]

People seemed to be suggesting the RT-AX86U was end of life there.

Where exactly? RT-AC86U and RT-AX68U are EoL.

 

[iFrogMac]

Where exactly? RT-AC86U and RT-AX68U are EoL.

Well, it was you who said it, and it's possible I mixed up the 6 and 8. Yes the AX68U is on the list, but it looked like the 86U was also mentioned. Sorry if I read it wrong, or if there was a typo that is now corrected on that thread.

 

[Tech9]

Well, it was you who said it, and it's possible I mixed up the 6 and 8.

Look again:

Also, as expected:

RT-AC86U
GT-AC2900
RT-AX68U

 

[iFrogMac]

Look again:

OK, yeah that' what happened, I mixed up the 6 and 8. I mixed up the numbers in your post about the AX68U post about having under 4 years of support and then EOL'd. Sorry about that.

 

[Tech9]

I expect firmware update soon. Other models were updated already. Asus discovered something off around AiMesh.

From other models recent firmware update changelog:

*Please be advised that due to a security upgrade in AiMesh, we strongly recommend against downgrading to previous firmware versions, as this may lead to connection issues. Should you encounter any difficulties, resetting the AiMesh router to its default settings and re-establishing the mesh connection can resolve the problem.