Re: Socket problems with latest -current

gnn_at_freebsd.org wrote:
> At Mon, 11 Dec 2006 01:35:17 -0800,
> Doug Barton wrote:
>> Doug Barton wrote:
>>> With sources cvsup'ed around 20:35 PST on 8 December everything works
>>> just fine. With sources cvsup'ed early this morning, 12:42 am PST on
>>> 10 December, I'm getting a lot of errors related to sockets:
>> I found the problem, it's the change made in version 1.4 of
>> rc.d/auto_linklocal. Reverting only that change, and using otherwise
>> up to date -current sources allows things to work just fine. Adding
>> that change on the same exact system causes the breakage I described
>> in my previous message.
>>
>> It's probably worth mentioning that I exactly fit the criteria from
>> the 1.4 commit message, I have INET6 in my kernel, but at the moment I
>> have ipv6_enable=no in rc.conf.
>>
>> This change should be backed out of HEAD and RELENG_6[_2] until the
>> cause of this breakage is understood.
> 
> I'll take a quick look at this too.  

Thanks. I installed a totally generic RELENG_6 system from scratch
yesterday, and confirmed that the problem I had in -current exists in
-stable too. This is a serious issue, given that the default
installation will have INET6 in the kernel, but ipv6_enable=no in
/etc/defaults/rc.conf.

It would be preferable of course to fix the actual problem, but
between "it works" and "it is fully RFC compliant," I have to pick the
former.

Doug

-- 

    This .signature sanitized for your protection