Posted: Mon Oct 20, 2014 8:01 Post subject: Netgear WNDR4300 Internet connection drops
Having an odd issue.
At least once a day my connection is "reset" when using DD-WRT, however using either stock firmware or connecting directly to the modem doesn't exhibit this issue.
I have actually gone as far as doing the 30/30/30 on the modem AND router and even manually re-entered all my settings.
This is a hassle as I have port forwarding, reserved IP's, and QOS rules in place.
Can anyone help me?
I have build 24160 installed. If needed I can provide more info. Just ask.
Here is a grab of the syslog from a little before it happened and after my connection was re-established:
hostapd: ath0: sta e0:XX:XX:XX:XX:c2 wpa: group key handshake completed (rsn)
hostapd: ath0: sta 64:XX:XX:XX:XX:00 wpa: group key handshake completed (rsn)
hostapd: ath1: sta 04:XX:XX:XX:XX:56 wpa: group key handshake completed (rsn)
<6>oct 20 02:24:52 kernel: [172837.320000] device vlan2 entered promiscuous mode
syslog: igmprt : multicast daemon successfully stopped
igmpproxy[2550]: select() failure; errno(4): interrupted system call
<6>oct 20 02:24:52 kernel: [172837.370000] device vlan2 left promiscuous mode
syslog: pppd : ppp daemon successfully stopped
pppd[6421]: pppd 2.4.6 started by root, uid 0
syslog: vpn modules : vpn modules successfully unloaded
syslog: vpn modules : nf_conntrack_proto_gre successfully loaded
syslog: vpn modules : nf_nat_proto_gre successfully loaded
syslog: vpn modules : nf_conntrack_pptp successfully loaded
syslog: vpn modules : nf_nat_pptp successfully loaded
syslog: process_monitor : process monitor successfully stopped
syslog: process_monitor successfully started
syslog: ddns : inadyn daemon successfully started
syslog: vpn modules : vpn modules successfully unloaded
syslog: vpn modules : nf_conntrack_proto_gre successfully loaded
syslog: vpn modules : nf_nat_proto_gre successfully loaded
syslog: vpn modules : nf_conntrack_pptp successfully loaded
syslog: vpn modules : nf_nat_pptp successfully loaded
<6>oct 20 02:24:54 kernel: [172839.310000] imq driver unloaded successfully.
syslog: wland : wlan daemon successfully stopped
syslog: vpn modules : vpn modules successfully unloaded
syslog: vpn modules : nf_conntrack_proto_gre successfully loaded
syslog: vpn modules : nf_nat_proto_gre successfully loaded
syslog: vpn modules : nf_conntrack_pptp successfully loaded
syslog: vpn modules : nf_nat_pptp successfully loaded
<6>oct 20 02:24:55 kernel: [172840.390000] imq driver loaded successfully. (numdevs = 2, numqueues = 1)
<6>oct 20 02:24:55 kernel: [172840.400000] ?hooking imq before nat on prerouting.
<6>oct 20 02:24:55 kernel: [172840.410000] ?hooking imq after nat on postrouting.
syslog: wland : wlan daemon successfully started
syslog: wan is up. ip: 75.56.49.112
syslog: igmprt : multicast daemon successfully started
process_monitor[6482]: we need to re-update after 3600 seconds
process_monitor[6482]: set timer: 3600 seconds, callback: ntp_main()
You provided no information a year ago, and none now. No hardware/model#. No configuration. And from what I can tell, you posted your os booting. That doesn't diagnose anything disconnecting when it isn't disconnecting. You usually want to observe it disconnecting, if at all possible.
In any case, could you provide some information about your router, modem, and config please?
Well, I did state that I am working with a Netgear 4300 for the router.
As for the modem, it's a D-Link DBL-2320B set up in bridge mode.
That log snippet is actually from when it lost the connection and re-connected.
Nothing was powered off, and I didn't modify the log.
As for my configuration, it doesn't seem to matter what I do. I connect via PPPoE, and if I let the router run with no other configuration and wireless disabled, I have the issue that I have with my standard configuration.
I use a limited IP range, DDNS setup to update my OpenDNS account, port forwarding and QOS rules for games and Netflix, and static IP address assignments.
I have made sure that there is no scheduled reboot on the router.
If I observe it disconnect, the LED never indicates a loss in the connection, and as you can see the log doesn't seem to show anything specific.
If any more information is needed, I will provide what I can.
Ok, as of now, I just started wall watcher with a fresh connection.
When it drops and re-connects again, I will pull an exert from the logs and post it here, as well as post the FULL log file.
The full log file will be uploaded and a link will be provided here.
Obviously, I will censor MAC addresses, and anything that I feel proposes a security risk.
If there is another program I should use, or specific settings please let me know.
I have it set to log router messages, all WW, and All router traffic. Use sub-types is also enabled.
Literally JUST happened, here is the Log for today.
2015/08/06 00:13:44.23 M <7>aug 6 05:13:48 kernel: [1633580.050000] udp: bad checksum. from ***.***.***.***:***** to ***.***.***.***:***** ulen 319
2015/08/06 00:58:49.59 M hostapd: ath0: sta "MAC ADDRESS" wpa: group key handshake completed (rsn)
2015/08/06 00:58:49.60 M hostapd: ath0: sta "MAC ADDRESS" wpa: group key handshake completed (rsn)
2015/08/06 00:58:55.64 M : inadyn : dynamic dns daemon successfully stopped
2015/08/06 00:59:10.66 M <6>aug 6 05:59:15 kernel: [1636306.640000] device vlan2 entered promiscuous mode
2015/08/06 00:59:11.19 M : igmprt : multicast daemon successfully stopped
2015/08/06 00:59:11.19 M igmpproxy[3641]: select() failure; errno(4): interrupted system call
2015/08/06 00:59:11.19 M igmpproxy[3641]: mrt_drop_membership failed; errno(19): no such device
2015/08/06 00:59:11.19 M igmpproxy[3641]: mrt_drop_membership failed; errno(19): no such device
2015/08/06 00:59:11.23 M <6>aug 6 05:59:15 kernel: [1636307.210000] device vlan2 left promiscuous mode
2015/08/06 00:59:11.23 M : pppd : ppp daemon successfully stopped
2015/08/06 00:59:11.40 M pppd[31874]: pppd 2.4.7 started by root, uid 0
2015/08/06 00:59:12.14 M : vpn modules : vpn modules successfully unloaded
2015/08/06 00:59:12.16 M : vpn modules : nf_conntrack_proto_gre successfully loaded
2015/08/06 00:59:12.19 M : vpn modules : nf_nat_proto_gre successfully loaded
2015/08/06 00:59:12.21 M : vpn modules : nf_conntrack_pptp successfully loaded
2015/08/06 00:59:12.23 M : vpn modules : nf_nat_pptp successfully loaded
2015/08/06 00:59:12.42 M : process_monitor : process monitor successfully stopped
2015/08/06 00:59:12.43 M : process_monitor successfully started
2015/08/06 00:59:12.46 M : ddns : inadyn daemon successfully started
2015/08/06 00:59:13.32 M : vpn modules : vpn modules successfully unloaded
2015/08/06 00:59:13.35 M : vpn modules : nf_conntrack_proto_gre successfully loaded
2015/08/06 00:59:13.41 M : vpn modules : nf_nat_proto_gre successfully loaded
2015/08/06 00:59:13.41 M : vpn modules : nf_conntrack_pptp successfully loaded
2015/08/06 00:59:13.42 M : vpn modules : nf_nat_pptp successfully loaded
2015/08/06 00:59:13.61 M <6>aug 6 05:59:18 kernel: [1636309.600000] imq driver unloaded successfully.
2015/08/06 00:59:13.71 M : wland : wlan daemon successfully stopped
2015/08/06 00:59:13.76 M <6>aug 6 05:59:18 kernel: [1636309.730000] imq driver loaded successfully. (numdevs = 2, numqueues = 1)
2015/08/06 00:59:13.76 M <6>aug 6 05:59:18 kernel: [1636309.730000] ?hooking imq before nat on prerouting.
2015/08/06 00:59:13.76 M <6>aug 6 05:59:18 kernel: [1636309.740000] ?hooking imq after nat on postrouting.
2015/08/06 00:59:15.02 M process_monitor[31972]: we need to re-update after 3600 seconds
2015/08/06 00:59:15.02 M process_monitor[31972]: set timer: 3600 seconds, callback: ntp_main()
2015/08/06 00:59:16.26 M : wland : wlan daemon successfully started
2015/08/06 00:59:16.32 M : wan is up. ip: ***.***.***.***
2015/08/06 00:59:16.34 M : igmprt : multicast daemon successfully started
2015/08/06 01:01:08.54 M igmpproxy[32667]: the origin for route 239.255.***.*** changed from 192.168.***.*** to 192.168.***.***
2015/08/06 01:01:30.08 E (Stopping - by user)
Here is a link to all the logs I have since I started on OneDrive. I only blocked out the IP addresses and MAC addresses, no other alterations were done.
If wanted, I will simply post the logs.
http://1drv.ms/1NbuvtI
I forgot to provide what I have observed from the hardware.
Aside from anything I'm doing online being halted, everything else works fine.
The modem stays on and connected, and the router LED's all operate normally. The power and Internet LED stay solid green, and anything that's trying to connect to the Internet blinks. All internal network traffic stays active without a single drop.
Joined: 03 Jan 2010 Posts: 7568 Location: YWG, Canada
Posted: Wed Aug 12, 2015 8:22 Post subject:
so it happens when ur plugged into it, assuming..since u said u disabled wifi before.
is the isp pppoe? do u HAVE to use pppoe? pppoe has had about a bus & a half load of random varying problems across multiple routers over the last year or 2..can u give a screenshot showing full pppoe settings, blank out username/password.. _________________ LATEST FIRMWARE(S)
BrainSlayer wrote:
we just do it since we do not like any restrictions enforced by stupid cocaine snorting managers
Joined: 03 Jan 2010 Posts: 7568 Location: YWG, Canada
Posted: Wed Aug 12, 2015 9:07 Post subject:
why did u increase keep alive redial period? it could be too long at 2 minutes, try the default which is 30 seconds.
ignore what the help file says for it, u cant enter the values it examples i just tried it so there goes that idea.. _________________ LATEST FIRMWARE(S)
BrainSlayer wrote:
we just do it since we do not like any restrictions enforced by stupid cocaine snorting managers
why did u increase keep alive redial period? it could be too long at 2 minutes, try the default which is 30 seconds.
ignore what the help file says for it, u cant enter the values it examples i just tried it so there goes that idea..
Actually, I didn't modify any of those values. The only area I altered advanced settings was in wireless for the correct regulatory domain.
However, it did let me change the keep alive value to 30 seconds. Unfortunately, I won;t know if that did anything for a day.
I will post either when the connection drops, or three days of a solid connection.
