What's new

ASUS RT-AC87U Firmware 3.0.0.4.380.3459

  • 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!

If you're having WAN error/issues after this firmware upgrade, please see this post:

I upgraded to this firmware a few days ago and noticed the same problems discussed here (disconnects, log errors, etc.), but I have good news.

Change to these settings:

WAN / Internet Connection / WAN DNS Setting / Connect to DNS Server automatically :No
- This improved my DNS lookup lag considerably by switching to OpenDNS servers. This had no effect on my disconnection issues however.

WAN / Internet Connection / Special Requirement from ISP / DHCP query frequency: Normal Mode
- This fixed my disconnection problems and cleared up the errors in System Log.

Additional info:
ISP: Comcast
Modem/Router: ARRIS TG862G (Rev. 5) in bridge Mode

It has been working flawlessly for two days now. Do these changes work for any of you?

This was from the AC3200 router firmware thread, but Asus must have introduced something in their latest firmware offering that affected multiple routers. Ever since I upgraded I was having WAN errors that would force me to reboot several times a day. I did a factory reset several times, but it did not fix the problem. I was just about ready to put the router in recovery mode and go back a few versions, but decided to try this and so far it seems to be working. I used GoogleDNS instead of OpenDNS.

Also, the Android app showed the router CPUs maxing out prior to this change, now it seems back to normal.

I am still getting UDP errors and kernel messages:

Jul 2 10:54:03 miniupnpd[3025]: Unknown udp packet received from 192.168.1.50:1900
Jul 2 10:54:03 miniupnpd[3025]: Unknown udp packet received from 192.168.1.50:1900
Jul 2 11:33:59 miniupnpd[3025]: Unknown udp packet received from 192.168.1.50:1900
Jul 2 11:33:59 miniupnpd[3025]: Unknown udp packet received from 192.168.1.50:1900
Jul 2 11:43:58 miniupnpd[3025]: Unknown udp packet received from 192.168.1.50:1900
Jul 2 11:43:58 miniupnpd[3025]: Unknown udp packet received from 192.168.1.50:1900
Jul 2 11:49:26 kernel: * Make sure sizeof(struct sw_struct)=160 is consistent
Jul 2 11:49:27 kernel: sizeof forward param = 160
Jul 2 11:50:33 kernel: Stop the IPS/AppID engine...
Jul 2 11:50:34 rc_service: bwdpi_check 449:notify_rc start_firewall
Jul 2 11:50:34 start_nat_rules: apply the nat_rules(/tmp/nat_rules_eth0_eth0)!
Jul 2 12:03:02 kernel: * Make sure sizeof(struct sw_struct)=160 is consistent
Jul 2 12:03:03 kernel: sizeof forward param = 160
Jul 2 12:03:15 kernel: Stop the IPS/AppID engine...
Jul 2 12:03:16 rc_service: bwdpi_check 449:notify_rc start_firewall
Jul 2 12:03:16 start_nat_rules: apply the nat_rules(/tmp/nat_rules_eth0_eth0)!
Jul 2 12:03:56 miniupnpd[3025]: Unknown udp packet received from 192.168.1.50:1900
Jul 2 12:03:56 miniupnpd[3025]: Unknown udp packet received from 192.168.1.50:1900
Jul 2 12:17:59 kernel: * Make sure sizeof(struct sw_struct)=160 is consistent
Jul 2 12:17:59 kernel: sizeof forward param = 160
Jul 2 12:18:12 kernel: Stop the IPS/AppID engine...
Jul 2 12:18:12 rc_service: bwdpi_check 449:notify_rc start_firewall
Jul 2 12:18:13 start_nat_rules: apply the nat_rules(/tmp/nat_rules_eth0_eth0)!

I am disappointed in Asus after this extremely buggy firmware. For me, this router was rock solid until I put this firmware on it. I would go many months before ever having to reboot. For the most part I only ever rebooted to tweak a setting here or there, or apply new firmware. The cynic in me thinks they purposely don't put enough effort to test firmware on devices older than a year (out of warranty), in hopes that if it is buggy people will just move on to the latest and greatest product.

Here's the whole AC3200 thread:
http://www.snbforums.com/threads/asus-rt-ac3200-firmware-3-0-0-4-380-3479.32906/
 
Nexus 5 keeps disconnecting from ac87u on both 2.4 and 5ghz bands for about 10 seconds and then reconnects. Ac87u is running the latest official firmware. Is this a ac87u problem or a nexus 5 wifi problem?
 
Nexus 5 keeps disconnecting from ac87u on both 2.4 and 5ghz bands for about 10 seconds and then reconnects. Ac87u is running the latest official firmware. Is this a ac87u problem or a nexus 5 wifi problem?

The ac87u doesn't play very nice with Android devices. 5ghz never works properly for me and cuts out often. I find 2.4ghz to be more reliable. Some report increased battery drain. There is supposed to be an antenna firmware problem that is taking forever to get fixed that might improve it.
 
All my android devices work ok with latest fw on both band. No problem with s6, a5, and galaxy tab s
 
Hi everyone.

My Android devices worked fine on 380.3459 however my routers themselves were too unstable. Rebooting several times a day and sometimes completely loosing internet connection completely saying the media connection cable was disconnected however it wasn't.

This evening, I just reverted back to 3.0.0.4.378_9460 using the recovery mode method and restoring the defaults and setting up my routers from scratch again. 378_9460 firmware was fairly solid last time I used it before trying 380.3459 so that's why I went back to this one. The GUI is a little flakey when viewing the client list with the icons and client names but everything else seems OK. So 378_9460 for me.

Asus really needs to get their stuff together and focus on proper firmware for the AC87U instead of these generic firmware versions for multiple routers causing stability issues. I'm getting fed up with this. It's getting really hard to recommend Asus products these days.
 
oh c'mon... using many AC87U features on 380_3459 and it's rock solid for me... Did you clear your settings prior to update and then for sure cleared them once again after the update followed by setting up your router from scratch?
 
oh c'mon... using many AC87U features on 380_3459 and it's rock solid for me... Did you clear your settings prior to update and then for sure cleared them once again after the update followed by setting up your router from scratch?

ankhazam, never seen you post in this thread before and now here you are discounting all the issues people are having. Although I am glad that you are not having issues with 380_3459, are your logs clean as well? What is your system uptime?

After I upgraded to 380_3459 I did restore the router to factory defaults, and then set it up manually. Once. I do this every time I flash new firmware.

C'mon.... Why would you think that restoring to factory defaults twice would be any different than once? Would restoring to factory defaults 3 or 5 times produce different results? Asus does not have this recommendation anywhere in their documentation although it does leave a lot to be desired.
 
I've been using this router for 2 years now, used the stable releases, tested internal firmwares from ASUS and gone over quite a few bugs during this time. The overall observation is that people after FW upgrade don't reset their settings to factory (yeah I know it's a hassle and I know ASUS should code the FW upg so that this step is unnecessary but meh... got tired of fighting for it) and....
people are expecting 5GHz network to work miracles over distance and walls which is simply against physics. I've got a dozen of devices connected fully stable over 2.4GHz and maybe 5 connecting over 5GHz in the same room as the router or the room next to it. Going further from the router is simply asking oneself for trouble, so for 99% of issues reported in these forums the source is one and it is the PEBCAK :)

Now my uptime is over a week but for previous releases e.g. the RT-AC87U_9.0.0.4_380_2695-g1b222cd it was over 2 months.

Best regards,
Ank
 
I've been using this router for 2 years now, used the stable releases, tested internal firmwares from ASUS and gone over quite a few bugs during this time. The overall observation is that people after FW upgrade don't reset their settings to factory (yeah I know it's a hassle and I know ASUS should code the FW upg so that this step is unnecessary but meh... got tired of fighting for it) and....
people are expecting 5GHz network to work miracles over distance and walls which is simply against physics. I've got a dozen of devices connected fully stable over 2.4GHz and maybe 5 connecting over 5GHz in the same room as the router or the room next to it. Going further from the router is simply asking oneself for trouble, so for 99% of issues reported in these forums the source is one and it is the PEBCAK :)

Now my uptime is over a week but for previous releases e.g. the RT-AC87U_9.0.0.4_380_2695-g1b222cd it was over 2 months.

Best regards,
Ank

The factory reset did not help my problems with the latest firmware. Even though changing a few WAN settings that Hard.Wired mentioned helped tremendously, I still had to reboot the router after 8 days because my wired devices were running painfully slow. I also noticed that with the newest firmware my wifi coverage on 2.4 GHz band dropped by about 1/3. I really think I need to get time this weekend and revert back to a previous version.
 
Well the last version dates from September 2016 | Version 3.0.0.4.380.3459 | Any hopes that ASUS will be providing additional version in the near futur? Asus does not seem to be in a hurry to get these "little" issues resolved... I have had this router for a while, and it is causing us a bit of issues... is it time to let it go.....? Opinions.

Or do I use it in its "current state" until the next "Big thing" comes out...? I'm just not sure...
 
WITH this fw i have reboots after 2-3 days....
I Have TA, AIProtection and other AI stuff are on.
I back to 9460 and yesterday i have reboot..... :(
I will try disable TA and will check.
 
go to merlin's latest... stable for at least a month ;)
hehe good joke.....On merlin fw i have reboots day by day.....
I think that is AIProtection bug or related to aiprotection services
 
If you have reboot issues with all these different firmware versions, then there's a chance the problem is your router, not the firmware.
 
maybe, but i read the forum and some people have same problem, so i think that is not a hardware problem.
I will check and use tips from other user like disable TA.
Asus have problems with AIProtections services in 87u even in 382 branch
 
maybe, but i read the forum and some people have same problem, so i think that is not a hardware problem.

You are describing a very, very generic symptom here (router reboot), which can be caused by a lot of different reasons, one of which being hardware issues. And for every user having stability issues, 10 other users have zero stability problem. You can't automatically conclude it's a firmware issue in your specific case because of that, as not everyone is affected by the same root cause.

The 382 branch is using a different Trend Micro engine than the 380 branch BTW.
 
ok RMerlin, but i have observed some specific symptoms
On your latest fw i have restart day by day with uptime less than 24h, on official 3459 fw reboot i have after 2-3 days. 9460 fw have best stability. For now this is my third 87u and all have this same problems, so then i think that is not hardware issue but some specific settings my routers like activated all AIProtecion services, pppoe isp, and etc.... What You think ?
and next questions
cpu_usage.png


cpu usage from top is not related to cpu usage from system status.... Why ?
 

Latest threads

Support SNBForums w/ Amazon

If you'd like to support SNBForums, just use this link and buy anything on Amazon. Thanks!

Sign Up For SNBForums Daily Digest

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