RT-N66U: Internet will cut out for a couple of mins a few times a day.

[GamerAsh]

Hey guys. two weeks I had the Asus N56U and I noticed that the internet was cutting out for a couple of mins every 4 hours or so. The internet would show as connected, and the router uptime would remain unchanged.

We rang our ISP (Virgin Media), and they told us to try using the their modem/router(the superhub) by it self. We did that, and for 2 days the connection was fine. So we thought the problem must have been the old router.

The superhub didn't offer enough features to use as a full time solution though. Today we bought the RT-N66U, and everything was running great until we got about 6 hours in when the same issue as before happened. It's done it about 3 times in a 12 hour period. I'll post snippets from the log:

Example 1(For some reason the earlier entry isn't in the log anymore. Does it reset at midnight): I remember it said this: WAN Connection: ISP's DHCP did not function properly. followed by the stuff below but with Ethernet link down in there too.

Example 2(What I find weird about this one is Ethernet link up is the first line when it disconnected):
Nov 17 03:27:24 WAN Connection: Ethernet link up.
Nov 17 03:27:24 rc_service: wanduck 347:notify_rc restart_wan_if 0
Nov 17 03:27:24 dnsmasq[459]: read /etc/hosts - 5 addresses
Nov 17 03:27:24 dnsmasq[459]: read /etc/hosts.dnsmasq - 1 addresses
Nov 17 03:27:24 dnsmasq-dhcp[459]: read /etc/ethers - 1 addresses
Nov 17 03:27:24 dnsmasq[459]: using nameserver 208.122.23.23#53
Nov 17 03:27:24 dnsmasq[459]: using nameserver 208.122.23.22#53
Nov 17 03:27:24 kernel: Attempt to kill tasklet from interrupt
Nov 17 03:27:25 kernel: br0: port 1(vlan1) entering disabled state
Nov 17 03:27:25 miniupnpd[520]: ioctl(s, SIOCGIFADDR, ...): Cannot assign requested address
Nov 17 03:27:25 miniupnpd[520]: Failed to get IP for interface eth0
Nov 17 03:27:25 miniupnpd[520]: SendNATPMPPublicAddressChangeNotification: cannot get public IP address, stopping
Nov 17 03:27:25 dnsmasq[459]: read /etc/hosts - 5 addresses
Nov 17 03:27:25 dnsmasq[459]: read /etc/hosts.dnsmasq - 1 addresses
Nov 17 03:27:25 dnsmasq-dhcp[459]: read /etc/ethers - 1 addresses
Nov 17 03:27:25 dnsmasq[459]: using nameserver 208.122.23.23#53
Nov 17 03:27:25 dnsmasq[459]: using nameserver 208.122.23.22#53
Nov 17 03:27:25 kernel: vlan1: dev_set_promiscuity(master, 1)
Nov 17 03:27:25 kernel: br0: port 1(vlan1) entering listening state
Nov 17 03:27:25 kernel: br0: port 1(vlan1) entering learning state
Nov 17 03:27:25 kernel: br0: topology change detected, propagating
Nov 17 03:27:25 kernel: br0: port 1(vlan1) entering forwarding state
Nov 17 03:27:25 dnsmasq[459]: read /etc/hosts - 5 addresses
Nov 17 03:27:25 dnsmasq[459]: read /etc/hosts.dnsmasq - 1 addresses
Nov 17 03:27:25 dnsmasq-dhcp[459]: read /etc/ethers - 1 addresses
Nov 17 03:27:25 dnsmasq[459]: using nameserver 208.122.23.23#53
Nov 17 03:27:25 dnsmasq[459]: using nameserver 208.122.23.22#53
Nov 17 03:27:26 dnsmasq[459]: read /etc/hosts - 5 addresses
Nov 17 03:27:26 dnsmasq[459]: read /etc/hosts.dnsmasq - 1 addresses
Nov 17 03:27:26 dnsmasq-dhcp[459]: read /etc/ethers - 1 addresses
Nov 17 03:27:26 dnsmasq[459]: using nameserver 208.122.23.23#53
Nov 17 03:27:26 dnsmasq[459]: using nameserver 208.122.23.22#53
Nov 17 03:27:26 rc_service: udhcpc 922:notify_rc start_firewall
Nov 17 03:27:26 start_nat_rules: apply the nat_rules(/tmp/nat_rules_eth0_eth0)!
Nov 17 03:27:26 dnsmasq[459]: exiting on receipt of SIGTERM
Nov 17 03:27:26 dnsmasq[929]: started, version 2.72test3 cachesize 1500
Nov 17 03:27:26 dnsmasq[929]: warning: interface ppp1* does not currently exist
Nov 17 03:27:26 dnsmasq[929]: asynchronous logging enabled, queue limit is 5 messages
Nov 17 03:27:26 dnsmasq-dhcp[929]: DHCP, IP range 192.168.1.2 -- 192.168.1.254, lease time 1d
Nov 17 03:27:26 dnsmasq[929]: read /etc/hosts - 5 addresses
Nov 17 03:27:26 dnsmasq[929]: read /etc/hosts.dnsmasq - 1 addresses
Nov 17 03:27:26 dnsmasq-dhcp[929]: read /etc/ethers - 1 addresses
Nov 17 03:27:26 rc_service: udhcpc 922:notify_rc stop_upnp
Nov 17 03:27:26 rc_service: udhcpc 922:notify_rc start_upnp
Nov 17 03:27:26 rc_service: waitting "stop_upnp" via udhcpc ...
Nov 17 03:27:26 dnsmasq[929]: using nameserver 208.122.23.23#53
Nov 17 03:27:26 dnsmasq[929]: using nameserver 208.122.23.22#53
Nov 17 03:27:26 miniupnpd[520]: shutting down MiniUPnPd
Nov 17 03:27:27 dhcp client: bound 192.168.100.2 via 192.168.100.1 during 30 seconds.
Nov 17 03:27:27 miniupnpd[957]: HTTP listening on port 37588
Nov 17 03:27:27 miniupnpd[957]: Listening for NAT-PMP/PCP traffic on port 5351
Nov 17 03:28:54 dnsmasq-dhcp[929]: DHCPREQUEST(br0) 192.168.1.170 90:a4:de:b9:ab:02
Nov 17 03:28:54 dnsmasq-dhcp[929]: DHCPACK(br0) 192.168.1.170 90:a4:de:b9:ab:02 Brian
Nov 17 03:29:14 miniupnpd[957]: ioctl(s, SIOCGIFADDR, ...): Cannot assign requested address
Nov 17 03:29:14 miniupnpd[957]: Failed to get IP for interface eth0
Nov 17 03:29:14 miniupnpd[957]: SendNATPMPPublicAddressChangeNotification: cannot get public IP address, stopping
Nov 17 03:29:14 miniupnpd[957]: ioctl(s, SIOCGIFADDR, ...): Cannot assign requested address
Nov 17 03:29:14 miniupnpd[957]: ioctl(s, SIOCGIFADDR, ...): Cannot assign requested address
Nov 17 03:29:14 dnsmasq[929]: read /etc/hosts - 5 addresses
Nov 17 03:29:14 dnsmasq[929]: read /etc/hosts.dnsmasq - 1 addresses
Nov 17 03:29:14 dnsmasq-dhcp[929]: read /etc/ethers - 1 addresses
Nov 17 03:29:14 dnsmasq[929]: using nameserver 208.122.23.23#53
Nov 17 03:29:14 dnsmasq[929]: using nameserver 208.122.23.22#53
Nov 17 03:29:15 rc_service: udhcpc 978:notify_rc start_firewall
Nov 17 03:29:15 dnsmasq[929]: read /etc/hosts - 5 addresses
Nov 17 03:29:15 dnsmasq[929]: read /etc/hosts.dnsmasq - 1 addresses
Nov 17 03:29:15 dnsmasq-dhcp[929]: read /etc/ethers - 1 addresses
Nov 17 03:29:15 dnsmasq[929]: using nameserver 208.122.23.23#53
Nov 17 03:29:15 dnsmasq[929]: using nameserver 208.122.23.22#53
Nov 17 03:29:15 start_nat_rules: apply the nat_rules(/tmp/nat_rules_eth0_eth0)!
Nov 17 03:29:15 dnsmasq[929]: exiting on receipt of SIGTERM
Nov 17 03:29:15 dnsmasq[985]: started, version 2.72test3 cachesize 1500
Nov 17 03:29:15 dnsmasq[985]: warning: interface ppp1* does not currently exist
Nov 17 03:29:15 dnsmasq[985]: asynchronous logging enabled, queue limit is 5 messages
Nov 17 03:29:15 dnsmasq-dhcp[985]: DHCP, IP range 192.168.1.2 -- 192.168.1.254, lease time 1d
Nov 17 03:29:15 dnsmasq[985]: read /etc/hosts - 5 addresses
Nov 17 03:29:15 dnsmasq[985]: read /etc/hosts.dnsmasq - 1 addresses
Nov 17 03:29:15 dnsmasq-dhcp[985]: read /etc/ethers - 1 addresses
Nov 17 03:29:15 dnsmasq[985]: using nameserver 208.122.23.23#53
Nov 17 03:29:15 dnsmasq[985]: using nameserver 208.122.23.22#53
Nov 17 03:29:15 rc_service: udhcpc 978:notify_rc stop_upnp
Nov 17 03:29:15 rc_service: waitting "start_firewall" via udhcpc ...
Nov 17 03:29:16 rc_service: udhcpc 978:notify_rc start_upnp
Nov 17 03:29:16 rc_service: waitting "stop_upnp" via udhcpc ...
Nov 17 03:29:16 miniupnpd[957]: shutting down MiniUPnPd
Nov 17 03:29:17 miniupnpd[1014]: HTTP listening on port 32913
Nov 17 03:29:17 miniupnpd[1014]: Listening for NAT-PMP/PCP traffic on port 5351
Nov 17 03:29:17 dhcp client: bound 82.27.141.11 via 82.27.140.1 during 556130 seconds.


I'm using the merlin firmware, and I don't have DDNS, AirCloud, or VPN turned on. However, I do have the USB option turned on to connect the printer.

I'm using unblock-us dns settings so we can watch american netflix.

I've tried to supply as much information I can and any help would be greatly appreciated.

 

[RMerlin]

If the Ethernet link went down, then it means the modem disappeared. Issue is the cable between the modem and the router, the modem itself, or the ISP link went down leading your modem to reboot.

 

[GamerAsh]

If the Ethernet link went down, then it means the modem disappeared. Issue is the cable between the modem and the router, the modem itself, or the ISP link went down leading your modem to reboot.

We've left the modem and router unplugged for 30 mins to refresh the connections, and we're using a different cat6 ethernet to link the router and modem so hopefully that will rectify some things.

Is it possible it could be a bad modem even though the connection worked perfectly when just using the modem's router functionality instead of an external router?

 

[GamerAsh]

It just happened again within 40 mins of the previous attempts of fixing it. I noticed it doesn't actually say ethernet link down this time. Here is the log:
Nov 17 18:20:00 WAN Connection: Ethernet link up.
Nov 17 18:20:00 rc_service: wanduck 345:notify_rc restart_wan_if 0
Nov 17 18:20:00 dnsmasq[477]: read /etc/hosts - 5 addresses
Nov 17 18:20:00 dnsmasq[477]: read /etc/hosts.dnsmasq - 1 addresses
Nov 17 18:20:00 dnsmasq-dhcp[477]: read /etc/ethers - 1 addresses
Nov 17 18:20:00 dnsmasq[477]: using nameserver 208.122.23.23#53
Nov 17 18:20:00 dnsmasq[477]: using nameserver 208.122.23.22#53
Nov 17 18:20:00 miniupnpd[523]: ioctl(s, SIOCGIFADDR, ...): Cannot assign requested address
Nov 17 18:20:00 miniupnpd[523]: Failed to get IP for interface eth0
Nov 17 18:20:00 miniupnpd[523]: SendNATPMPPublicAddressChangeNotification: cannot get public IP address, stopping
Nov 17 18:20:00 dnsmasq[477]: read /etc/hosts - 5 addresses
Nov 17 18:20:00 dnsmasq[477]: read /etc/hosts.dnsmasq - 1 addresses
Nov 17 18:20:00 dnsmasq-dhcp[477]: read /etc/ethers - 1 addresses
Nov 17 18:20:00 kernel: Attempt to kill tasklet from interrupt
Nov 17 18:20:01 dnsmasq[477]: using nameserver 208.122.23.23#53
Nov 17 18:20:01 dnsmasq[477]: using nameserver 208.122.23.22#53
Nov 17 18:20:01 kernel: br0: port 1(vlan1) entering disabled state
Nov 17 18:20:01 kernel: vlan1: dev_set_promiscuity(master, 1)
Nov 17 18:20:01 kernel: br0: port 1(vlan1) entering learning state
Nov 17 18:20:01 kernel: br0: topology change detected, propagating
Nov 17 18:20:01 kernel: br0: port 1(vlan1) entering forwarding state
Nov 17 18:20:03 dnsmasq[477]: read /etc/hosts - 5 addresses
Nov 17 18:20:03 dnsmasq[477]: read /etc/hosts.dnsmasq - 1 addresses
Nov 17 18:20:03 dnsmasq-dhcp[477]: read /etc/ethers - 1 addresses
Nov 17 18:20:03 dnsmasq[477]: using nameserver 208.122.23.23#53
Nov 17 18:20:03 dnsmasq[477]: using nameserver 208.122.23.22#53
Nov 17 18:20:08 WAN Connection: ISP's DHCP did not function properly.
Nov 17 18:22:05 dnsmasq-dhcp[477]: DHCPREQUEST(br0) 192.168.1.209 20:68:9d:46:22:98
Nov 17 18:22:05 dnsmasq-dhcp[477]: DHCPACK(br0) 192.168.1.209 20:68:9d:46:22:98 Marie-PC
Nov 17 18:22:06 miniupnpd[523]: ioctl(s, SIOCGIFADDR, ...): Cannot assign requested address
Nov 17 18:22:06 miniupnpd[523]: ioctl(s, SIOCGIFADDR, ...): Cannot assign requested address
Nov 17 18:22:53 rc_service: udhcpc 666:notify_rc start_firewall
Nov 17 18:22:53 dnsmasq[477]: read /etc/hosts - 5 addresses
Nov 17 18:22:53 dnsmasq[477]: read /etc/hosts.dnsmasq - 1 addresses
Nov 17 18:22:53 dnsmasq-dhcp[477]: read /etc/ethers - 1 addresses
Nov 17 18:22:53 dnsmasq[477]: using nameserver 208.122.23.23#53
Nov 17 18:22:53 dnsmasq[477]: using nameserver 208.122.23.22#53
Nov 17 18:22:53 start_nat_rules: apply the nat_rules(/tmp/nat_rules_eth0_eth0)!
Nov 17 18:22:53 dnsmasq[477]: exiting on receipt of SIGTERM
Nov 17 18:22:53 dnsmasq[673]: started, version 2.72test3 cachesize 1500
Nov 17 18:22:53 dnsmasq[673]: warning: interface ppp1* does not currently exist
Nov 17 18:22:53 dnsmasq[673]: asynchronous logging enabled, queue limit is 5 messages
Nov 17 18:22:53 dnsmasq-dhcp[673]: DHCP, IP range 192.168.1.2 -- 192.168.1.254, lease time 1d
Nov 17 18:22:53 dnsmasq[673]: read /etc/hosts - 5 addresses
Nov 17 18:22:53 dnsmasq[673]: read /etc/hosts.dnsmasq - 1 addresses
Nov 17 18:22:53 dnsmasq-dhcp[673]: read /etc/ethers - 1 addresses
Nov 17 18:22:53 miniupnpd[523]: upnp_event_notify_connect: connect(9, 192.168.1.90, 16): Network is unreachable
Nov 17 18:22:53 miniupnpd[523]: upnp_event_notify_connect: connect(4, 192.168.1.209, 16): Network is unreachable
Nov 17 18:22:53 rc_service: udhcpc 666:notify_rc stop_upnp
Nov 17 18:22:53 rc_service: waitting "start_firewall" via udhcpc ...
Nov 17 18:22:53 dnsmasq[673]: using nameserver 208.122.23.23#53
Nov 17 18:22:53 dnsmasq[673]: using nameserver 208.122.23.22#53
Nov 17 18:22:54 rc_service: udhcpc 666:notify_rc start_upnp
Nov 17 18:22:54 rc_service: waitting "stop_upnp" via udhcpc ...
Nov 17 18:22:54 miniupnpd[523]: shutting down MiniUPnPd
Nov 17 18:22:55 dhcp client: bound 82.27.141.11 via 82.27.140.1 during 502511 seconds.
Nov 17 18:22:55 miniupnpd[701]: HTTP listening on port 33774
Nov 17 18:22:55 miniupnpd[701]: Listening for NAT-PMP/PCP traffic on port 5351
Nov 17 18:22:58 WAN Connection: WAN was restored.

 

[RMerlin]

It just happened again within 40 mins of the previous attempts of fixing it. I noticed it doesn't actually say ethernet link down this time. Here is the log:

See if that modem has any web interface where you could see if the modem rebooted itself (many devices will report an uptime).

If it did, contact your ISP about it, tell him your modem reboots itself randomly.

If it didn't, it could be some odd compatibility issue between the two. I've seen a few cases, people typicall resolved it by installing a cheap network switch between the modem and the router.

 

[GamerAsh]

See if that modem has any web interface where you could see if the modem rebooted itself (many devices will report an uptime).

If it did, contact your ISP about it, tell him your modem reboots itself randomly.

If it didn't, it could be some odd compatibility issue between the two. I've seen a few cases, people typicall resolved it by installing a cheap network switch between the modem and the router.

The modem sadly doesn't have logs when it's in modem only mode. You can only access those when you enable it as a router.

We had the n55u for a long time with the modem and we never had any trouble until recently. I'm thinking the ISP has changed something, but when we rang them they told us to basically just use their modem/router.

I'll try turning off DCHP(Since thats the error coming up), and if it does it again i'll use a switch I have, and check the logs in the morning.

Thanks for your help through this merlin. Your firmware is great.

 

[RMerlin]

Don't turn DHCP off, you will create far more serious issues if you do.

 

[ColinTaylor]

The modem sadly doesn't have logs when it's in modem only mode. You can only access those when you enable it as a router.

Even in modem mode you can go to the routers web page at 192.168.100.1 and at the top right corner of the page is the Router Status button.

Click that and you can find the status information and network log.

 

[owlyn]

It is more likely that the modem is disconnecting. I just had the same symptoms, and I found that the modem would enter a Unicast Maintenance Ranging state, and not get any responses. It would increase the Upstream level until it reached the maximum, and then reboot. This would happen about twice a day. I finally put in a bi-directional amp (I had one laying around that I bought at Radio Shack to use with a previous modem). This decreased the upstream level on my modem (a good thing), and so far, the modem has not rebooted, or gotten stuck in the Unicast Maintenance mode. It's been two full days. The US and DS signal levels have been holding pretty steady, too.

 

[nemesis122]

same issue with merlin firmeware bigger as 339

Hi all

I have the same issue with merlin firmeware newer as 374.39 with 374.39 all is ok and run very fast with firmeware newer as 339 the internetconnection is lost and then the modem hangs up (lost signal to the cableprovider).
And i have changed the Modem UBee (Complete new from the cableprovider) and the Router(I have 2 RT N66u) and all Lan Cable between the Modem and Router and Switch( Cat 6)
This issues only happen with Merlin Firmeware biggers as 374.39 so in this case as example for 374.40 until 374.47.
With 374.39 no issues there must be a change in the newer firmeware that this issue is caused.
Internetconnection 250 mbit down and 20 mbit up UPC Cablecom Swiss Cable provider.
The Problem is caused with big load on the internetconnection and en other PC use skype(only en example) also with heavy load from Bittorrent then the internetconnection goes down i dont know exactly why.
I have at home 22 Client wired and wireless and always big load on the internetconnection and in the network and with 339 all run very fast.
Someone knows is there a Problem with firmeware newer as 374.39 ??
My Friend has the same setup Provider Cablemodem and Router and the issue is also happen with this newer firmeware as 374.39!

I found that this must be the problem :

My other assumption is the router will not send some DHCP Ip's adresses to the client and then the Modem (has 3 External IP adresses) will send en IP for the DHCP client instead then Router and als example when there is no external IP for the router because the modem will reboot.
My DHCP Pool in the Router is 192.168.1.2 to 192.168.199.
This must be the Problem and i dont know why this happen any Suggestion for this ?????
Thank you for your feedback.
BR

Michael

I have a en idee but im not sure i think the router will change the external ip to en local network ip as example the ip is 46..... and the router will change the external ip to 192...and then the internetconnetion goes down i have then to switch off the router and reboot them modem only with firmewares newer as 339
Also is posbile to threre is en issue with the lease time the Router will not renew the external ip from the modem thats only speculations i have no clue exactly why.
Also is possbilet hat there is en issue with NAT.

 

[BlauUmlaut]

Good morning -

I saw this post and thought I would stop lurking and register.

My home network experiences something very similar. I need to figure out how to start logging events.

 

[nemesis122]

this must be the problem only happen with firmeware newer as 339.

My other assumption is the router will not send some DHCP Ip's adresses to the client and then the Modem (has 3 External IP adresses) will send en IP for the DHCP client instead then Router and als example when there is no external IP for the router because the modem will reboot.
My DHCP Pool in the Router is 192.168.1.2 to 192.168.1.199.
This must be the Problem and i dont know why this happen any Suggestion for this ?????

See this logfile from the start from this thread that is this what is happen :
17 03:29:14 miniupnpd[957]: Failed to get IP for interface eth0
Nov 17 03:29:15 rc_service: udhcpc 978:notify_rc stop_upnp
Nov 17 03:29:15 rc_service: waitting "start_firewall" via udhcpc ...
Nov 17 03:29:16 rc_service: udhcpc 978:notify_rc start_upnp
Nov 17 03:29:16 rc_service: waitting "stop_upnp" via udhcpc ...
Nov 17 03:29:16 miniupnpd[957]: shutting down MiniUPnPd

This means there is some broken NAT or DHCP or UPNP issues im 100 sure this log line is only happen in newer firmeware as 339.

 

[ColinTaylor]

Hi Guys,

This problem has nothing to do with DHCP.

I have the same ISP and cable modem as the OP. I have just simulated the cable modem rebooting (by turning it off and on). Here is the relevant section of the log:

Nov 18 17:07:00 WAN Connection: Ethernet link up.
Nov 18 17:07:00 rc_service: wanduck 306:notify_rc restart_wan_if 0
Nov 18 17:07:00 stop_wan(): perform DHCP release
:
Nov 18 17:07:06 WAN Connection: ISP's DHCP did not function properly.
:
Nov 18 17:07:21 WAN Connection: Ethernet link up.
Nov 18 17:07:21 rc_service: wanduck 306:notify_rc restart_wan_if 0
Nov 18 17:07:21 stop_wan(): perform DHCP release
:
Nov 18 17:07:26 dhcp client: bound 192.168.100.2 via 192.168.100.1 during 30 seconds.
:
Nov 18 17:07:29 WAN Connection: WAN was restored.
:
Nov 18 17:08:09 WAN Connection: ISP's DHCP did not function properly.
:
Nov 18 17:08:10 dhcp client: bound 81.102.242.34 via 81.102.242.1 during 427917 seconds.
:
Nov 18 17:08:14 WAN Connection: WAN was restored.

These are normal messages for when the modem has rebooted itself.

The problem is with the modem or ISP (Virgin Media).

@GamerAsh: You'll have to talk to VM again. I know from experience how painful that can be! Tell them that the router is rebooting itself. If you're lucky enough to be speaking to someone who isn't in their Indian call centre they should be able to diagnose the fault.

Even if the Superhub works in "router" mode it should still work in "modem" mode. If it doesn't get them to replace the Superhub.

If you don't get anywhere on the phone I suggest you post a message on their forum. It takes a few days for them to respond but they know their stuff, unlike some of the people on the phone.

http://community.virginmedia.com/t5/Up-to-60Mb-Setup-Equipment/Superhub-keeps-rebooting/td-p/2439341

 

[RMerlin]

My other assumption is the router will not send some DHCP Ip's adresses to the client and then the Modem (has 3 External IP adresses) will send en IP for the DHCP client instead then Router and als example when there is no external IP for the router because the modem will reboot.
My DHCP Pool in the Router is 192.168.1.2 to 192.168.1.199.
This must be the Problem and i dont know why this happen any Suggestion for this ?????

See this logfile from the start from this thread that is this what is happen :
17 03:29:14 miniupnpd[957]: Failed to get IP for interface eth0
Nov 17 03:29:15 rc_service: udhcpc 978:notify_rc stop_upnp
Nov 17 03:29:15 rc_service: waitting "start_firewall" via udhcpc ...
Nov 17 03:29:16 rc_service: udhcpc 978:notify_rc start_upnp
Nov 17 03:29:16 rc_service: waitting "stop_upnp" via udhcpc ...
Nov 17 03:29:16 miniupnpd[957]: shutting down MiniUPnPd

This means there is some broken NAT or DHCP or UPNP issues im 100 sure this log line is only happen in newer firmeware as 339.

You are missing the big elephant in the room here in that first posted log:

Nov 17 03:27:24 WAN Connection: Ethernet link up

The Ethernet connection physically went down. This has nothing to do with DHCP, configuration, NAT or anything software - the modem physically disappeared from the router's Ethernet jack. That is the core element of the problem that must be troubleshooted according to what was already posted in this thread. Everything else in the log after this line is just a symptom of the root cause - modem was no longer visible for a certain period of time.

 

[nemesis122]

i have no idee i know only one thing.

Hi Merlin

I know only that my friend and myself have big problems with firmeware newer as 339.
That is what i know and always when we have a big load or many connections on the interconnection that Router hang up and after them we have to restart Modem and Router and that is only happen with firmeware newer as 339. that is what i know.
And the logfile is nearly the same as postet in first post.
DHCP from the ISP works not properly and then the WAN Port goes down.
And im not a networkspecialist in this case but i think the issue appears the router will not send under heavy load en ip or DNS to to the client and then the Modem has 3 IP external ip adresses and will send to the client beucase the router will not send the ip or dns and after them the router has no external ip adress from the Modem(ISP) and then the internet goes down.

I know its strange but im 100% sure this is firmeware related because i have changed everything in my envirmoment ( 2 Router N66u , all Lan Cables, 2 New Modems UBEE, and the main cable from the ISP ) and the problem comes up again and again then i went back to firmeware 339 and all working very fast NP with over 500 connections on 3 Servers 22 Client etc.
That is what i know and i hope the day will coming that you believe me that this is firmeware related.

Excuse my english is not my main Language.
That is my Modem :
http://www.ubeeinteractive.com/products/cable/evw3230

So i will stay with the old firmeware and im happy all runs very fine with firmeware 339 with 345 and 347 i have only troubles and i dont know exactly why.

thank you

Michael

 

[nemesis122]

kills internetconnection again with firmeware 339

Hi all

with Firmeware 339 i have also that the internetconnection goes down.
I think now that plex Media server kills the router or Modem.
BR

Michael

 

[nemesis122]

the issue is solved for me

Hi all
I have now tested 4 Asus Routers and all have the same WAN disconnects
RT-N66U = disconnected under heavy Load with asus and Merlin Firmwares / my friend has the same Problem with the same server hardware and ISP.
RT-Ac66U= Disconnected under heavy Load
RT-Ac68u= Disconneted and rebooted after 15 min with no Load.

Then i flashed tomato on the asus routers and all is working fine / no disconnetcs the problem is here fast nat. I have 250mbit connection and tomato has only 140 mbit downstream because fast nat is not enabled.
Now I switched toTP link Router and all is working perfect realy realy perfect better wlan more throughput in the internal network more range for the 5ghz wlan.
Im Happy.

I will now sell my 4 Asus Routers
BR

Michael

 

[hggomes]

What kind of ISP you have? How connections are made?