NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
OrbiOS 2.4.1 - Total mess
2.4.1 is an unbelievably bad firmware upgrade!! The router restarts every 2-3 minutes (observed in http://orbilogin.com/RST_statistic.htm). All wireless devices disconnects after a few seconds (often...
I too have had issues with wired backhaul and the latest firmware. I found that no matter what I did, the satellite would eventually revert to wireless backhaul and connect via a very low signal back to the router. I think this was then causing network loops as my entire network would start having issues ( basically there are two routes to the satellite). I tried downgrading firmware manually on the satellite and that worked, but the next day the satellite had auto updated the firmware again (Netgear not allowing you to keep older fw that works while they push out new poorly tested fw is a joke). Anyway, I have now stabilized things based on info from another forum that I will not name.
Here is what I did:
1. Point your browser to the satellite that you want to use wired backhaul but change the url to .......debug.htm. Then enable telnet.
2. Using telnet, log into your satellite (same username and password as used on router)
3 Type the following:
brctl stp br0 1
this will turn on spann8ng tree protocol. Why it is off is anyone’s guess, but my understanding is it stops the crazy traffic loops. After doing this and waiting about 5 minutes, my satellite went to wired backhaul and so far has stayed there. And, no other network instabilities hav occurred
4. Go back to the debug page and disable telnet.
Note that this fix fix is not persistent, meaning that if you power off the satellite you have to repeat the steps above. If anyone knows how to save this as persistent, please speak up.
For your configuration, do you have any network switches in between the router and satellite? If so, whats the mfr and model# of the switch?
Zdman wrote:
I too have had issues with wired backhaul and the latest firmware. I found that no matter what I did, the satellite would eventually revert to wireless backhaul and connect via a very low signal back to the router. I think this was then causing network loops as my entire network would start having issues ( basically there are two routes to the satellite). I tried downgrading firmware manually on the satellite and that worked, but the next day the satellite had auto updated the firmware again (Netgear not allowing you to keep older fw that works while they push out new poorly tested fw is a joke). Anyway, I have now stabilized things based on info from another forum that I will not name.
Here is what I did:
1. Point your browser to the satellite that you want to use wired backhaul but change the url to .......debug.htm. Then enable telnet.
2. Using telnet, log into your satellite (same username and password as used on router)
3 Type the following:
brctl stp br0 1
this will turn on spann8ng tree protocol. Why it is off is anyone’s guess, but my understanding is it stops the crazy traffic loops. After doing this and waiting about 5 minutes, my satellite went to wired backhaul and so far has stayed there. And, no other network instabilities hav occurred
4. Go back to the debug page and disable telnet.
Note that this fix fix is not persistent, meaning that if you power off the satellite you have to repeat the steps above. If anyone knows how to save this as persistent, please speak up.
No I do not. However, my satellite is quite far from the router (450 feet) as it s in my guest house. So I use two Enstation 5 ac units as the wired bridge. When I started having issues I did wire directly with a cable at about 100 feet with the same results so I don’t think the enstation link was an issue. Also, this setup worked up until the last fw update. It would really be nice to have a setting on the satellite where we could force it to wired uplink -as I noted above, it seems odd that a satellite would prefer a very week wireless backhaul to a high quality wired one
Ok, just checking. Seen issues with managed switches vs non managed.
Seems that they probably have changed someting in the FW. :smileyfrustrated:
Zdman wrote:
No I do not. However, my satellite is quite far from the router (450 feet) as it s in my guest house. So I use two Enstation 5 ac units as the wired bridge. When I started having issues I did wire directly with a cable at about 100 feet with the same results so I don’t think the enstation link was an issue. Also, this setup worked up until the last fw update. It would really be nice to have a setting on the satellite where we could force it to wired uplink -as I noted above, it seems odd that a satellite would prefer a very week wireless backhaul to a high quality wired one
I would consider my enstation more like a managed switch I guess as it does have routing capabilities but I have most of that disabled. With turning STP on having resolve my issue (so far)I have a feeling that what is happening here is that the satellite is circling packets over wired and wireless and creating data loops that eventually will crash the network. However, I am not a network expert.
I should clarify that the two enstation units should appear to the network as a direct wired connection, or maybe a wired connection through an Ethernet switch. They basically take wired data, convert to wireless, beam to other end over a secure wireless link, then the other end converts it back to a wired connection again.