NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Orbi 850 running V7.2.8.5_5.1.21 dhcp issues
Hi I recently switched my Orbi 850 back to router mode from AP mode as I have a new ISP.
What i've found within a day is that the dhcp function on the Orbi 850 (+1 satellite) running V7.2.8.5_5.1.21 is incredibly flaky.
We have about 80 devices at home, the majority of which are nanoleaf light bulbs (~40 or so), sonos devices and various other "smart" appliances.
I've rebooted it multiple times to try and get things working, and it works for some but then other devices cannot get connected. Symptoms I've seen are:
- Windows PCs getting the default microsoft IP address of 169.254, which means it could not get an IP address.
- Devices that were connected before the reboot won't connect after.
- Devices showing incorrect device "names" against the respective mac address in the device list.
Overall it seems to be incredibly unreliable.
Anyone else experienced this?
21 Replies
All reserved addresses were wiped during the change and re-setting up dhcp on the orbi as the router.
Looks like it is time to switch to TP-link. sick of these issues.
What i've found within a day is that the dhcp function on the Orbi 850 (+1 satellite) running V7.2.8.5_5.1.21 is incredibly flaky.
The DHCP service is being provided by your ISP router, all the Orbi is doing is forwarding those requests to that router.
Are the two Orbi units in the same place as they were before?
Is the ISP router wifi turned off?
Any evidence of poor speeds on the connections that are made?
One possibility is that the ISP router can't handle that many connections.
Um no. I switched the Orbi 850 from AP mode to Router mode and connected it directly to the ISP, no other router in between. I made it the DHCP, as is the norm for you ISP router. It is this functionality that is flaky as hell, failing within a few hours. Couldn't connect any new devices. Cannot configure any timers.
The DHCP service is being provided by your ISP router, all the Orbi is doing is forwarding those requests to that router.
This was the case when the Orbi was in AP mode connected to the previous ISP. When the ISP changed, the Orbi was placed in Router mode.
This was the case when the Orbi was in AP mode connected to the previous ISP. When the ISP changed, the Orbi was placed in Router mode.
Oops, read it backwards. The 850 can handle 80 connections in router mode, so it is not that.
I am wondering if David9 did a factory reset when switching to Router mode. That might help.
I did reset it. A few times.
What brand and model# is the ISP modem that the RBR is connected too?
CAT# LAN cable used in between the modem and RBR?
What IP address pool string are you using on the RBR? Default 192.168.1.1?
Might try using a different DHCP IP address pool range. .100 to .200. I do.
Make sure all wifi adatper drivers are up to date for PCs that have these adapters.
Make use of the separate IoT network for IoT devices
Use manual channels 1 and 40 or 11 and 48.
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
I've used this same FW version on my 960 series Orbi, same code base, bit different WIFI features, saw zero issues with DHCP and devices connected. I know my 850 series would work just as good.
How many device are on your network?
The ISP provides a fibre service and then Ethernet converter as an NTU/modem. It is a direct connection from that to the WAN port on the ORbi 850. This is not the issue.
I have tried changing the DHCP range from default to .50 to .199 but made no difference. I don't want to use an IOT. But wouldn't that use the same DHCP range or does that have its own range?
I would try the IoT network for your IoT stuff.
50 devices here. All on main WLAN.
I might bring my 850 series out and check this.
But wouldn't that use the same DHCP range or does that have its own range?
Yes. There is only one DHCP 'pool'. IoT devices will be assigned IPs the same as devices on the primary network. However, "assigned" or "reserved" IP addresses do not need to be in the pool. My practice is to use the LAN Setup page to reserve IP addresses for devices (using their hardware MAC address) which are separate from the 'pool' of addresses that are available for other devices.
For example, if those 40+ nanoleaf bulbs are entered into the LAN setup table with IP's such as 192.168.1.21 through 192.168.1.(60 whatever), those are the IP addresses that will be offered to the bulbs when they make a DHCP request.
It seems to crap out at around 60ish.
It appears to allow the amount of devices to connect via wifi when NOT a DHCP server and it is the DHCP server function that is the issue when in router mode.
....and yes I did factory reset it. ...twice.
Regarding the connectivity etc. I have worked in telecomms and IT networking for over 38 years. I understand networks, routing, subnets and DHCP servers. There was no ISP router in the new connection when initally connected to the Orbi "WAN" port. To resolve the issue in the interim I've installed an old ISP router, which now acts as the DHCP for 192.168.1.0/24 and reverted the Orbi to AP mode. It appears to have stabilised for now, but you can never tell whether all devices are working. Unfortunately that old ISP router only allows up to 32 IP address reservations.
I should also state, that over the years I've had the orbi I do have to reboot it every few weeks to keep it "reliable".
What's the size of the home in sq feet?
It is currently approximately 125 square metres, Single level 3 bedroom apartment. Previously we had in a 100 square metre two storey apartment. I'll come to the issue here, which is the DHCP function when in router mode. I can live with AP mode and rebooting every few weeks or so, but the DHCP router mode function was abysmal, and from what I've read I'm not the first person to report this issue.
