Spent the past day and a half trying to figure this out and I'm pretty sure the only explanation is some sort of firewall or weird configuration setting in the Nest Wifi router itself.
I regularly use SSH tunnelling to connect to a remote hosts for storage and processing of data.
Since using setting up the Nest Wifi 90% of the SSH commands I enter through my terminal interface (macOS) don't actually run; this also applies to RSYNC and SCP commands.
Once in a while - sometimes if I've just restarted my terminal software or the computer - I'll get lucky and the SSH command will run successfully. But for the most part I hit enter and the command line just sits there blinking.
When I look at the verbose output of the SSH attempt, it will end at:
"Connecting to <hostname> port 22.
There is no "refused connection", "connection timed out" or any other error message.
I do not have this issue on other Wifi networks.
Please let me know if there is any way to fix this issue and make SSH commands work from my computer; otherwise I'll be returning the Google Nest Wifi device.
Thanks in advance!
Sorry for the late reply here and for the frustrating experience you've had. I did want to check to see if you kept your Nest WiFi device and were wanting to take another look at things. If there's anything I can do to help you out here, let me know.
No I didn't keep my Nest WiFi device because Google technical support did not reply to me for over a week with any help - my solution was to buy a cheaper product, from a competing brand, which worked.
For a company with nearly 140,000 employees working mostly from home over the past couple of years, I'm sure you understand why I could not continue to wait any longer for a solution that would allow me to return to work; I returned the Nest WiFi device several days ago.
I'd suggest that you folks need to do some digging into your security/firewall settings to figure out why SSH protocols can't be run regularly using your router.
Thanks for letting me know, Astroboy981.
I'm sorry we weren't able to get this resolved for you. I'll pass your comments along to our internal teams as well. I'll go ahead and close up this thread since we have our answer. If there's anything else you need, please feel free to open up a new thread.