09-03-2021 01:04 PM
Disclaimer: This thread was migrated from our previous version of the Google Nest Community. You can continue to receive updates on your thread issue here or simply ask, browse or more in the new Google Nest Community.
Original Poster:Bill Schiller
I am unable to complete a clone of a GitHub repository using an SSH git connection when my laptop is connected through a Google Nest Mesh Wifi network. The git clone command connects and reports that it has received ~10% of the objects and then stops updating progress. I have run Wireshark and I consistently see that the connection is established to the GitHub IP and is downloading data over the SSH connection until the git server stops responding. Wireshark reports that my laptop is retransmitting packets but there is no reply from the GitHub IP.
09-13-2021 12:05 AM
Also facing issue on GithUb push while on Nest wifi, are you able to perform github push?
09-17-2021 11:36 AM
Hi, Bill and sanketgaglani.
Sorry for the issues you're experiencing with GitHub and your WiFi setups. I imagine that's quite frustrating to deal with. Let's see if we can figure out what's going on here.
Before diving too deep, I do have a quick question. Have you tried using HTTPS instead of SSH for running through this? It's interesting that it works over Ethernet but not through WiFi and sort of complicates a possible answer here. If you could try running it over HTTPS rather than SSH, let's see if we get any different results.
I look forward to hearing back from you. Thanks.
09-19-2021 09:30 PM
HI Jeff, For the work purpose I have to run over SSH only and it shouldn't really matter to Modem as we don't do any firewalling. Would you please run this in your lab environment? and confirm.
09-22-2021 12:57 PM
Hi, sanketgaglani.
Thanks for the clarification on your situation there. I'll send this through to an internal team and we'll check to see if there are any identifiable issues. I'll reach back out as soon as I know more.
Thanks.
10-01-2021 10:49 AM
Hello, sanketgaglani.
This is being looked at internally, but I wanted to see if anything has changed on your end. If so, just let me know.
Thanks.
11-19-2021 01:39 PM
Hey, all.
It's been quite a while since we've touched on this. Has anybody here seen any improvement in their situations, or are the same issues still persistent? I know some of you were in touch with internal support teams, so hopefully that helped. If you're still needing help, let me know and we can pick back up on this.
Thanks.
11-23-2021 03:57 PM
Hi, everyone.
As we haven't had any activity here recently I'm going to go ahead and close the thread. If you have more to add, feel free to start a new discussion.
Thanks