Is this a bug on Asus firmware? WAN disconnections

[RMerlin]

Reflashing a firmware does absolutely nothing. It's more likely that it's the 5 mins your router spends offline while flashing that actually causes your issue to disappear, not the flash process itself.

 

[sovereignty68]

You are right, reflashing does nothing. But the modem was still on during the whole process before the router was able to retrieve the WAN IP. I forgot to mention that I had cloned my computer's MAC address before the modem was able to assign the IP. I did some testing again last night and figured out how I managed to get the modem to assign IP to the router properly without flashing the firmware or powering off the modem for 5-10min.

1) Connect the modem directly the computer
2) Reboot the modem, wait until the modem/ISP assigns the IP address to the computer
3) Reconnect the modem to the router's WAN interface. Don't reboot the modem or the router.
4) In WAN setting, clone the MAC address of the same computer that received the IP from the ISP and apply the setting
Router should able to receive the IP address, if not, reboot the router.

The whole process took less than 2 minutes. Simply changing the MAC address of the WAN interface on the router doesn't work. Simply clone the MAC address from the computer without performing step 1&2 above doesn't work either.

Hope this helps others who might have similar problem.

 

[xrecar]

Resetting via the wps button (clearing the nvram) is my solution - happens about every 6 days with my new ac-n66u. Reflashing worked with the rt-N66U when I was using it. Modem stays on. Your not the only one with the problem. Asus even sent me a new router. Since the ac does it less frequently I'm selling the rt.

 

[mikeg]

I had this issue with RT-N66U when I exchanged it to a AC66U I have had no problems at all.

Resetting via the wps button (clearing the nvram) is my solution - happens about every 6 days with my new ac-n66u. Reflashing worked with the rt-N66U when I was using it. Modem stays on. Your not the only one with the problem. Asus even sent me a new router. Since the ac does it less frequently I'm selling the rt.

 

[xrecar]

I'm going out on a limb here. Any of you guys running a windows 7 client? I just had about 4 dhcp failures-wan disconnects when the win 7 laptop was on and downloading. It is off now and I'm not having the disconnects. I tried with a usb wireless adapter and it didn't seem to help, but killed the router again. Seem improbable? I've been needing a solution to the Internet disconnects

**the period of 6 days it was up, the laptop was hardwired to the router.

 

[xrecar]

Well it's not windows 7. I upgraded to 8, and loaded up sabnzbD and router was offline within 5 minutes. I'll try wireless nzb download with another laptop.

 

[xrecar]

Lessened the connections to 5 on sabnzbd and seemed to run ok until i allowed the bandwidth to go over 2Mb/sec- Got a isp dhcp fail. Think i should get a new modem? The sb6121 is less than a year old. It runs 4Mb/sec wired without problems & 15 connections. Its what makes me think it is the router.

 

[RMerlin]

Lessened the connections to 5 on sabnzbd and seemed to run ok until i allowed the bandwidth to go over 2Mb/sec- Got a isp dhcp fail. Think i should get a new modem? The sb6121 is less than a year old. It runs 4Mb/sec wired without problems & 15 connections. Its what makes me think it is the router.

Have you checked that the cable between your modem and your router was Cat5e or Cat6? Older Cat5 cables will be very unstable once you start pushing too much traffic through them, since the router's WAN is gigabit-capable.

 

[xrecar]

Its the thin cat 6 (I think) that was pkged with the ac66u. Going to return it tommorow and try a different brand router. Shame cause i really like all the features when its working. Same problem with the n66u that I cant return. What would cause it to bomb out using wifi, but not wired? I relagated to hooking up the laptop wired when i want to grab large nzbs- shouldnt have to do that.

 

[xrecar]

Bought a netgear 6300 noticed some dropouts while downloading - but it would recover, where the r66u would not. Streaming from the r6300 / signal strength is what made me return it. Cant touch the asus. Max i could get from attached hd was 6000Kb Via ftp. Picked up a zoom docsis 3 modem on a hunch - tried the same download with 15 connections in sabnzbd - max bandwidth and no drops 7 gigs complete.

Try swapping the modem stupid <--Me.

 

[smc]

I have also intermittently experienced this same problem on my RT-N56U, and I believe the fault lies with the ASUS router and/or firmware. I also have a VOIP terminal on the same connection that has never experienced similar failures.

When my network connection went offline today, I power cycled the router and the VOIP ATA box came back online immediately, while the N56U was still stuck reporting:

Dec 31 16:00:16 WAN Connection: Ethernet link down.
Dec 31 16:00:16 WAN Connection: ISP's DHCP did not function properly.

Dec 31 16:00:23 miniupnpd[478]: ioctl(s, SIOCGIFADDR, ...): Cannot assign requested address
Dec 31 16:00:23 miniupnpd[478]: ioctl(s, SIOCGIFADDR, ...): Cannot assign requested address

I'm using firmware 3.0.0.4.260, and believe this is a bug.

(BTW, I'm using the thin ethernet cable that came with the router, but I can't imagine this has anything to do with the problem)

 

[RMerlin]

Dec 31 16:00:16 WAN Connection: Ethernet link down.

That error indicates a problem in the connection between the router and the modem. I would try a different Ethernet cable.

 

[krum]

I think its a bug .270

Mar 16 22:10:05 notify_rc : restart_allnet
Mar 16 22:10:07 dnsmasq[621]: exiting on receipt of SIGTERM
Mar 16 22:10:08 radvd[802]: Exiting, sigterm or sigint received.
Mar 16 22:10:08 radvd[802]: sending stop adverts
Mar 16 22:10:08 radvd[802]: removing /var/run/radvd.pid
Mar 16 22:10:08 radvd[800]: Exiting, privsep_read_loop had readn return 0 bytes
Mar 16 22:10:08 notify_rc : start_radvd
Mar 16 22:10:08 rc_service: start_radvd is waitting restart_allnet...
Mar 16 22:10:09 stop_wan(): perform DHCP release
Mar 16 22:10:09 stop_wan(): perform DHCP release
Mar 16 22:10:09 kernel: br0: port 1(vlan1) entering disabled state
Mar 16 22:10:09 kernel: vlan1: dev_set_promiscuity(master, 1)
Mar 16 22:10:09 kernel: br0: port 1(vlan1) entering listening state
Mar 16 22:10:09 kernel: br0: port 1(vlan1) entering learning state
Mar 16 22:10:09 kernel: br0: topology change detected, propagating
Mar 16 22:10:09 kernel: br0: port 1(vlan1) entering forwarding state
Mar 16 22:10:10 WAN Connection: ISP's DHCP did not function properly.
Mar 16 22:10:10 notify_rc : stop_nat_rules
Mar 16 22:10:10 rc_service: stop_nat_rules is waitting restart_allnet...
Mar 16 22:10:11 kernel: br0: port 3(eth2) entering disabled state
Mar 16 22:10:11 kernel: br0: port 2(eth1) entering disabled state
Mar 16 22:10:11 kernel: br0: port 1(vlan1) entering disabled state
Mar 16 22:10:11 kernel: Ebtables v2.0 registered
Mar 16 22:10:11 kernel: br0: port 1(vlan1) entering disabled state
Mar 16 22:10:11 kernel: vlan1: dev_set_promiscuity(master, -1)
Mar 16 22:10:11 kernel: device vlan1 left promiscuous mode
Mar 16 22:10:11 kernel: device eth1 left promiscuous mode
Mar 16 22:10:11 kernel: br0: port 2(eth1) entering disabled state
Mar 16 22:10:11 kernel: device eth2 left promiscuous mode
Mar 16 22:10:11 kernel: br0: port 3(eth2) entering disabled state
Mar 16 22:10:12 wanduck exit: apply the nat_rules(/tmp/nat_rules)!
Mar 16 22:10:12 kernel: eth1: Broadcom BCM4331 802.11 Wireless Controller 6.30.39.31 (r341183)
Mar 16 22:10:12 kernel: eth2: Broadcom BCM4360 802.11 Wireless Controller 6.30.39.31 (r341183)
Mar 16 22:10:12 kernel: br0: starting userspace STP failed, staring kernel STP
Mar 16 22:10:12 kernel: device eth1 entered promiscuous mode
Mar 16 22:10:13 kernel: wlc_phy_cal_init_acphy: NOT Implemented
Mar 16 22:10:13 kernel: device eth2 entered promiscuous mode
Mar 16 22:10:13 kernel: br0: port 3(eth2) entering listening state
Mar 16 22:10:13 kernel: br0: port 2(eth1) entering listening state
Mar 16 22:10:13 stop_nat_rules: apply the redirect_rules!
Mar 16 22:10:13 kernel: br0: port 1(vlan1) entering listening state
Mar 16 22:10:13 kernel: br0: port 3(eth2) entering learning state
Mar 16 22:10:13 kernel: br0: port 2(eth1) entering learning state
Mar 16 22:10:13 kernel: br0: port 1(vlan1) entering learning state
Mar 16 22:10:13 kernel: br0: topology change detected, propagating
Mar 16 22:10:13 kernel: br0: port 3(eth2) entering forwarding state
Mar 16 22:10:13 kernel: br0: topology change detected, propagating
Mar 16 22:10:13 kernel: br0: port 2(eth1) entering forwarding state
Mar 16 22:10:13 kernel: br0: topology change detected, propagating
Mar 16 22:10:13 kernel: br0: port 1(vlan1) entering forwarding state
Mar 16 22:10:13 WAN Connection: ISP's DHCP did not function properly

 

[Radiator]

Been getting the same...

"WAN Connection: ISP's DHCP did not function properly."

Unplugged cable modem for 15min. Using Cat5e (tried several).

 

[RMerlin]

Been getting the same...

"WAN Connection: ISP's DHCP did not function properly."

Unplugged cable modem for 15min. Using Cat5e (tried several).

What ISP? Which firmware version?

 

[Marinemaster]

RT-N66U

I am running cat 6 and had Linksys router on the same cat 6 and same cable modem never had any disconnect.

I was on 270 for about three weeks, no disconnect. Then I upgraded to 354 and had disconnect after few days. I downgrade to 270 and after few days another/second disconnect. After the second disconnect I downloaded fresh 270 from Asus website, flash the router again to 270 and reset and wps.

I will report here in about a week or so how stable it is or if it happens again.

 

[RMerlin]

RT-N66U

I am running cat 6 and had Linksys router on the same cat 6 and same cable modem never had any disconnect.

I was on 270 for about three weeks, no disconnect. Then I upgraded to 354 and had disconnect after few days. I downgrade to 270 and after few days another/second disconnect. After the second disconnect I downloaded fresh 270 from Asus website, flash the router again to 270 and reset and wps.

I will report here in about a week or so how stable it is or if it happens again.

Flashing/reflashing won't help. Disconnects are usually related to either the modem or the ISP.

 

[Marinemaster]

I had the Linksys router for like 8 years and the same cable modem for like one year and same cat 6 cable connecting them. I never had any disconnects. Unlikely the ISP or the cable modem.

When the two disconnects happened, I connect my PC straight into cable modem and Internet worked. Then I power off cable modem and Asus several times, it did not fix issue.

I would say unlikely is the cable modem. Both disconnects happened when I was not home. If say the ISP drops the connection during the day, then Asus cannot reconnect on its own. Maybe it needs some kind of keep alive or similar to re-establish the connection.

I had the same ISP for the past 8 years. Few years back they did maintenance around 2 AM or so and the Internet did go down for that time period. Linksys did re-establish Internet connection on its own after the maintenance window.

Ill monitor the Asus and report back.

 

[Lukebad]

Came across this topic while searching for solutions of this same problem...
My N66U will always lose connection overnight, especially if I leave my bittorrent client running.
(I have to check if it's only when I leave my bittorrent client running...)

Same thing as everyone:

Apr 25 02:31:49 WAN Connection: ISP's DHCP did not function properly.
Apr 25 02:31:49 notify_rc : stop_nat_rules
Apr 25 02:31:49 stop_nat_rules: apply the redirect_rules!

Then when I unplug and replug my modem:

Apr 25 06:26:23 WAN Connection: Ethernet link up.
Apr 25 06:26:23 notify_rc : restart_wan_if 0

I was using a cat5 cable yesterday, and switched to a cat5e (the one that comes with the N66U), but it happened again...

----

Oh, I don't know if this is useful, but after the restart_wan_if 0, this shows up:

Apr 25 06:26:23 stop_wan(): perform DHCP release
Apr 25 06:26:23 kernel: vlan1: dev_set_promiscuity(master, -1)
Apr 25 06:26:23 kernel: br0: port 1(vlan1) entering disabled state
Apr 25 06:26:23 kernel: vlan1: dev_set_promiscuity(master, 1)
Apr 25 06:26:23 kernel: br0: port 1(vlan1) entering listening state
Apr 25 06:26:23 kernel: br0: port 1(vlan1) entering learning state
Apr 25 06:26:23 kernel: br0: topology change detected, propagating
Apr 25 06:26:23 kernel: br0: port 1(vlan1) entering forwarding state

-----

And on another issue, I have spamming of these messages:
One of these:

Apr 25 06:10:29 miniupnpd[925]: ioctl(s, SIOCGIFADDR, ...): Cannot assign requested address
Apr 25 06:10:29 miniupnpd[925]: Failed to get ip address for interface eth0

Followed by about 10 or so of these

Apr 25 06:15:59 dnsmasq-dhcp[662]: DHCPACK(br0) 192.168.13.13 00:25:11:71:cc:92 ATRON-MarkII
Apr 25 06:17:10 dnsmasq-dhcp[662]: DHCPINFORM(br0) 192.168.13.13 00:25:11:71:cc:92

Should I try to disable manual ip assigning?

-----

So, if anyone could try and help me... I'd be very grateful.
Cheers.

 

[Skooma Breath]

rt-n56u disconnecting

internet goes down for like 20 seconds and restores by itself several times throughout the day. I'm using an rt-n56u router on the latest firmware (3.0.0.4.360), a cable modem, model dpx2203, and also the cat5e cable that came with the router.


May 24 18:34:44 WAN Connection: Ethernet link down.
May 24 18:34:44 stop_nat_rules: apply the redirect_rules!
May 24 18:34:45 WAN Connection: Ethernet link up.
May 24 18:34:45 rc_service: wanduck 417:notify_rc restart_wan_if 0
May 24 18:34:45 stop_wan(): perform DHCP release
May 24 18:34:45 kernel: eth3: ===> VirtualIF_close
May 24 18:34:47 kernel: GDMA2_MAC_ADRH -- : 0x00003085
May 24 18:34:47 kernel: GDMA2_MAC_ADRL -- : 0xa96abf70
May 24 18:34:47 kernel: eth3: ===> VirtualIF_open
May 24 18:34:48 WAN Connection: ISP's DHCP did not function properly.
May 24 18:34:48 start_nat_rules: apply the nat_rules(/tmp/nat_rules_eth3_eth3)!
May 24 18:34:48 rc_service: udhcpc 4321:notify_rc stop_upnp
May 24 18:34:48 rc_service: udhcpc 4321:notify_rc start_upnp
May 24 18:34:48 dhcp client: bound 192.168.100.10 via 192.168.100.1 during 30 seconds.
May 24 18:34:53 WAN Connection: WAN was restored.
May 24 18:35:15 start_nat_rules: apply the nat_rules(/tmp/nat_rules_eth3_eth3)!
May 24 18:35:15 rc_service: udhcpc 4353:notify_rc stop_upnp
May 24 18:35:15 rc_service: udhcpc 4353:notify_rc start_upnp
May 24 18:35:15 dhcp client: bound 173.89.59.207 via 173.89.32.1 during 27182 seconds.
May 24 18:36:48 WAN Connection: Ethernet link up.
May 24 18:36:48 rc_service: wanduck 417:notify_rc restart_wan_if 0
May 24 18:36:48 stop_wan(): perform DHCP release
May 24 18:36:48 kernel: eth3: ===> VirtualIF_close
May 24 18:36:48 kernel: eth3: ===> VirtualIF_open
May 24 18:36:49 start_nat_rules: apply the nat_rules(/tmp/nat_rules_eth3_eth3)!
May 24 18:36:50 rc_service: udhcpc 4392:notify_rc stop_upnp
May 24 18:36:50 rc_service: udhcpc 4392:notify_rc start_upnp
May 24 18:36:50 dhcp client: bound 192.168.100.10 via 192.168.100.1 during 30 seconds.
May 24 18:37:16 start_nat_rules: apply the nat_rules(/tmp/nat_rules_eth3_eth3)!
May 24 18:37:16 rc_service: udhcpc 4427:notify_rc stop_upnp
May 24 18:37:16 rc_service: udhcpc 4427:notify_rc start_upnp