Subject: bin/13497: ssh/scp complain verbosly when connecting from IPv4 only machines to servers with IPv6 address
To: None <gnats-bugs@gnats.netbsd.org>
From: None <martin@duskware.de>
List: netbsd-bugs
Date: 07/17/2001 23:25:56
>Number:         13497
>Category:       bin
>Synopsis:       ssh/scp complain verbosly when connecting from IPv4 only machines to servers with IPv6 address
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    bin-bug-people
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Tue Jul 17 14:23:00 PDT 2001
>Closed-Date:
>Last-Modified:
>Originator:     Martin Husemann
>Release:        1.5W cvs updated somewhere around beginning of Juli
>Organization:
	
>Environment:
	
System: NetBSD setting-sun.duskware.de 1.5W NetBSD 1.5W (SETTINGSUN) #0: Mon Jul 16 23:54:59 MEST 2001 martin@setting-sun.duskware.de:/usr/src/sys/arch/sparc64/compile/SETTINGSUN sparc64
Architecture: sparc64
Machine: sparc64
>Description:

My machine is IPv4 only (no option INET6 in the kernel config).
When I try to ssh or scp to ftp.netbsd.org, I get a spurious warning

socket: Protocol not supported

The connection works, nevertheless. I suppose it's trying all addresses it got
back from the nameserver, where the IPv6 one fail and cause this warning.

>How-To-Repeat:
s/a

>Fix:
Not sure:
Fix the resolver routines to remove IPv6 replies when running on IPv4 only machines?
Make ssh/scp not complain as long as at least one address works?
>Release-Note:
>Audit-Trail:
>Unformatted: