NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
What happened to my posting
I posted then edited the posting with a different title and it disappeared? https://community.netgear.com/t5/Orbi/Sat-WiFi-downloads-slow-to-kilobits-s-with-wired-backhaul/td-p/1789011 I spent a lo...
HTBruceM wrote:.......
I REALLY need some stability in the network because I'm planning to drop my Dish Network and switch to YouTube TV streaming service in the next month, so even TV viewing will then be dependent on internet access. Technically I don't even really need a mesh system because I've got the CAT6 wiring I need to just use APs. Whatever; this is where I am right now.
I have a very stable and robust wifi network currently with 2.3.5.30. All I needed to do related to wired backhaul is mentioned in this post: https://community.netgear.com/t5/Orbi/Wired-Backhaul-in-recent-firmware-releases/m-p/1783871#M67538
This should not e difficult to do to fix your issues and improve your system.
What is the Mfr and model# of the ethernet switch if one is in the configuration when your trying ethernet backhaul?
Diasy Chain needs to be disabled when the RBS is connected via LAN to the RBR.
What is the size of your home? Sq Ft?
What is the distance between the router and satellite(s)? 30 feet is recommended in between them to begin with depending upon building materials when wirelessly or wire connected.
When you getting broadcast storms on the system when wire connected with the RBS, usually means the RBS is in IP address conflict with a different devices IP address. I saw this a couple of times when I first got my Orbi. I managed to keep this at bay with by first connecting the RBS via wireless then wired and then setting a IP address reservation on the RBR before connecting all other LAN devices to the system. I haven't seen this issue since.
HTBruceM
Mfr/Model: No switch exists between the RBR50 and RBS50s. All wired devices connect to a TP-Link 24p unmanaged switch, and the switch is connected directly to a LAN port of the RBR50. Both RBS50s were connected directly to RBR50 LAN ports.
Daisychain: Yes I had it enabled (checkbox ticked).
Size of home: 2250. RBS50-1 and RBS50-2 are both about 35ft with intervening walls. CAT6 path is obviously longer.
Storms: I have IP reservations for the RBS50, set to .2 and .3. I don't believe there are any IP conflicts; everything is DHCP; and I have about 6 total reservations defined.
Bear in mind, this system was working fine for many days (maybe 1 weeks?) after the FW upgrade. But at some point, downstream bandwidth dropped dramatically (upload speeds not affected), and ONLY on devices connected via WiFi to either RBS. The condition remained this way constantly. When I forced a WiFi connection to the RBR, it's bandwidth was NOT affected, nor were any of my wired devices, in either upstream or downstream.
BTW I did the FW upgrade while in the wired backhaul configuration, and did not do any special manual power cycling/resetting. I understand that you advocate the brute force wipe everything clean method but I did not do that.
At the moment I've got the wired backhaul disconnected and I've rebooted a couple times. Switched off daisychain also. Apparently I don't need it, since my backhaul status still shows "GOOD" on WiFi. No issues seen at this point with WiFi backhaul.
I REALLY need some stability in the network because I'm planning to drop my Dish Network and switch to YouTube TV streaming service in the next month, so even TV viewing will then be dependent on internet access. Technically I don't even really need a mesh system because I've got the CAT6 wiring I need to just use APs. Whatever; this is where I am right now.
HTBruceM wrote:.......
I REALLY need some stability in the network because I'm planning to drop my Dish Network and switch to YouTube TV streaming service in the next month, so even TV viewing will then be dependent on internet access. Technically I don't even really need a mesh system because I've got the CAT6 wiring I need to just use APs. Whatever; this is where I am right now.
I have a very stable and robust wifi network currently with 2.3.5.30. All I needed to do related to wired backhaul is mentioned in this post: https://community.netgear.com/t5/Orbi/Wired-Backhaul-in-recent-firmware-releases/m-p/1783871#M67538
This should not e difficult to do to fix your issues and improve your system.
Ekhalil & FURRYe38 - I may give those steps for wired backhaul a try when time permits. But it's doubtful I'll be able to try without the TP-Link switch since so much of my network depends on it. Plus I have no idea how long it takes for the degradation to occur and cannot live without full network until that time.
Honestly I think this router just knows how to get under my skin, and I don't want to turn this into a career. I'm retired from the tech industry and not really excited about beta testing :smileyhappy:
If you have not factory reset and setup from scratch, this would be the next step. If you have tried everything else.
I would also set a smaller default router DHCP IP address pool, try using 192.168.1.100 to .200. This what I use.
I have this DISH Hopper system with Joeys and it's all connected to the router thru switches. RBS is actually behind 4 switches. Don't ask, lol. Daisy chain is disabled here.
Can you test the system with out the TP-Link switch being online to see if anything changes?
I had a window of time this morning in which I could take down the network. I performed the RBS50 factory reset/<remove from devices>/sync procedure while the wired backhaul is connected. Daisychain was UNCHECKED (disabed) during this process and remains so. It came up as expected and appears to be running normally. No changes to IP ranges though.
Fingers crossed.
I'll repost back here if it goes south, and I'll try to remember to also checkin here if things remain stable.