NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
conkerick
May 20, 2021Tutor
XRM570 Wifi DHCP Issue
Hi, since I bought the XRM570 (XR500) I am having this issue: From time to time, randomly, the router does not assign an IP address over WiFi. The devices indicate "could not assign or get an ip ...
Netduma-Fraser
Jul 24, 2021NetDuma Partner
Thanks for that, copy the WAN IP from the XR System Information page then access the Huawei and enter it into the DMZ function. Also on the Huawei set that same IP as static/reserved for the XR. Then see if the problem is resolved/happens less please
conkerick
Jul 24, 2021Tutor
Ok, so...
Modem IP is 172.16.0.1
Router IP is 172.16.0.2 (reserved with a 30 days lease and DMZ enabled)
The router is configured: "Internet IP Address -> Use Static IP Address".
- Netduma-FraserJul 24, 2021NetDuma PartnerOkay great, let us know how you get on!
- conkerickJul 25, 2021Tutor
Hello, the daily reboot did not occur yesterday. However, the same DHCP issue occurred again.
This time it happened in a way that I had previously noticed.
In my country we suffer from electrical problems, voltage spikes and power outages.
The router and modem are connected to an UPS, which allows me to continue having Internet and WiFi.Today we suffered a power outage that lasted approximately 2 hours. As soon as the service was restored, I realized that no WiFi device could connect to the router. I unplugged the extender and the problem continued.
Only my phone and my wife's phone were still connected to the WiFi, as soon as I logged out and tried to connect, my phone was not getting ip address.
The only way to connect my phone was by putting a fixed ip, because with dhcp it does not work.
My PC which is wired, DHCP is working fine:
Microsoft Windows [Versión 10.0.19043.1110] (c) Microsoft Corporation. Todos los derechos reservados. C:\Users\xxx>ipconfig /release Configuración IP de Windows Adaptador de Ethernet Ethernet: Sufijo DNS específico para la conexión. . : Vínculo: dirección IPv6 local. . . : fe80::e032:ca72:87c9:9ab4%5 Puerta de enlace predeterminada . . . . . : C:\Users\xxx>ipconfig /renew Configuración IP de Windows Adaptador de Ethernet Ethernet: Sufijo DNS específico para la conexión. . : Vínculo: dirección IPv6 local. . . : fe80::e032:ca72:87c9:9ab4%5 Dirección IPv4. . . . . . . . . . . . . . : 192.168.8.3 Máscara de subred . . . . . . . . . . . . : 255.255.255.0 Puerta de enlace predeterminada . . . . . : 192.168.8.1 C:\Users\Erick Ospino>
It seems that when the electricity returns, the large number of devices trying to connect to the router, the DHCP collapses or blocks or believe that there is an attack?
I must clarify that the router never turned off during the power outage and I have not restarted it either, so I have still the issue. I have not wanted to reboot until find something that solve the issue.
Current Time: Sunday, Jul 25, 2021 15:26:48 [DumaOS] Marking device that is marked 192.168.8.36 14 35., Sunday, July 25, 2021 15:26:48 [DumaOS] DHCP lease change., Sunday, July 25, 2021 15:26:47 [DumaOS] DHCP new event., Sunday, July 25, 2021 15:26:47 [DHCP IP: 192.168.8.36] to MAC address d8:0d:17:20:69:1a, Sunday, July 25, 2021 15:26:47 [DumaOS] DHCP lease change., Sunday, July 25, 2021 15:26:46 [DumaOS] DHCP new event., Sunday, July 25, 2021 15:26:46 [DHCP IP: 192.168.8.37] to MAC address 68:ff:7b:e8:65:0c, Sunday, July 25, 2021 15:26:46 [DumaOS] DHCP lease change., Sunday, July 25, 2021 15:26:44 [DumaOS] DHCP new event., Sunday, July 25, 2021 15:26:44 [DHCP IP: 192.168.8.37] to MAC address 68:ff:7b:e8:65:0c, Sunday, July 25, 2021 15:26:44 [DumaOS] Marking device that is marked 192.168.8.40 13 35., Sunday, July 25, 2021 15:26:37 [DumaOS] DHCP lease change., Sunday, July 25, 2021 15:26:36 [DumaOS] DHCP new event., Sunday, July 25, 2021 15:26:36 [DHCP IP: 192.168.8.40] to MAC address 68:ff:7b:e8:5b:28, Sunday, July 25, 2021 15:26:36 [DumaOS] Marking device that is marked 192.168.8.36 14 35., Sunday, July 25, 2021 15:26:35 [DumaOS] DHCP lease change., Sunday, July 25, 2021 15:26:35 [DumaOS] DHCP new event., Sunday, July 25, 2021 15:26:35 [DHCP IP: 192.168.8.36] to MAC address d8:0d:17:20:69:1a, Sunday, July 25, 2021 15:26:35 [DumaOS] Marking device that is marked 192.168.8.33 25 35., Sunday, July 25, 2021 15:26:33 [DumaOS] DHCP lease change., Sunday, July 25, 2021 15:26:33 [DumaOS] DHCP new event., Sunday, July 25, 2021 15:26:33 [DHCP IP: 192.168.8.33] to MAC address 68:ff:7b:e8:7a:e8, Sunday, July 25, 2021 15:26:33 [DumaOS] Marking device that is marked 192.168.8.39 16 35., Sunday, July 25, 2021 15:26:31 [DumaOS] DHCP lease change., Sunday, July 25, 2021 15:26:31 [DumaOS] DHCP new event., Sunday, July 25, 2021 15:26:31 [DHCP IP: 192.168.8.39] to MAC address 98:da:c4:c8:24:18, Sunday, July 25, 2021 15:26:31 [DumaOS] Marking device that is marked 192.168.8.39 16 35., Sunday, July 25, 2021 15:26:30 [DumaOS] DHCP lease change., Sunday, July 25, 2021 15:26:29 [DumaOS] DHCP new event., Sunday, July 25, 2021 15:26:29 [DHCP IP: 192.168.8.39] to MAC address 98:da:c4:c8:24:18, Sunday, July 25, 2021 15:26:29 [admin login] from source 192.168.8.3, Sunday, July 25, 2021 15:26:27 [DumaOS] Marking device that is marked 192.168.8.36 14 35., Sunday, July 25, 2021 15:26:22 [DumaOS] DHCP lease change., Sunday, July 25, 2021 15:26:22 [DumaOS] DHCP new event., Sunday, July 25, 2021 15:26:22 [DHCP IP: 192.168.8.36] to MAC address d8:0d:17:20:69:1a, Sunday, July 25, 2021 15:26:22 [DumaOS] Marking device that is marked 192.168.8.33 25 35., Sunday, July 25, 2021 15:26:21 [DumaOS] DHCP lease change., Sunday, July 25, 2021 15:26:20 [DumaOS] DHCP new event., Sunday, July 25, 2021 15:26:20 [DHCP IP: 192.168.8.33] to MAC address 68:ff:7b:e8:7a:e8, Sunday, July 25, 2021 15:26:20 [admin login] from source 192.168.8.3, Sunday, July 25, 2021 15:26:19 [admin login] from source 192.168.8.3, Sunday, July 25, 2021 15:26:19 [admin login] from source 192.168.8.3, Sunday, July 25, 2021 15:26:19 [admin login] from source 192.168.8.3, Sunday, July 25, 2021 15:26:19 [admin login] from source 192.168.8.3, Sunday, July 25, 2021 15:26:19 [DumaOS] DHCP lease change., Sunday, July 25, 2021 15:26:19 [DumaOS] DHCP new event., Sunday, July 25, 2021 15:26:19 [DHCP IP: 192.168.8.37] to MAC address 68:ff:7b:e8:65:0c, Sunday, July 25, 2021 15:26:19 [DumaOS] Marking device that is marked 192.168.8.39 16 35., Sunday, July 25, 2021 15:26:05 [DumaOS] DHCP lease change., Sunday, July 25, 2021 15:26:05 [DumaOS] DHCP new event., Sunday, July 25, 2021 15:26:05 [DHCP IP: 192.168.8.39] to MAC address 98:da:c4:c8:24:18, Sunday, July 25, 2021 15:26:05 [DumaOS] Marking device that is marked 192.168.8.39 16 35., Sunday, July 25, 2021 15:26:04 [DumaOS] DHCP lease change., Sunday, July 25, 2021 15:26:04 [DumaOS] DHCP new event., Sunday, July 25, 2021 15:26:04 [DHCP IP: 192.168.8.39] to MAC address 98:da:c4:c8:24:18, Sunday, July 25, 2021 15:26:04 [DumaOS] Marking device that is marked 192.168.8.41 24 35., Sunday, July 25, 2021 15:25:54
- Netduma-FraserJul 25, 2021NetDuma PartnerThe only fix for this will be a software fix from the NG devs, while this is something they're working on I don't have a specific ETA on that but I'm hoping it will be relatively soon. Given it was caused by power fluctuations I think the only thing you can do is to reboot it
- conkerickJul 26, 2021Tutor
I "solved" the issue without rebooting:
- Disabled XR as a DHCP server.
- Installed DDWRT software in my R9000 (which was operating without problems until I decided to upgrade to XR).
- Configured the R9000 to work only as a DHCP server.
- Everything is working flawlessly. WITHOUT REBOOTING THE XR.
So... there is definitely a very serious issue with DHCP on the XR.
I think it is a lack of respect on the part of Netgear that they don't solved this problem yet. If you search on this forum or Google, you'll find people with same problem. It's a shame that the experience of the users and DumaOS, is affected by this HUGE issue.
DHCP functionality is basic on all routers. I describe this issue like: A glass of water that cannot hold water.
Hoping that Netgear fix this soon.
Thank you for all your support Liam and Fraser.
- Netduma-LiamJul 26, 2021NetDuma Partner
Well done for working out your own solution!
Thanks for your feedback too, we're aware that it's very disruptive for the users that experience it.
Keep an eye on the forum for when a fix is released, thanks again for your patience.