I just upgraded from Google WiFi (Gen 1) and port forwarding isn't working consistently from within my network.
That maybe requires some explaining, to avoid misunderstandings:
Now it's completely normal for routers to work this way. Since the packet didn't arrive on the WAN interface, many routers won't apply the forwarding rules. But Google WiFi (Gen 1) was one of the good routers that forwarded no matter where you were coming from.
Why would I want that? So that I can use the same address regardless of what network I'm on. For example I could go to https://home.example.com or I could do ssh home.example.com from home or from anywhere and it works exactly the same.
So naturally my first suspicion was that Nest WiFi Pro doesn't support this, but it turns out it works sometimes!
Another bit of evidence that something is wrong: Chrome Connectivity Diagnostics claims it can't contact the the local network gateway (the main Nest WiFi Pro router) but it can contact the Internet just fine.
Anyone else seeing something similar? There's another thread about "Port forwarding crashing" and it does seem like that could be related, but that thread is locked, and claims it has an answer, and the resolution doesn't seem to be applicable.
I just setup my Nest Wifi Pro (3 units) - upgrading from the Nest Wifi - and I have the same problem, although my internal port forwarding doesn't work at all.
I remember the old Onhubs had this issue when they first came out but Google eventually fixed it with an update.
** Edit - I stand corrected -- the forwarding worked briefly (about 2 minutes) then stopped...
This seems to be resolved as of last night. Around 11pm EST all of my devices disconnected and reconnected. My ring bridge went offline, a few of my TIVO televisions powered on to report internet loss, and almost all of my Google hubs and smart speakers sync'd and/or emitted a reboot sound. It was quite startling for it to happen all at once, reminded me of Close Encounters. In any case, as of this morning the internal port forwarding no longer seems to be an issue. Coincidence with regards to what happened last night, I think not. If all it took was for Google to wake me up, I'm fine with that. I just hope that doesn't happen every time they fix something or they schedule taking EST people into consideration.
Thanks for posting what the resolution ended up being for you. Hopefully the others here see this and can see a similar situation play out. The restart was most likely the network installing an update that hadn't been applied yet, as it will automatically restart to complete that process. Let me know if you see any changes in your situation from here.
Exact same results. Anything I want to connect to internally using DDNS fails. I have to switch over to cellular in order for the links to work or I would have to create a separate set of links for all my servers for internal and external which would be a real pain. I hope this gets addressed and they add this functionality. Furthermore I can add this worked on Google WiFi as well as Nest Wifi, so this is a new bug / loss of ability just with the Pro.