NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
raykag
Apr 29, 2018Guide
OrbiOS 2.1.4.10 kills Internet access if you use Ethernet back haul
I'd been happily using the RBK50 Orbi AC3000 single satellite system since June of 2017 and started using ethernet back haul succesfully around October 2017. Typically 8-16 connections at any given ...
- Oct 04, 2018
I updated my firmware to 2.2.1.210 today and it solved the ethernet back haul taking the internet connection down and eliminated a couple of other oddities that I was experiencing.
raykag
Apr 30, 2018Guide
Thanks FURRYe38 and Elofi. I'll give that a shot.
FURRYe38
Apr 30, 2018Guru - Experienced User
Let us know how it turns out.
- WAPApr 30, 2018Apprentice
I've come to the conclusion that ethernet backhaul in 2.1.4.1 doesn't work even though it worked fine for me in the previous release (2.1.3.6?). I've come to that conclusion based upon the following:
-6 days ago was autoupdated to 2.1.4.1 the problems started immediately. My setup was 2 wired sats and 1 wireless sat.
-performed full-reset as has been advocated on the forum. still nothing but problems.
-on day 5 decided to convert one of the wired sats back to wireless and left the other wired sat unplugged. (meaning I now have 2 wireless sats). I had 3 days of zero problems with this config.
-to test if the wired sat was the problem I turned it back on. It connected but it immediately knocked off one of my 2 wireless sats. No combination of router rebooting or sat rebooting could get the knocked off wireless sat to come back.
-conclusion: given that I had 3 days with zero problems without ethernet backhaul and then no more than 5 minutes after plugging in the 3rd sat with ethernet nothing but problems my conclusion is that ethernet backhaul is broken.
To advise netgear of my config, I've been on the forum for months and made sure that when I did the full reset 6 days ago that I had everything turned off including daisy chain. My wifi devices are very simple, a bunch of ipads and iphones and a couple of laptops. I don't have sonos, I don't have apple home, I don't have cameras, I don't use VPN. Other than a 2.5 ghz wifi sprinkler it is about as simple as you can get. All told I have less than 10 wifi clients. It can't be a orbi hardware issue because as soon as I unplugged the ethernet backhaul satellite and rebooted the wireless satellite and router one last time, the wifi satellite that refused to connect when there was ethernet sat present came back online in less than 3 minutes once that ether sat was gone.
-Right now I'm limping along with my 2 sats on wifi, really would like to be able to plug that 3rd sat back in but it is too far away from the orbi router is use wifi backhaul...this sat needs to be ethernet...ethernet availablilty was the whole reason I bought the orbi back in december.
My ISP is Uverse Gigapower. BGW210 is the gateway (wifi disabled). I have all the TV Set-top boxes isolated on a completely seperate netgear switch to ensure Uverse's multicast IGMP flooding is avoided. The orbi router is in AP mode with static IP. Every orbi option is turned off. I've set the wifi channel to one. I'm getting great performance out of the router and 2 wifi sats. Getting 400 MBPS up and down on all three.
Netgear: I'm hoping that you have enough evidence from the field now that you need to look closer at this latest firmware and provide an update to the forum community.
- Peace_105Apr 30, 2018Aspirant
I have the same issue I believe (started around April 24, 2018 while I was away on travels, but wife and kids complained), seems it has started after firm-ware auto updated to 2.1.4.10.
There has been NO changes in devices setups, satelite distance etc, so the problem seems definitely caused by Netgear latest firmware auto-update..
Symptom: My single Satelite goes Magenta (on and off all the time)... very frustrating. Have done the basic reboot, sync etc. Problem persists.
Not sure what "Ethernet backhaul" is?
Thus, not sure what I should do? or wait for Netgear to address this?... Appreciate any advice, thx.
- Peace_105Apr 30, 2018Aspirant
Update: I have unchecked the Enable Daisy-Chain Topology under Advanced tab --> Advanced Setup--> Wireless Settings as I only have one satellite (I do not need Daisy-chain)
Rebooted everything.
Still the problem persists = the Satellite drops connection with the Router repeatedly (goes on Magenta ... then goes blue, then Magenta again etc etc, all within 3-5 minutes cycles as it seems.
- raykagMay 01, 2018Guide
OK, it's only been about four hours, but Ethernet Back Haul with 2.1.4.10 has been working without any hitches after disabling Daisy Chain mode. I'm not sure you need to do all of what I did, but here are the steps I took to make it work:
- From a state of NO internet connectivity using Orbi Router and Single satellite with Ethernet Back Haul cable connected using firmware 2.1.4.10
- Disconnect Ethernet Back Haul cable
- Disconnected all other hard wire conections to router and satellite
- Turned off router and satellite. I did NOT factory reset them.
- Reset my cable modem (just to eliminate any doubt, but I'm not convinced this is necessary)
- Powered up the router and satellite and let them connect via wireless backhaul per the manual
- Reconnected the hard wires (except do NOT connect Ethernet back haul) and verified I had good connections with my devices, and most importantly, that my wife had internet :<)
- Waited a day, both to make sure wireless back haul was working, and for a time I would not deprive the household of internet if things went bad
- Logged into router and went to "Advanced" tab, Advanced Setup, Wireless Settings and deselect "Enable Daisy-Chain Topology". In other words, remove the check mark.
- The previous step took a few minutes, so be patient. There is no real indicator of what is going on. Sorry, I forget whether the router webpage just reappeared or if I had to re-log-in
- LAN and internet still worked with wireless back haul. I let it run in this config (Daisy Chain disabled) for a few hours to be sure.
- Turned off the router and the satellite. Reconnected Ethernet Back Haul cable.
- Held my breath and powered up the router and satellite. The satellite ring turned blue very quickly. I should have logged into the router to see if it had established a wired connection, but I was suspicious and pressed "Synch" on the router and satellite anyway. After about a minute, the satellite ring turned magenta, but do NOT PANIC. Wait a couple more minutes and the satellite ring turned blue again.
- Logged into router and under "Basic", "Attached Devices", the Satellite showed as a Wired connection!
- Checked my devices and had LAN and internet except for a single Windows 10 laptop. Rebooted the laptop and the internet and LAN worked fine. Rebooted my wireless printers for good measure, which are always finicky anyway.
- Anyway, been working for four hours plus. Wish I could disable auto firmaware updates, or that my router config would be left the same after an auto update.
Hope this helps anyone else with this problem and thanks again to Elofi and FURRYe38!
- FURRYe38May 01, 2018Guru - Experienced User
Ok, thanks for the details post.
One thing that users shouldn't need to do however they can follow your process if they want to, you don't need to turn OFF the router and satellite then connect the ethernet back haul cable then turn on and hit the sync buttons. In a wireless backhaul configuration and the system is ON, users should be able to connect the ethernet cable to the satellite and then let the system re-configure the connect automatically. give 5 minutes and look for the BLUE Led on top. This method should work as well.
Glad yours seems to be working. Let us know how it goes thru the weekend.
- sventhegrinchMay 06, 2018Tutor
Confirmed, that solution fixed the wired backhaul issue for me as well. It would be really nice if Netgear would either allow me to disable auto updates (like this one that left my family without network while I was on a trip) or push working firmware updates. Either one... I prefer actually a combination where I can choose to update to a working firmware when I am around.
Side note... having a link in the support page associated with the recent formware update that "shows how to disable auto update" for a different model or version of the firmware also doesn't help. Would be good to obsolete that article, or make the connection more explicit.
Thanks for the advice,
Sven
- FURRYe38May 06, 2018Guru - Experienced User
Did you try blocking port 443 and 20-21 to the IP address of the router?
sventhegrinch wrote:
Confirmed, that solution fixed the wired backhaul issue for me as well. It would be really nice if Netgear would either allow me to disable auto updates (like this one that left my family without network while I was on a trip) or push working firmware updates. Either one... I prefer actually a combination where I can choose to update to a working firmware when I am around.
Side note... having a link in the support page associated with the recent formware update that "shows how to disable auto update" for a different model or version of the firmware also doesn't help. Would be good to obsolete that article, or make the connection more explicit.
Thanks for the advice,
Sven