From owner-freebsd-ipfw Mon Jan 14 13:51:43 2002 Delivered-To: freebsd-ipfw@freebsd.org Received: from chk.phattydomain.com (12-225-230-182.client.attbi.com [12.225.230.182]) by hub.freebsd.org (Postfix) with ESMTP id 483EC37B405 for ; Mon, 14 Jan 2002 13:51:36 -0800 (PST) Received: (from chuck@localhost) by chk.phattydomain.com (8.11.6/8.11.4) id g0ELqrR99190; Mon, 14 Jan 2002 13:52:54 -0800 (PST) (envelope-from chuck) Date: Mon, 14 Jan 2002 13:52:54 -0800 (PST) From: chk no Message-Id: <200201142152.g0ELqrR99190@chk.phattydomain.com> To: freebsd-ipfw@freebsd.org Subject: ip_dummynet.c:"*** OUCH! pipe should have been idle!" Cc: chkno@dork.com Reply-To: chkno@dork.com Sender: owner-freebsd-ipfw@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG $ grep OUCH /var/log/messages Jan 12 23:45:46 chk /kernel: *** OUCH! pipe should have been idle! Running the error message through 5 popular search engines hit only on mirrors of the source. I gather that it is not common for this to occur. This machine is running 4.4-STABLE, cvsuped Wed Dec 19 15:02:20 PST 2001. There have been some other issues with ipfw+natd packet loops (more packets pass through the system than enter it) if the pipe queue is set too low, packet loops if the network activity gets too hectic (mutella). I was about to cvsup & reinstall, but i'll hold off if anyone wants to look at it. It's still up & crunching packets... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ipfw" in the body of the message