NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Firmware Version 1.10.1.2
Does anybody know what they fixed? All it has in the release notes is "fixed some bugs" That is not a release note. That is a joke.
Hello Everyone
We have release firmware version 1.12.0.18 this firmware has fixes for disconnects and many more I posted the release notes below.
https://kb.netgear.com/000044171/RBR50-Firmware-Version-1-12-0-18
If you are still having issues after updating your Orbi unit you may want to factory reset the Orbi and test again. If you are still having disconnect issues or other issues with this firmware please create a new thread or contact our support team.
http://www.netgear.com/support/contact.aspx
Thanks
DarrenM
Timch, would you mind checking the backhaul on your system using whatever method you prefer?
Then to see if the drops make a difference, make a Wi-Fi call while connected to the satellite. You can watch your call drop. I think it would be great to have a scientist look into this. The more eyes the better because the graphs are definitely not lying.
Then to see if the drops make a difference, make a Wi-Fi call while connected to the satellite. You can watch your call drop. I think it would be great to have a scientist look into this. The more eyes the better because the graphs are definitely not lying.
@BobertSaget wrote:
Timch, would you mind checking the backhaul on your system using whatever method you prefer?
Then to see if the drops make a difference, make a Wi-Fi call while connected to the satellite. You can watch your call drop. I think it would be great to have a scientist look into this. The more eyes the better because the graphs are definitely not lying.Well, I'm not a scientist, but I have a master's degree in computer engineering and 28 years of experience developing (and debugging) computer products.
Like Timch, it's not clear to me that the backhaul disappearing from a WiFi scanning app means there's a problem. The data I've collected doesn't support that hypothesis. My Orbis is stable and I don't have a consistent backhaul in WiFI scanning apps.
I've tried at least four WiFi scanning apps on my MacBookPro. The backhaul very rarely shows up on any of them during normal operation. This would indicate that whatever protocol Netgear is using for the backhaul is not standard WiFi and does not reliably appear on WiFi scanners. There are other devices that use WiFi channels to communicate and don't appear on scanners. Sonos is one example.
We don't know how Netgear is using the backhaul channels, so it's a major (and possibly invalid) assumption to conclude that the backhaul must continuously appear in a WiFi scanner for proper operation of Orbi.
I downloaded WiFi Explorer yesterday and it will sometimes show the backhaul. I have a screenshot where you can see the backhaul on channel 157 and it disappears from the graph. However, immediately after the backhaul disappears I was still able to transfer data at 90 Mbps to a Raspberry Pi that's hardwired to the satellite. So, definitely the backhaul was still working even though it wasn't showing in WiFi Explorer.
If somone could collect data that directly correlates the timing of the backhaul signal changes with network outages and returns to service, then that would be more meaningful.
Also Computer Engineer with 17 years in the field.. I tried there beta firmware and again discconecting all of my devices.. I wish they would post something fast not a good look for future sales.. if it wasnt for the range i would just keep my FIOS Gateway
1) The backhaul drops, by definition, are a problem. It is literally the equivalent of unplugging and replugging an Ethernet cable every few seconds. You may not notice on TCP, due to liberal socket timeouts, but with fire-and-forget UDP (nee streaming and VoIP), you will absolutely see disruption.
2) I can't say a thing about your scanning apps, but yes, the backhaul is standard wifi with no SSID broadcast. With a master's in computer engineering, I'll take it as read you know how to telnet:
root@RBR50:/# iwconfig ath2 ath2 IEEE 802.11ac ESSID:"NETGEAR_ORBI_hidden85" Mode:Master Frequency:5.785 GHz Access Point: [redacted] Bit Rate:1.7333 Gb/s Tx-Power:30 dBm RTS thr=64 B Fragment thr:off Encryption key:[redacted] [2] Security mode:open Power Management:off Link Quality=0/94 Signal level=-95 dBm Noise level=-95 dBm Rx invalid nwid:9172 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0It is not the same situation as Sonos, whose non-802.11 interference with 5GHz channel overlap is well-documented.
3) We actually know precisely how Netgear uses backhaul - I documented it extensively shortly after the product's release on this very forum. We also later determined and documented how 2.4GHz backhaul fallback functions.
You may want to do a bit of academic research on how wireless communications function before coming to erroneous conclusions that total signal loss doesn't cause a problem. I suggest you start with a more meaningful test that uses UDP or custom packet framing, as TCP by design will not show loss in very short bursts.
Rodney
Orbi uses the one of the 5.0 Ghz channels as the backhaul.
It’s also not a true mesh system like a Ruckus but we are hopeful they will fix this.
It works more as a point to node system. So if you have more then one satellite to want the base in the center of them.
A true mesh system it would not make any difference where the base is.