NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
kaitech
Aug 20, 2018Aspirant
XR500 DHCP issue
I've had this router for 4 months now and it works fine most of the time. Once in a while I'll notice that some LAN devices become unresponsive, when I look into the issue it turns out that they have...
JediZavv
Jan 11, 2021Aspirant
Running XR500 v2.3.2.66;
Been using the router for 2+ years without major problem until yesterday;
1 LAN connection to router with N WiFi connections;
LAN connection randomly dropped off around every 5 mins and reconnect after 1 min, not noticing issue with WiFi devices while LAN PC is dropped off;
Notice the "[DumaOS] Error parsing line in ARP table" for 00:01:5c:64:ae:46;
While my PC's mac addr is d8:cb:8a:57:21:ac, I cannot identify the mac addr 00:01:5c:64:ae:46, it's not the router's mac addr nor the modem's and obviously not any one of the on/offline device under Device Manager -> Network Map.
Note: no setting has changed other than the always-on auto-firmware update which might have updated firmware a week or two ago.
p.s. I honestly don't want to load debug firmware and try more, typing this reply already spent too much of my time... good luck.
[DumaOS] DHCP lease change., Monday, January 11, 2021 03:00:03 [DumaOS] DHCP new event., Monday, January 11, 2021 03:00:03 [DHCP IP: 192.168.1.2] to MAC address d8:cb:8a:57:21:ac, Monday, January 11, 2021 03:00:03 [DumaOS] Error parsing line in ARP table: 'fe80::201:5cff:fe64:ae46 dev brwan lladdr 00:01:5c:64:ae:46 router STALE', Monday, January 11, 2021 02:59:51 [DumaOS] Error parsing line in ARP table: 'fe80::201:5cff:fe64:ae46 dev brwan lladdr 00:01:5c:64:ae:46 router STALE', Monday, January 11, 2021 02:59:35 [DumaOS] DHCP lease change., Monday, January 11, 2021 02:46:45 [DumaOS] DHCP new event., Monday, January 11, 2021 02:46:45 [DHCP IP: 192.168.1.2] to MAC address d8:cb:8a:57:21:ac, Monday, January 11, 2021 02:46:45 [DumaOS] Error parsing line in ARP table: 'fe80::201:5cff:fe64:ae46 dev brwan lladdr 00:01:5c:64:ae:46 router STALE', Monday, January 11, 2021 02:46:12 [DumaOS] DHCP lease change., Monday, January 11, 2021 02:46:09 [DumaOS] DHCP new event., Monday, January 11, 2021 02:46:09 [DHCP IP: 192.168.1.2] to MAC address d8:cb:8a:57:21:ac, Monday, January 11, 2021 02:46:09 [DumaOS] Error parsing line in ARP table: 'fe80::201:5cff:fe64:ae46 dev brwan lladdr 00:01:5c:64:ae:46 router STALE', Monday, January 11, 2021 02:46:08 [DumaOS] Error parsing line in ARP table: 'fe80::201:5cff:fe64:ae46 dev brwan lladdr 00:01:5c:64:ae:46 router STALE', Monday, January 11, 2021 02:46:03 [DumaOS] Error parsing line in ARP table: 'fe80::201:5cff:fe64:ae46 dev brwan lladdr 00:01:5c:64:ae:46 router STALE', Monday, January 11, 2021 02:45:47 [DumaOS] Error parsing line in ARP table: 'fe80::201:5cff:fe64:ae46 dev brwan lladdr 00:01:5c:64:ae:46 router STALE', Monday, January 11, 2021 02:45:44 [DumaOS] DHCP lease change., Monday, January 11, 2021 02:44:55 [DumaOS] DHCP new event., Monday, January 11, 2021 02:44:55 [DHCP IP: 192.168.1.6] to MAC address 40:d2:8a:8b:a7:e4, Monday, January 11, 2021 02:44:55 [admin login] from source 192.168.1.2, Monday, January 11, 2021 02:44:44 [DumaOS] DHCP lease change., Monday, January 11, 2021 02:42:06 [DumaOS] DHCP new event., Monday, January 11, 2021 02:42:06 [DHCP IP: 192.168.1.2] to MAC address d8:cb:8a:57:21:ac, Monday, January 11, 2021 02:42:06 [DumaOS] Error parsing line in ARP table: 'fe80::79e2:676f:7459:3391 dev br0 lladdr d8:cb:8a:57:21:ac STALE', Monday, January 11, 2021 02:41:43 [DumaOS] Error parsing line in ARP table: 'fe80::201:5cff:fe64:ae46 dev brwan lladdr 00:01:5c:64:ae:46 router STALE', Monday, January 11, 2021 02:41:43 [DumaOS] DHCP lease change., Monday, January 11, 2021 02:41:37 [DumaOS] DHCP new event., Monday, January 11, 2021 02:41:37 [DHCP IP: 192.168.1.2] to MAC address d8:cb:8a:57:21:ac, Monday, January 11, 2021 02:41:37 [DumaOS] Error parsing line in ARP table: 'fe80::79e2:676f:7459:3391 dev br0 lladdr d8:cb:8a:57:21:ac STALE', Monday, January 11, 2021 02:41:13 [DumaOS] Error parsing line in ARP table: 'fe80::201:5cff:fe64:ae46 dev brwan lladdr 00:01:5c:64:ae:46 router STALE', Monday, January 11, 2021 02:41:13
- Netduma-FraserJan 11, 2021NetDuma PartnerJediZavv that MAC address belongs to Arris so I assume that is the make of your modem. It might be that your public IP address renewed and it took the router a little while to reconnect properly. Have you encountered the issue again since then?
- JediZavvJan 14, 2021Aspirant
It's still happening, tried rebooting with no success; symptom seems to get worse now it can't even load into DumaOS, barely got through the login prompt and the red background then stuck loading forever, most other website load through only 1 or two elements as well.
Meanwhile, using my laptop's WiFi or using USB WiFi dongle on my PC works fine.
My modem is from Spectrum (Model E31T2V1), the label on the modem says
CM MAC: 589630ED4DA7
MTA MAC: 589630ED4DA8
no mention of the 00:01:5c:64:ae:46 from the log error
[DumaOS] DHCP lease change., Wednesday, January 13, 2021 20:55:44 [DumaOS] DHCP new event., Wednesday, January 13, 2021 20:55:44 [DHCP IP: 192.168.1.2] to MAC address d8:cb:8a:57:21:ac, Wednesday, January 13, 2021 20:55:44 [DumaOS] Error parsing line in ARP table: 'fe80::79e2:676f:7459:3391 dev br0 lladdr d8:cb:8a:57:21:ac STALE', Wednesday, January 13, 2021 20:55:38 [DumaOS] Error parsing line in ARP table: 'fe80::201:5cff:fe64:ae46 dev brwan lladdr 00:01:5c:64:ae:46 router STALE', Wednesday, January 13, 2021 20:55:38 [DumaOS] DHCP lease change., Wednesday, January 13, 2021 20:55:31 [DumaOS] DHCP new event., Wednesday, January 13, 2021 20:55:31
this error only shows up when I use my PC [wired connection], nowhere else in the log when there are only WiFi connection; and I've been using this exact same wired connection without problem for years.
again, router is set to use default mac addr.
- Netduma-LiamJan 14, 2021NetDuma Partner
Were any changes made to the network or configuration prior to this issue occuring for the first time?
Had you captured these logs after attempting to reboot the router?