NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
This frustrating intermittent issue.
We have observed that Orbi continuously reassigns IP addresses to certain devices, which causes those devices to experience frequent and intermittent Wi-Fi disconnections.
This issue has been present for a long period of time and also affects the RBE97X series, indicating that it is not limited to a single model.
At this point, we would like to understand when a permanent fix is expected. This issue has already impacted multiple customers, and despite our continued efforts to troubleshoot and explain, the situation has become increasingly difficult to manage.
As a distributor, we are under significant pressure, and it is becoming very challenging to maintain customer confidence without a clear resolution timeline or roadmap from NETGEAR.
We sincerely request this issue to be prioritized and would appreciate any update, workaround, or estimated timeline for resolution.
model：RBE773
FW：v10.5.20.7
4 Replies
What is the Mfr and model# of the Internet Service Providers modem/ONT the NG router is connected too?
Be sure your using a good quality LAN cable between the modem and router. CAT6A STP is recommended.
What kinds of devices are connected to the system?
How many devices in total are connected to the system?
Be sure to disable any MAC Address randomizers on phones and pads while at home:
NETGEAR Mobile Applications and Android/Apple/Windows Devices FAQ | NETGEAR Communities
What is the size of your home? Sq Ft?
What is the distance between the router 📡 and satellite(s)🛰️? 30 feet or more is recommended in between RBR 📡 and RBS 🛰️ to begin with depending upon building materials when wired or wirelessly connected.
https://kb.netgear.com/31029/Where-should-I-place-my-Orbi-satellite 🛰
What channels are you using? Auto? Try setting manual channel 1, 6 or 11 on 2.4Ghz and 40 to 48 channel on 5Ghz.
Is IPv6 enabled on the RBR?
Is detected ISP DNS being used on the RBR or custom DNS?
Using default DHCP IP address pool range? Try changing to .100 to .200:
Try disabling the following and see:
Armor, Smart Parental Controls or Circle, IPv6, Protection Engine, Traffic Meter.
You'll need to make contact with NG support to let them know about issues seen that we can't solve here in the forums. NETGEAR doesn't give roadmaps to when they fix things. No router mfr does.
Netbridge-Brian this has been happening for years - the DHCP flooding part of the problem that is. You can search for DHCP flooding on the forums thru Google and find a number of posts. Here is one of mine back in 2024:
Odd behavior - RBS960 Satelllites flooding DHCP requests | NETGEAR Communities
Now, like CrimpOn said, DHCP is always client-initiated. A router (or DHCP server) cannot force a device to ask for an address, but it can create conditions that make the client decide it needs to ask again (more on that below). In my experience over 3-4 years and different Orbis, I see it on specific Apple devices; many devices on my network only asked for DHCP consistent with their lease. What devices show these messages?
I think you have 2 issues - the DHCP flooding, and device disconnects. I said above that the router can create conditions that make the client decide it needs to ask again. Typical reasons are, reboots, renegotiated link, and I believe moving to a different Orbi device if the client device is moving around the building. Someone with an iPhone walking around a building a lot will generate a lot of DHCP requests. That alone is not really an issue, but your disconnects are.
My experience is with the 960s and now the 970s - I see you have the 770 series. I am not sure about the FW fixes, I know on the 970s the disconnects of mobile devices went away like 99% with 9.13.2.1. Maybe FURRYe38 or someone else can comment on whether the latest 770 FW has improvements for disconnects.
Does this happen:
- Only to devices connected via WiFi? (never to Ethernet connected devices?)
- To only some specific devices? (or to ALL devices?)
Troubleshooting DHCP issues with Ethernet connected devices is a relatively simple process. WiFi devices are MUCH more difficult because it is technically difficult to capture the network traffic over WiFi.
The reason a network capture is essential is because DHCP is a well-defined protocol. The DHCP server (Orbi router) responds to DHCP requests made by clients. It does not spontaneously decide, "hey, let's assign an IP address to this device over and over again." The Orbi log may show entries of DHCP assigning IP addresses to a device many times, but that is simply a record of the device making requests over and over. A network capture would show the sequence of packets. The log file shows only the final result.
There are several active conversations on the Forum about WiFi7 Orbi systems dropping WiFi connections. I do not recall DHCP being involved in those discussions.
