As many in this forum, the issues I've been having are:
Google support points the finger to "double NAT" (my ISP router sits in front of the Google Wifi network) and the suggested "fix" is to put the ISP router in bridge mode. Called my ISP (AT&T) and initially they said this wasn't possible on my Pace 5268AC.
However, a few minutes later, one of their technical engineers called me back and suggested it would be possible using what they call DMZ+ mode: essentially you put the pod that is acting as the gateway into the DMZ where it grabs the WAN IP address of the ISP router and the ISP router forwards all inbound traffic from the Internet to it. This is enabled in my case in the Settings / LAN / LAN IP Address Allocation tab:
So, now going to see if this fixes the slowdowns & disconnects. I have my doubts, since even Google's documentation (https://support.google.com/googlenest/answer/6277579?hl=en) admits that in most cases "double NAT isn't a problem" (can be an issue ins some cases with games & uPnP--neither of which apply to my situation).
I'm willing to bet $ that this is ultimately due to memory leaks in the Google firmware--hence why the systems work initially but then fail a few days in. Anybody at Google/Nest willing to take my bet?
Ok. So this evening I had my two (bridge-mode) pods start blinking yellow.
The Google Home app showed that both went “out of range” (ridiculous of course, since their backhaul is via ethernet). In the other part of the app, both are showing as “great connection”
However, both pods had blinking yellow lights and my home devices were not connecting to them (they switched to the pod (called Garage WiFi).
This is while my home network no longer has a “double NAT”, proving my point that despite what the forum facilitators keep suggesting—this issue is not caused by NAT. Besides, why would it? NAT is just inefficient: the routers replace the IP address in the packet headers so that they can make their way from and to their destination but shouldn’t cause the pods to go offline. They just have to talk to the router, which applies the network policies (whether to allow packets to go through, etc.).
I’ve now done two things:
So far, it seems like in my case, that the pods start to act up after about 48 hours. So I’m going to see if a nightly power cycle (of at least 1 pod) is going to allow that pod to function reliably. I can also compare that to the other one that is in bridge mode.
Thanks for posting. Our apologies for the late reply.
We appreciate you providing all the details regarding troubleshooting you've done so far. I'd like to check in and see if you're still experiencing dropping issues with your Nest Wifi Pro points. Feel free to reply to this thread and we'll be happy to help out.
Well, since you and the support team have done zip all, I’d say that the issue is still there. The product is defective and per terms of your warranty: “Google warrants that a new Google Product (including any ancillary parts that may be packaged with it) will be free from defects in materials and workmanship under normal use in accordance with Google’s published user documentation for one year from the date of original retail purchase in its original packaging by you” it is not “free from defects”. I therefore opened a case a week ago to get a refund. Despite my daily inquiries to proceed—no response from anyone at Google/Nest.