HELLO GOOGLE -- ARE YOU THERE?!?!?! - Major Nest Wifi Issues

[ShellDude]

As of the latest firmware update (14150.882.9) I can no longer power cycle my Nest Wifi Router reliably via managed power switch.

As best as I can tell the Nest Router is failing to negotiate a DHCP address through my ONT to my ISP (Verizon FIOS).

It takes multiple reboots to resolve when it falls into this state.   Rebooting the ONT typically does not help either.  I've used the "Verizon FIOS Troubleshooter" a couple times to get it to trigger the DHCP refresh but it too is unreliable.

And of course, I have to reboot my router daily because if I don't bandwidth on my LAN degrades to the point of it being unusable over time.

And to add insult to injury, since Google has failed to give us a reboot schedule option (like every other router on the planet has these days) I've had to resort to using a managed power outlet to perform the reboot.

I am so sick and tired of this train wreck.  I have had nothing but problems since I moved to Nest mesh last year.  

[PatrickP_Viking]

Hey @ShellDude .

Can you advise what your network looks like (i.e connections from Fios entering the home to the Nest Wifi)? This issue is indicative of Double NAT.

[ShellDude · Accepted solution]

No Patrick, I don't have double nat as the nest router is the only router on my network and is plugged directly into my ONT.

Google nerfed their oobe logic and sequencing for making the public interface routable in this latest firmware.

It now must be able to resolve an external DNS server BEFORE it will make the public interface available.

The other issues reported remain and now I'm forced to allow the router to talk to an external DNS server.