From owner-freebsd-current@FreeBSD.ORG Wed Dec 13 18:39:34 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id E189816A47C for ; Wed, 13 Dec 2006 18:39:34 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mx21.fluidhosting.com [204.14.89.4]) by mx1.FreeBSD.org (Postfix) with SMTP id D328443CB5 for ; Wed, 13 Dec 2006 18:38:02 +0000 (GMT) (envelope-from dougb@FreeBSD.org) Received: (qmail 18309 invoked by uid 399); 13 Dec 2006 18:39:26 -0000 Received: from localhost (HELO ?192.168.0.5?) (dougb@dougbarton.us@127.0.0.1) by localhost with SMTP; 13 Dec 2006 18:39:26 -0000 X-Originating-IP: 127.0.0.1 Message-ID: <458048DB.2020002@FreeBSD.org> Date: Wed, 13 Dec 2006 10:39:23 -0800 From: Doug Barton Organization: http://www.freebsd.org/ User-Agent: Thunderbird 1.5.0.8 (X11/20061125) MIME-Version: 1.0 To: gnn@freebsd.org References: <457C81E9.7040806@FreeBSD.org> <457D2655.9050500@FreeBSD.org> In-Reply-To: X-Enigmail-Version: 0.94.1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: re@freebsd.org, freebsd-current@freebsd.org Subject: Re: Socket problems with latest -current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Dec 2006 18:39:35 -0000 gnn@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