Date: Sat, 26 Feb 2000 00:26:28 -0500 From: "Crist J. Clark" <cjc@cc942873-a.ewndsr1.nj.home.com> To: cdel <c_deless@efn.org> 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> In-Reply-To: <Pine.GSU.4.05.10002251111130.1768-100000@garcia.efn.org>; from c_deless@efn.org on Fri, Feb 25, 2000 at 12:53:09PM -0800 References: <Pine.GSU.4.05.10002251111130.1768-100000@garcia.efn.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000226002628.B20702>