Subject: Re: kernel option for "socket: Protocol not supported"
To: None <tech-kern@NetBSD.org>
From: Ignatios Souvatzis <is@netbsd.org>
List: tech-kern
Date: 02/22/2006 09:32:37
--ew6BAiZeqk4r7MaW
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Wed, Feb 22, 2006 at 09:17:15AM +0100, Martin Husemann wrote:
> On Tue, Feb 21, 2006 at 10:20:53PM +0100, Ignatios Souvatzis wrote:
> > I agree here; but note that we surely also have a lot of code that
> > breaks or at least gives similar error messages if we disable IPv4.
>=20
> The bug is simply that our libc resolver code returns addresses for famil=
ies
> that the kernel does not support. It should check and remove them upfront.
=20
Martin: for this specific error, this would help. But... why should the
resolver lie about the entries in the database? You would at least need to
add a flag for "need this to open a connection" (as opposed to the "want to
read the database") case, in my opinion.

Besides: I've also seen the "host/network down/unreachable" case.
Hm, just tried; this is fixed now, and the PROTONOTSUPP should be
added.

	-is
--=20
seal your e-mail: http://www.gnupg.org/

--ew6BAiZeqk4r7MaW
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (NetBSD)

iD8DBQFD/CGlN4tiz3B8hB0RAh0BAJ0QIDJbpaeZgz0rKgJwSbSz8kZ6QwCgqIAJ
Ti8C9K3IiR1ZBlJUw02FOKE=
=UUw2
-----END PGP SIGNATURE-----

--ew6BAiZeqk4r7MaW--