NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Orbi router solid magenta (not the satellite)
My Orbi router (not the satellite) stays solid magenta after rebooting. When I login to the router, every parameter looks OK. The router is in Access Point mode and has received an IP address from my...
Since my previous post I followed the recommendation to turn off Beamforming and Mumimo. This didn't, in and of itself, resolve the magenta light on the Orbi router, nor did it resolve dropped calls as I moved between the router and either of the satellites. However, the phone situation seemed a bit better and so I've left it that way.
I wondered - and this may not make any networking sense, whether the magenta light was a "signal" (unintended), that the router cache had become clogged. My Fios gigabyte browsing had slowed down a small amount and this was another thing that made me think along these lines. In my oh-so-many years with cable the cache on my surfboard modem had to dumped every few weeks. I would unplug and leave it for a good 10 or 15 minutes and use /flushdns in windows.
Now with the FIOS gigabit router and the Orbi, I changed the DNS addresses using ones generally considered safe and fast rather than letting FIOS choose the DNS. I did a /flushdns in Windows and also cleaned the cache on my default browser. After this I went to my unplugging routine below.
I then unplugged the power from the Orbi router and both the satellites. I also unplugged the ethernet cable running from my FIOS router to the Orbi. Following old-school technigques with cable I left everything unplugged for over an hour. I then plugged one thing back at a time and gave each device about 10 minutes to "settle in". So first I plugged the network cable from FIOS to Orbi and powered the Orbi router. Waited a good ten minutes. No magenta light and router working (checked with my phone by standing close to it). Then I plugged the power into one of the satellites and repeated the ten minute waiting game. Then...the last satellite. It's been about two weeks and everything is working very smoothely without any magenta light or loss of speed.
Then the cell phone (Android LG V10). I found that calls frequently "held on" as I moved between router and satellites - but not always. Found an excellent Android download Home WiFi Alert. It gives very sensitive readings of WiFi signal strength (-db) which I ended up using to fine tune the placement of the Orbi satellites. This led to only very occasional dropped calls - usually when I moved very quickly. I tried several apps and found that SwiFi allowed me to customize instructions to the phone as to when to change to a different SSID - how poor should the signal be and where should it change to. Making this work seemed to require the use of my Guest network as well as my single SSID but this is not a problem for me.
Hope this helps some folks and I'll update as I recognize the "solution" has only been successful so far for two weeks.
Hello,
I have a RBR50 running V1.12.0.18 for weeks without issue. I moved the physical position of the router device and its uplink moved to a different port on my HP1910 switch. Ever since this move (or perhaps it was simply a power off/on), the router device is showing the magenta solidly and is not manageable. I use a Sophos UTM firewall to assign IP addresses (MAC address mapping aka DHCP reservation) so I always know that my PCs and devices will have the same IP address (even when they are set to use DHCP). I am able to manage (like other people have noted) the satellite device (which displays no light ring so all is well), and I can see the wireless network is working correctly and internet works for wireless devices. But the router device cannot be managed by what should be its reserved IP.
I did a power reset on the router device and I noticed that pings to the DHCP reserved IP address did work for around 10-30 seconds and then loss of pings. I checked my firewall DHCP log and it showed the following:
2017:08:16-07:15:09 firewall dhcpd: DHCPDISCOVER from b0:b9:8a:59:ab:42 via eth0
2017:08:16-07:15:09 firewall dhcpd: DHCPOFFER on 10.4.1.25 to b0:b9:8a:59:ab:42 via eth0
2017:08:16-07:15:14 firewall dhcpd: DHCPREQUEST for 10.4.1.25 (10.4.1.1) from b0:b9:8a:59:ab:42 via eth0
2017:08:16-07:15:14 firewall dhcpd: DHCPACK on 10.4.1.25 to b0:b9:8a:59:ab:42 via eth0
2017:08:16-07:15:19 firewall dhcpd: DHCPDISCOVER from b0:b9:8a:59:ab:42 via eth0
2017:08:16-07:15:19 firewall dhcpd: DHCPOFFER on 10.4.1.25 to b0:b9:8a:59:ab:42 via eth0
2017:08:16-07:15:24 firewall dhcpd: DHCPREQUEST for 10.4.1.25 (10.4.1.1) from b0:b9:8a:59:ab:42 via eth0
2017:08:16-07:15:24 firewall dhcpd: DHCPACK on 10.4.1.25 to b0:b9:8a:59:ab:42 via eth0
2017:08:16-07:16:01 firewall dhcpd: DHCPRELEASE from b0:b9:8a:59:ab:42 specified requested-address.
2017:08:16-07:16:01 firewall dhcpd: DHCPRELEASE of 10.4.1.25 from b0:b9:8a:59:ab:42 via eth0 (not found)
2017:08:16-07:16:01 firewall dhcpd: DHCPRELEASE from b0:b9:8a:59:ab:42 specified requested-address.
2017:08:16-07:16:01 firewall dhcpd: DHCPRELEASE of 10.4.1.25 from b0:b9:8a:59:ab:42 via eth0 (not found)
The HP switch shows the correct MAC address and the IP address (that the firewall has assigned to the RBR50) under the switch's ARP Management: Arp table. RTSP Port fast (aka port edge) was on for the port it was changed to. Turning off Port fast did not help.
Despite what https://kb.netgear.com/23664/How-do-I-locate-my-router-s-IP-address tells us, that the management IP should be 192.168.1.1 or 192.168.0.1, using Wireshark to look at ethernet traffic led me to find that the IP was really 169.254.29.170.
Using this self-assigned IP, I was able to get to the management page (after I changed my computer to be in that IP range) and try out the suggested trick of setting the Advanced: Advanced Setup: Router/AP mode to be AP mode (even though it is already selected), and hitting apply. After the Orbi rebooted, it was able to pickup the DHCP reserved IP from the firewall and hold onto it for more than a minute. But only until the next reboot. Then it would do the usual sequence:
1. Obtain from DHCP an IP address.
2. Release the IP address
3. Become self-assigned.
Just to be sure my Sophos UTM was not to blame with some sort of DHCP reservation problem, I cleared the DHCP leases on the firewall. Then I rebooted the orbi but with the reservation removed from the firewall. As expected, the Orbi got an IP from the DHCP pool and then released it 10 seconds later and became self-assigned. Same sort of nonsense recorded in the firewall DHCP log as above, except where ever it said "(not found)", it was showing "(found)"
The trick of "selecting" AP mode and doing a reboot only works until you next reboot the Orbi router. Setting the "Choose IP Address settings on this access point" from "Get dynamically from existing router" to "Use fixed IP Address (not recommended)", and then setting the fixed IP to be the same as the DHCP reservation I had on the firewall, seems to be the best option for me to continue to have a manageable Orbi (so I can see Attached devices), which withstands Orbi reboots. You can only set the fixed IP when in this Router/AP mode screen as the other Internet Setup screens are disabled.
Don't ask me why other people are finding it helpful to do the opposite of what was my solution - going from the Router/AP mode of using "Use fixed IP Address (not recommended)" to "Get dynamically from existing router".
- jacher's tip of setting AP Mode's static IP address on the RBR50 router node makes the router node stay on the assigned address as desired for v1.12.0.18 firmware. Thank you very much for the detective work, jacher.
I wish I had returned this Orbi kit. It wastes my time.
Aaargh, I just got a message in the Orbi web console that v2.0.0.72 firmware is available.
atlr wrote:
I just got a message in the Orbi web console that v2.0.0.72 firmware is available.Does this mean Netgear has stopped its totally obnoxious practice of pushing f/w updates at their convenience, not yours?
I finally gave up on my Orbi entirely, laregly because of that issue. I got a Synology RT2600ac and it's so much better.
My Orbi router web page (no problems with getting remote access management since changing to static IP) shows no update available (yet). And yes, I did add another satellite, set with DHCP reservation, which was able to be seen by the router after I updated its firmware.
I will wait for the next incremental version after 2.0.0.72 before upgrading/rocking the boat potentially.
Model Name Device Name Current Version Status Router RBR50 RBR50 V1.12.0.18 No new firmware version available. Satellite RBS50 RBS50_1 V1.12.0.18 No new firmware version available. Satellite RBS50 RBS50_2 V1.12.0.18 No new firmware version available. Just a quick update from my perspective. The date is Sept 15, 2017. I use my Orbi system as an access point (AP) and not as a full up router.
No new firmware is available that I can see. The Orbi does not see any new firmware nor does the Netgear website offer any new firmware. Latest version is 1.12.0.18. The magenta light error on the main Orbi router has been present for over 6 weeks at my place. Does not matter whether I use a fixed IP assigned to the Orbi or allow DHCP to assign an IP.
As far as I can see, the magenta error light basically signals "Web Interface Offline - System NOT controllable by web browser interface". All other functions seem to work fine. This is a very annoying fault that Netgear should fix immediately. The hardware seems well thought out but they really need to put a little TLC into the software.
Silent_Forest wrote:....No new firmware is available that I can see. The Orbi does not see any new firmware nor does the Netgear website offer any new firmware. Latest version is 1.12.0.18....
The links to the 2.0 firmware can be found in the following thread:
https://community.netgear.com/t5/Orbi/OrbiOS-2-0-availability/td-p/1368730
I would avoid the firmware in these links. This firmware was pulled back and taken off the official download page for " futher testing". In other posts on this message board, you will see Orbi users who tried this firmware and had issues.
- As ridiculous as it sounds, try doing what always works for me to clear the magenta light. I posted it awhile back.
Silent_Forest wrote:I would avoid the firmware in these links. This firmware was pulled back and taken off the official download page for " futher testing". In other posts on this message board, you will see Orbi users who tried this firmware and had issues.
Not wishing to argue, but if you are already experiencing severe 'hair pulling' issues, there is not much reason to avoid the pre-release beta firmware that has been posted. This is not alpha firmware. I just updated my RBK3000 with the two satallites and everything is behaving. I am still not turning on UPnP but the release feels solid and even a little faster than previous firmware. If it remains solid for the next week, I'll turn on UPnP and see if that works now.
Hi, this is my first post in the community.
Yesterday i got my RBR50+RBS50 AC3000.
I have a 4G internet connection in a Huawei b315, working also as a router (and i can't put it in brigde mode, so i have to usea de orbi in AP mode), in the third plant of the house.
Before yesterday i also had a Netgear RT6400 (just working as a AP+Switch, connected with cable to the huawei), a TP-Link switch (connected to the netgear) in the second plant. Finally i had a tp-link repeater RE450 in the first plant wireless connected to the netgear.
Yesterday i put down the netgear router, the tp-link repeater, and turned off the huawei wifi. Then i connect the orbi router in the place of the netgear rt6400, and the satellite in the place of the tp-link repeater. Everything was fine! i could setup it fast and with no problem, set the router in AP mode with a fixed ip, connect all the devices to the new wifi (16 in total)... and i was very happy, just one ssid that covers all my house! Hue Lights, Netatmo camera, thermostat, weather station, smartphones, tablets, laptops, tv, xbox, mediaplayers, satbox, Nas... all working fine.
This morning: The router has the ***** magenta light... (satellite was fine) I have to go to work, so i could not check it properly, but i think that this is the only problem... i can access the nas, and lights and other stuff from my work, so inetnet is working...
Will come back when i get home and could check the web ui and other stuff, and try the "solutions" you found.hopefully! i will check when i return home :)
When i returned home yesterday the magenta light was on, i tried the "recheck ap mode" trick and the light goes off, but come back after an hour or so...
I could access the web ui and all my devices an services were connected to internet without problems...
Next i upgrade the router and the satellite to the new 2.0.0.72 firmware and so far so good. No magenta light and the "connected devices" list shows a really good (and new) information...
Will keep posting if something changes...
After a couple of weeks of no Magenta light on the router (operating in AP mode) and with two satellites now in play, I thought to myself (morbid curiosity), why not reboot the router and see if the magenta light problem comes back. After I did a software reboot (using the management page of the router (still accessible on the static IP (and dhcp reserved IP))), no magenta light. Great!. But in the morning, the magenta light was on. I did a hard power off (pulled the plug) and waited a few seconds and plugged it back in. No magenta light. But hours later, the magenta light was back on. The magenta light remains on but I see no issue with connectivity, management of the device, wireless devices or satellite connectivity. All is good -- EXCEPT in the firmware update (under Advanced), the router shows "No internet" and thus can't determine if there is a firmware update. The satellites both show "No new firmware version available." So this "No internet" is the only clue that there might be a problem and the only ill effect of the magenta light (other than what is supposed to be invisible being purple).
I would guess that the router periodically tries to contact some server on the internet (as a test of internet connectivity) and if it fails, it turns on the status light to purple. And it never tries again to see if the server is reachable. So it remains purple.
Model Name Device Name Current Version Status Router RBR50 RBR50 V1.12.0.18 No Internet Satellite RBS50 RBS50_2 V1.12.0.18 No new firmware version available. Satellite RBS50 RBS50_1 V1.12.0.18 No new firmware version available. Hi,
I have exactly the same problem/behavior with one satellite in place. I have not rebooted the MESH infrastructure now for more than 2 month and I have no magenta ligt, but I'm pretty sure that I will get the light back on when I reboot the rooter or do a firware update. I also have the message "No internet" in the firmware update page and I have very old firmware in place, which is OK for me up to now because I don't have an issue with the MESH ;-) My RBR50 FW is V1.8.0.6 and the RBS50 V1.9.1.12.
From my point of view it's VERY ANNOYING that Netgear DOES NOT seem to make any changes to fix this BUG. We are not talking about a repeater system which costs 50€, we are talking about a high end solution which costs more than 400€.
I'm very happy with the general spped of the mesh system, but the support of Netgear is unbelievable!!!
I hope someone from Netgear will read there own form entries!
Regards from an angry Netgear Orbi user
Ralf
- When i had the magenta light, the only place wher i could see a problem was de "No internet" that you talking about... I'm with the 20. firmware and i rebooted the router three or four times, no more magenta lith yet... Someone with the 2.0 firmware and this problem? maybe this firmware fixed the issue...
Hi,
one question regarding the firmware update to 2.x.
Have you done this update manually by downloading the files? Because of the "No Internet" I don't see a new firmware on the GUI Firmware Update page.
Can you please also share the location from where you have downloaded the V2.x firmware for RBR50/RBS50?
Thanks in advance for your help!
Regards,
Ralf
Of course!
I downloaded the firmware from this forum, official post:
https://community.netgear.com/t5/Orbi/OrbiOS-2-0-availability/td-p/1368730
And updated the router and satelite manually
The attached devices list now looks better and also shows more info (satellite/router conected).
This firmware also allows a "chain" setup like Ruter<->Satellite<->Satellite and other fixes... (maibe magenta lights?)
I'm working with it for three days now, and so far so good. Ap mode with fixed ip and 12/14 devices attached...
Hi,
Thanks a lot for the infos. I will give it a try and will share my expiriences here in the forum.
Regards,
Ralf
Hi,
I have just updated my RBR50/RBS50 systems to the latest available firmware 2.0.0.72. The good news - everything seems to work fine, I can access the GUI, the spped ist as it was before and in the Firmware Update tab I can check for available firmware also for the RBR50 - no longer the message: No Internet. No good news with bad news :-( As expected, the RBR50 Router shows the magenta light :-( :-(
From my point of view this bug is still available, and as I mentioned before Netgear seems to be NOT INTERESTED in fixing the problem.
Regards,
Ralf
Sorry to hear that...
So i can expect to get the magenta light back at any moment... :(
If i get it back before the "90 days of live support" i will open a ticket...
ralfboernemeier There is a newer .74 firmware available on the download site. I don't know if this will fix your issue, but it's worth a try.
Hi,
Thanks for the hint - I have just done the update to V2.0.0.74 - but still the same problem - magenta ring solid on :-( GUI and Internet works as I can say until now without problems.
Still an open issue. I will wait a few days and post my findings here.
Have a nice weekend.
Regards,
Ralf
Looks like 2.0.0.74 is being released to the wider public. I did a check for updates on the router, and saw:
A new firmware upgrade is available. Click here to get it.
Model Name
Device Name
Current Version
Status
Router
RBR50
RBR50
V1.12.0.18
No Internet
Satellite
RBS50
RBS50_1
V1.12.0.18
V2.0.0.74
Satellite
RBS50
RBS50_2
V1.12.0.18
V2.0.0.74
Release Notes:
[New Feature and Enhancements] Supports daisy-chain topology, which allows Orbi satellites to connect to other satellites or to the router.
[New Feature and Enhancements] Updates the Speedtest API to provide in-progress data.
[New Feature and Enhancements] Updates the Attached Device page in the UI with the following changes:1. Shows device type. 2. Shows connected Orbi and band. 3. Allows connected device and Orbi satellite renaming.
[New Feature and Enhancements] Supports radio transmit power control.
[Bug Fix] Fixes a bug when the main SSID contains a space.
[Bug Fix] Fixes a bug where the genie remote reboot command might trigger a system factory reset.
[Bug Fix] Fixes a bug where genie remote access fails when the Orbi system is in AP mode.
[Bug Fix] Fixes security vulnerabilities.
Lucky for me, I do not see any auto-update occuring. Perhaps the router being solid magenta (and not seeing the internet supposedly) is preventing the auto-update from occuring.
Perhaps I will follow Butch1326 advice and disable auto-update to be sure as seen in forum post: https://community.netgear.com/t5/Orbi/Firmware-V1-12-0-18-Discussion/td-p/1320421/page/5
I see the firmware update message this morning. will update when i get back home after work.
BTW, second week without issues...
Skimmed through this thread as I have been going through similiar issues as well. Orbi is in AP mode and have just experienced a flurry of issues and frustration.
I've been fighting both scenario's of the orbi router or orbi sat's having a magenta light. After using the WAN port on the router and rebooting all the devices (several times), they are all normal. This is after an insanly horrible experience of getting .74 firmware installed.
The problem I'm having in this scenario now (curious if you all are?) is that my satellites are getting an IP from my Asus router, and I can access them, but they keep falling off the attached dervices on the Orbi router and all wireless devices are being sent to the Orbi router.
This systems feel far too flakey to warrant the price tag.
