NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Orbi firmware update v2.1.4.16 availability
We’ve been monitoring issues that some customers have experienced in OrbiOS 2.1.4. In response, we’re releasing firmware that provides a permanent fix for the homekit issue along with various other fixes. Please use the manual firmware upgrade process to apply to your Orbi.
Release note:
- Fixes issues with the Apple HomeKit connectivity
- Fixes the wireless crash and reboot issue when the router is under stress
- Fixes WiFi disconnection and IOT issues
- Fixes an issue where devices on the Guest Network are able to see (but not connect to) some devices on the main network
- Fixes an issue where device boot order caused devices connected over Ethernet Backhaul to connect wireless backhaul
- Updates the OpenVPN certificate from MD5 to SHA-256
Note:
CBR40 will be available later this month.
We look forward to hearing your feedback.
-NETGEAR Team
808 Replies
Oh well, that didnt last long.
Same issue persists. The difference now, it appears while using the device, whereas previoulsy, it happened upon waking.
Ipad shows connected to wifi and internet drops out. Ipad wifi must by cycled to reconnect again.
Support can reach out to me for logs, I have them saved.
Back to the locked room for more exercizes in futility.
Been running 2.1.4.10 for a while with no issues. I upgraded this morning to 2.1.4.16. At initial glance everything looks ok. If I have issues I'mm update the post, but I'm happy with the stability of the last few releases.
- I have installed this update hoping to fix severe disconnect issues. That seems to be better, but now wireless speed is down significantly, from 50+ mbps to less than 20. Wired tests to my router are still very good. I'm running an rbs40 in AP mode, no satellite currently.
Why am i getting this error when i attempted to update the satellites?
401 Unauthorized
Access to this resource is denied, your client has not supplied the correct authentication.
Ok, found the issue. The Orbi firmware update interface does not like Safari. When i used Chrome, i could see the login prompt for the Satellite (this prompt didn't show up in Safari).
I have an RBR50 and two RBS50's on wireless backhaul; download/upload speeds seem to be staying pretty good for me. 890Mbps/36Mbps down/up on my desktop wired to the router, and 550Mbps/37Mbps down/up on my iPhone X. All HomeKit issues I was experiencing seem to have gone away as well. *fingers crossed*
I thought this update was supposed to fix Apple Homekit connectivity issue. I had occasional issue with Homekit when the router/satellites were on v2.1.4.10. Now that they are updated to v2.1.4.16, Homekit is completely broken. I can't connect any of the devices in the Homekit network. Anyone else having the same issue?
Nice try but the router still reboot like before.
Router in AP mode, factory reset router and satellite.
Router System Uptime 01:25:35 !!
Satellite System Uptime 14:48:55Both started yesterday, same time...
Satellite connected with wired directly to my main router.
Router connected too with wired directly to my main router.
Is there a reason why the uptime can't be stable for the router !? Satellite works well ! in AP mode what could do the router more than the satellite that cause the reboot !!? it's a basic mode !
No issues. Mine is working perfectly - best its ever been. I have four Lifx globes, and I bought my Orbi RBK50 system mid March, and since then, I have had varying success with the Orbis, Lifx and Homekit. The beta FW just before 14 was the best, but two days ago I downloaded and installed FW V2.1.4.16. By the way, my Orbis are in Access Point mode.
Here's what happened
- There is one router and one satellite. The router shows 27 attached devices, 7 wired, and the satellite shows 14.
- It took about an hour of pink and blue ovals on both devices after I manually installed the FW (satellite first). I reverted to WiFi backhaul and once everything settled, I plugged in my Ethernet backhaul cable to the satellite with no problems
- After power-cycling a few devices, they eventually sorted themselves out and attached to the nearest Orbi
- Every device connected at 2.4Ghz is only able to do that - they have no 5Ghz capability (Lifx, iRobot, TP-Link switches, Google Chromecast and Wemo Link)
- Every device capable of both 2.4Ghz and 5Ghz (Apple, Google and Amazon stuff) is connected at 5Ghz
- Four Lifx globes connect to their own cloud, and also to Homekit, with no fuss. Until V2.1.4.16, a couple of Lifx globes connected but, despite bring fixed, wandered between the satellite and the router, but no more, for at least 48 hours.
I have Mac computer hardware, which runs a Mac app called WiFi explorer that shows signal strength and stability amongst other things. In the following snapshot the 2.4Ghz (blue) line shows the strongest signal but is less stable than the rock-solid 5Ghz line. (If I moved closer to the satellite it would rise to the top)
Here's a snapshot of my router config
- I was having iPhone and iPad issues for a while tried a bunch of stuff . Didn’t work . Finally I bit the bullet took a back up config . Did a factory reset upload clean firmware and applied config back . So far no major issues . I think the issue might be with incremental updates .
Well that experiment was short-lived. Updated from 2.1.4.1 to this new 2.1.4.16 on both the RBR50 and my single RBS50. Not only did the random WiFi drops out and router hangs issues continue they increased and changed a bit. Now when I try to connect with certain devices (like the Playstation PS4 connected wirelessly to play a game) the Router hangs and loses internet but does not stop broadcasting the WiFi signal. So all devices think they are connected but... no internet and no access to 192.168.1.1 on web or app. The app thinks the Orbi is not on the network but yet everything thinks it is connected. On 2.1.4.1 at least the WiFi network would drop completely so it would trigger my WiFi PowerSwitch to do a reboot and fix the issue (yes overkill for a home router and annoying but it is my fix). I tried hard rebooting many times and I tried factory reset and all options configured manually but... nope this new firmware is actually less stable for my system than 2.1.4.1 which did the drop and or reboot thing about 3-4 times a day average. Running a RBR50 and a single RBS50, no wired backhaul, daisy chain off. Lots of devices connect (about 13-19 at a time average) but seriously pretty standard set up. Bummed as I thought finally we had a solution to the family complaining "Dad the internet is gone again" issue. At least the remote WiFi power switch reboots it for me on 2.1.4.1 so I dont have to be there to do it myself now. I tried Velop but the speed decrease was about 40-50% slower than Orbin and the range was awful in comparison so I sent it back and kept the Orbi. Not sure what to do now. Orbi has the speed and range dialed in over everything else but... this uptime issue is terrible.
Same boat - tried velop changed to Orbi and was stable until this last 2.1.4.16 release. Now had to pull wired back haul just to get the network functional. Speedtest showing 200mbs for my gig service even when 2 feet from the router. Waiting to dump and switch ...but not to netgear. The app is not as functional as competition and this Orbi situation has left a bad taste.
I'm at the end of the line. I am returning this terrrible router/satellite to Costco. I have never had so many issues with a router/computer/TV or any electronic device as I have had with the Orbi. I tried to stick it out but after 1 full year of inconsistent internet I am done. I have tried all remedies suggested by Orbi including beta firmware, replacing the actual satellite/router and none have worked. The only consistent thing about the ORBI is that it does not work consistently.
This firmware update is no better and is the same old story. Performed this update and the router and satellites have been disconnecting non stop. Multiple reboot and power on/off cycles and still not working as it should.
Goodbye ORBI
Hsc1102 I feel your pain haha. What do you plan to move too? I tried Velop and it was a no go for me (40-50% speed decrease and I would need like 5 nodes to get close to the coverage of just the Orbi router and one satellite). I am entertaining alternatives always and not sure what is worth trying. Curious as to what you decide. Thanks!
I am ordering the Google wifi. I know that in all tests and reviews the ORBI was best performing but in my time of ownership, the ORBI rarely if ever attained and maintained that performance. At this point I would rather take consistency.
arosstyler wrote:
Hsc1102 I feel your pain haha. What do you plan to move too? I tried Velop and it was a no go for me (40-50% speed decrease and I would need like 5 nodes to get close to the coverage of just the Orbi router and one satellite). I am entertaining alternatives always and not sure what is worth trying. Curious as to what you decide. Thanks!
Just to add my experience to this, my Orbi RBK50 has been working all right on wired backhaul since v2.1.3.4, and it's so far so good on v2.1.4.16 as well. I updated manually—satellite first, then router (as recommended)—and then also power cycled both units subsequently ("simulate power outage") and everything came back up as expected.
Evidently not all users are having an issue-free time here, so just looking at my setup maybe there's one more thing those who are having issues (especially with wired backhaul) can try. I've set up my Satellite to get an assigned IP from my Router (10.0.0.2 in my case because I've got 192.168.1.x used by my ISP modem/router, but others can use 192.168.1.2 and so on, accordingly), since the Satellite is always going to be a part of the network. There shouldn't be any harm in trying this, and perhaps the assigned IP helps the system with reconfiguring when switching from wireless to wired backhaul, or quickly recognising the wired backhaul connection straightaway when (re-)booting up. No guarantees this fixes anything for anyone, but hopefully it helps somebody out there!
i haven't had any e backhaul issues since version x.x.4.10 (x.x.4.16 is ok too) since i made sat's 0.2 and 0.3 ip's. Before it gets stable with wired, wireless IP will be all over the place but when it settles to 0.2 and 0.3, its all good
Just wanted to chime in and let you know, that updating my RBK40 to 2.1.4.16 went just as smooth as 2.1.4.10 did. This comes as no surprise, since my system didn't had any issues with previous FWs. However, the - more cosmetic - issue, of my RBR showing solid magenta after reboot, due to the wired backhaul setup, hasn't been fixed, but I can live with that. Simply turning the LED ring off is easy enough, since my system never booted on its own.
Finally, it resolved my previous problems. Internet back to normal. Thank you for the bug fixes.
Best regards,
Elofi
Updated to 2.1.4.16 and the system works fine. But, I've never had any issues in the 17 months I've owned Orbi. I'm running in AP mode, with IP addresses statically assigned to the Orbi router and two sateliites by my Mikrotik router. I have numerous Sonos devices, Bluetooth sensor devices, Hue bulbs, wireless thermostats, and some custom 2.4 GHz Zigbee sensors in the house.
I want to call out a "good job" to the Netgear team for posting this beta and NOT forcing it on everyone - and instead, waiting for feedback etc.
I understand it doesn't solve everyone's problems, but I think the method here is better and responds to the complaints on this message board that new versions are just launched/forced on everyone and then new problems are introduced.
This version did also address specific concerns (MD5 etc) so at least it's a bit of progress, even if it's not the silver bullet.
Keep working on improvements and fixes please.
And by the way, I did install it, and no new problems for me. I re-did my VPN with the update and that works correctly.
Thanks for sharing.
I would like to achieve the following setup: RBR50 as AP (connected to Cisco Router) and 2x RBS50 with wired backhaul.
Hope you can help with my questions below:
Question 1
Is this wiring correct for RBR50 as AP?
>> Connect wire from RBR50 [Internet port] to Cisco Router [LAN port].
Question 2
Can I have wired backhaul with RBR50 as AP?
If yes, how should it be wired? LAN cable from RBS50 connect to Cisco Router or RBR50?
Thanks in advance
To tanws2005, post 419.
I have no experience with a Cisco router, so I'm assuming it is this device that connects to your internet service and handlse your routing needs, eg firewall, NAT, DHCP, security, port management if any, etc. Having these services delivered by your Cisco means you must put your Orbi router into AP mode, which is your intention. Does the Cisco also handle WiFi? If so, disable it.
- Question 1, your wiring is correct, whether its AP mode or not.
- Question 2, yes you can have a wired backhaul with your RBR50 in AP mode. This is how I have mine set up although I have only one satellite.
If your Cisco router delivers a good service to you now then that should be preserved, because AP mode disable the Orbi system's router functions altogether. It's just a WiFi distribution system, which I have used now in AP mode for around 3 months quite satisfactorily, more recently with FW v2.1.4.16, and a wired backhaul.
Prior to setting up the Orbi system, download the latest 2.1.4.16 firmwear and save it. Put the satellites in the same room as the router for setup. Connect the RBR50 to the Cisco as per question 1, and connect your PC/Mac to a port on the Cisco. Switch on the RB50 and the two RBS50s, but do not cable-connect the satellites yet. On your browser enter "orbilogin.com" (If this doesn't work, the defaule IP address is 192.168.1.1). Once the router fires up, follow the steps, including letting it find the satellites. At this stage, you should be connected, but in this basic form you are in router mode at the starting point for detailed configuration. At this point, click on the Advanced tab, go to Advanced Setup, and choose the second item "Router/AP Mode". You will be presented with a couple of squares, the right one of which is AP mode. Choose this, then hit "Apply". When you recover from this, you will be in AP mode with all your settings inherited from the Cisco router. Don't forget that the default IP address for the Orbis before AP mode is 192.168.1.1, but if your Cisco router has a diffent IP address, like 192.168.100.1, then your Orbis will inherit the IP addresses allocated by the Cisco's DHCP server. You may have to search for them in the Cisco's connected devices. I recommend that in your Cisco router you assign reserved IP addresses for your Orbis so these addresses are constants. I have mine set up as 192.168.100.40, and 192.168.100.41.
Assuming you have success here, you can load the Orbi router and satellites in different tabs on your browser, and look at the attached/connected devices to prove that everything works. Under the RBR50's Advanced tab, goto Advanced Setup > Wireless Settings. I have everything checked, and my system continues to run just fine, but others have reported mixed success with some of the se settings. For your information, Daisy-Chain Topology means that your furthest away satellite connects to your next satellite, then to the router. The unchecked alternative is a star topology where all satellites communicate with the router, like the spokes of a wheel. I have just one satellite so for me it's either or, but in your case, this setting may have more meaning.
If all is OK so far, move the satellites to their destination, still on wireless for the time being, and recheck. It seems that others have had success leaving the system in wireless backhaul mode for a day or two to let it settle down. Then you can try connecting your ethernet cables to the satellites. Many contributors to the Orbi forum have had success if their internet cable between the router and satellite(s) is as direct as possibe, eg bypassing switches, and indeed mine is configured this way.
I hope this has been helpful and you have success. Good luck
