I've seen a couple posts with no resolution on this. I have a feeling it's a feature that's broken on Nest WiFi that worked with Google WiFi.
I "upgraded" by getting a new Nest WiFi system. I reset my existing Google WiFi devices and started from scratch. The Nest WiFi router is connected directly to my fiber modem. I have 2 Google WiFi devices configured and when using WiFi they work great.
The problem is the LAN ethernet ports on the Google WiFi devices. After hours spent troubleshooting, fiddling with DNS settings, etc I found the behavior. I can connect a PC or other device to the LAN port and access internal network devices, like my NAS box. But if I try to connect to any external site it fails. I even tried accessing Google.com via IP address, but that also fails. About the only thing I can do to access the outside world is to ping 8.8.8.8 That works, indicating that there is a network connection. I didn't find anything that responded to a ping besides the DNS.
It's very frustrating. The Google Home app shows the devices connected. The app doesn't show "wired", but it just doesn't say "great connection" for wired devices. I can see upload and download speeds when accessing my NAS box. But I cannot make any connection outside the house when connected via ethernet. The same device connecting via WiFi works great.
Is this a feature that was removed from Nest WiFi? It feels like it since I was surprised to find the Nest Point has no ethernet.
If this is how it's supposed to work, then I'll just remove the Nest WiFi from my system, return it, and go back to just the Google WiFi. The only "solution" I found was someone suggesting using a WiFi repeater as a WiFi-to-Ethernet device. For me, that's a lame fix versus just going back to Google WiFi that worked for years.
