NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Massive packet loss over Ethernet backhaul
I believe I have read all the threads on this topic and tried the suggested solutions that are relevant to my particular network. My apologies if I have missed something!
My Orbi RBK50 (one rou...
Mooose Good troubleshooting and interesting observations. It's clear that the packet loss is directly related to the wired backhaul.
I'm now running the ongoing beta software (2.3.0.23) and I can see that NG has done quite good improvements on wired device handling. Would you want to test this SW and see if you will see improvements? If yes, please PM to ChristineT and ask to get the SW download links.
Great troubleshooting and narrowing it down. I was hoping one of your devices would reveal something.
Is the ATV up to date?
Keep us posted.
Feels like I'm back to square one. Had no packet loss all night. Reconnected Ethernet backhaul this morning, and ran 200000 pings from a device at each end of the backhaul to five or six other devices on the network. It was fine until this afternoon, when the second test showed 8%.
I disconnected the Apple TV and connected the Drobo (attached to the router instead of the satellite) and ran a new test. The result was pretty much the same.
In both cases the pinging laptop at the same end (i.e. *.35 for the Drobo and *28 for the Apple TV) showed zero loss to the respective device, but the one at the other end of the backhaul did show loss in both cases.
I feel the only thing I have accomplished is proving that the packet loss is somewhat intermittent even though it is fairly consistent, which means that practically all my testing where the result was no packet loss is useless.
The only thing I know for sure is that I have only been able to measure packet loss exceeding 0.3% when the Ethernet backhaul is connected, and when there is packet loss I only see it between devices at opposite ends of the backhaul.
There are simply too many variables and testing is too time-consuming, so my only hope now is that a new firmware will resolve this.
Can you reboot the router and satellite while wire connected and leave OFF the ATV and Drobo devices for the weekend and test the system here and there over the the weekend. It's possible that once the system gets in a bad state due to something on the network, it can't get back to a good state and needs a reboot. Seen this before with mine,especailly if the loop happens. Just curious if a longer duration with out those two devices being online if system will maintain or have the problem appear again.
Hope you can get ahold of the beta FW as well and test that out.
Mooose wrote:
Feels like I'm back to square one. Had no packet loss all night. Reconnected Ethernet backhaul this morning, and ran 200000 pings from a device at each end of the backhaul to five or six other devices on the network. It was fine until this afternoon, when the second test showed 8%.
I disconnected the Apple TV and connected the Drobo (attached to the router instead of the satellite) and ran a new test. The result was pretty much the same.
In both cases the pinging laptop at the same end (i.e. *.35 for the Drobo and *28 for the Apple TV) showed zero loss to the respective device, but the one at the other end of the backhaul did show loss in both cases.
I feel the only thing I have accomplished is proving that the packet loss is somewhat intermittent even though it is fairly consistent, which means that practically all my testing where the result was no packet loss is useless.
The only thing I know for sure is that I have only been able to measure packet loss exceeding 0.3% when the Ethernet backhaul is connected, and when there is packet loss I only see it between devices at opposite ends of the backhaul.
There are simply too many variables and testing is too time-consuming, so my only hope now is that a new firmware will resolve this.
FURRYe38 wrote:
Can you reboot the router and satellite while wire connected and leave OFF the ATV and Drobo devices for the weekend and test the system here and there over the the weekend. It's possible that once the system gets in a bad state due to something on the network, it can't get back to a good state and needs a reboot. Seen this before with mine,especailly if the loop happens. Just curious if a longer duration with out those two devices being online if system will maintain or have the problem appear again.
I'd love to do more testing and actually figure out what is going on, but the family needs their stuff up and running again, as do I. I have also lost about two weeks of productivity, and more testing will without a doubt lead me down more rabbit holes.
If I am offered a beta firmware I will try that, but other than that I won't be doing any more testing.
Even if I managed to track down the cause it seems likely that the network would be so fragile, requiring connecting and restarting devices in a specific way, that it would still not be practically usable.
Everything is back on the network now, about 35 devices in total. I just finished a run of 200000 pings from two devices at opposite ends of the (wireless) backhaul to six different destinations each with a result of 0.0% packet loss. A few of them even managed every single ping, so obviously there is nothing wrong with any of my attached devices.
I also realized that I can hook the Nintendo Switch up to the backhaul Ethernet cable directly to the router and reduce its latency that way. It sucks that other devices will have to deal with unnecessary latency and wifi congestion, but it's still workable.
I really appreciate all the advice. Thanks, all!
Mooose wrote:........
If I am offered a beta firmware I will try that, but other than that I won't be doing any more testing.
........
Have you sent a PM to ChristineT regarding the beta participation?
ekhalil wrote:
Have you sent a PM to ChristineT regarding the beta participation?Yes, I have both posted in her thread on the subject and sent a PM.