NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
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 ...
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.
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!
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
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
Thanks, the suggestion to disable the daisy chain made the wired backhaul work. So did of course not using wired backhaul and instead falling back to wireless (which I didn't want long term).
In what way would an open port on 443 and/or 20-21 be needed? And if so, why is that something that an end user would have to know/do, backhaul configuration should (IMHO) be something that works without user intervention. Not sure I see a place where backhaul internals are exposed... or are you saying that regular wireless connectivity is affected/affecting backhaul?
Thanks,
Sven
Blocking ports, not opening. Seems the others have said the blocking these ports directed to the routers IP address seems to stop the auto update.
sventhegrinch wrote:
Thanks, the suggestion to disable the daisy chain made the wired backhaul work. So did of course not using wired backhaul and instead falling back to wireless (which I didn't want long term).
In what way would an open port on 443 and/or 20-21 be needed? And if so, why is that something that an end user would have to know/do, backhaul configuration should (IMHO) be something that works without user intervention. Not sure I see a place where backhaul internals are exposed... or are you saying that regular wireless connectivity is affected/affecting backhaul?
Thanks,
Sven
Rather than disabling daisy chaining entirely, I went in to the wired backhaul satellite and enabled STP (spanning tree protocol). You can search my other post for instructions. This has stabilized my network for now until Netgear puts out a fix. I do wonder if STP is one of the internal settings that gets changed when daisy chaining is toggled on and off. The only problem with STP is that it is not persistent - in other words, if the satellite loses power the. STP gets reset.
Daisy chain is only needed if two or more Satellites are in used and if the user has them placed in a chain so they are able to use the daisy chain feature. So if theres only one satellite, Dasiy Chain isn't really needed as is easier to juts disable the check mark and save settings for the average home user.
Zdman wrote:
Rather than disabling daisy chaining entirely, I went in to the wired backhaul satellite and enabled STP (spanning tree protocol). You can search my other post for instructions. This has stabilized my network for now until Netgear puts out a fix. I do wonder if STP is one of the internal settings that gets changed when daisy chaining is toggled on and off. The only problem with STP is that it is not persistent - in other words, if the satellite loses power the. STP gets reset.
