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.
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
Ah... that was for auto update... sorry, didn't get that :-). Didn't read the full thread. Thanks for the suggestions, that feels too hacky for me, but I can see how that might help. This is more a "hey Netgear... please improve the user experience!" :-).
Is a suggestion only.
Good luck.
sventhegrinch wrote:
Ah... that was for auto update... sorry, didn't get that :-). Didn't read the full thread. Thanks for the suggestions, that feels too hacky for me, but I can see how that might help. This is more a "hey Netgear... please improve the user experience!" :-).