Subject: Re: kernel option for "socket: Protocol not supported"
To: Ignatios Souvatzis <is@netbsd.org>
From: None <jonathan@dsg.stanford.edu>
List: tech-kern
Date: 02/21/2006 13:11:52
In message <20060221210414.GA27831@beverly.kleinbus.org>,
Ignatios Souvatzis writes:

>On Tue, Feb 21, 2006 at 03:42:57PM -0500, George Georgalis wrote:
>> On Tue, Feb 21, 2006 at 11:54:38AM -0800, Jonathan Stone wrote:
>Uhm... in George's case, disabling it was what created the error. 
>Enabling it and the lo0 device would have made it succeed ;-)

But only if you *want* local IPv6, and by removing options INET6,
George is saying quite clearly that he doesn't.

I think the real ``bug'' is forcing IPv6 down people's throats
whethher they want it or no, which leads to nobody bothering to
test IPv6-less configs, which leads to bugs (or more accurately,
buggy error messgaes) like the one George encountered.