From owner-freebsd-stable Tue Apr 3 7: 4:46 2001 Delivered-To: freebsd-stable@freebsd.org Received: from ece.cmu.edu (ECE.CMU.EDU [128.2.236.200]) by hub.freebsd.org (Postfix) with ESMTP id 9788737B718 for ; Tue, 3 Apr 2001 07:04:43 -0700 (PDT) (envelope-from allbery@ece.cmu.edu) Received: from tully (TULLY.ECE.CMU.EDU [128.2.136.132]) (authenticated) by ece.cmu.edu (8.11.0/8.10.2) with ESMTP id f33E43r02326; Tue, 3 Apr 2001 10:04:03 -0400 (EDT) Date: Tue, 03 Apr 2001 10:04:03 -0400 From: "Brandon S. Allbery KF8NH" To: Kenneth W Cochran , Dan Larsson Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Strange localhost NS look attempts Message-ID: <33600000.986306643@tully> In-Reply-To: <200104031355.JAA15831@world.std.com> X-Mailer: Mulberry/2.0.6 (Linux/x86) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tuesday, April 03, 2001 09:55:53 AM -0400, Kenneth W Cochran wrote: +----- | So, why should that be an invalid connection attempt? | Looks to me like localhost should always be allowed to | connect to itself... (?) +--->8 If we ignore the LOG_IN_VAIN red herring, what's really happening here is that you are running a nameserver on localhost which is returning some kind of response after the querant (netscape?) has timed out (and therefore closed its query socket). So the real question is, why is the nameserver timing out? -- brandon s. allbery [os/2][linux][solaris][japh] allbery@kf8nh.apk.net system administrator [WAY too many hats] allbery@ece.cmu.edu electrical and computer engineering KF8NH carnegie mellon university ["better check the oblivious first" -ke6sls] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message