If you're having WAN error/issues after this firmware upgrade, please see this post:
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/
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/