Aus RT-N66U Issue

[Diggs24]

First off I must confess I am not super tech savvy. This has me a bit stumped. I've had the RT-N66U for about a year now. About 6 months ago I used my old router as a secondary access point to extend coverage to the rest of my house. It is hard wired to my Asus. I have not had any issues until a few months ago so don't think adding the other router caused it but wanted to throw that out there. Firmware is stock and besides changing some settings like forcing the 2.4 ghz channel to 1 and setting wireless N only it is unchanged from default. My issue is not just the wireless, but also wired as this computer is hardwired to the router and has the same issue as any other wireless devices.

The issue:
The ethernet link goes down. Some days it's fine, and others (such as now) it is bad.

Here is my log:

Jan 25 16:45:39 WAN Connection: Ethernet link down.
Jan 25 16:45:39 stop_nat_rules: apply the redirect_rules!
Jan 25 16:45:44 WAN Connection: Ethernet link up.
Jan 25 16:45:44 rc_service: wanduck 324:notify_rc restart_wan_if 0
Jan 25 16:45:44 stop_wan(): perform DHCP release
Jan 25 16:45:44 kernel: Attempt to kill tasklet from interrupt
Jan 25 16:45:44 start_nat_rules: apply the nat_rules(/tmp/nat_rules_eth0_eth0)!
Jan 25 16:45:45 rc_service: udhcpc 4722:notify_rc stop_upnp
Jan 25 16:45:45 miniupnpd[4607]: received signal 15, good-bye
Jan 25 16:45:45 rc_service: udhcpc 4722:notify_rc start_upnp
Jan 25 16:45:45 miniupnpd[4751]: HTTP listening on port 45410
Jan 25 16:45:45 miniupnpd[4751]: Listening for NAT-PMP traffic on port 5351
Jan 25 16:45:45 dhcp client: bound 64.126.34.221 via 64.126.32.1 during 28800 seconds.
Jan 25 16:45:49 WAN Connection: WAN was restored.
Jan 25 16:51:42 WAN Connection: Ethernet link down.
Jan 25 16:51:42 stop_nat_rules: apply the redirect_rules!
Jan 25 16:51:47 WAN Connection: Ethernet link up.
Jan 25 16:51:47 rc_service: wanduck 324:notify_rc restart_wan_if 0
Jan 25 16:51:47 stop_wan(): perform DHCP release
Jan 25 16:51:47 kernel: Attempt to kill tasklet from interrupt
Jan 25 16:51:51 start_nat_rules: apply the nat_rules(/tmp/nat_rules_eth0_eth0)!
Jan 25 16:51:51 rc_service: udhcpc 4763:notify_rc stop_upnp
Jan 25 16:51:51 miniupnpd[4751]: received signal 15, good-bye
Jan 25 16:51:51 rc_service: udhcpc 4763:notify_rc start_upnp
Jan 25 16:51:51 miniupnpd[4792]: HTTP listening on port 42451
Jan 25 16:51:51 miniupnpd[4792]: Listening for NAT-PMP traffic on port 5351
Jan 25 16:51:51 dhcp client: bound 64.126.34.221 via 64.126.32.1 during 28800 seconds.
Jan 25 16:51:53 WAN Connection: WAN was restored.
Jan 25 17:03:48 WAN Connection: Ethernet link down.
Jan 25 17:03:48 stop_nat_rules: apply the redirect_rules!
Jan 25 17:03:53 WAN Connection: Ethernet link up.
Jan 25 17:03:53 rc_service: wanduck 324:notify_rc restart_wan_if 0
Jan 25 17:03:53 stop_wan(): perform DHCP release
Jan 25 17:03:53 kernel: Attempt to kill tasklet from interrupt
Jan 25 17:03:54 start_nat_rules: apply the nat_rules(/tmp/nat_rules_eth0_eth0)!
Jan 25 17:03:54 rc_service: udhcpc 4805:notify_rc stop_upnp
Jan 25 17:03:54 miniupnpd[4792]: received signal 15, good-bye
Jan 25 17:03:54 rc_service: udhcpc 4805:notify_rc start_upnp
Jan 25 17:03:54 miniupnpd[4834]: HTTP listening on port 60749
Jan 25 17:03:54 miniupnpd[4834]: Listening for NAT-PMP traffic on port 5351
Jan 25 17:03:54 dhcp client: bound 64.126.34.221 via 64.126.32.1 during 28800 seconds.
Jan 25 17:03:59 WAN Connection: WAN was restored.
Jan 25 17:07:54 WAN Connection: Ethernet link down.
Jan 25 17:07:54 stop_nat_rules: apply the redirect_rules!
Jan 25 17:07:59 WAN Connection: Ethernet link up.
Jan 25 17:07:59 rc_service: wanduck 324:notify_rc restart_wan_if 0
Jan 25 17:07:59 stop_wan(): perform DHCP release
Jan 25 17:07:59 kernel: Attempt to kill tasklet from interrupt
Jan 25 17:08:00 start_nat_rules: apply the nat_rules(/tmp/nat_rules_eth0_eth0)!
Jan 25 17:08:00 rc_service: udhcpc 4846:notify_rc stop_upnp
Jan 25 17:08:00 miniupnpd[4834]: received signal 15, good-bye
Jan 25 17:08:00 rc_service: udhcpc 4846:notify_rc start_upnp
Jan 25 17:08:00 miniupnpd[4875]: HTTP listening on port 55345
Jan 25 17:08:00 miniupnpd[4875]: Listening for NAT-PMP traffic on port 5351
Jan 25 17:08:00 dhcp client: bound 64.126.34.221 via 64.126.32.1 during 28800 seconds.
Jan 25 17:08:04 WAN Connection: WAN was restored.


As you can see today is a bad day.

I have tried unplugging the router and modem. I've read maybe the cable is bad, but I don't need to touch anything and it will come back. I think I am going to replace the cable between the modem and router anyways, but open to anyone that might know why this is happening? Maybe the modem is on its way out? It is from the ISP and is a good 5 years old. Thanks in advance.

 

[RMerlin]

Most common issues for WAN link going down are:

- Bad Ethernet cable
- Modem crashes and reboots
- Cablemodem losing sync, and rebooting to re-negotiate channels with the ISP's equipment

 

[Diggs24]

Most common issues for WAN link going down are:

- Bad Ethernet cable
- Modem crashes and reboots
- Cablemodem losing sync, and rebooting to re-negotiate channels with the ISP's equipment

Thanks RMerlin for the response. I will replace the cable and see if that works. If not, on to the ISP for a new modem.

 

[Diggs24]

Most common issues for WAN link going down are:

- Bad Ethernet cable
- Modem crashes and reboots
- Cablemodem losing sync, and rebooting to re-negotiate channels with the ISP's equipment

Sorry, I'm back. Replaced the cable between the router and modem but still having the issue. In the above, what is the difference between a modem and a cablemodem? I do not have TV cable, just internet.

I have this modem (but it actually says Scientific Atlanta on it):

http://www.amazon.com/dp/B002V41X2M/?tag=snbforums-20

I'm going to ask them to replace it. There is also the box on the back of my house. Anything in there they should investigate while I have them looking into this?

TIA and I appreciate the help.

 

[RMerlin]

Sorry, I'm back. Replaced the cable between the router and modem but still having the issue. In the above, what is the difference between a modem and a cablemodem? I do not have TV cable, just internet.

I have this modem (but it actually says Scientific Atlanta on it):

http://www.amazon.com/dp/B002V41X2M/?tag=snbforums-20

I'm going to ask them to replace it. There is also the box on the back of my house. Anything in there they should investigate while I have them looking into this?

TIA and I appreciate the help.

A cablemodem is used when your ISP brings a coax cable into your house, similar to cable TV, but carrying only Internet access.

In your case, this is a cablemodem (an older DOCSIS 2.0, to be more accurate - the current standard is DOCSIS 3.0).

Ask your ISP to check for signal issues first, it could be a wiring issue as well if your modem does reboot itself in an attempt to resync.