From owner-freebsd-hackers Sun Jul 11 9:58:13 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id E2A4E14FB9 for ; Sun, 11 Jul 1999 09:58:11 -0700 (PDT) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.1) with ESMTP id JAA08690; Sun, 11 Jul 1999 09:58:10 -0700 (PDT) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id JAA32031; Sun, 11 Jul 1999 09:58:09 -0700 (PDT) (envelope-from jdp@polstra.com) Date: Sun, 11 Jul 1999 09:58:09 -0700 (PDT) Message-Id: <199907111658.JAA32031@vashon.polstra.com> To: imp@village.org Subject: Re: a BSD identd In-Reply-To: <199907102150.PAA33167@harmony.village.org> References: <57350.931626797@axl.noc.iafrica.com> Organization: Polstra & Co., Seattle, WA Cc: hackers@freebsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <199907102150.PAA33167@harmony.village.org>, Warner Losh wrote: > > Some ftpd and sendmail servers make the queries. When I have my fake > identd in place, they go much faster... :-) Are you sure? If you simply don't run an identd, the queries will get an instant connection refused error. That's even faster than sending back a bogus response. The only way a long timeout can occur is if you have a filter rule installed that drops the incoming packets without responding to them. You can block the incoming packets but still avoid the timeout with a filter rule that sends back a reset: add reset tcp from any to any auth setup in via etha16 John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "No matter how cynical I get, I just can't keep up." -- Nora Ephron To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message