Is this a bug on Asus firmware? WAN disconnections

[RocketJSquirrel]

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.

I would suspect the modem. Trade that old one in for a new DOCSIS 3 modem if your ISP supports D3.

 

[TwiztidGuy]

It's not a bad router.

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.

I didn't have any issues with my router until i did that same firmware update you have. It has to be an issue with the Firmware. Seeing that you are using router, the same firmware version, and having the same problem... I'm going to roll back my firmware to an earlier version. I know this is an old thread but I believe this just determined what the issue is. I had this router for 8 months with no problems until i did that 3.0.0.4.360 firmware update.

 

[chamberc]

It is the firmware. I had a n66u that started this with the same firmware upgrade. Two weeks ago we were hit directly by lightning. I now have an ac66u all new cables, modem and drop to the pedestal. Same thing happening.

 

[mirt]

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.

I registered just to say thank you! This method worked perfectly for me and my rt-n266u...

 

[jgs2n]

Wan Connection Ethernet link down

I have rt-n66u with Merlin 354.29

I keep getting Wan drops. I read this thread. I changed the cable from modem to router with new cat5e. I disconnected and unplugged modem for 20 minutes.

I keep getting random drops from charter cable internet. Below are some lines from my router log. Anyone have ideas of how to troubleshoot this?
Thanks.

Jun 26 19:40:28 WAN Connection: Ethernet link down.
Jun 26 19:40:28 stop_nat_rules: apply the redirect_rules!
Jun 26 19:40:28 dnsmasq[3827]: exiting on receipt of SIGTERM
Jun 26 19:40:28 dnsmasq[3870]: started, version 2.65 cachesize 1500
Jun 26 19:40:28 dnsmasq[3870]: compile time options: IPv6 GNU-getopt no-RTC no-DBus no-i18n no-IDN DHCP DHCPv6 no-Lua TFTP no-conntrack

 

[lalala]

I had the same issue/symptoms with my Asus RT-AC66U, I solved it by using the "Factory Reset" option. After that the router had no issue getting an DHCP IP from my ISP.

 

[Pericynthion]

You might want to check the modem itself (192.168.100.1 on my comcast link), because you can see the actual modem-uplink state rather than just the modem-router.

In my case I saw a WAN drop on the AC66U, and looking at the modem log I see this at the same time;

Jun 27 2013 04:40:35 4-Error D103.0 DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=cc:7d:37:1a:9e:66;CMTS-MAC=00:1d:45:70:5a:3a;CM-QOS=1.1;CM-VER=3.0;

Which is telling me this is an ISP link issue rather than the modem / router link.

Obviously if you dont see any corresponding local-loop messages then its potentially a modem / router issue, but I would check the ISP first (as its been the root of the problem in 99.9% of all my WAN disconnects)

 

[jgs2n]

Thanks for the suggestions.

I have restored to factory default and checked my modem log. No help. Still getting random disconnects.

Here is the message I get in the router log.

Jun 29 22:11:35 WAN Connection: ISP's DHCP did not function properly.
Jun 29 22:11:35 stop_nat_rules: apply the redirect_rules!
Jun 29 22:11:35 dnsmasq[767]: exiting on receipt of SIGTERM
Jun 29 22:11:35 dnsmasq[789]: started, version 2.65 cachesize 1500
Jun 29 22:11:35 dnsmasq[789]: compile time options: IPv6 GNU-getopt no-RTC no-DBus no-i18n no-IDN DHCP DHCPv6 no-Lua TFTP no-conntrack
Jun 29 22:11:35 dnsmasq[789]: asynchronous logging enabled, queue limit is 5 messages
Jun 29 22:11:35 dnsmasq-dhcp[789]: DHCP, IP range 192.168.1.2 -- 192.168.1.254, lease time 1d

 

[Requi3m]

This just started happening to me after upgrading to the latest beta merlin firmware from the latest stock firmware. I will be reverting to the stock firmware and see what happens.

It says

Jul 1 13:27:23 WAN Connection: Ethernet link down.

But my cable tests good. I must admit that I also moved my router to my attic and I am now using a different cable that I crimped the ends on myself. I will do some more tests.

 

[RMerlin]

"Ethernet link down" is almost certainly a sign of a problem at the Ethernet level, usually the cable. The router has a gigabit WAN port, so you need a gigabit-cable cable (Cat5e or better, and fairly recent RJ-45 connectors as well - I've seen older connectors having trouble dealing with gigabit speed).

You must also ensure that you are using the correct wire order when crimping your connectors (just making sure - I've seen people randomly order the colors without realising that twisted pairs cannot be randomly mixed).

 

[col2k3]

This is weird.

I'm using a very old Merlin FW version (3.0.0.4.264.22) Haven't had any issues, neither showed up on this boards for months, and during the last week I started getting random WAN disconnections as well.

Tried everything, rebooting connection, resetting modem, releasing ip, nothing works, until... I plug the Cable modem directly to the pc, then it instantly goes back online, and I can then hook the modem back to the router (& it will still work), but 1 day or 2 later it starts happening again.

What can I do?

P.D. RT-N66U

 

[Requi3m]

"Ethernet link down" is almost certainly a sign of a problem at the Ethernet level, usually the cable. The router has a gigabit WAN port, so you need a gigabit-cable cable (Cat5e or better, and fairly recent RJ-45 connectors as well - I've seen older connectors having trouble dealing with gigabit speed).

You must also ensure that you are using the correct wire order when crimping your connectors (just making sure - I've seen people randomly order the colors without realising that twisted pairs cannot be randomly mixed).

It's cat5e and I definitely wired it right (I'm a network technician.) I might put new ends on it anyway. Things have been fine since going back to the stock non-beta firmware. We'll see what happens tomorrow.

It sucks that I've changed so many variables all at once so I'm not exactly sure what caused it. It was either the new firmware, heat (I've had a box fan pointed at it up there just in case), or the cable I made. I've seen the 5 ghz chipset get up to 70C up there in my attic even with the box fan.

 

[Requi3m]

My WAN has not disconnected ever since I switched back to stock firmware 3.0.0.4.270 yesterday. It's probably still too early to say it's fixed. It's not as hot today as it was yesterday so it could potentially still be a heat issue.

I ordered one of these: http://www.newegg.com/Product/Product.aspx?Item=9SIA1NV0K68813

If it works I'm going to order a second because I think two will fit on there. I'm kind of doubting that the wireless chipset is really capable of being 80C. When I came home today I had to restart the wireless because my signal strength was 2 bars instead of five.

Edit: I just re-read the thread and realized that a lot of us that are having issues are using the motorola SB6121. I'm using the same modem.

 

[Requi3m]

There it went again. It's not my cable and it's not heat that's causing it. That leaves asus's software or hardware as the cause. I must say highly I'm highly disappointed in this router considering I paid $200 for it. I really hope this is a software issue and they can get it fixed. I'm going to be submitting a bug report to asus. Here's the last log entries. You'll notice that this time it never says the WAN went down, only that it came back up.

Jul 3 21:14:21 WAN Connection: Ethernet link up.
Jul 3 21:14:21 notify_rc : restart_wan_if 0
Jul 3 21:14:21 dnsmasq[553]: read /etc/hosts - 3 addresses
Jul 3 21:14:21 dnsmasq[553]: using nameserver 24.113.0.30#53
Jul 3 21:14:21 dnsmasq[553]: using nameserver 24.113.32.30#53
Jul 3 21:14:21 dnsmasq[553]: using nameserver 24.113.32.29#53
Jul 3 21:14:21 stop_wan(): perform DHCP release
Jul 3 21:14:21 kernel: br0: port 1(vlan1) entering disabled state
Jul 3 21:14:21 dnsmasq[553]: read /etc/hosts - 3 addresses
Jul 3 21:14:21 dnsmasq[553]: using nameserver 24.113.0.30#53
Jul 3 21:14:21 dnsmasq[553]: using nameserver 24.113.32.30#53
Jul 3 21:14:21 dnsmasq[553]: using nameserver 24.113.32.29#53
Jul 3 21:14:21 dnsmasq[553]: read /etc/hosts - 3 addresses
Jul 3 21:14:21 kernel: br0: port 1(vlan1) entering listening state
Jul 3 21:14:21 kernel: br0: port 1(vlan1) entering learning state
Jul 3 21:14:21 kernel: br0: topology change detected, propagating
Jul 3 21:14:21 kernel: br0: port 1(vlan1) entering forwarding state
Jul 3 21:14:21 dnsmasq[553]: read /etc/hosts - 3 addresses
Jul 3 21:14:21 dnsmasq[553]: using nameserver 192.168.100.1#53
Jul 3 21:14:21 notify_rc : start_nat_rules
Jul 3 21:14:21 start_nat_rules: apply the nat_rules!
Jul 3 21:14:21 notify_rc : stop_upnp
Jul 3 21:14:21 miniupnpd[601]: received signal 15, good-bye
Jul 3 21:14:21 notify_rc : start_upnp
Jul 3 21:14:21 syslog: SNet version started
Jul 3 21:14:22 dhcp client: bound 192.168.100.10 via 192.168.100.1 during 20 seconds.
Jul 3 21:14:22 miniupnpd[674]: HTTP listening on port 51576
Jul 3 21:14:22 miniupnpd[674]: Listening for NAT-PMP traffic on port 5351
Jul 3 21:14:50 dnsmasq[553]: read /etc/hosts - 3 addresses
Jul 3 21:14:50 dnsmasq[553]: using nameserver 192.168.100.1#53
Jul 3 21:14:52 WAN Connection: ISP's DHCP did not function properly.
Jul 3 21:14:52 notify_rc : stop_nat_rules
Jul 3 21:14:52 stop_nat_rules: apply the redirect_rules!
Jul 3 21:15:19 dnsmasq[553]: read /etc/hosts - 3 addresses
Jul 3 21:15:19 dnsmasq[553]: using nameserver 24.113.0.30#53
Jul 3 21:15:19 dnsmasq[553]: using nameserver 24.113.32.30#53
Jul 3 21:15:19 dnsmasq[553]: using nameserver 24.113.32.29#53
Jul 3 21:15:19 notify_rc : start_nat_rules
Jul 3 21:15:19 start_nat_rules: apply the nat_rules!
Jul 3 21:15:19 notify_rc : stop_upnp
Jul 3 21:15:19 miniupnpd[674]: received signal 15, good-bye
Jul 3 21:15:19 notify_rc : start_upnp
Jul 3 21:15:19 syslog: SNet version started
Jul 3 21:15:19 miniupnpd[709]: HTTP listening on port 43685
Jul 3 21:15:19 miniupnpd[709]: Listening for NAT-PMP traffic on port 5351
Jul 3 21:15:19 dhcp client: bound 24.113.5.63 via 24.113.4.1 during 86400 seconds.
Jul 3 21:15:23 WAN Connection: WAN was restored.

So now I'm getting the DHCP errors others are reporting. I wonder if this is related to the modem I and others in this thread are using.

 

[RMerlin]

There it went again. It's not my cable and it's not heat that's causing it. That leaves asus's software or hardware as the cause. I must say highly I'm highly disappointed in this router considering I paid $200 for it. I really hope this is a software issue and they can get it fixed. I'm going to be submitting a bug report to asus. Here's the last log entries. You'll notice that this time it never says the WAN went down, only that it came back up.



So now I'm getting the DHCP errors others are reporting. I wonder if this is related to the modem I and others in this thread are using.

I see two lines here that tells me that the problem is your modem rebooting. See this:

Jul 3 21:14:22 dhcp client: bound 192.168.100.10 via 192.168.100.1 during 20 seconds.

And a few lines later this:

Jul 3 21:15:19 dhcp client: bound 24.113.5.63 via 24.113.4.1 during 86400 seconds.

The only way your router could get such an IP from your modem is if the modem was rebooting, and its own internal DHCP server was answering, until the moment the modem finished booting, and your ISP's DHCP started answering requests. That also explains the link down messages.

 

[Requi3m]

The only way your router could get such an IP from your modem is if the modem was rebooting, and its own internal DHCP server was answering, until the moment the modem finished booting, and your ISP's DHCP started answering requests. That also explains the link down messages.

What about if the WAN port on the router was malfunctioning? Wouldn't that cause the same behavior?

I suppose I could connect my modem directly to my computer and setup something to monitor it closely, but my brother probably wouldn't be too happy about that.

Someone posted this on the newegg reviews. I wonder if it's related:

There are quite a few people who experience dropped connections on a 10-15 minute basis with many of these new high end routers. Poster Phuzion at DD-WRT forum had this to say:

No there is not any build that fixes it so don't waste your time. The firewall scripts works fine. The problem is really with half-bridge modems that assign the router a public IP but send DHCP from their private LAN IP which is outside of the WAN subnet. The firewall prevents the lease from being renewed since the replies are coming from a different subnet than the WAN IP is in. After the lease expires, the WAN IP is lost, and the firewall no longer cares where the new DHCP lease comes from.

http://svn.dd-wrt.com/ticket/973

I lucked out and found a tech support agent at Windstream who knew her stuff and she walked me through manually bridging the modem, even though it was supposed to bridge itself if a router was downstream, and the issue is solved.

mine doesn't disconnect every 15 minutes but the DHCP problems are interesting.

 

[RMerlin]

What about if the WAN port on the router was malfunctioning? Wouldn't that cause the same behavior?

No. If the router WAN port was malfunctioning, the next DHCP lease it would obtain would be another 24.xxx.xxx.xxx from your ISP, not an internal 192.168.100.xxx from your modem. That 192 lease is the red erring here, it means the modem was not bridging your network with your ISP's DHCP server at that time - almost always a sign that the modem has just rebooted and isn't done yet re-establishing the link with the ISP.

 

[Requi3m]

Well I am embarrassed to admit you are right. It is the damn modem! I just realized there's a web interface with logs. And sure enough:

No Ranging Response received - T3 time-out;CM-MAC=7c:bf:b1:61:a5:3b;CMTS-MAC=00:1d:45:6f:d4:4d;CM-QOS=1.1;CM-VER=3.0;

Other people are mentioning this exact same error in the amazon reviews. People using the motorola SB6121, that is the problem! I will be buying a new modem. Thanks for your assistance and patience merlin. You only had to tell me three times.

It could possibly the signal level and I'm going to have a technician come out and look at it. But this seems to be a common issue with this modem.

SB6121 users view your log here: http://192.168.100.1/cmLogs.htm

 

[Pericynthion]

my 121 modem has been pretty good for nearly 2 years now - I do occasionally see the ranging error message, but its pretty much guaranteed to be Comcast in my case. I dread to think how many repeaters, and splits the cable goes through to get to me here ;-)

FWIW heres my current signal levels (no doubt someone will point out that I'm lucky to be getting a signal at all)

 

[RMerlin]

Glad you got the actual issue tracked down.

For the record, I use a Thomson DCM475 here, works flawlessly so far with my 30 Mbits cable connection (Vidéotron network, through Teksavvy). Supported modems are highly dependent on your actual ISP however. I think Rogers's network has problems with the Thomson modems, some specific FW revisions don't work very well there.