NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
SXR80 Can’t Obtain IP Reliably After Power Cycle
I just purchased the Orbi Pro SXK80 (comprised of the SXR80 and a single SXS80). Since I have owned it, I have been doing work on the house and have had to flip the breaker at least once a day. Thi...
Hi, I’m an owner of a SXR80 (plus 4 SXS80) also with the firmware 3.2.6.100,I have the same issue of the user jcharnet.If I unplug the router from the wall outlet, I have to wait also hours (with the device unplugged) before to plug it again and finally see the white light on.This is an absurd behaviour for a device business oriented!Is there a fix to solve the problem?Or also a workaround to recover fastly the situation when, for example, a power outage happens?
pierpox72 wrote:Hi, I’m an owner of a SXR80 (plus 4 SXS80) also with the firmware 3.2.6.100,I have the same issue of the user jcharnet.If I unplug the router from the wall outlet, I have to wait also hours (with the device unplugged) before to plug it again and finally see the white light on.This is an absurd behaviour for a device business oriented!Is there a fix to solve the problem?Or also a workaround to recover fastly the situation when, for example, a power outage happens?
Ugh, this is NOT what I needed to see, after coming here to try and figure out what the SXR80 default IP is.... and after upgrading the satellite to firmware 3.2.6.100 literally less than an hour ago.
Backstory: Power outage during the recent "heat dome" event in the northwest, lasted several hours into the evening (less than a day). When it came back on, everything came back up.... but the Orbi router (in AP mode) and satellite (wired backhaul) both had the lovely magenta light, even after multiple power cycles, and the Insight app shows it as "offline" as well. Everything connected via ethernet to our switch works fine, and wireless devices work fine, so I left it until I had some time this weekend to muck around with it.
What I've found so far:
- The SXS80's IP got reset to 192.168.1.250 (what I presume is it's default)
- The username and password were not reset, however.
- The SSID and WPA2 key were not reset either.
- Updated to firmware 3.2.6.100, in hopes that kept it from happening in the future, and shut it down while I went to work on the SXR80. Crossing my fingers it comes back up quickly, after seeing the messages here.
- The SXR80 is a complete mystery at this point. I've power-cycled it several times, and tried accessing it via the custom IP it's supposed to pull from our DHCP server (reserved). No luck. Tried accessing it via orbilogin.com/.net - nothing. Tried accessing via 192.168.1.1 and 192.168.1.250, and again - no luck. I'm using a Surface Pro, hard-wired into one of the ethernet ports.
- I was trying to avoid doing a factory reset, because getting the darn things set up was a nightmare - and I really don't want to go back through that again. It looks like there may not be any other choice, though. *sigh*
And yes, I'll be backing up my settings (again) after all this is finally resolved - but if I have to do a factory reset and restore from backup settings after every power outage - well, that's not a very business friendly device, IMO.
I have this exact same issue if I have a power outtage. It's absolutely infuriating. I upgraded from an Orbi RBK853 which never had this issue if I lost power or unplugged the device. It's driving me nuts. I'll spend 30-60 minutes after the power comes back just trying to get the thing to work. Same symptoms. It'll like work for a bit, then not work for a while, then work again, then not. Even the hard wired ethernet ports have the same behavior (my computer is plugged in physically to the satellite which is plugged into the router for ethernet backhaul). I'm also on 3.2.6.100. Again, I had 0 issues with power outtages with the Orbi RBK853.
This isn't the most recent log but I don't want to go test turning it off and on again and waiting another 7 years for it to come back online. There seems to be some issues with syncing to the router, at least from what the log looks like: (192.168.1.254 is my SXR80's static IP, it's in AP mode connceted to my pfsense hardware firewall):
[admin login] from source 192.168.1.109, Saturday, July 03, 2021 18:35:30
[Config Sync] Satellite 94:A6:7E:XX:XX:1F configuration isn't synced. re-syncing., Saturday, July 03, 2021 18:24:47
[Config Sync] Satellite 94:A6:7E:XX:XX:A7 configuration isn't synced. re-syncing., Saturday, July 03, 2021 18:18:38
[Time synchronized with NTP server] Saturday, July 03, 2021 18:18:25
[Config Sync] Satellite 94:A6:7E:XX:XX:A7 configuration isn't synced. re-syncing., Saturday, July 03, 2021 18:18:07
[Internet connected] IP address: 192.168.1.254, Saturday, July 03, 2021 18:17:56
[Internet connected] IP address: 192.168.10.2, Saturday, July 03, 2021 18:17:52
[Internet connected] IP address: 192.168.20.6, Saturday, July 03, 2021 18:17:52
[Internet disconnected] Saturday, July 03, 2021 18:17:39
[Internet disconnected] Saturday, July 03, 2021 18:17:05
[admin login] from source 192.168.1.109, Saturday, July 03, 2021 18:16:59
[Time synchronized with NTP server] Saturday, July 03, 2021 18:16:08
[Initialized, firmware version: V3.2.6.100] Saturday, July 03, 2021 18:16:03Man, I WISH it'd only been 30-60 minutes to get it resolved. I'm up to the 3-4 hour range, and have lost track of how many factory resets and power cycles I'm up. Had to take a break, as I was getting close to losing my temper.
Additional observations:
- Following a factory reset, I can generally get most of the way through the manual configuration.
- Automatic config isn't an option if you want to use the setting for port 2 at 1G, vs the normal Internet port. Why would you use the slower speed port? Because that was required to get the ethernet backhaul setup during the initial nightmare marathon config - not sure if it's still required with 3.2.6.100. (This has now reached a new nightmare level, btw - surpassing that of my in-laws)
- There seems to be an issue with how network detection is operating. A few times now, I've gotten a message that there was a "conflict with my ISP's settings, and your LAN 1 IP address has been reset to 10.0.0.1."
- For the record, I had the LAN 1 IP set to 194.168.X.X, and the DHCP address issued to the router for the "Internet" port is 192.168.Y.Y.
- Sometimes that 10.0.0.1 sticks, and sometimes it flips back to the assigned IP - seems to be random.
- Putting it into AP mode is as far as I've gotten - once it starts processing the swap, you're pretty much done being able to do anything until you start the factory reset dance all over again. I've never gotten the admin portal to come back up, no matter what IPs I've tried - not the 10.0.0.X range, not the default 192.168.1.1, nor the custom assigned IP. DHCP server shows a lease for the correct management IP, but the page won't load & there's no response to ping / tracert. And yes, that's while direct attached to it with a known good cable.
I'm literally done, at this point. Typing all this out, and thinking about how much time I've wasted following the troubleshooting steps from the manual, adding the tricks I've picked up over the years, and scouring the forums - I'm done messing with it. I may give it another 30 minutes or so tomorrow, but otherwise - it's going back in the box, and our old reliable Nighthawk will be back in action.
If that happens, I'll also be updating my Amazon review.
Addendum: About halfway through this debacle, the Insight app informed me that I had deleted it from my location..... Yeah, I did no such thing. The Insight app is a whole 'nother issue - but at least it's not as bad as the Logitech GHub! :smileyvery-happy:
Actually I solved my problems using an APC for each device,no power outage no trouble.I can say also that SXR80 is used in AP mode and in this fashion I never had problems about IP addresses,the router correctly receive its ip and distribute the other ips to the satellites.It never lost its configuration also after hours that was off...
I've actually got each satellite connected to a power strip. Unless by APC you mean like one of those back up units that can supply power for a while in the event of an outtage (my strip brand happens to be APC haha)...that sounds like a neat idea that I just might have to try. I actually don't have an issue w/ not getting an IP (I have the MAC address of the router set to a static IP on the firewall: the router just simply gets that IP via DHCP). The problem is the connectivity. All the same symptoms everyone in here reported i.e. magenta, periodically working for a bit then stopping etc. Seems like it takes roughly 30-60 minutes for everything to 100% fully shake out and stop having issues in this situation. The router and satellites don't have any internet connection for a long period after an outtage. Yesterday it was about 20m. The hardware firewall itself comes back up in 90 seconds. During the time when the Orbis lack a net connection (I can connect to the router's static IP most of this time time btw, it just shows no net connection), if I directly connect to an open port on my physical firewall I have a network connection. It's really weird that after an outtage, besides taking a while to just get a connection, when I do get one, it'll last for a bit, then periodically stop connecting, then come back, etc. It's like there's some long period where maybe the router and satellites are just having issues syncing everything or something (idk just spit balling). Next the I have an outtage I'll do more in depth tracking of the colors and everything as well as logs and follow up here. It's summer in Pittsburgh so that means any minute now my power will go out in a storm.
I should mention I just got these (router and 4 satellites) roughly 2 weeks ago directly from Netgear's site. After initial set up following the instructions I immediately upgraded to the latest firmware and then did my configuration. Not sure if that makes a difference or not.
- You cannot say you solved your problem by having backup power, meaning you will never turn off the router! That clearly is not a solution. Netgear needs to fix this. I returned my router and got a new one. My first tests unplugging worked so far. Hopefully it remains this way.
Yes it's a workaround!However,having a UPS to protect your devices it's also a right practice.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
