So, I've had this mesh network for a couple yrs and up until 6 months ago it seemed to be running as designed. I repeatedly get the notice within the Google Home app that there's "another DHCP server detected", but have ignored it since the system seemed to be ok. 6 months ago, or so, all (3 at the time, now 2) of the wifi points lights were pulsing orange. As suggested at the time by someone in this forum, I physically connected each wifi point to the primary Google unit until the light went solid white, then returned them to their original locations. All fine until a week ago when the wifi points started pulsing orange again.
All units are NLS-1304-25, running sw ver 14150.43.81
Primary unit: LAN & WAN IP add, since it's conn'd via ethernet to my VPN router (behind the ISP's modem)//Home app says it's connected to 2 wifi points.
Wifi units: No LAN IP//Mesh connection
Speed test: BLAZING
Mesh test: 1 or more units are offline (both indicate offline after mesh test) "Fix it" tells me to go into settings of each wifi point and make changes...can't do that unless it's actually offline.
When initially opening Home app>wifi: app says all units are ok.
I've reset power multiple times, but can't get the steady white indication anymore.
It's NOT effective to have to re-accomplish the physical cable connection every month or whatever, I might as well just remove the "mesh" and hope for the best.
Hopefully this is enough info for someone to point me to a solid and "permanent" fix.
Could you tell us more about your setup? Why do you have a VPN router between the ISP equipment and Nest Wifi, and how is it set up? Tunnel all vs. split tunneling, DHCP, NAT, firewall. Does not sound like a topology that Nest Wifi were designed for, which might cause strange behavior.
I have the VPN router for very obvious reasons...protection.
ISP fiber modem > VPN router > Google base unit. (ISP modem is not broadcasting wifi/VPN router broadcasting a separate distinct wifi SSID/Google system broadcasts wifi for all IoT devices to connect to.)
The VPN router has user-configured tuners to select which items connect to which VPN server, i.e., computers to one, cameras to another, streaming devices to yet another, etc. Within each tuner, devices can be selectively blocked from internet accessor passed-through bypassing the VPN.
As for "Does not sound like a topology that Nest Wifi were designed for, which might cause strange behavior.", why would it matter if there is a router between the Google system and ISP modem? The Google system has to get WAN access somewhere.
It matters because the "Google system" is a router, managed by Google hosted services.
Double NAT (assumption as your VPN router has Wi-Fi), double firewall, VPN with split tunneling (assuming based on your description about "tuners"). Begging for problems IMO. All management goes through Google hosted services, I'm just imagining that your setup might confuse the management plane, giving you strange behavior.
Nest Wifi is an AIO solution for the average, non-technical Joe, I think you'd be better of with a more advanced/ flexible Wi-Fi solution. Maybe Ubiquiti UniFi, TP-Link Omada or similar?
If you don't need the mesh functionality of Nest Wifi, just using them as access points, maybe bridging them would be better?
If you still want it to work as is, do you have local breakout for all Nest Wifi related traffic? Sure you are not blocking anything relevant?
My home network still indicates all devices (primary + 2 access points) are online and connected, yet still pulse orange (the 2 APs). Reading the support item you included, I checked via the Home app: "Device mode has been automatically set."
Primary is in NAT mode, the 2 APs are in bridge mode.
From the app:
To enable bridge mode (on the primary unit), there needs to be another router between the modem and the primary Google unit (there already is as prev noted). (It's not connected directly to the ISP modem.)
As for changing the wifi option as you suggested, I've already spent $200+ on the Google system, I'm not spending another $150+ on something entirely different (that may or may not fix the mesh problem I'm experiencing) and being left trying to recover some of the $ spent on the old Google system by trying to sell it for far less than I paid.