Date: Fri, 15 Dec 2006 12:14:13 -0800 From: "Bruce A. Mah" <bmah@freebsd.org> To: Doug Barton <dougb@freebsd.org> Cc: gnn@freebsd.org, freebsd-current@freebsd.org, re@freebsd.org Subject: Re: Socket problems with latest -current Message-ID: <45830215.9020607@freebsd.org> In-Reply-To: <4582F2DE.8080806@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>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigCEB177AAF08B7A52933FFC71 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable If memory serves me right, Doug Barton wrote: > Bruce A. Mah wrote: >> I'm trying to reproduce this problem but without success. I did an >> install of 6.2-RC1/i386 from CD into a Parallels VM, then manually >> updated /etc/rc.d/auto_linklocal to version 1.1.2.3.2.1 (same as 1.4 y= ou >> tested with).=20 >=20 > I'm not sure if they're relevant or not, but the differences between > what you did and what I did are: >=20 > 1. I installed on a real box > 2. I installed 6.1-RELEASE from CD, then cvsup'ed to RELENG_6. >=20 > One other possible difference, I'm on a Core 2 Duo, running i386 SMP. >=20 > You might also try enabling named for your testing. The default > configuration should give you a simple local resolver which you can > then test things like 'dig @127.0.0.1 www.yahoo.com' Thanks for the info. BIND seems to work OK in this environment too. (What was the failure mode for you?) Part of me is hoping that there's something odd in your environment, especially because I haven't heard any other similar reports of problems so far on current@, stable@, or net@. I figure if sendmail or named can't bind sockets there'd be a pretty loud outcry from a lot of people. 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. Would it be too much to ask for a (possibly slightly sanitized) /etc/rc.conf and kernel configuration file from the machine in question? (Privately obviously.) 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. Thanks! Bruce. PS. I'm in the process of updating a physical machine to the tip of RELENG_6 but this takes awhile (it's a UP 1GHz P-III and believe it or not the fastest FreeBSD machine I own). --------------enigCEB177AAF08B7A52933FFC71 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFgwIV2MoxcVugUsMRArQzAKDIouYycGunJHFiNkYzRr5jRVnH4gCgorGq ve/EA+U1iSeTRBGNCNrIgSI= =s/6e -----END PGP SIGNATURE----- --------------enigCEB177AAF08B7A52933FFC71--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?45830215.9020607>