NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Ethernet randomly disconnects for a few seconds
Hey all, so I've been fighting this issue with my XR500 for about 2 months now. Out of the blue, my desktop would randomly lose connection for a few seconds and then regain connection. As far as I ca...
Not that I'm aware of. All I know for sure is if I restart the router, the 30 minutes thing resets to the time the router comes back on. Say if I restart it right now, it'll disconnect at 3:36, and again at 4:06.
I did PM both you and Alex the logs over on the Netduma forums, don't know if you've taken a look yet though.
I can't see anything in the logs indicating what the issue could be unfortunately. Could you try putting the router in AP mode please and see if it continues? This would essentially disable DumaOS altogether and then we can narrow down the issue a bit more.
Alex, my SB8200 is just a standard modem, not a modem/router combo. Won't this matter if I put in AP mode as the modem won't be assigning IP addresses?
Tried it anyways and had no access to internet from my wired devices.
Er, Fraser, not Alex. Little early in the morning still. :p
- Good point, it should work though if you just have one device - i.e. a wired device connected to it. Do you have a spare router you could put between the modem and XR for the test?
Put it after the RAX75 I ended up picking up, it's not doing it in AP mode.
- Interesting, if you switch it back to router mode and put the XR500 WAN IP in the DMZ of the RAX75 does it go back to the disconnections?
It seems to only want to do it when it's getting the IP directly from the modem. The RAX75 isn't doing it at all, so that's interesting.
I did unplug the RAX and put the XR500 back behind the modem, still getting those 30 minute DHCP renew/releases though. Personally, I'd rather keep using the XR500 if possible since I got a little better range, but those 30 minute drops were driving me nuts.
One more thing, Cox seems to only be giving me a 1 hour DHCP lease, so the router is asking every 30 minutes to renew it and is losing that connection momentarily when it renews I guess.
- Is there anyway you can extend the lease on the modem/ask CoX to do this? It may be then extend the time the XR500 renews as well.
I can see try, but they're currently saying that this is Netgear issue since the device should not be losing connection on renewal though.
Any idea why the RAX75 has no issues with renewal while the XR does?
- You're right it shouldn't be. Probably because they're handled by different teams. Could you change the Internet Setup to static instead of dynamic please and also do some static/reserved IPs for the LAN devices and see if that helps. Hopefully bypassing DHCP would help.
I believe I did that previously and completely lost internet around the 1 hour mark. A connection drop didn't happen at 30 minutes though. It's unfortunate that Cox does not allow residential customers the ability to get a static IP, otherwise I would have done that.
- I assume you're using the ISP DNS, if you could change that to 1.1.1.1 and 1.0.0.1 does that make any difference? It shouldn't do ordinarily but if they're releasing every hour it may do.
No, I've actually been using 1.1.1.1 for a while now. Also have their ipv6 dns setup as well.
- Could you provide some logs from the System Information page showing some times where the internet has disconnected please?
Netduma-Fraser wrote:
Could you provide some logs from the System Information page showing some times where the internet has disconnected please?[LAN access from remote] from 71.6.199.23:16741 to 192.168.1.2:2379, Wednesday, January 29, 2020 17:09:27 [DumaOS] config write 'com.netdumasoftware.devicemanager.database', Wednesday, January 29, 2020 17:09:15 [LAN access from remote] from 82.102.173.94:58387 to 192.168.1.2:49152, Wednesday, January 29, 2020 17:09:08 [DumaOS] DHCP lease change., Wednesday, January 29, 2020 17:09:00 [DumaOS] DHCP new event., Wednesday, January 29, 2020 17:09:00 [DHCP IP: 192.168.1.2] to MAC address 70:85:c2:5b:e5:d5, Wednesday, January 29, 2020 17:09:00 [DumaOS] Error parsing line in ARP table: 'fe80::d6ad:71ff:fe0c:1c19 dev brwan lladdr d4:ad:71:0c:1c:19 router STALE', Wednesday, January 29, 2020 17:08:51 [DumaOS] Error parsing line in ARP table: 'fe80::1c94:190d:fcd3:29fb dev br0 lladdr 80:b0:3d:2c:5b:8c REACHABLE', Wednesday, January 29, 2020 17:08:51 [DumaOS] Error parsing line in ARP table: 'fe80::1c94:190d:fcd3:29fb dev ethlan FAILED'., Wednesday, January 29, 2020 17:08:51 [LAN access from remote] from 185.250.205.36:56620 to 192.168.1.2:58992, Wednesday, January 29, 2020 17:08:50 [LAN access from remote] from 194.61.24.149:42216 to 192.168.1.2:4766, Wednesday, January 29, 2020 17:08:39 [Internet connected] IP address: 24.254.39.186, Wednesday, January 29, 2020 17:08:36 [LAN access from remote] from 77.247.108.119:54950 to 192.168.1.2:5038, Wednesday, January 29, 2020 17:08:32 [LAN access from remote] from 59.173.13.251:52248 to 192.168.1.2:1433, Wednesday, January 29, 2020 17:07:59 [LAN access from remote] from 194.61.24.149:42216 to 192.168.1.2:4139, Wednesday, January 29, 2020 17:07:37 [LAN access from remote] from 1.163.115.229:1678 to 192.168.1.2:5555, Wednesday, January 29, 2020 17:07:31 [LAN access from remote] from 80.82.64.229:58912 to 192.168.1.2:18652, Wednesday, January 29, 2020 17:07:23 [LAN access from remote] from 81.22.45.126:57582 to 192.168.1.2:4722, Wednesday, January 29, 2020 17:07:10 [DumaOS] DHCP new lease allocated., Wednesday, January 29, 2020 17:07:04 [DumaOS] DHCP new event., Wednesday, January 29, 2020 17:07:04 [DHCP IP: 192.168.1.8] to MAC address hidden, Wednesday, January 29, 2020 17:07:04 [LAN access from remote] from 92.53.90.132:42340 to 192.168.1.2:7738, Wednesday, January 29, 2020 17:06:42 [LAN access from remote] from 94.102.56.215:47034 to 192.168.1.2:1065, Wednesday, January 29, 2020 17:05:56 [LAN access from remote] from 185.156.73.54:54504 to 192.168.1.2:2616, Wednesday, January 29, 2020 17:05:43 [LAN access from remote] from 80.82.64.229:58912 to 192.168.1.2:18646, Wednesday, January 29, 2020 17:05:25 [LAN access from remote] from 83.97.20.167:38467 to 192.168.1.2:1434, Wednesday, January 29, 2020 17:05:24 [LAN access from remote] from 80.82.64.229:58912 to 192.168.1.2:18649, Wednesday, January 29, 2020 17:05:22
This is the most recent one.
- You're getting some weird login attempts from foreign IP addresses and it did occur around the time the connection regained itself. What is your physical setup? I would recommend also disabling respond to ping in WAN settings.
[LAN access from remote] from 80.82.64.229:42596 to 192.168.1.2:18724, Wednesday, January 29, 2020 18:30:09 [LAN access from remote] from 194.61.24.149:42498 to 192.168.1.2:3977, Wednesday, January 29, 2020 18:30:03 [LAN access from remote] from 185.156.73.54:54504 to 192.168.1.2:2658, Wednesday, January 29, 2020 18:29:18 [DumaOS] DHCP lease change., Wednesday, January 29, 2020 18:29:03 [DumaOS] DHCP new event., Wednesday, January 29, 2020 18:29:03 [DHCP IP: 192.168.1.7] to MAC address f0:c3:71:45:05:79, Wednesday, January 29, 2020 18:29:03 [DumaOS] DHCP lease change., Wednesday, January 29, 2020 18:29:02 [DumaOS] DHCP new event., Wednesday, January 29, 2020 18:29:02 [DHCP IP: 192.168.1.7] to MAC address f0:c3:71:45:05:79, Wednesday, January 29, 2020 18:29:02 [LAN access from remote] from 63.143.35.226:51359 to 192.168.1.2:80, Wednesday, January 29, 2020 18:28:48 [LAN access from remote] from 194.61.24.149:42216 to 192.168.1.2:3446, Wednesday, January 29, 2020 18:28:22 [LAN access from remote] from 185.156.73.54:54504 to 192.168.1.2:2614, Wednesday, January 29, 2020 18:27:50
here's a more recent one.
In the WAN area, I have disable port scan and ddos protection unchecked, respond to ping on internet port is unchecked, disable IGMP proxying is checked, NAT Filtering is open, and I have my DMZ on for my desktop since I was having some issues getting my NAT settings working right for a few games.
[DumaOS] DHCP lease change., Wednesday, January 29, 2020 18:39:01 [DumaOS] DHCP new event., Wednesday, January 29, 2020 18:39:01 [DHCP IP: 192.168.1.2] to MAC address , Wednesday, January 29, 2020 18:39:01 [DumaOS] Error parsing line in ARP table: 'fe80::d6ad:71ff:fe0c:1c19 dev brwan lladdr d4:ad:71:0c:1c:19 router STALE', Wednesday, January 29, 2020 18:38:51 [LAN access from remote] from 223.71.167.163:30807 to 192.168.1.2:50000, Wednesday, January 29, 2020 18:38:49 [Internet connected] IP address: 24.254.39.186, Wednesday, January 29, 2020 18:38:36 [UPnP set event: del_nat_rule] from source 192.168.1.2, Wednesday, January 29, 2020 18:38:28
and here's the newest one.
Well those settings all sound fine. I'm still confused about the remote access attempts. Is 192.168.1.2 your desktop? That's getting contacted a lot from outside.
It's not reccomended to put a computer into DMZ because it leaves it very vulerable to attack.
Yeah, that's my desktop. I could turn it off and double check if my NAT settings are fine with it open.
Any other ideas though? Not sure what else to try, and I imagine you guys are still a while out for DumaOS 3.0 (and that's assuming there's a slim chance it fixes my issue with it)
- Definitely take your PC out of the DMZ, with NAT Filtering Open you shouldn't have any port/NAT issues. Having them both enabled may have created conflicts that caused devices not to receive the correct packets so it may appear as a disconnection. I would suggest you also tick IGMP Proxying as it may get rid of those LAN access attempts.
[DumaOS] DHCP lease change., Thursday, January 30, 2020 12:55:46 [DumaOS] DHCP new event., Thursday, January 30, 2020 12:55:46 [DHCP IP: 192.168.1.2] to MAC address , Thursday, January 30, 2020 12:55:46 [DumaOS] Error parsing line in ARP table: 'fe80::d6ad:71ff:fe0c:1c19 dev brwan lladdr d4:ad:71:0c:1c:19 router STALE', Thursday, January 30, 2020 12:55:36 [Internet connected] IP address: 24.254.39.186, Thursday, January 30, 2020 12:55:21 [admin login] from source 192.168.1.2, Thursday, January 30, 2020 12:53:01 [admin login] from source 192.168.1.2, Thursday, January 30, 2020 12:43:24 [admin login] from source 192.168.1.2, Thursday, January 30, 2020 12:41:47 [admin login] from source 192.168.1.2, Thursday, January 30, 2020 12:41:47 [admin login] from source 192.168.1.2, Thursday, January 30, 2020 12:41:47 [admin login] from source 192.168.1.2, Thursday, January 30, 2020 12:41:46 [DoS Attack: ACK Scan] from source: 54.226.98.156, port 443, Thursday, January 30, 2020 12:34:36 [DoS Attack: ACK Scan] from source: 54.226.98.156, port 443, Thursday, January 30, 2020 12:34:21
Did as suggested, still drops on renewal. Going to let the router get my DNS servers from the ISP and see if that makes a difference instead of using 1.1.1.1
- Let us know, if that doesn't work and static doesn't work then it may be worth creating a ticket with Netgear and seeing if they have any other suggestions.
Yeah, still disconnects unfortunately. Is that error parsing line of any significance at all?
As for Netgear, unfortunately, I only have the warranty itself left on the router according to my support page, no email, chat, or phone support is available. Don't know if they'd even offer to exchange it since I never uploaded the receipt, and don't have it anymore either.
Can't really think about nothing else in the router settings itself. I could always try factory resetting the SB8200, but it's not like I can configure anything on that anyways.
