ASUS RT-AC3200 Firmware version 3.0.0.4.380.3479

[Hard.Wired]

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?

 

[zoomee]

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.

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

First change defo improved web browsing performance but I notice my PING is double what it usually is.

Second changed crashed the router - rebooted, and seems to be working ok for now - will report back if any more errors in logs, thanks.

I think this must be the worst performing firmware I have seen so far on this product.

 

[zoomee]

22hrs since making the change above - logs:

Jun 18 13:16:45 rc_service: ntp 719:notify_rc restart_upnp
Jun 18 13:16:45 miniupnpd[716]: shutting down MiniUPnPd
Jun 18 13:16:45 miniupnpd[726]: version 1.9 started
Jun 18 13:16:45 miniupnpd[726]: HTTP listening on port 35070
Jun 18 13:16:45 miniupnpd[726]: Listening for NAT-PMP/PCP traffic on port 5351
Jun 18 13:16:46 rc_service: ntp 719:notify_rc restart_diskmon
Jun 18 13:16:46 disk_monitor: Finish
Jun 18 13:16:47 kernel: * Make sure sizeof(struct sw_struct)=160 is consistent
Jun 18 13:16:47 disk monitor: be idle
Jun 18 13:16:48 kernel: sizeof forward param = 160
Jun 18 13:16:50 rc_service: udhcpc 545:notify_rc start_firewall
Jun 18 13:16:50 dhcp client: bound 82.29.183.41 via 82.29.183.1 during 398758 seconds.
Jun 18 13:16:52 miniupnpd[726]: add_filter_rule() : chain FUPNP not found
Jun 18 13:16:52 miniupnpd[726]: Failed to redirect 8001 -> 192.168.1.103:8000 protocol TCP
Jun 18 13:16:52 start_nat_rules: apply the nat_rules(/tmp/nat_rules_eth0_eth0)!
Jun 18 13:16:52 rc_service: udhcpc 803:notify_rc start_firewall
Jun 18 13:16:52 rc_service: waitting "start_firewall" via ...
Jun 18 13:16:52 WAN Connection: ISP's DHCP did not function properly.
Jun 18 13:16:52 DualWAN: skip single wan wan_led_control - WANRED off
Jun 18 13:16:52 miniupnpd[726]: add_filter_rule() : chain FUPNP not found
Jun 18 13:16:52 miniupnpd[726]: Failed to redirect 30816 -> 192.168.1.103:80 protocol TCP
Jun 18 13:16:52 miniupnpd[726]: add_filter_rule() : chain FUPNP not found
Jun 18 13:16:52 miniupnpd[726]: Failed to redirect 34846 -> 192.168.1.103:554 protocol TCP
Jun 18 13:16:52 miniupnpd[726]: add_filter_rule() : chain FUPNP not found
Jun 18 13:16:52 miniupnpd[726]: Failed to redirect 9011 -> 192.168.1.103:9010 protocol TCP
Jun 18 13:16:52 miniupnpd[726]: add_filter_rule() : chain FUPNP not found
Jun 18 13:16:52 miniupnpd[726]: Failed to redirect 9021 -> 192.168.1.103:9020 protocol TCP
Jun 18 13:16:52 miniupnpd[726]: add_filter_rule() : chain FUPNP not found
Jun 18 13:16:52 miniupnpd[726]: Failed to redirect 8200 -> 192.168.1.103:8200 protocol TCP
Jun 18 13:16:52 miniupnpd[726]: add_filter_rule() : chain FUPNP not found
Jun 18 13:16:52 miniupnpd[726]: Failed to redirect 8001 -> 192.168.1.103:8000 protocol TCP
Jun 18 13:16:52 miniupnpd[726]: add_filter_rule() : chain FUPNP not found
Jun 18 13:16:52 miniupnpd[726]: Failed to redirect 30816 -> 192.168.1.103:80 protocol TCP
Jun 18 13:16:52 miniupnpd[726]: add_filter_rule() : chain FUPNP not found
Jun 18 13:16:52 miniupnpd[726]: Failed to redirect 34846 -> 192.168.1.103:554 protocol TCP
Jun 18 13:16:52 miniupnpd[726]: add_filter_rule() : chain FUPNP not found
Jun 18 13:16:52 miniupnpd[726]: Failed to redirect 9011 -> 192.168.1.103:9010 protocol TCP
Jun 18 13:16:52 miniupnpd[726]: add_filter_rule() : chain FUPNP not found
Jun 18 13:16:52 miniupnpd[726]: Failed to redirect 9021 -> 192.168.1.103:9020 protocol TCP
Jun 18 13:16:52 miniupnpd[726]: add_filter_rule() : chain FUPNP not found
Jun 18 13:16:52 miniupnpd[726]: Failed to redirect 8200 -> 192.168.1.103:8200 protocol TCP
Jun 18 13:16:52 miniupnpd[726]: add_filter_rule() : chain FUPNP not found
Jun 18 13:16:52 miniupnpd[726]: Failed to redirect 8001 -> 192.168.1.103:8000 protocol TCP
Jun 18 13:16:52 miniupnpd[726]: add_filter_rule() : chain FUPNP not found
Jun 18 13:16:52 miniupnpd[726]: Failed to redirect 30816 -> 192.168.1.103:80 protocol TCP
Jun 18 13:16:52 miniupnpd[726]: add_filter_rule() : chain FUPNP not found
Jun 18 13:16:52 miniupnpd[726]: Failed to redirect 34846 -> 192.168.1.103:554 protocol TCP
Jun 18 13:16:52 miniupnpd[726]: add_filter_rule() : chain FUPNP not found
Jun 18 13:16:52 miniupnpd[726]: Failed to redirect 9011 -> 192.168.1.103:9010 protocol TCP
Jun 18 13:16:52 miniupnpd[726]: add_filter_rule() : chain FUPNP not found
Jun 18 13:16:52 miniupnpd[726]: Failed to redirect 9021 -> 192.168.1.103:9020 protocol TCP
Jun 18 13:16:52 stop_nat_rules: apply the redirect_rules!
Jun 18 13:16:52 miniupnpd[726]: add_filter_rule() : chain FUPNP not found
Jun 18 13:16:52 miniupnpd[726]: Failed to redirect 8200 -> 192.168.1.103:8200 protocol TCP
Jun 18 13:16:52 miniupnpd[726]: add_filter_rule() : chain FUPNP not found
Jun 18 13:16:52 miniupnpd[726]: Failed to redirect 8001 -> 192.168.1.103:8000 protocol TCP
Jun 18 13:16:52 miniupnpd[726]: add_filter_rule() : chain FUPNP not found
Jun 18 13:16:52 miniupnpd[726]: Failed to redirect 30816 -> 192.168.1.103:80 protocol TCP
Jun 18 13:16:52 miniupnpd[726]: add_filter_rule() : chain FUPNP not found
Jun 18 13:16:52 miniupnpd[726]: Failed to redirect 34846 -> 192.168.1.103:554 protocol TCP
Jun 18 13:16:52 miniupnpd[726]: add_filter_rule() : chain FUPNP not found
Jun 18 13:16:52 miniupnpd[726]: Failed to redirect 9011 -> 192.168.1.103:9010 protocol TCP
Jun 18 13:16:52 miniupnpd[726]: add_filter_rule() : chain FUPNP not found
Jun 18 13:16:52 miniupnpd[726]: Failed to redirect 9021 -> 192.168.1.103:9020 protocol TCP
Jun 18 13:16:52 miniupnpd[726]: add_filter_rule() : chain FUPNP not found
Jun 18 13:16:52 miniupnpd[726]: Failed to redirect 8200 -> 192.168.1.103:8200 protocol TCP
Jun 18 13:16:53 start_nat_rules: apply the nat_rules(/tmp/nat_rules_eth0_eth0)!
Jun 18 13:16:54 wan: finish adding multi routes
Jun 18 13:16:54 rc_service: udhcpc 803:notify_rc stop_upnp
Jun 18 13:16:54 rc_service: waitting "start_firewall" via udhcpc ...
Jun 18 13:16:55 rc_service: udhcpc 803:notify_rc start_upnp
Jun 18 13:16:55 rc_service: waitting "stop_upnp" via udhcpc ...
Jun 18 13:16:55 miniupnpd[726]: shutting down MiniUPnPd
Jun 18 13:16:56 ddns update: ez-ipupdate: starting...
Jun 18 13:16:56 miniupnpd[866]: version 1.9 started
Jun 18 13:16:56 miniupnpd[866]: HTTP listening on port 47698
Jun 18 13:16:56 miniupnpd[866]: Listening for NAT-PMP/PCP traffic on port 5351
Jun 18 13:16:57 ddns update: connected to nwsrv-ns1.asus.com (103.10.4.108) on port 80.
Jun 18 13:16:57 ddns update: Asus update entry:: return: HTTP/1.1 200 OK^M Date: Sat, 18 Jun 2016 12:16:55 GMT^M Server: Apache^M Content-Length: 0^M Connection: close^M Content-Type: text/html^M ^M
Jun 18 13:16:57 ddns update: retval= 0, ddns_return_code (,200)
Jun 18 13:16:57 ddns update: asusddns_update: 0
Jun 18 13:16:58 ddns: ddns update ok
Jun 18 13:16:59 WAN Connection: WAN was restored.
Jun 18 13:17:02 rc_service: udhcpc 803:notify_rc start_firewall
Jun 18 13:17:02 dhcp client: bound 82.29.183.41 via 82.29.183.1 during 398739 seconds.
Jun 18 13:17:03 start_nat_rules: apply the nat_rules(/tmp/nat_rules_eth0_eth0)!
Jun 18 13:17:16 crond[476]: time disparity of 464416 minutes detected
Jun 18 13:18:34 hour monitor: ntp sync fail, will retry after 120 sec
Jun 18 14:00:47 disk_monitor: Got SIGALRM...
Jun 18 20:17:19 miniupnpd[866]: upnp_event_recv: recv(): Connection reset by peer
Jun 18 23:00:47 disk_monitor: Got SIGALRM...
Jun 19 09:47:52 miniupnpd[866]: HTTP Connection from 192.168.1.23 closed unexpectedly

 

[Hard.Wired]

Zoomee: Yikes! That is bizarre. What make/model/version is your modem (not router)? Have you ever logged into that to play with its settings?

 

[zoomee]

Zoomee: Yikes! That is bizarre. What make/model/version is your modem (not router)? Have you ever logged into that to play with its settings?

I'm using a standard UK Virgin Media Superhub 3 router/modem set to modem only mode. There isn't any settings I can change from this side other than to place it in router or modem mode.

Not sure what all them errors are about tbh - 192.168.1.103 is one of the Hikvision IP cameras I have but never seen errors like that before in the logs!

 

[zoomee]

Uptime 5 days 23 hours:

Jun 19 12:33:14 miniupnpd[866]: upnp_event_recv: recv(): Connection reset by peer
Jun 20 16:54:36 miniupnpd[866]: upnp_event_recv: recv(): Connection reset by peer
Jun 21 10:46:06 miniupnpd[866]: upnp_event_recv: recv(): Connection reset by peer
Jun 21 10:48:56 miniupnpd[866]: upnp_event_process_notify: connect(192.168.1.128:2869): Connection timed out
Jun 21 13:44:11 miniupnpd[866]: upnp_event_recv: recv(): Connection reset by peer
Jun 21 16:23:53 miniupnpd[866]: upnp_event_process_notify: connect(192.168.1.82:2869): Connection timed out
Jun 22 16:23:38 miniupnpd[866]: upnp_event_process_notify: connect(192.168.1.82:2869): Connection timed out
Jun 23 12:13:56 miniupnpd[866]: upnp_event_recv: recv(): Connection reset by peer
Jun 23 12:32:44 miniupnpd[866]: upnp_event_process_notify: connect(192.168.1.128:2869): Connection timed out


No idea whats going on with all this upnp stuff.!

 

[RMerlin]

Uptime 5 days 23 hours:

Jun 19 12:33:14 miniupnpd[866]: upnp_event_recv: recv(): Connection reset by peer
Jun 20 16:54:36 miniupnpd[866]: upnp_event_recv: recv(): Connection reset by peer
Jun 21 10:46:06 miniupnpd[866]: upnp_event_recv: recv(): Connection reset by peer
Jun 21 10:48:56 miniupnpd[866]: upnp_event_process_notify: connect(192.168.1.128:2869): Connection timed out
Jun 21 13:44:11 miniupnpd[866]: upnp_event_recv: recv(): Connection reset by peer
Jun 21 16:23:53 miniupnpd[866]: upnp_event_process_notify: connect(192.168.1.82:2869): Connection timed out
Jun 22 16:23:38 miniupnpd[866]: upnp_event_process_notify: connect(192.168.1.82:2869): Connection timed out
Jun 23 12:13:56 miniupnpd[866]: upnp_event_recv: recv(): Connection reset by peer
Jun 23 12:32:44 miniupnpd[866]: upnp_event_process_notify: connect(192.168.1.128:2869): Connection timed out


No idea whats going on with all this upnp stuff.!

It simply indicates that an application forwarded a port through UPNP, then that application was closed, leaving a forwarded port pointing at nothing.

It's not an error message, but a warning just ignore it.

 

[zoomee]

Thanks RMerlin - .128 and .82 are both Windows 10 based PC's - wierd that they would both be trying to do the same thing as they are used for different purposes (.128 is a gaming pc, whereas .82 is a basic web browser).

Never had these warnings before in any of the logs of this or previous Asus routers.

 

[kdawg]

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?

Thank you. I believe this has helped my problem! I have an RT-AC87U, but after the firmware upgrade earlier in the month, I was having similar WAN issues. I also noticed that on the Android app, that 1/2 CPUs was pegged at 100%. Even after a reboot, it would go right back to maxing out. I was rebooting my modem (SB6141) and router several times a day.

I made the changes last night, and so far all seems to be working good. I changed to GoogleDNS instead of OpenDNS, but so far no WAN errors in the log. CPU(s) utilization seems to be back to normal. I still get plenty of the UDP warnings, and this kernel entries just popped up a few minutes ago, so I haven't looked too closely into those yet:

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

Thanks for the help on the WAN issues. I am going to post this over on AC87U forum for this firmware.


If anyone from Asus reads this -- your support sucks. I opened up two tickets and got a canned response that had nothing to do with my issue. When I responded to the support person via email I got no response back. It was a complete waste of time. You managed to screw something up across multiple routers with your latest firmware upgrade. You need to make sure your support team is aware, and develop a fix for this. I am going to be very reluctant to upgrade this firmware in the future (assuming this is finally stable with these settings).

 

[zoomee]

snip

If anyone from Asus reads this -- your support sucks. I opened up two tickets and got a canned response that had nothing to do with my issue. When I responded to the support person via email I got no response back. It was a complete waste of time. You managed to screw something up across multiple routers with your latest firmware upgrade. You need to make sure your support team is aware, and develop a fix for this. I am going to be very reluctant to upgrade this firmware in the future (assuming this is finally stable with these settings).

I have to fully agree here. They finally managed to get the firmware for this router to some form of stability without having to lose functionality and then they go and completely screw it up with this silly change.
Back to square one - waiting 2 months for them to get off their butts and give me a product that actually does what it says on the tin. It really is pathetic levels of support for this router.

 

[just a has been]

I have to fully agree here. They finally managed to get the firmware for this router to some form of stability without having to lose functionality and then they go and completely screw it up with this silly change.
Back to square one - waiting 2 months for them to get off their butts and give me a product that actually does what it says on the tin. It really is pathetic levels of support for this router.

I also have contacted Asus support, see replies pasted below (no support at all just wait and see)
everyone needs to just keep giving them hassle via phone numbers below.
I have reverted to firmware two releases back and is now more stable see below for how
Good Luck
(below pasted replies and links from Asus support)

Thank you for your reply and system log.

Your feedback is very much appreciated.

It will aid in further developments of our products to fit customer needs. Your feedback has been send to our development department accordingly.

For now, as the problem does not occur when using the previous firmware version, we would like to advise that you downgrade the firmware.

Unfortunately we cannot provide an ETA on when new firmware is going to be released. My advice would be to keep an eye out on the RT-AC3200 support page here:

https://www.asus.com/us/Networking/RTAC3200/HelpDesk/

If you have any further questions, please do not hesitate to contact us.

Kind regards,

Patrick K
ASUS UK Support Team

Hotline: 01442-265548
Website: www.asus.com
Email: http://vip.asus.com/eservice/techserv.aspx

Dear Sir,
Thank you for contacting Asus Technical Support.

You can do the firmware restoration by following the guide bellow:

https://www.asus.com/support/faq/1000814
After you finish the setup, you should do a reset to factory settings, by pressing the router’s reset button for 5 seconds.

You can download the firmware restoration tool from the link below:

http://dlcdnet.asus.com/pub/ASUS/wi...000.zip?_ga=1.215322327.1924375045.1464075938

You can download the firmware version you desire from the link below:

https://www.asus.com/support/Download/11/2/0/136/sk9NsZJBiTmcVrql/8/


My regards,

Paul L.
Asus Tech Support Team
Hotline: 01442 265 548
Email: http://vip.asus.com/eservice/techserv.aspx
Website: www.asus.com

 

[zoomee]

In the past I would have no problem rolling back to an older version of firmware but one thing that it looks like even Asus support are forgetting here is that older firmware will be running on older versions of the Trend AV engine. Whilst DAT's can be updated the actual engine needs a full firmware update to upgrade it.

In effect this whole rubbish about rolling back to older firmware makes one of the main features of this supposedly top-end router almost useless and quickly out-dated.

 

[bayern1975]

i did not try this firmware yet and asking here what is problem with this firmware?

sent from Kodi 17 Krypton

 

[shez]

Thank the lord I decided to check this thread before I updated!

 

[bit curation]

i did not try this firmware yet and asking here what is problem with this firmware?

sent from Kodi 17 Krypton

For one, I lost WAN port forwarding once a while. Seems related to whenever I make changes to IP/Mac binding, or even parent protection etc. Not too sure what's even that triggers the loss of port forwarding.

Report to Asus through its router admin page, couple times, never heard back. On firmware 3.0.0.4.380_3479, which has not been updated for 3 months. Looks like Asus doesn't give a damn to rt-ac3200 anymore.

 

[zoomee]

Well I cascaded my old AC-3200 using this firmware to a different house.
Problem I now have is all the wireless bands keep turning themselves off!
Have to go into the router wifi professional settings to re-enable the radios before it starts working again.

Will we ever see a newer firmware release?

 

[L&LD]

Well I cascaded my old AC-3200 using this firmware to a different house.
Problem I now have is all the wireless bands keep turning themselves off!
Have to go into the router wifi professional settings to re-enable the radios before it starts working again.

Will we ever see a newer firmware release?

Did you do a full reset to factory defaults and follow that with a minimal and manual configuration of the router to secure it and connect to your ISP? Doesn't seem to be an issue for many others?

http://www.snbforums.com/threads/rt-ac66u-slow-wan-to-lan.12973/page-3#post-269410

http://www.snbforums.com/threads/no...l-and-manual-configuration.27115/#post-205573

It is only three months since the last firmware, I think a little patience is needed to see something newer.

Asus is probably concentrating on their latest 382.xxx release(s).

 

[zoomee]

Both the AC-5300 and the AC-88U have firmware revision 3941 - why was the AC-3200 missed out?

I'll tell you why - this is a dirty sales tactic from Asus. They force users to upgrade if they want the latest software. It's not something unique to just their routers - they do the same with all their tech (i've experienced this first hand with motherboards, and soundcards too) - they don't bother releasing anything after about a year of support unless there's bigtime complaints, in which case they'll drip feed us some beta rubbish just to keep us quiet.

I'm sick of it tbh - The AC-3200 cost me more than the AC-88U I now also own!! If there were other router manufacturers who had the same level of features I woulda jumped ship a long time ago.

Oh and asking me to wait 3 months patiently whilst something I've paid for can't do what it says on the tin is a tad dissapointing. It took them over a year to get the AC-3200 firmware stable then they go and screw it all up just to implement a locked down firmware.

 

[L&LD]

Both the AC-5300 and the AC-88U have firmware revision 3941 - why was the AC-3200 missed out?

I'll tell you why - this is a dirty sales tactic from Asus. They force users to upgrade if they want the latest software. It's not something unique to just their routers - they do the same with all their tech (i've experienced this first hand with motherboards, and soundcards too) - they don't bother releasing anything after about a year of support unless there's bigtime complaints, in which case they'll drip feed us some beta rubbish just to keep us quiet.

I'm sick of it tbh - The AC-3200 cost me more than the AC-88U I now also own!! If there were other router manufacturers who had the same level of features I woulda jumped ship a long time ago.

Oh and asking me to wait 3 months patiently whilst something I've paid for can't do what it says on the tin is a tad dissapointing. It took them over a year to get the AC-3200 firmware stable then they go and screw it all up just to implement a locked down firmware.

I still think you're over reacting, but to each his own.

Asus is far and away the best con/pro sumer router manufacturer with regards to the length of their support well past what others in the industry are offering.

Did it 'do what it said on the tin' when you first bought it? If so, go back to a firmware version that does what you need (at the expense of security and other issues, of course). If not? That was the time to return the product. Not keep it and complain needlessly and without recourse except doing what I suggested in the first place; have patience while Asus works on their stable of products to get everything possible to the 382.xxx release series.

 

[zoomee]

I'd say its fair to over-react when the last firmware we got was about 5 months ago for this device. If I still had this router in my home setup instead of at a friends it wouldn't have worked for me due to the outstanding networkmap issue with this revision and hikvision cameras causing it to crash.