NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Fixed IP Addresses On Guest Network
I use the Guest Network for IoT devices. Is there a way to have consistent/fixed IP addresses on the Guest Network? It appears the Address Reservation capability in the router is only for the pr...
When I attempt to do an Address Reservation:
* They're only allowed on IP addresses in the DHCP Server range.
* DHCP Server range only allowed in the 192.168.1.* network.
* Guest Network is in 192.168.2.* range.
* I don't see a way to change the subnet for the Guest Network.
When I attempt an Address Reservation the page makes it look like I can change the subnet for the reservation being made, but an error is generated when the reservation is Applied. (Error is something like "Address reservations can only be made in the DHCP range.")
Firmware version: V4.6.5.14_2.0.54
You are, of course, entirely correct. Netgear "changes things" from one Orbi product to the next. Guest network IP addresses is one of the things that changed (I knew that, but when the time came to remember it, "poof".) On the original Orbi, Guest WiFi IP's were in the same subnet as primary WiFi IP's. That changed with the AX series.
My guess is that "Guest" means "a device that comes for a while, and then goes away, perhaps never to be seen again."
Sorry I messed up.
No worries! Your post caused me to look at the situation in a different way. It's much appreciated.
I'm wondering if the Guest Network's DHCP server mimics the DHCP settings on the private side. I'm going to try lowering the top end DHCP IP address range - and try setting one of the clients on the Guest Network to be above the revised top DHCP address - but in the Guest subnet.
I appreciate the fact a Guest Network is designed to have things come and go. On the other hand, they allow intra-network communications on the Guest Network (which is why I want fixed IPs for some devices).
Thanks for the help!
Wish you luck.... but am not optimistic. Netgear solved one problem by splitting the IP subnets for primary vs. guest WiFi.... and created another.
In the original Orbi, all devices had IPs in the same subnet and code in the Orbi was set to allow (or deny) guest devices access (a) to each other, and (b) to the primary network. This must have been complicated to manage.
With the new scheme of primary and guest subnets being separate, keeping guests out of the primary network is trivial. (they are separate) it is sort of 'telling' that there is no option in the 750/850 router user manuals to have guests "see each other" and "access the primary network." Not having an AX router, I have no idea whether devices on the guest WiFi can 'see' each other or not.
It is tempting to point out that some users turn off the Orbi DHCP feature and use a separate computer to handle IP assignments. (pfSense, Pi-Hole). Without the Orbi's internal logic to know which devices are on primary and which are on guest, I have serious doubts that a separate DHCP server could maintain the separation of primary vs. guest devices. They would all be simply "devices" asking for an IP address.
Good Luck finding a solution!
It appears it's working. I'm stunned.
I set the DHCP address range to end at 192.168.1.200. I have set a couple of Guest Network clients to be fixed IPs above that 200 range (e.g. 192.168.2.220).
The router is letting them connect with those above-the-DHCP-range fixed IPs and I can talk with them normally.
This has been working a grand total of about 15 minutes. LOL. Hopefully it stays that way.