Hi All,
I will throw in my two-penneth as I think there is a danger of over complicating what may be the issue that Sitara is experiencing.
1. Although the B2 will only connect to a SSID broadcast on the 2.4Ghz frequency band it is irrelevant that other devices are connected at 5Ghz on the same network subnet(IP address range). The router knows about both frequency bands so can happily route the traffic unless the router has software bug (as some British Telecom routers did)
2. For the B2 to unwittingly connect to another unsecured network it would mean that the Brennan software would have to explicitly allow such a connection without any confirmatory dialogue and that is such a security chasm that it cannot be the case.
3. Most routers will automatically pick a frequency band channel that is least utilized unless explicitly set manually so I'm dubious about interference from nearby routers. Symptoms are more likely to be performance because of network retries.
3. If the B2 is picking up an IP address the simplest way to check whether it is in the same subnet as your other devices is to visually compare them and you can also ping or traceroute from one device to another.
4. If the COX equipment is a router and not just a cable modem then if the primary Google mesh router has simply been plugged into the COX and the COX is still acting as a router itself ,rather than be placed in bridge (modem only) mode, then there will be two DHCP servers active and its possible that some devices will get their IP addresses from one and some from another.
Given that the COX and the Google Mesh are likely to be offering two different DHCP IP ranges and thus two different subnets then devices will not be able to see each other.
e. g. COX range 192.168.0.10 to 192.168.0.255, Google Mesh range 192.168. 86.20 to 192.168.86.250
Fred's suggestion of a wired connection will hopefully solve the problem for the B2 but any other shared network resource that gets its IP address via DHCP over Wi-Fi could have the same issues
John