ASUS RT-AC87U Firmware 3.0.0.4.380.3459

[The Cool Dude]

Hello again.

So I'm home and checked my router. Uptime 8 days 1 hours 47 minute(s) 50 seconds.

The log is fairly clean but no WAN Connection entries at all except for one but it didn't happen again.

Jun 1 18:43:40 miniupnpd[1100]: HTTP listening on port 41495
Jun 1 18:43:40 miniupnpd[1100]: Listening for NAT-PMP/PCP traffic on port 5351
Jun 1 18:43:40 WAN Connection: WAN was restored.
Jun 1 18:43:44 rc_service: udhcpc 1059:notify_rc start_firewall
Jun 1 18:43:44 dhcp client: bound 192.168.0.10 via 192.168.0.1 during 3600 seconds.
Jun 1 18:43:44 start_nat_rules: apply the nat_rules(/tmp/nat_rules_eth0_eth0)!
Jun 1 18:43:49 qtn: bootcfg.tgz exists
Jun 1 18:43:56 crond[434]: time disparity of 440683 minutes detected
Jun 1 18:43:56 dfs: start dfs scan
Jun 1 18:43:56 nodfs_scan: complete
Jun 1 18:44:54 rc_service: rc 1672:notify_rc restart_wrs
Jun 1 18:45:05 miniupnpd[1100]: upnp_event_process_notify: connect(192.168.11.75:2869): Connection timed out
Jun 1 18:45:05 miniupnpd[1100]: upnp_event_process_notify: connect(192.168.11.75:2869): Connection timed out
Jun 1 18:45:05 miniupnpd[1100]: upnp_event_process_notify: connect(192.168.11.75:2869): Connection timed out
Jun 1 18:45:19 hour monitor: ntp sync fail, will retry after 120 sec
Jun 1 19:00:30 disk_monitor: Got SIGALRM...
Jun 1 23:00:31 disk_monitor: Got SIGALRM...
Jun 8 20:43:38 miniupnpd[1100]: HTTP Connection from 192.168.11.26 closed unexpectedly
Jun 8 20:43:38 miniupnpd[1100]: HTTP Connection from 192.168.11.26 closed unexpectedly
Jun 8 20:43:38 miniupnpd[1100]: HTTP Connection from 192.168.11.26 closed unexpectedly

I was beginning to think I was going to have to revert to firmware ver 9460 but everything seems ok right now. I'm still curious as to what was going on when my router crashed last week and I lost my internet connection.

 

[dunkin]

My WIFI settings were just reset while I was configuring WPS on my RT-AC87R with this firmware, 3.0.0.4.380_3264

First, I was redirect to http://ec2-54-202-251-7.us-west-2.compute.amazonaws.com/find/router.html, then I found my WIFIs are reset to default. The behavior is very strange. Is it a bug?

 

[dunkin]

My WIFI settings were just reset while I was configuring WPS on my RT-AC87R with this firmware, 3.0.0.4.380_3264

First, I was redirect to http://ec2-54-202-251-7.us-west-2.compute.amazonaws.com/find/router.html, then I found my WIFIs are reset to default. The behavior is very strange. Is it a bug?

I just reproduce the issue. It is actually the Reset button on WPS page. I thought it resets WPS settings only. It actually resets all WIFI settings.

Would Asus give an alert when user clicks the button?

 

[L&LD]

My WIFI settings were just reset while I was configuring WPS on my RT-AC87R with this firmware, 3.0.0.4.380_3264

First, I was redirect to http://ec2-54-202-251-7.us-west-2.compute.amazonaws.com/find/router.html, then I found my WIFIs are reset to default. The behavior is very strange. Is it a bug?

I just reproduce the issue. It is actually the Reset button on WPS page. I thought it resets WPS settings only. It actually resets all WIFI settings.

Would Asus give an alert when user clicks the button?

That redirect is new (RMerlin's firmware offers the option to disable it, I believe).

Resets all router settings. This is in the manual.

If the gui and/or router is unresponsive, how would an alert (that it probably couldn't give) be of any use?

 

[Al Krealman]

I'm having a strange issue with my RT-AC87U
At least once a day the router seems to reboot and I don't know why.
For example, I'm using my WIFI and suddenly the network just dissapears for about 3 minutes and then it comes back.
If I check the router's log the uptime is reset to zero.
This is happening ever since I installed the last beta firmware and keeps happening with the lastest version (3.0.0.4.380_3459) it never happened before.
Did I have to do a hard reset after this last firmware update? cause I didn't, and since these new versions are not compatible with the previous firmwares (I'm talking about the possibility of rolling back from within the web interface since there is a new verification process) maybe there is something with my configuration that is causing these random reboots.

Please let me know what to do.

Thanks!

 

[L&LD]

I'm having a strange issue with my RT-AC87U
At least once a day the router seems to reboot and I don't know why.
For example, I'm using my WIFI and suddenly the network just dissapears for about 3 minutes and then it comes back.
If I check the router's log the uptime is reset to zero.
This is happening ever since I installed the last beta firmware and keeps happening with the lastest version (3.0.0.4.380_3459) it never happened before.
Did I have to do a hard reset after this last firmware update? cause I didn't, and since these new versions are not compatible with the previous firmwares (I'm talking about the possibility of rolling back from within the web interface since there is a new verification process) maybe there is something with my configuration that is causing these random reboots.

Please let me know what to do.

Thanks!

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


With (seemingly unexplainable) random issues and glitches like you're experiencing, a reset to factory defaults is always recommended. This puts the router into a known, good state from where real troubleshooting can happen.

If it does continue after following the steps in the link above, it is either a true bug (unlikely in this case) or an indication of a hardware or local network issue.

Since most people do not have the issue you're reporting, unless and until you put the router into a known/good state (via reset to factory defaults) nobody can reliably give you good recommendations (they will be hit or miss, if anyone is able to respond at all).

 

[pjotr2k]

After 13 Days of uptime the 2.4 ghz guest Network stoped working.

Jun 14 15:30:14 rc_service: httpd 443:notify_rc restart_net
Jun 14 15:30:17 miniupnpd[1047]: shutting down MiniUPnPd
Jun 14 15:30:18 kernel: Attempt to kill tasklet from interrupt
Jun 14 15:30:20 wanduck exit: apply the nat_rules(/tmp/nat_rules_eth0_eth0)!
Jun 14 15:30:21 kernel: Interface br0 doesn't exist
Jun 14 15:30:21 kernel: Interface br0 doesn't exist
Jun 14 15:30:21 kernel: Interface br0 doesn't exist
Jun 14 15:30:23 kernel: wl_module_init: passivemode set to 0x0
Jun 14 15:30:23 kernel: wl_module_init: igs set to 0x1
Jun 14 15:30:23 kernel: wl_module_init: txworkq set to 0x0
Jun 14 15:30:23 kernel: eth1: Broadcom BCM4360 802.11 Wireless Controller 6.37.14.126 (r561982)
Jun 14 15:30:23 stop_nat_rules: apply the redirect_rules!
Jun 14 15:30:23 wan: [wan0_hwaddr] == [30:5A:3A:6D:1F:B0]
Jun 14 15:30:24 RT-AC87U: start httpd - SSL
Jun 14 15:30:24 RT-AC87U: start httpd
Jun 14 15:30:24 miniupnpd[1305]: version 1.9 started
Jun 14 15:30:24 miniupnpd[1305]: add_filter_rule() : chain FUPNP not found
Jun 14 15:30:24 miniupnpd[1305]: Failed to redirect 58848 -> 192.168.1.101:58848 protocol UDP
Jun 14 15:30:24 miniupnpd[1305]: add_filter_rule() : chain FUPNP not found
Jun 14 15:30:24 miniupnpd[1305]: Failed to redirect 14186 -> 192.168.1.89:443 protocol TCP
Jun 14 15:30:24 miniupnpd[1305]: add_filter_rule() : chain FUPNP not found
Jun 14 15:30:24 miniupnpd[1305]: Failed to redirect 8080 -> 192.168.1.90:443 protocol TCP
Jun 14 15:30:24 miniupnpd[1305]: add_filter_rule() : chain FUPNP not found
Jun 14 15:30:24 miniupnpd[1305]: Failed to redirect 21590 -> 192.168.1.89:80 protocol TCP
Jun 14 15:30:24 miniupnpd[1305]: add_filter_rule() : chain FUPNP not found
Jun 14 15:30:24 miniupnpd[1305]: Failed to redirect 3128 -> 192.168.1.90:80 protocol TCP
Jun 14 15:30:24 miniupnpd[1305]: HTTP listening on port 60639
Jun 14 15:30:24 miniupnpd[1305]: Listening for NAT-PMP/PCP traffic on port 5351
Jun 14 15:30:24 qtn: bootcfg.tgz exists
Jun 14 15:30:27 miniupnpd[1305]: add_filter_rule() : chain FUPNP not found
Jun 14 15:30:27 miniupnpd[1305]: Failed to redirect 58848 -> 192.168.1.101:58848 protocol UDP
Jun 14 15:30:27 miniupnpd[1305]: add_filter_rule() : chain FUPNP not found
Jun 14 15:30:27 miniupnpd[1305]: Failed to redirect 14186 -> 192.168.1.89:443 protocol TCP
Jun 14 15:30:27 miniupnpd[1305]: add_filter_rule() : chain FUPNP not found
Jun 14 15:30:27 miniupnpd[1305]: Failed to redirect 8080 -> 192.168.1.90:443 protocol TCP
Jun 14 15:30:27 miniupnpd[1305]: add_filter_rule() : chain FUPNP not found
Jun 14 15:30:27 miniupnpd[1305]: Failed to redirect 21590 -> 192.168.1.89:80 protocol TCP
Jun 14 15:30:27 miniupnpd[1305]: add_filter_rule() : chain FUPNP not found
Jun 14 15:30:27 miniupnpd[1305]: Failed to redirect 3128 -> 192.168.1.90:80 protocol TCP
Jun 14 15:30:27 miniupnpd[1305]: add_filter_rule() : chain FUPNP not found
Jun 14 15:30:27 miniupnpd[1305]: Failed to redirect 58848 -> 192.168.1.101:58848 protocol UDP
Jun 14 15:30:27 miniupnpd[1305]: add_filter_rule() : chain FUPNP not found
Jun 14 15:30:27 miniupnpd[1305]: Failed to redirect 14186 -> 192.168.1.89:443 protocol TCP
Jun 14 15:30:27 miniupnpd[1305]: add_filter_rule() : chain FUPNP not found
Jun 14 15:30:27 miniupnpd[1305]: Failed to redirect 8080 -> 192.168.1.90:443 protocol TCP
Jun 14 15:30:27 miniupnpd[1305]: add_filter_rule() : chain FUPNP not found
Jun 14 15:30:27 miniupnpd[1305]: Failed to redirect 21590 -> 192.168.1.89:80 protocol TCP
Jun 14 15:30:27 miniupnpd[1305]: add_filter_rule() : chain FUPNP not found
Jun 14 15:30:27 miniupnpd[1305]: Failed to redirect 3128 -> 192.168.1.90:80 protocol TCP
Jun 14 15:30:27 miniupnpd[1305]: add_filter_rule() : chain FUPNP not found
Jun 14 15:30:27 miniupnpd[1305]: Failed to redirect 58848 -> 192.168.1.101:58848 protocol UDP
Jun 14 15:30:27 miniupnpd[1305]: add_filter_rule() : chain FUPNP not found
Jun 14 15:30:27 miniupnpd[1305]: Failed to redirect 14186 -> 192.168.1.89:443 protocol TCP
Jun 14 15:30:27 miniupnpd[1305]: add_filter_rule() : chain FUPNP not found
Jun 14 15:30:27 miniupnpd[1305]: Failed to redirect 8080 -> 192.168.1.90:443 protocol TCP
Jun 14 15:30:27 miniupnpd[1305]: add_filter_rule() : chain FUPNP not found
Jun 14 15:30:27 miniupnpd[1305]: Failed to redirect 21590 -> 192.168.1.89:80 protocol TCP
Jun 14 15:30:27 miniupnpd[1305]: add_filter_rule() : chain FUPNP not found
Jun 14 15:30:27 miniupnpd[1305]: Failed to redirect 3128 -> 192.168.1.90:80 protocol TCP
Jun 14 15:30:27 rc_service: udhcpc 1335:notify_rc start_firewall
Jun 14 15:30:28 start_nat_rules: apply the nat_rules(/tmp/nat_rules_eth0_eth0)!
Jun 14 15:30:28 wan: finish adding multi routes
Jun 14 15:30:29 rc_service: udhcpc 1335:notify_rc stop_upnp
Jun 14 15:30:29 rc_service: udhcpc 1335:notify_rc start_upnp
Jun 14 15:30:29 rc_service: waitting "stop_upnp" via udhcpc ...
Jun 14 15:30:29 miniupnpd[1305]: shutting down MiniUPnPd
Jun 14 15:30:31 miniupnpd[1378]: version 1.9 started
Jun 14 15:30:31 miniupnpd[1378]: HTTP listening on port 35869
Jun 14 15:30:31 miniupnpd[1378]: Listening for NAT-PMP/PCP traffic on port 5351
Jun 14 15:30:31 ddns update: ez-ipupdate: starting...
Jun 14 15:30:31 ddns update: connected to nwsrv-ns1.asus.com (103.10.4.108) on port 80.
Jun 14 15:30:32 ddns update: Asus update entry:: return: HTTP/1.1 200 OK^M Date: Tue, 14 Jun 2016 13:30:29 GMT^M Server: Apache^M Content-Length: 0^M Connection: close^M Content-Type: text/html^M ^M
Jun 14 15:30:32 ddns update: retval= 0, ddns_return_code (,200)
Jun 14 15:30:32 ddns update: asusddns_update: 0
Jun 14 15:30:32 ddns: ddns update ok
Jun 14 15:30:33 WAN Connection: WAN was restored.
Jun 14 15:30:37 rc_service: udhcpc 1335:notify_rc start_firewall
Jun 14 15:30:37 dhcp client: bound 78.68.101.189 via 78.68.101.129 during 1200 seconds.
Jun 14 15:30:38 start_nat_rules: apply the nat_rules(/tmp/nat_rules_eth0_eth0)!
Jun 15 00:04:14 disk_monitor: Got


This is what i can se happened during the Day in the log, its like the wlan is non existing.

Byt the non guest Network still Works on 2.4.

 

[kdawg]

I have had similar issue with my router since I upgrade to 3.0.0.4.380_3459-gfbf1f06 on June 8. The router is now very unstable and reboots several times a day. The log is filled with the WAN connection errors. I had no problems before this upgrade. ASUS support was completely worthless. I've had the router almost two years and never had a single issue. I was really happy with the performance of the router until this point. Firmware upgrades worked flawlessly until now. My wife can't even work at home any more because the connection is so unstable.

 

[LiquidOcelot]

Hello guys and many thanks for everyone`s posts that help all the comunity,

Now I have a problem with my AC87u...running 380_3459 official and i want to go back to older fw ver and i cannot do that , i do select the .trx file and click upload then i get a window error message that it cannot upload bad transmision or image file selected, something like that. I did after that, reboot, to factory and nothing worked. The router only allows me to reflash the existing one, 380_3459 i`m running it atm. Can you give me a solution please ! Have a great one everybody ! Thanks

 

[VANT]

You must use recovery mode if You want to back before .380.3xxx series

 

[LiquidOcelot]

Solved many thanks

 

[rtcomputersinc]

Ok just upgraded my 87u from 380.2695 to 380.3459. I have 3 repeaters on this two 66u's and one 68u. The link rates on one 66u are at a higher link rate than the previous fw which was all over the place. Its now from 135 to 162 link rate. The 68u shows the same link rate as the first 66u. The other 66u shows from 300 to 450 link rate and I thought the max was actually only 300. Nope just checked its 450 and is the first time i have seen with this router in this configuration go over 300. A speed test on the first repeater show a 10 meg up and download increase over previous fw. Will update if things change.

 

[vaszago]

I have 3 repeaters on this two 66u's and one 68u

What firmware have you on your AC68 Router.

Is the Repeater mode realy working. I have problem since 1 year. The reapeater mode will not working. The last working was the Merlin 378.54_1

 

[rtcomputersinc]

What firmware have you on your AC68 Router.

Is the Repeater mode realy working. I have problem since 1 year. The reapeater mode will not working. The last working was the Merlin 378.54_1

All are on the latest fw available. I have never had an issue with the repeaters except for the past few fw releases. I have my repeaters all with static set IP's. What I did find after updating my 66's and 68 is that if I did a manual configuration I would lose connectivity to my repeater. The way I did a work around on that is I factory reset it again and went with everything as automatic setup. I then did an ip scan found the repeater and them manually changed it to the static ip. For some reason manually setting up doesn't work. I had same issue with all my repeaters and fix above worked perfectly for my setup. Not sure your exact setup but this is how I fixed mine.

 

[vaszago]

All are on the latest fw available.

On original FW or on Merlin.

I have my repeaters all with static set IP's.

I have also made automatic setup and then change to on a staic IP.

I then did an ip scan found the repeater and them manually changed it to the static ip.

The problem is when i give the Repeater a static ip. That my Clients get no ip from the Repeater. Only when my Clients have a static ip the clients connect with repeater.
I connect the Repeater with 5GHZ. Maybe that's the problem.

Thats the problem what i have with the repeater mode since one Year.

Have your Clients a problem to get a ip from the Router, or have your clients a static IP.

 

[rtcomputersinc]

On original FW or on Merlin.



I have also made automatic setup and then change to on a staic IP.

Original fw not merlin but problem could be source code.


The problem is when i give the Repeater a static ip. That my Clients get no ip from the Repeater. Only when my Clients have a static ip the clients connect with repeater.
I connect the Repeater with 5GHZ. Maybe that's the problem.

Thats the problem what i have with the repeater mode since one Year.

It could be same problem I never tried to set a device with static and see if it works. My devices get the standard cant assign an ip of 169.x.x.x. I do have a second setup with an 88u and a 66u repeater. I did an upgrade of the 66u to latest. Went in and selected auto for everything except the ssid it forces RPT on the end of the names. I manually set the name up and had the same issue like its not getting an ip. So I factory reset once again. went it let it auto everything. When it came back up it came up correct except with RPT on it which I did go in and manually remove RPT on both the 2.4 and 5 channels an applied. Then changed the ip to a static that worked for my particular setup. There is something funny with the manual setup.

Have your Clients a problem to get a ip from the Router, or have your clients a static IP.

QUOTE="vaszago, post: 267987, member: 25506"]On original FW or on Merlin.



I have also made automatic setup and then change to on a staic IP.

Original fw not merlin but problem could be source code.


The problem is when i give the Repeater a static ip. That my Clients get no ip from the Repeater. Only when my Clients have a static ip the clients connect with repeater.
I connect the Repeater with 5GHZ. Maybe that's the problem.

Thats the problem what i have with the repeater mode since one Year.

It could be same problem I never tried to set a device with static and see if it works. My devices get the standard cant assign an ip of 169.x.x.x. I do have a second setup with an 88u and a 66u repeater. I did an upgrade of the 66u to latest. Went in and selected auto for everything except the ssid it forces RPT on the end of the names. I manually set the name up and had the same issue like its not getting an ip. So I factory reset once again. went it let it auto everything. When it came back up it came up correct except with RPT on it which I did go in and manually remove RPT on both the 2.4 and 5 channels an applied. Then changed the ip to a static that worked for my particular setup. There is something funny with the manual setup.

Have your Clients a problem to get a ip from the Router, or have your clients a static IP.[/QUOTE]

They get ip from router. If you auto setup the repeater have you checked it prior to making manual changes that it works right or not?
?

 

[VANT]

i use 87u with 9460fw and 66u as repeater with latest asus fw and work ok with automatic settings for all except ssid (i change to same name as main router)

 

[rtcomputersinc]

i use 87u with 9460fw and 66u as repeater with latest asus fw and work ok with automatic settings for all except ssid (i change to same name as main router)

That worked with my 87u and 66u (have 2-66u and 1-68u) the same way as you where I could change the ssid no issue. My 88u and 66u had issue with manually changing the ssid. It use to work flawless imputing the correct settings as I went. Now i have to change it all at the end . Once I did everything auto it was happy and would let me change ip and ssid to anything I want. The ssid's on all my routers match the main router as well.

 

[vaszago]

@rtcomputersinc

Thank you for the Answer.

So there is no guarantee that the repeater mode works.
I have to test it.

As long as I can downgrade wit the cfe methode i will risk the latest Merlin on both Routers.
Keep your fingers crossed that it works.

 

[rtcomputersinc]

@rtcomputersinc

Thank you for the Answer.

So there is no guarantee that the repeater mode works.
I have to test it.

As long as I can downgrade wit the cfe methode i will risk the latest Merlin on both Routers.
Keep your fingers crossed that it works.

No problem there are no guarantees in life. I can only pass on the strange things I needed to do to make it work and hopefully it helps you. Its a bug and not too many are running them as repeaters. Seeming's Merlins is built off of the Asus code there is a good possibility of the same bug tell us how you make out.