What's new

Release RT-AX88U Firmware version 3.0.0.4.386.45375 2021/08/31

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

This update ruined almost all of my smart home light switches and plugs. They are all on the 2.4 GHz network and all of a sudden they were not getting a stable connection. They would connect and disconnect right away, it was a nightmare trying to troubleshoot this. I eventually found this forum and reverted my router to the previous firmware and just like magic it is now all fixed.
Is there a known issue? I have cell phones, a thermostat, and AV equipment using the 2.4GHz band and so far haven’t noticed an issue.
 
Is there a known issue? I have cell phones, a thermostat, and AV equipment using the 2.4GHz band and so far haven’t noticed an issue.
Not sure, I downloaded the update yesterday morning and I started noticing my issues.
 
Is there a known issue? I have cell phones, a thermostat, and AV equipment using the 2.4GHz band and so far haven’t noticed an issue.
I only noticed issues with 5ghz.
 
Code:
Sep  2 17:05:00 rc_service: service 20000:notify_rc restart_letsencrypt
Sep  2 17:05:00 Let's Encrypt: Err, DDNS update failed.
Sep  2 17:10:00 rc_service: service 20718:notify_rc restart_letsencrypt
Sep  2 17:10:00 Let's Encrypt: Err, DDNS update failed.
Sep  2 17:15:00 rc_service: service 21441:notify_rc restart_letsencrypt
Sep  2 17:15:00 Let's Encrypt: Err, DDNS update failed.

Found my own workaround for the above snap shot of every 5 minutes Let's Encrypt Error in Syslog.
  • I downgraded FW to RT-AX88U_3.0.0.4_386_44266-g7f6b0df
  • Factory Reset Via GUI, setup configuration from scratch
  • No more Let's Encrypt Error in Syslog
  • Upgrade over GUI (ie. Dirty Flash) to FW RT-AX88U_3.0.0.4_386_45375
  • QED ... No more Let's Encrypt Error in Syslog
Sorry,
Spoke too early still getting this message every 5 minutes in Syslog, hope Asus fixed in the next Firmware. This does not happen on Merlin's recent Firmware including 386.3_2
Code:
Sep  9 21:00:00 rc_service: service 5386:notify_rc restart_letsencrypt
Sep  9 21:00:01 Let's Encrypt: Err, DDNS update failed.
 
I've been experiencing drops in my 5ghz wireless since flashing this, anyone else?
I just ran iperf3 and my numbers dropped from 700Mbs to 400Mbps. I am rounding up.

Edit:
5G AX
Accepted connection from 192.168.50.62, port 57976
[ 5] local 192.168.50.1 port 5201 connected to 192.168.50.62 port 57978
[ ID] Interval Transfer Bandwidth
[ 5] 0.00-1.00 sec 32.2 MBytes 270 Mbits/sec
[ 5] 1.00-2.00 sec 42.2 MBytes 354 Mbits/sec
[ 5] 2.00-3.00 sec 37.3 MBytes 313 Mbits/sec
[ 5] 3.00-4.00 sec 40.5 MBytes 341 Mbits/sec
[ 5] 4.00-5.00 sec 42.5 MBytes 356 Mbits/sec
[ 5] 5.00-6.00 sec 38.1 MBytes 320 Mbits/sec
[ 5] 6.00-7.00 sec 38.6 MBytes 323 Mbits/sec
[ 5] 7.00-8.00 sec 40.0 MBytes 335 Mbits/sec
[ 5] 8.00-9.00 sec 46.0 MBytes 386 Mbits/sec
[ 5] 9.00-10.00 sec 46.1 MBytes 386 Mbits/sec
[ 5] 10.00-10.02 sec 1.32 MBytes 458 Mbits/sec
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bandwidth
[ 5] 0.00-10.02 sec 0.00 Bytes 0.00 bits/sec sender
[ 5] 0.00-10.02 sec 405 MBytes 339 Mbits/sec receiver

Wired is good:

┌──(rootByteEnable)─[/home/ByteEnable]
└─# iperf3 -c 192.168.50.1
Connecting to host 192.168.50.1, port 5201
[ 5] local 192.168.50.83 port 58360 connected to 192.168.50.1 port 5201
[ ID] Interval Transfer Bitrate Retr Cwnd
[ 5] 0.00-1.00 sec 102 MBytes 858 Mbits/sec 221 428 KBytes
[ 5] 1.00-2.00 sec 111 MBytes 933 Mbits/sec 0 437 KBytes
[ 5] 2.00-3.00 sec 112 MBytes 944 Mbits/sec 0 454 KBytes
[ 5] 3.00-4.00 sec 112 MBytes 944 Mbits/sec 0 464 KBytes
[ 5] 4.00-5.00 sec 111 MBytes 933 Mbits/sec 0 472 KBytes
[ 5] 5.00-6.00 sec 112 MBytes 944 Mbits/sec 0 472 KBytes
[ 5] 6.00-7.00 sec 112 MBytes 944 Mbits/sec 0 472 KBytes
[ 5] 7.00-8.00 sec 110 MBytes 923 Mbits/sec 0 484 KBytes
[ 5] 8.00-9.00 sec 106 MBytes 891 Mbits/sec 0 485 KBytes
[ 5] 9.00-10.00 sec 112 MBytes 944 Mbits/sec 0 499 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-10.00 sec 1.08 GBytes 926 Mbits/sec 221 sender
[ 5] 0.00-10.00 sec 1.07 GBytes 923 Mbits/sec receiver
 
Last edited:
funny, I have AX86u, installed this same version and my 2.4ghz kept losing connections like once or twice a day. My nest doorbell would lose connectivity for 10+ minutes but then will eventually reconnect.

Still haven't figured out whats causing it. I seperate 2.4ghz/5ghz access points too.

I think there's definitely something wrong with this firmware version though.
 
Same issue, some of the appliances lost the 2.4. It's really annoying, one of them reconnected fine but the other one is losing connection after x hours...
 
funny, I have AX86u, installed this same version and my 2.4ghz kept losing connections like once or twice a day. My nest doorbell would lose connectivity for 10+ minutes but then will eventually reconnect.

Still haven't figured out whats causing it. I seperate 2.4ghz/5ghz access points too.

I think there's definitely something wrong with this firmware version though.

Personally don't think this is necessarily connected to this specific firmware as I had many issues with previous upgrades in the past. Depends on your configuration an how you upgrade...
I have zero issues just some weird log messages both bands are rock solid, that is RT-AX86U.
 
i don't agree, i upgraded to the newest fw after seeing this thread, i went to check my devices and 2 of them lost connection to the 2.4. It worked for more than a year before this
 
Personally don't think this is necessarily connected to this specific firmware as I had many issues with previous upgrades in the past. Depends on your configuration an how you upgrade...
I have zero issues just some weird log messages both bands are rock solid, that is RT-AX86U.
100% it is the firmware.

I updated firmware, right after reboot of the router, 2.4ghz couldn't be connected.

I did factory reset, everything is back to normal. 1 day after, 2.4ghz connection could not be connected again. When my devices try to connect, it fails.

I rolled back my firmware, has been stable for 1 week now.

Definitely something's wrong with the firmware.
 
The thing is that most likely the vast majority who upgraded have no issues...
If I were you I would of course stay on the previous firmware but also consider completely starting from new, clear NVRAM... set up router from new....
 
it's not because a vast majority has no issues that there is no symptoms. The fact that we can reproduce the bugs on a similar environment -or almost is relevant enough, it's just not a coincidence and this is extremely typical of software development.
I'm interested though in how clear nvram. Any good tutorial?

Thanks!
 
100% it is the firmware.

Definitely something's wrong with the firmware.

Maybe in combination with a specific configuration or devices. I’m not having a single issue.

My own cell phone (one of several devices) is connected to the 2.4 GHz network and has been rock solid.
 
Maybe in combination with a specific configuration or devices. I’m not having a single issue.

My own cell phone (one of several devices) is connected to the 2.4 GHz network and has been rock solid.

How about your System Log? My log is bad, before it was empty and now tons of messages... router works great though...
Log Level 5.
 
Getting spammed for No-IP DDNS in log

Sep 26 12:36:02 rc_service: watchdog 1347:notify_rc start_ddns
Sep 26 12:36:02 start_ddns: update WWW.NO-IP.COM default@no-ip.com, wan_unit 0
Sep 26 12:36:02 inadyn[18978]: In-a-dyn version 2.8.1 -- Dynamic DNS update client.
Sep 26 12:36:32 watchdog: start ddns.
Sep 26 12:36:32 rc_service: watchdog 1347:notify_rc start_ddns
Sep 26 12:36:32 start_ddns: update WWW.NO-IP.COM default@no-ip.com, wan_unit 0
Sep 26 12:36:32 inadyn[19023]: In-a-dyn version 2.8.1 -- Dynamic DNS update client.
Sep 26 12:37:02 watchdog: start ddns.
Sep 26 12:37:02 rc_service: watchdog 1347:notify_rc start_ddns
Sep 26 12:37:02 start_ddns: update WWW.NO-IP.COM default@no-ip.com, wan_unit 0
Sep 26 12:37:02 inadyn[19087]: In-a-dyn version 2.8.1 -- Dynamic DNS update client.
Sep 26 12:37:32 watchdog: start ddns.
Sep 26 12:37:32 rc_service: watchdog 1347:notify_rc start_ddns
Sep 26 12:37:32 start_ddns: update WWW.NO-IP.COM default@no-ip.com, wan_unit 0
Sep 26 12:37:32 inadyn[19133]: In-a-dyn version 2.8.1 -- Dynamic DNS update client.

I also get a yellow exclamation mark in front of DDNS name on main page.
 
100% it is the firmware.

I updated firmware, right after reboot of the router, 2.4ghz couldn't be connected.

I did factory reset, everything is back to normal. 1 day after, 2.4ghz connection could not be connected again. When my devices try to connect, it fails.

I rolled back my firmware, has been stable for 1 week now.

Definitely something's wrong with the firmware.
Did you find the solution for this? My 2.4 network has been dropping and not allowing some of my smart home devices to connect.
 
This update sucks! Went back to the previous. Nothing works. Nothing connects. Always shows the internet is not connected! COME on. Does anybody check this shirt before they publish it. If nothing connects, Then we do not have to worry about SECURITY!
This update ruined almost all of my smart home light switches and plugs. They are all on the 2.4 GHz network and all of a sudden they were not getting a stable connection. They would connect and disconnect right away, it was a nightmare trying to troubleshoot this. I eventually found this forum and reverted my router to the previous firmware and just like magic it is now all fixed.
Mine also!! Nothing connects!
 

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top