NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Mooose
Jan 30, 2019Luminary
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...
- Feb 06, 2019
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.
ekhalil
Jan 30, 2019Master
I have wired backhaul so I thought to try to simulate your case, so I connected my laptop with a LAN cable to the router, disconnected the wifi network (did not disable wifi) in the laptop, started command prompt and typed the ping message, and guess what, I got packet loss exactly as you did, BUT.....
While trying to collect some date from Orbi I noticed that my speakers (usually connected to the satellite) started to blink indicating no network then I saw they got attached to the router, waited few minutes, I saw that my router rebooted, so I disconnected the laptop.
When I looked in the laptop IP configuration I noticed that I had it set up for a static IP address (192.168.10.101) outside the Orbi subnet and remembered that I did this setting last time when I was configuring a VoIP router for a friend. I really don't know how I managed to get LAN connectivity with this settings but it seems that somehow the wifi was sending the packets not the LAN port.
Of course the family at this point started to complain about loss of internet and I did not want to try again.
What I concluded from this short test -together with my previous experience with Orbi- is the following:
- Orbi LAN ports are very sensitive to the wired devices connected to it
- This "sensitivity" is more evident when you have wired backhaul
- I should be cautious with devices that have wireless capability when using them as wired devices in Orbi, they can cause loops and system instability.
At this point I'm not sure what made my Orbi unstable when I connected my laptop, is it the bad LAN port configuration, or the loops caused by combination of wired and wireless connections in the same device.
I will try again later and see if I can simulate this case again. Meanwhile I have the following questions:
- Do you have any static IP settings in your wired computers?
- Are you sure that wireless is completely disabled in those computers
- Does the same issue happen if you disconnect one of the computers (one at a time) and ping from the other computer to any other device (wired or wireless), repeat the the same with the other computer? It can be only one of the computers is causing this issue.
- Is Daisy Chain Disabled? you mentioned that but please make sure it's unticked.
Another test that I would like to do, at later stage, to avoid loops in backhaul, is to disable the wireless backhaul (with telnet commands) and see if this will do any improvement.
- MoooseJan 30, 2019Luminary
Thanks for looking into this!
I believe I have never set any static IP addresses, and I am sure the two laptops used for the test received theirs through DHCP.
I am certain macOS and Windows 10 on the two computers involved think wifi is disabled. I have also verified that they do not show up as wireless connected devices in the Orbi web interface.
I have done similar tests with these two particular devices turned off, it was packet loss from the Drobo to the Apple TV that originally alerted me that something was wrong.
I will try turning them off one at a time tomorrow and ping from the wifi laptop.
Daisy Chain is disabled. (Or, unticked, at least.)
I am surprised wireless backhaul cannot be easily disabled from the web interface.