Date: Fri, 27 Feb 2004 16:18:03 -0500 From: "JJB" <Barbish3@adelphia.net> To: "Chuck Swiger" <cswiger@mac.com> Cc: freebsd-questions@freebsd.org Subject: RE: Problems resolving hosts Message-ID: <MIEPLLIBMLEEABPDBIEGCEBAFNAA.Barbish3@adelphia.net> In-Reply-To: <403F8AB0.7060403@mac.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Well if you had paid closer attention to what Travis wrote you would have read that nothing had changed on that 5.2 lan box or his lan network so your guess about resolv.conf is way off base, and that UFS2 being the problem is a much more sound opinion. And as far as IPFW goes, your statement is again another case of you not paying attention to what was written. You really need to read closely before opening your mouth saying things which are not true. I never said "that IPFW is completely broken" what I said is ipfw stateful rules do not work in an Lan network when ipfw's divert/nated legacy subroutine is used. This subject was beat to death in a long thread back around the first of the year. You should check the archives for the technical details before you sound off demonstrating to everyone how little you know about what truly has transpired. Open mouth insert foot. You should also read all the posts to this list and see for your self all the 5.2.1 problems people are having. Bottom line is 5.2 is an very dirty release and is an long way from being moved to stable. It's formal release date has all ready been moved back 3 time and will more than likely move back again. The kernel development team just bit off more than it could handle this time. If it gets moved to stable in it current condition it will only end up being one of those 5.2.1.1.1 releases as fixes are applied to the stable branch and fixing stable releales is not an goal of the stable branch. -----Original Message----- From: Chuck Swiger [mailto:cswiger@mac.com] Sent: Friday, February 27, 2004 1:22 PM To: Barbish3@adelphia.net Cc: Travis Troyer; freebsd-questions@freebsd.org Subject: Re: Problems resolving hosts JJB wrote: > You are experiencing one of the many problems created by the new > file system in the 5.x development releases. The file system gets > all locked up and then times out before releasing the sector on the > hard drive so it can be read by program. Dude, Travis' problem sounds a lot more like what would happen if one of the nameservers listed in /etc/resolv.conf wasn't responding to DNS queries. Your responses would be more helpful to other people if you refrained from locking the notion that all problems with 5.x are due to UFS2 into your brain, or for that matter, being convinced that IPFW is completely broken and there is a conspiracy against other firewalls on FreeBSD. :-) -- -Chuck PS: To debug your problem, try using "dig @ns1 host", where you replace ns1 with each of the DNS resolvers you have listed or available, and replace host with one or more hostnames that have been causing delays. This will show you how quickly DNS is working and thus confirm whether the problem lies in this area, or else expose which nameserver isn't working and maybe why...
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?MIEPLLIBMLEEABPDBIEGCEBAFNAA.Barbish3>