Package: ssh Version: 1:3.8.1p1-8.sarge.4 Severity: normal Tags: upstream The problem with using something like: BindAddress 2001:1418:13:1::2 in ssh_config is that it will break IPv4 connections: md@attila:~$ ssh -v xxxxxx.xxx.it OpenSSH_3.8.1p1 Debian 1:3.8.1p1-8, OpenSSL 0.9.7d 17 Mar 2004 debug1: Reading configuration data /etc/ssh/ssh_config debug1: Connecting to xxxxxx.xxx.it [xx.xxx.0.26] port 22. getaddrinfo: 2001:1418:13:1::2: Address family for hostname not supported ssh: connect to host xxxxxx.xxx.it port 22: Success [Exit 1] Binding to an IPv4 address instead only logs an error when connecting to an IPv6 host: md@attila:~$ ssh baol.linux.it getaddrinfo: 213.92.8.2: Address family for hostname not supported [and then it regularly connects] This makes the BindAddress command not really practical to use. -- ciao, Marco
Attachment:
signature.asc
Description: Digital signature