Date: Fri, 15 Dec 2006 18:00:42 -0800 From: Doug Barton <dougb@FreeBSD.org> To: "Bruce A. Mah" <bmah@freebsd.org> Cc: gnn@freebsd.org, freebsd-current@freebsd.org, re@freebsd.org Subject: Re: Socket problems with latest -current Message-ID: <4583534A.7010909@FreeBSD.org> In-Reply-To: <45830215.9020607@freebsd.org> References: <457C81E9.7040806@FreeBSD.org> <457D2655.9050500@FreeBSD.org> <m23b7klzjz.wl%gnn@neville-neil.com> <458048DB.2020002@FreeBSD.org> <4582D0B0.40108@freebsd.org> <4582F2DE.8080806@FreeBSD.org> <45830215.9020607@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4583534A.7010909>