From owner-freebsd-questions Fri Feb 25 21:21:49 2000 Delivered-To: freebsd-questions@freebsd.org Received: from cc942873-a.ewndsr1.nj.home.com (cc942873-a.ewndsr1.nj.home.com [24.2.89.207]) by hub.freebsd.org (Postfix) with ESMTP id 3883537BC5C for ; Fri, 25 Feb 2000 21:21:46 -0800 (PST) (envelope-from cjc@cc942873-a.ewndsr1.nj.home.com) Received: (from cjc@localhost) by cc942873-a.ewndsr1.nj.home.com (8.9.3/8.9.3) id AAA20835; Sat, 26 Feb 2000 00:26:28 -0500 (EST) (envelope-from cjc) Date: Sat, 26 Feb 2000 00:26:28 -0500 From: "Crist J. Clark" To: cdel Cc: freebsd-questions@FreeBSD.ORG Subject: Re: Ipfw block udp in to 53 spurs runaway popper!? Message-ID: <20000226002628.B20702@cc942873-a.ewndsr1.nj.home.com> Reply-To: cjclark@home.com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from c_deless@efn.org on Fri, Feb 25, 2000 at 12:53:09PM -0800 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Feb 25, 2000 at 12:53:09PM -0800, cdel wrote: > I inadvertently blocked inbound udp from DNS:53 to box:any and noticed > that qpopper (2.53) started creating errant, cpu slowing processes that > went away > when I opened it back up. I was able to reproduce the behavior repeatedly. > > Box is 3.3-RELEASE. > > Is this just a quirk of misconfiguration? Box is running NAT and net is > private. Only clients accessing popper are on private net. This is > probably an issue more for Qualcomm but I though't I'd check here first. Well, it sure sounds like a DNS issue; processes waiting for a look-up to time-out. I don't use qpopper, but does it try to reverse look-up any client that connects? Seems like that would explain this. -- Crist J. Clark cjclark@home.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message