[Firmware Bugs] RT-AC87u Firmware 3.0.0.4.378-9383

[binggesoft]

Dec 12 12:54:00 kernel: htb: htb qdisc 17: is non-work-conserving?
Dec 12 12:54:21 kernel: htb: htb qdisc 17: is non-work-conserving?
Dec 12 12:54:56 Aaews: Init fail -989
Dec 12 12:55:00 Mastiff: run aae
Dec 12 12:55:00 Aaews: Init
Dec 12 12:55:28 Aaews: Init fail -989
Dec 12 12:55:30 Mastiff: run aae
Dec 12 12:55:30 Aaews: Init
Dec 12 12:55:31 Aaews: Init fail -989
Dec 12 12:55:40 Mastiff: run aae
Dec 12 12:55:41 Aaews: Init
Dec 12 12:55:53 kernel: htb: htb qdisc 14: is non-work-conserving?
Dec 12 12:56:27 Aaews: Init fail -989
Dec 12 12:56:30 Mastiff: run aae
Dec 12 12:56:31 Aaews: Init
Dec 12 12:56:31 Aaews: Init fail -989
Dec 12 12:56:40 Mastiff: run aae
Dec 12 12:56:41 Aaews: Init
Dec 12 12:57:01 Aaews: Init fail -989
Dec 12 12:57:10 Mastiff: run aae
Dec 12 12:57:11 Aaews: Init
Dec 12 12:57:11 Aaews: Init fail -989
Dec 12 12:57:20 Mastiff: run aae
Dec 12 12:57:21 Aaews: Init
Dec 12 12:57:41 rc_service: httpd 455:notify_rc restart_sendmail
Dec 12 12:57:44 feedback: wan0=[wan], wan1=[lan]
Dec 12 12:58:07 Aaews: Init fail -989
Dec 12 12:58:10 Mastiff: run aae
Dec 12 12:58:11 Aaews: Init
Dec 12 12:58:57 Aaews: Init fail -989
Dec 12 12:59:00 Mastiff: run aae
Dec 12 12:59:02 Aaews: Init
Dec 12 12:59:23 Aaews: Init fail -989
Dec 12 12:59:31 Mastiff: run aae
Dec 12 12:59:31 Aaews: Init
Dec 12 12:59:32 Aaews: Init fail -989
Dec 12 12:59:41 Mastiff: run aae
Dec 12 12:59:41 Aaews: Init
Dec 12 12:59:42 Aaews: Init fail -989
Dec 12 12:59:51 Mastiff: run aae
Dec 12 12:59:52 Aaews: Init
Dec 12 13:00:13 Aaews: Init fail -989
Dec 12 13:00:20 disk_monitor: Got SIGALRM...
Dec 12 13:00:21 Mastiff: run aae
Dec 12 13:00:22 Aaews: Init
Dec 12 13:00:22 Aaews: Init fail -989
Dec 12 13:00:31 Mastiff: run aae
Dec 12 13:00:32 Aaews: Init
Dec 12 13:00:32 Aaews: Init fail -989
Dec 12 13:00:41 Mastiff: run aae
Dec 12 13:00:42 Aaews: Init
Dec 12 13:01:04 Aaews: Init fail -989
Dec 12 13:01:11 Mastiff: run aae
Dec 12 13:01:12 Aaews: Init
Dec 12 13:01:12 Aaews: Init fail -989
Dec 12 13:01:21 Mastiff: run aae
Dec 12 13:01:22 Aaews: Init
Dec 12 13:01:23 Aaews: Init fail -989
Dec 12 13:01:31 Mastiff: run aae
Dec 12 13:01:32 Aaews: Init
Dec 12 13:02:18 Aaews: Init fail -989
Dec 12 13:02:21 Mastiff: run aae
Dec 12 13:02:22 Aaews: Init
Dec 12 13:03:08 Aaews: Init fail -989
Dec 12 13:03:11 Mastiff: run aae
Dec 12 13:03:12 Aaews: Init
Dec 12 13:03:13 Aaews: Init fail -989
Dec 12 13:03:21 Mastiff: run aae
Dec 12 13:03:22 Aaews: Init
Dec 12 13:04:08 Aaews: Init fail -989
Dec 12 13:04:12 Mastiff: run aae
Dec 12 13:04:12 Aaews: Init
Dec 12 13:04:13 Aaews: Init fail -989
I don't know what it is, I don't know when I have a friend!

 

[krum]

Reset to factory defaults and reconfigure,

 

[binggesoft]

Reset to factory defaults and reconfigure,

I have hard reset, and the configuration is also reset, and no CFG recovery is used. Not know what the situation is

 

[ASUS_ASUSWRT]

I have hard reset, and the configuration is also reset, and no CFG recovery is used. Not know what the situation is

Did you install AiCloud? Can you login to AiCloud?
We guess that firewall block you and cause this issue. Thanks

 

[binggesoft]

Did you install AiCloud? Can you login to AiCloud?
We guess that firewall block you and cause this issue. Thanks

Yes, I installed AICLOUD, and turned on the firewall, but 9313 did not appear this kind of situation

 

[ASUS_ASUSWRT]

Yes, I installed AICLOUD, and turned on the firewall, but 9313 did not appear this kind of situation

Can you use AiCloud as normal with 9383?

 

[binggesoft]

Can you use AiCloud as normal with 9383?

I am now relegated to 9313, I do not know how to solve the problem of 9383. So it's important to be stable

 

[vanic]

Hi all,
We have known that, we are proceeding to fix. It's because enabling AiCloud.

Thanks,
Vanic

 

[binggesoft]

Hi all,
We have known that, we are proceeding to fix. It's because enabling AiCloud.

Thanks,
Vanic

Now use 87 to be laughed at! Both of them are BCM chips, with the exception of quantenna using the 87U. Said all the tears

 

[MasterBash]

Im 100% done with this router at this point. I tested it out properly this week and I still get packet loss on 5ghz on all devices. Now to make matters worse, whenever I try to use it in Media Bridge mode, the router reboots and I cant access web gui until I hard reset the router.

This router is gonna give me cancer. This is my second one. I guess I will go for a second replacement. They want me to pay shipping for a replacement... Fine. However, if I do get a bad one again I am definitely going to try to get my full money back for this crap or exchange it for a working one.

 

[VANT]

@MasterBash what packet loss ? You ping some devices and have packet loss ?
Can You explain me ? I will try to reproduce this in my 87u

 

[MasterBash]

I ping an external address using pingplotter and I let it run for a while. It shows packet loss on the AC87U (first hop, 192.168.1.1) all the way to the destination. Online games also freeze.

It only happens with the AC87U. When I use my N66U or R7000 as primary router, I get no packet loss. I was trying to use the AC87U as a Media Bridge today, but I don't know if its because of a firmware or what, but I am unable to do so anymore. It reboots as soon as I try to connect to another router, then I cant access the web gui without hard resetting the router.

I am not sure, but I dont think I had this problem when the AC87U was used as a media bridge. I could be wrong. Some of my devices seem to take a while to get some packet loss to the router, but eventually they all do.

 

[VANT]

hmm... For me when i ping eg. google.com -t sometimes i have one packet loss, but i use 2.4GHz.
I have this same on rt-n66u, but i think that is not router problem but website.
Maybe try ping router (192.168.1.1) and observe.

 

[MasterBash]

The packet loss is at the router level (192.168.1.1) all the way to the destination. Problem with pinging only one hop is that its quite hard to tell if its actually packet loss or the fact that ICMP is often put in low priority or something else... I don't think this is a problem with consumer router, which is why I also pinged 192.168.1.1 and the same thing happened.

 

[fax]

No packet loss whatsoever here pinging 192.168.1.1. Sounds like an issue with the network card driver? Have you tried another system on the same LAN not using the same hardware?

 

[MasterBash]

Yes, I tried 2 laptops, one PC, 2 routers as bridge... I get packet loss on all of them. However, when I use those routers (N66U and R7000) in "Router" mode, none of my devices get packet loss when connected to them. I also tried bridging the N66U to R7000 and vice-versa, no problem.

In fact, when I am going to connect the N66U to the AC87U on 5ghz, I can notice the signal keeps changing from 2 to 5 bars constantly... Only 15ft away with a dry wall, nothing else. I am guessing the low signal is disconnecting my devices (sometimes they disappear briefly in the list of devices, sometimes they dont), which is causing the packet loss.

When I bridge the N66U to R7000, I have no signal problem. Stable. No issue. There are no 5ghz devices in my neighbourhood.

It only happens with the AC87U on 5ghz. 2.4ghz is fine.

 

[scavenger]

I just tried pingplotter and I'm getting a flat line, constant 2ms roundtrip against the router IP from ~35 feet away through a door. What happens if you factory-reset the router, associate with ASUS_5G and ping against that?

If that's clean, then there's some other post-config setting that is interfering with ICMP. If the problem persists, then yes, that does imply there's something basic wrong with it, given that you've got so many different clients that all behave the same.

 

[kdan3388]

Mine is same here. Error package loss! Everything is clean factory settings. Only on 9383 tho

 

[MasterBash]

I just tried pingplotter and I'm getting a flat line, constant 2ms roundtrip against the router IP from ~35 feet away through a door. What happens if you factory-reset the router, associate with ASUS_5G and ping against that?

If that's clean, then there's some other post-config setting that is interfering with ICMP. If the problem persists, then yes, that does imply there's something basic wrong with it, given that you've got so many different clients that all behave the same.

The ping is fine, 2ms constant. However, I did try a factory reset with default SSID and I even tried without any security. Nothing works. However, its not just ICMP, its all packets... League of Legends freezes and I get a "reconnecting" popup, so UDP packets are affected too. Its just packet loss overall, not just ICMP.

I tried ALL Control Channel, Channel Bandwidth and Wireless Mode. Still getting packet loss.

Like I said, 2.4ghz is fine. Its only on 5ghz. This second router does the exact same thing as my first one. I replaced it in-store the first time.

 

[scavenger]

Well, it sounds like you've built up the science. If it's behaving this way at a factory reset with no security, against a wide range of clients using different 5G devices and driver stacks, and only on this firmware and not specific earlier ones, then IMHO the only possible solution is a bad 5GHz chip with a bad operating envelope exposed by the current firmware.

Per that last bit, do you have the router air-cooled? I have a laptop cooler under mine, and it does make a difference. Without it I was much more unstable, but that was many thousands of build numbers ago that I last tried that.