Firmware Version 1.10.1.2

---

@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.