NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Can't connect to router after switching to AP mode mode.
I know the IP but I can't connect... Netgear RAXE300 (AXE7800). No matter what I do (wired, static IP with it disconnected from the network, or connected to the network trying to visit from PC on t...
If your home subnet is 192.168.0.x, then you need to set a static IP address on the RAXE for a IP address on this same subnet. 192.168.0.30 would work in AP mode then access it's web page there. If you do this, the host routers Default IP address pool range should be set to .100 thru .200. Any static IP addressed devices needs to be outside of the host routers default DHCP IP address pool range.
https://kb.netgear.com/20927/How-do-I-change-my-NETGEAR-router-to-AP-mode
If your home subnet is 192.168.0.x, then you need to set a static IP address on the RAXE for a IP address on this same subnet. 192.168.0.30 would work in AP mode then access it's web page there. If you do this, the host routers Default IP address pool range should be set to .100 thru .200. Any static IP addressed devices needs to be outside of the host routers default DHCP IP address pool range.
https://kb.netgear.com/20927/How-do-I-change-my-NETGEAR-router-to-AP-mode
Is 192.168.0.221 not considered to be on the 192.168.0.x subnet? I'm confused. I was able to get into the web interface after setting a static IP on my main router and forcing the AXE300 to get 192.168.0.4 - no magically I can connect. I don't understand why 192.168.0.221 wasn't working (wasn't letting me connect to it) but doesn't matter I suppose.
I'm not sure I agree / understand why DHCP pool range must not include any reserved (static) addresses within it, but yes, my router is configured to start handing out dynamically at x.x.x.100...
- Because you'll have IP conflicts when the pool range is also within that range.
I would have assumed that any half decent DHCP server would not issue a reserved address anything but the MAC address its reserved for. And even if it did, I would assume that it would give the reserved-IP client a different IP (or none at all) while the one it's sposed to get is reserved. If we're being overly cautious, I get it.
But that's not the point of this post anyway 🙂
You're on a router, with constrained resources where every MB matters. A stripped down, basic DHCP is all you get.
