Le 16/01/2019 à 00:05, Karl Berry a écrit : > ~ $ time ssh t...@fencepost.gnu.org true > real 2m8.751s > > traceroute may be more diagnostic than the raw time, to see if the > problem is in the routing in between. Or ssh -vvv if it's the ssh > negotiation that's taking the two minutes. > > I also wonder if ssh on fencepost is trying to do reverse dns on your > host and that is inducing the delay. It's a common reason for such delays. > > I also wonder about forcing a connection over IPv4 to see if that makes > a difference, e.g., maybe it's trying to negotiate over v6 that is > taking forever. Another common culprit. --good luck, karl. >
The culprit is IPv6: ~ $ ssh -vvv t...@fencepost.gnu.org OpenSSH_7.2p2 Trisquel_GNU/Linux_8.0-1, OpenSSL 1.0.2g 1 Mar 2016 debug1: Reading configuration data /etc/ssh/ssh_config debug1: /etc/ssh/ssh_config line 19: Applying options for * debug2: resolving "fencepost.gnu.org" port 22 debug2: ssh_connect_direct: needpriv 0 debug1: Connecting to fencepost.gnu.org [2001:470:142:3::e] port 22. debug1: connect to address 2001:470:142:3::e port 22: Connection timed out debug1: Connecting to fencepost.gnu.org [209.51.188.10] port 22. debug1: Connection established. debug1: identity file /home/therese/.ssh/id_rsa type 1 debug1: key_load_public: No such file or directory debug1: identity file /home/therese/.ssh/id_rsa-cert type -1 debug1: key_load_public: No such file or directory [...] Thérèse
