Red Hat Bugzilla – Bug 1262245
ssh failback to ipv4 a long time
Last modified: 2015-09-14 02:49:03 EDT
Created attachment 1072498 [details] screenshot Description of problem: My server sy24.ru uses both ipv4 and ipv6 protocols. When I use domain name as host, ssh try use ipv6 protocol first, but when my ISP have some troubles with ipv6, I have to wait a long time when ssh automatically go to ipv4. Modern browsers make it immediately. I want here that ssh use less timeout for failback to ipv4, or use both protocols in parallel. $ ssh synergy-demo@sy24.ru -vvv OpenSSH_7.1p1, OpenSSL 1.0.2d-fips 9 Jul 2015 debug1: Reading configuration data /etc/ssh/ssh_config debug1: /etc/ssh/ssh_config line 56: Applying options for * debug2: ssh_connect: needpriv 0 debug1: Connecting to sy24.ru [2a02:c200:1:10:2:2:5208:1] port 22. debug1: connect to address 2a02:c200:1:10:2:2:5208:1 port 22: Connection timed out debug1: Connecting to sy24.ru [213.136.82.171] port 22. debug1: Connection established.
There is option ConnectTimeout in ssh_config, which should suit for your needs. Please let me know it it works for you. I don't have ISP with IPv6 troubles. It should work for you in this way for 10s timeout: $ ssh synergy-demo@sy24.ru -vvv -oConnectTimeout=10 or you can store it in your global /etc/ssh/ssh_config as a line ConnectTimeout 10
Thanks, it helps. With this option timeout can be decreased to 1 sec. Do not you think that necessary to reduce the default timeout? Or make a more intelligent algorithm as in browsers.
I don't think so. Default timeout is none, which will rely on the TCP timeout. This is usually the best when you don't have any information about network infrastructure (default). Setting the limit too low can make connection over high latency network fail. This is not something you want by default, but if you know what are you doing, it can be useful tuning for your setup.