NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Ethernet Backhaul
I originally set up the system with wireless backhaul. Just now reconfigured as wired. Router status still shows satellites connected as 5G. Do I need to reset the satellites or perform some other...
So I got the new cable and everything is installed. But for some reason, every time I plug the cable in, it generates a huge packet storm over the network and everything disconnects or gets very unstable. I have tried a few times already and recently just restarted both router and satellite and trying out again.
It's just giving me no confidence as it goes down any time it likes. I have the router setup as a router, not as an AP too.
I really hope they update the firmware to make it more stable. It's really bad right now.
EDIT: While I was typing this out, the whole network went down again. I had to unplug the cable and leave it unplugged to make it work again and post this reply.
Hi,
if you get the chance to login into your router via telnet, you could check the STP parameters of your network, because STP should prevent such events… Also, do you happen to have anothet router in your system?
Hi,
Just a regular telnet session to my router's IP doesn't work. Is there anything special I need to do to telnet into it? Also, how do I check the STP?
I have another router on my network but its DHCP server as well as Wifi is disabled and it is being used as an access point, to connect one room with multiple devices (via its gigabit ports).
I can try taking this off the network but it's not a solution for me, as I need this device for my file server etc to talk to the rest of the network.
You will have to enable telnet for your Orbi on the debug page: http://<your orbi>/debug.htm
If you really do have another router on your network, or a switch for that matter that does support Spanning Tree (STP), then you should make sure, that the "central" one, has the STP bridge with the lowest number/ID, which will make it the root bridge of you rentire network.
However, it might be easier to disconnect the other router for testing. Just for the sake of completeness, this is what my router (in AP mode) tells me about its STP config:
root@RBR40:/# brctl showstp br0 br0 bridge id 8000.b0395675b7e5 designated root 8000.b0395675b7e5 root port 0 path cost 0 max age 20.00 bridge max age 20.00 hello time 2.00 bridge hello time 2.00 forward delay 2.00 bridge forward delay 2.00 ageing time 30.00 hello timer 0.16 tcn timer 0.00 topology change timer 0.00 gc timer 0.16 flags ath0 (3) port id 8003 state forwarding designated root 8000.b0395675b7e5 path cost 100 designated bridge 8000.b0395675b7e5 message age timer 0.00 designated port 8003 forward delay timer 0.00 designated cost 0 hold timer 0.00 flags hairpin mode 1 ath01 (4) port id 8004 state forwarding designated root 8000.b0395675b7e5 path cost 100 designated bridge 8000.b0395675b7e5 message age timer 0.00 designated port 8004 forward delay timer 0.00 designated cost 0 hold timer 0.00 flags hairpin mode 1 ath1 (5) port id 8005 state forwarding designated root 8000.b0395675b7e5 path cost 100 designated bridge 8000.b0395675b7e5 message age timer 0.00 designated port 8005 forward delay timer 0.00 designated cost 0 hold timer 0.00 flags hairpin mode 1 ath2 (6) port id 8006 state forwarding designated root 8000.b0395675b7e5 path cost 100 designated bridge 8000.b0395675b7e5 message age timer 0.00 designated port 8006 forward delay timer 0.00 designated cost 0 hold timer 0.00 flags hairpin mode 1 eth0 (2) port id 8002 state disabled designated root 8000.b0395675b7e5 path cost 100 designated bridge 8000.b0395675b7e5 message age timer 0.00 designated port 8002 forward delay timer 0.00 designated cost 0 hold timer 0.00 flags eth1 (1) port id 8001 state forwarding designated root 8000.b0395675b7e5 path cost 4 designated bridge 8000.b0395675b7e5 message age timer 0.00 designated port 8001 forward delay timer 0.00 designated cost 0 hold timer 0.00 flags
You can see, that each wireless interface has a path cost of 100 assigned to its designated root bridge, which happens to be the one br0. There musn't be any other bridge designated to these interfaces, that would indicate that there's another root bridge on your network somewhere, which would at least be an performance issue, since all traffc would be routed via that remote bridge.
Also note, that eth1, which is my ethernet backhaul only has a path cost of 4 assigned to it, make it the way of choise for all MACs that are "seen" on that interface.