NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Wrong IPs being given out
I have a SXR80 modem as well as a SXS80 satellite mesh system. Everything was working fine until a slight power outage happened and all of my IoT devices restarted. Of my 30 light switches, 3 conne...
tehBob wrote:
I have a SXR80
modemrouter as well as a SXS80 satellite mesh system.
Just a tiny correction: The SRX80 router is connected to an Internet Service Provider (ISP) cable modem or Optical Network Terminator (ONT). It is itself a combination router/WiFi unit.
tehBob wrote:
I don't have an IP range set for 192.168.1.xxx at all.
Surely LAN1 has numbers in the DHCP fields? Are they simply the default values of 1 thru 254?
tehBob wrote:
I had the same problem in the past, and it was suggested I assign static IPs to everyone on my IoT VLAN, which I did. Looking at my connected devices, I can see a bunch of the devices connecting with correct IP addresses (192.168.30.xxx)
Reserving (assigning) IP addresses is a common practice. (I assign IPs to every device that is more or less permanent on the network: desktops, televisions, printers, cameras, light switches, etc. Only truly transient devices are assigned IPs from the DHCP 'pool'.) Any memory of how this problem was resolved the last time?
I would want to confirm that these devices are receiving DHCP assignments from the router, but this is not trivial with WiFi devices. It would mean capturing WiFi on the IoT network as a device is powered up and examining the DHCP packets.
One tactic might be:
- disable the IoT network
- power the router and satellite off
- boot up only the router.
- let the network stabilize and verify that none of the IoT devices have connected.
- enable the IoT network
My goodness, what a mess!
CrimpOn wrote:
One tactic might be:
- disable the IoT network
- power the router and satellite off
- boot up only the router.
- let the network stabilize and verify that none of the IoT devices have connected.
- enable the IoT network
My goodness, what a mess!
I tried this last night. No luck. After turning everything back on and getting the IoT network back up, the 192.168.1.80 devices came back. I've tried every different combination of disabling network, disabling DHCP, removing IP addresses from the pool...you name it, no luck. For fun I decided to try to add my cell phone to this network. It tried for a little bit and then failed with the error "unable to get an IP from the server". I tried to add my laptop as well, it got an IPv6 address, but no actual IPv4 (169.254.89.58 with a subnet of 255.255.0.0). Not sure if that helps anything.
tehBob wrote:
I tried to add my laptop as well, it got an IPv6 address, but no actual IPv4 (169.254.89.58 with a subnet of 255.255.0.0). Not sure if that helps anything.This indicates that the laptop failed to get an IP address from the network. 169.254 IP addresses are known as Link Local addresses, created by the laptop itself. (both the IPv4 and IPv6 addresses) Nothing came from a DHCP server.
CrimpOn wrote:
tehBob wrote:
I tried to add my laptop as well, it got an IPv6 address, but no actual IPv4 (169.254.89.58 with a subnet of 255.255.0.0). Not sure if that helps anything.This indicates that the laptop failed to get an IP address from the network. 169.254 IP addresses are known as Link Local addresses, created by the laptop itself. (both the IPv4 and IPv6 addresses) Nothing came from a DHCP server.
https://en.wikipedia.org/wiki/Link-local_address
Correct, which would indicate there is a problem with DHCP server. Which in this case is the Orbi.
How is the laptop connected (wired? WiFi?)
Are all of the LANs affected?
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
