NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
-Malux-
Dec 09, 2020Tutor
Orbi RBR 50 DHCP issue after Reboot
This issue is maddening. A simlpe router reboot causes DHCP to stop working. I have the satellite off, and the router just will not allow my iPhone 11 Pro (and most of the other devices on my ...
FURRYe38
Dec 10, 2020Guru - Experienced User
Let me clairify, when I mean disconnect, I mean disconnect them from the wireless SSID, not from the power lines where there installed.
Ya, seems like possible the DHCP service is getting bogged down and can't catch up with all the REQs coming in from all these devices, so which is why I suggested wirelessly disconnecting them from the router and then graduale adding them 1 at a time. And again, try setting up some IP address reservations would help the DHCP server manage these as well.
-Malux-
Dec 10, 2020Tutor
I think that's exactly what's going on. We're thinking the same thing: DHCP is getting overwhelmed.
This is intersting, I've been turning DHCP off and on and off and on and off and on. Everytime I do that a few more devices get IPs.
It's crazy, but it's working....I'm up to 55 of 77 devices active now...
- FURRYe38Dec 10, 2020Guru - Experienced User
Ya, having all those online at the same time is causing the server to bog down...You need to set them one maybe a small group at a time, also assign IP address reservastions for each so that if someting happens, the server will already have these addresses assigned.
- -Malux-Dec 11, 2020Tutor
Considering the class of device though, you'd imagine the orbi should be able to handle the load.
I did opened a case with TP-Link and made some suggestions on how to throttle their request rate. That said, I want to open a case with the netgear dev team.
Here's the big question: Netgear offered to replace my router. I'm not convinced a router replacement will do anything. What do you guys think? Should I move forward with the replacement or leave it alone?
- FURRYe38Dec 11, 2020Guru - Experienced User
You can try the replacement to see if you notice anything different, if not, send it back.
Just seems like there is a handling issue with having ALL those devices trying to get an IP address, mostly all at once and the server can't handle that. Most home class routers only handle upwards to about 40-50 for average homes. Having more then that, espeically all trying to get something ALL at once, may impact any home class router.
I have around 30 and don't see this issue with this amount connecting...
- -Malux-Dec 22, 2020Tutor
FURRYe38 well, the replacement had the same exact issue. I sent it back. That said, I was able to resolve my problem by giving DHCP reservations to each individual smart device on the network. With the DHCP reservations in place, I was able to successfully reboot my router without my entire network going haywire.
With that addressed (no pun intended), I now, I have to contend with the V2.7.1.60 of the firmware. I have the latest app (v2.7.2.18) on my phone and am getting the error CDIL-API-FAIL when when I try to see the attached devices.
This really should be simpler! Honestly, I don't know how the app passed QA. We're not talking about an edge case here. This is core functionality...
- FURRYe38Dec 22, 2020Guru - Experienced User
Could be two area, either FW maybe a problem for your configuration or something on your network maybe causing problems thus a reservation seems to be a problem solver though it maybe masking the real problem. I'm thinking there is somethign on your network that maybe causing a problem. Last resort idea would be just a faulty RBR, however you would need to test this RBR out in a different envrionment to see if the problem followed or not.
I have not seen this problem with my 50 series system while using v16 FW. I didn't see anything like yours with v2.7 loaded however I didn't take a longer review of this version since I found the problem with v2.7x versions causing ARP storms with RBS ethernet connected, so after I reviewed that, I reverted back to v16. I leave most everything dynamic IP addressed sans 4 cameras, two NAS and 3 printers that are static assigned on these devices. Other then that, my IP address pool of .100 to .150 works for me and the rest of the dynamic IP addressed devices.