The topology is simple and conventional. No unusual port settings, DHCP settings, or anything "advanced" like that.
Further details:
I have AT&T Fiber service, which uses an Arris BGW210-700 Fiber Modem / Router.
The only device connected to the Arris BGB210 is the first Google Nest Wifi Pro 6e which acts as the router for the rest of the devices on my network.
That first Nest WiFi Pro 6e, and the remaining 5 other WiFi Pro 6Es are then connected to a conventional unmanaged Ethernet switch for backhaul purposes. This Ethernet switch is a 24 port Ethernet switch, where 6 ports are occupied via the WiFi Pro 6e backhaul ethernet connections. The remaining ports are used by other ethernet devices which allows them to communicate with the "router" WiFi Pro 6e node for address assignment and routing as would be expected.
It all seems to work perfectly well with cloud services on. The only issue is the reporting of "wireless" backhaul when the cloud services are off. I'm not even sure if it really is doing a "wireless" backhaul. The reason I say that I am unsure if it really is a wireless backhaul is that, if I disconnect Ethernet and do a mesh test, the test reports different strength interconnections (as would be expected, given different distances, etc.). But if I leave the Ethernet connected, and turn off cloud services, even though it says wireless interconnection is being used between the nodes, the mesh test still shows each node as having a "green" (excellent) interconnection.
So, a first suspicion is that maybe the Google Home App on iOS reports a "wireless" interconnection is in use whenever cloud services is off even if "ethernet" is still connected and used.
This seems like something that would be pretty easy for Google to verify with a few of these access points and a basic ethernet switch.
Thanks!
