For the last few weeks or so I've had really poor reliability when it comes to making ssh connections (over wifi). For example I can run the following command three times, and the first two times it will work and the third time it will time out:
$ email@example.com -vvv OpenSSH_7.3p1, OpenSSL 1.0.2j 26 Sep 2016 debug1: Reading configuration data ~/.ssh/config debug1: ~/.ssh/config line 1: Applying options for * debug1: Reading configuration data /usr/local/etc/ssh/ssh_config debug2: resolving "github.com" port 22 debug2: ssh_connect_direct: needpriv 0 debug1: Connecting to github.com [22.214.171.124] port 22. debug1: connect to address 126.96.36.199 port 22: Operation timed out ssh: connect to host github.com port 22: Operation timed out
I've done the usual power cycling on both my laptop and the Superhub. Visiting github.com in the browser works absolutely fine every time. If I run a speed test I get:
Thank you for opting to report this to our Forum, welcome on board
Interestingly I dealt with another report of this issue earlier today. Please read the customer's post and my reply here.
The fault ticket I've raised, ref: F004864037, is specific to that customer and this would now appear to be a more widespread issue as you are connected to a different CMTS. If you don't mind I'd like to see how the afore-mentioned fault pans out as I suspect it will also impact you. If at any point I feel the need to raise an individual ticket against your connection then I shall do so.
I'll keep an eye on this to see what happens and shall update you accordingly.
gets through perhaps half a dozen of them. Then the ssh connection starts timing out, and it's impossible to establish a new ssh connection to that host. There's no error, there's simply no response:
$ ssh -v bamboo.dreamhost.com
OpenSSH_7.4p1, LibreSSL 2.5.0
debug1: Reading configuration data /Users/ronen/.ssh/config
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Connecting to bamboo.dreamhost.com [188.8.131.52] port 22.
ssh: connect to host bamboo.dreamhost.com port 22: Operation timed out
If I stop trying to connect then wait a few minutes, ssh connections can be established again.
Here's a traceroute when ssh was jammed (though it doesn't seem to be different when ssh is jammed) or isn't:
$ traceroute bamboo.dreamhost.com traceroute to bamboo.dreamhost.com (184.108.40.206), 64 hops max, 52 byte packets 1 routerlogin.net (192.168.0.1) 5.631 ms 2.682 ms 2.578 ms 2 10.234.172.1 (10.234.172.1) 19.964 ms 13.102 ms 8.698 ms 3 sgyl-core-2b-xe-210-0.network.virginmedia.net (220.127.116.11) 11.849 ms 17.479 ms 9.924 ms 4 * * * 5 * * * 6 nrth-ic-1-ae1-0.network.virginmedia.net (18.104.22.168) 20.485 ms 24.708 ms 18.736 ms 7 m674-mp2.cvx1-b.lis.dial.ntli.net (22.214.171.124) 27.431 ms 19.596 ms 19.467 ms 8 ae-11.r24.londen12.uk.bb.gin.ntt.net (126.96.36.199) 18.376 ms 19.276 ms 20.610 ms 9 ae-5.r24.nycmny01.us.bb.gin.ntt.net (188.8.131.52) 119.741 ms 112.178 ms 113.724 ms 10 ae-1.r25.nycmny01.us.bb.gin.ntt.net (184.108.40.206) 118.054 ms 111.784 ms 113.316 ms 11 ae-9.r22.asbnva02.us.bb.gin.ntt.net (220.127.116.11) 117.103 ms 117.436 ms 112.714 ms 12 ae-7.r06.asbnva02.us.bb.gin.ntt.net (18.104.22.168) 117.790 ms 115.733 ms 119.127 ms 13 ae-1.a03.asbnva02.us.bb.gin.ntt.net (22.214.171.124) 112.492 ms 112.092 ms 111.574 ms 14 ae-0.dreamhost.asbnva02.us.bb.gin.ntt.net (126.96.36.199) 116.711 ms 112.044 ms 112.752 ms 15 ip-208-113-156-8.dreamhost.com (188.8.131.52) 120.419 ms 114.814 ms 114.527 ms 16 ip-208-113-156-14.dreamhost.com (184.108.40.206) 118.998 ms 120.808 ms 113.409 ms 17 * * * 18 * * * 19 * * * 20 * * * 21 * * * 22 * * * 23 * * * 24 * * * 25 * * * 26 * * * 27 *^C
I had a long session with a sysadmin at the other end and he verified that the problem wasn't with the server; no firewall or DDOS blocking was happening and he was able to make ssh connections while I was blocked. So he said to check with my ISP, and I found this thread...
Thanks for the reply. I did get things working, but it doesn't give me the parallelism that I'd hope for -- ideally i'd open multiple ssh sessions simultaneously so that I can send data in parallel. So still if it's possible to resolve whatever issue there may be with having multiple ssh sessions that'd be great.
And thanks for noticing--and dealing with--the power levels!