From owner-freebsd-current@FreeBSD.ORG Sat Dec 16 02:00:49 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 B7C1616A4AB for ; Sat, 16 Dec 2006 02:00:49 +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 0AC8F43CA2 for ; Sat, 16 Dec 2006 01:59:02 +0000 (GMT) (envelope-from dougb@FreeBSD.org) Received: (qmail 30360 invoked by uid 399); 16 Dec 2006 02:00:45 -0000 Received: from localhost (HELO ?192.168.0.5?) (dougb@dougbarton.us@127.0.0.1) by localhost with SMTP; 16 Dec 2006 02:00:45 -0000 X-Originating-IP: 127.0.0.1 Message-ID: <4583534A.7010909@FreeBSD.org> Date: Fri, 15 Dec 2006 18:00:42 -0800 From: Doug Barton Organization: http://www.freebsd.org/ User-Agent: Thunderbird 1.5.0.8 (X11/20061125) MIME-Version: 1.0 To: "Bruce A. Mah" References: <457C81E9.7040806@FreeBSD.org> <457D2655.9050500@FreeBSD.org> <458048DB.2020002@FreeBSD.org> <4582D0B0.40108@freebsd.org> <4582F2DE.8080806@FreeBSD.org> <45830215.9020607@freebsd.org> In-Reply-To: <45830215.9020607@freebsd.org> X-Enigmail-Version: 0.94.1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: gnn@freebsd.org, freebsd-current@freebsd.org, re@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: Sat, 16 Dec 2006 02:00:49 -0000 Bruce A. Mah wrote: > BTW, I started looking at this because re@ needs to decide what to do > here for 6.2. If a default (or even "normal") configuration is possible > to produce the problems you saw, we obviously can't ship this way. Good news for you, I found the problem. Bad news for me, I'm apparently an idiot. Well, not quite an idiot, but I have a local script to set up the wired interface if it's connected, and the wireless if it's not. Somewhere in there I forgot about configuring lo0, but it was magically being done for me. With the change that hrs made to rc.d/auto_linklocal, the magic stopped happening, and in focusing on the new fe80::1 address I missed the fact that the IPv4 address wasn't there. Why the change caused lo0 to stop being configured for IPv4 is a new mystery, but that one is more in my area. Sorry about the false alarm. > Oh yeah. Is it possible that the machine has a hostname that only has a > AAAA record (no A record) in DNS or some other thing like this? I don't > expect that you'd do something so "interesting" but I had to ask. Interesting that you asked that question, it's definitely the right track, and it's what made me go back and look harder at what I was doing behind the scenes. Thanks! Doug -- This .signature sanitized for your protection