To be clear: My Orbi mesh is working as normal now. I have reconnected everything except the ethernet. I will test later by reconnecting the ethernet switch and see if its a direct failure or something less logical.
As for other points:
- I've learned lots of people - particularly Comcast technicians -- believe evil of Sonos. I'll never claim to be a sonos expert, but I've got a Bridge wired to Orbi Router, an old Connect hanging off the far end of the network, and 5 speakers. I've rarely had issues and the only significant one was resolved with a firmware upgrade. So, make of that what you will. Personally, I'd have 20 Sonos hanging off my network if they weren't so darn expensive.
- The switch is PPC Evo9-1-U/U -- its a powered coaxial non-managed switch. Never had any issues and the PoE adapter appears to be working properly. But I cracked it yesterday (doing other maintenance) and now the wiring seems to be the problem, so I'm blaming the PoE/Switch until I can isolate something else.
- I had IPv6 off until recently. Don't think that's the issue, but I'll toggle it when testing. Currently its active.
- I do have Daisy Chain active because I have a rather large distance to cover and a couple stone walls to cross to get there. As with IPv6, its been operating that way for awhile with no issues and is active as we speak.
- I do not have, never have had, Mimo or Fast Roaming.
- I was not aware of the 20/40mhz flag but intend to play with it. I noticed during this testing that when I force RBR50 to open channels (2.4ghz is on 1 at the moment), it makes a new complaint (part of firmware 210?): 'If there is a conflict, you will be defaulted to 20mhz and it will reduce throughput'. Definitely don't want that, so interested in any wisdom you guys have on configuring that aspect.
- Finally, I keep forcing 5ghz to 36 and it keeps moving itself back to 48 -- what's up with that? 36 is almost wide open while 48 has a bunch of squatters.
