Release ASUS RT-AX86U Firmware version 3.0.0.4.386_49447 (2022/06/20)

[Volt]

Well, so much for everything working well... Just tried to copy to/from the USB2 SanDisk thumbdrive formatted with FAT32. Faiiled on both and router GUI locked up.

Very strange. I'm pretty sure that cache itself cannot lock the GUI. For comparison, on my RT-AX56U, which has 512MB of RAM, with the latest firmware installed that has the same cache behavior as the current AX86U firmware (that is, cache is not cleared immediately as it was in the previous firmwares), I often see up to 90% RAM usage after heavy Samba usage that is freed maybe only in a day or two. And I have never experienced any GUI lockups or crashes (and that's after copying some backups that are about 30gigs in size). On the contrary, I find this cache behavior more natural and resulting in better stability.

 

[Tech9]

I’m going to reset it one more time and test with no TrendMicro involvement for cleaner results. Not sure what is causing the hiccups, the new SDK or the 3rd party tools in firmware.

 

[willyburz]

It now aggressively wants to switch away from 160 hertz lock into 80. Ugh.

 

[OzarkEdge]

It now aggressively wants to switch away from 160 hertz lock into 80. Ugh.

Can we know what you are setting for 5.0 bandwidth and control channel?

OE

 

[willyburz]

Locked 36, locked 160

It's changed out of 160 to 80, three times since new update. It only did it once since the January update previously.

 

[bbunge]

I can crash https again and again with transfers to USB stick. There is no better firmware @bbunge. Just different issues. Reports for dnsmasq crashing on Merlin. Also needs fixing, I guess.

I ran 386.7 for a couple of days with Diversion/pixelserv and had no issues other than the RAM going up. Did not have a dnsmasq crash.

 

[OzarkEdge]

Locked 36, locked 160

It's changed out of 160 to 80, three times since new update. It only did it once since the January update previously.

And does it return to 160? If not, try:

5.0 auto, low DFS - 20/40/80/160MHz bw; ch Auto, excluding DFS channels (36-48,149-165)

OE

 

[willyburz]

And does it return to 160? If not, try:

5.0 auto, low DFS - 20/40/80/160MHz bw; ch Auto, excluding DFS channels (36-48,149-165)

OE

No, I have to restart it to kick back. I'll switch to auto on the 20-160 setting and keep 36 locked.

 

[neil0311]

Locked 36, locked 160

It's changed out of 160 to 80, three times since new update. It only did it once since the January update previously.

That was exactly my experience. Why I back rev’d.

 

[willyburz]

That was exactly my experience. Why I back rev’d.

Yah, just checked and it's back to 80 again. Ugh, gonna have to wait til next update now.

 

[OzarkEdge]

Yah, just checked and it's back to 80 again. Ugh, gonna have to wait til next update now.

Now try 20/40/80/160MHz bw; ch Auto, excluding DFS channels.

OE

 

[Tech9]

This firmware version has new wireless drivers and they may detect better DFS channel radio communications. The fact 160MHz used to work before doesn't necessarily mean this firmware is worse. It can be actually better following DFS rules.

 

[Paliv]

This firmware version has new wireless drivers and they may detect better DFS channel radio communications. The fact 160MHz used to work before doesn't necessarily mean this firmware is worse. It can be actually better following DFS rules.

I was thinking the same thing.

 

[OzarkEdge]

This firmware version has new wireless drivers and they may detect better DFS channel radio communications. The fact 160MHz used to work before doesn't necessarily mean this firmware is worse. It can be actually better following DFS rules.

I was thinking the same thing.

I was also thinking we don't know what the firmware does and that several here have reported 'this didn't work, but that does', so why not try that.

OE

 

[willyburz]

It seems too touchy to switch out of 160 to 80 though. Too aggressive.

 

[Jbennett360]

Suppose I'll look at updating the AX86S at some point today

 

[bbunge]

I have gone back to defaults and manually set up with basic settings. Am using WPA2/WPA3-Personal and have enabled DFS. No issues with WIFI and it switches from 80 MHz to 160 MHz and back with no problems. Using DoT to Cloudflare Secure with UPnP off. Not running any Trend Micro. No thumb drive. RAM at 46%

 

[tallytr]

This firmware version has new wireless drivers and they may detect better DFS channel radio communications. The fact 160MHz used to work before doesn't necessarily mean this firmware is worse. It can be actually better following DFS rules.

...my notebook "lost" 160MHz, one day after updating to this firmware...hmmm, re-booted, lets see how long it sticks now... before it was on 160MHz for a couple weeks...darn thing, should just do what I want it to do!

 

[OzarkEdge]

...my notebook "lost" 160MHz, one day after updating to this firmware...hmmm, re-booted, lets see how long it sticks now... before it was on 160MHz for a couple weeks...darn thing, should just do what I want it to do!

I have seen my ax client at 1200Mbs link rate right after waking it up. But it soon climbs to 2400Mbs upon use.

OE

 

[tallytr]

I have seen my ax client at 1200Mbs link rate right after waking it up. But it soon climbs to 2400Mbs upon use.

OE

For me to achieve that I will need to move that airport farther away