From owner-freebsd-ipfw  Tue Jan 15  5:11:32 2002
Delivered-To: freebsd-ipfw@freebsd.org
Received: from guinness.syncrontech.com (guinness.syncrontech.com [62.71.8.19])
	by hub.freebsd.org (Postfix) with ESMTP
	id C376837B405; Tue, 15 Jan 2002 05:11:24 -0800 (PST)
Received: from there (coffee.syncrontech.com [62.71.8.37])
	by guinness.syncrontech.com (8.11.1/8.11.1) with SMTP id g0FD2dw92151;
	Tue, 15 Jan 2002 15:02:39 +0200 (EET)
	(envelope-from ari.suutari@syncrontech.com)
Message-Id: <200201151302.g0FD2dw92151@guinness.syncrontech.com>
Content-Type: text/plain;
  charset="iso-8859-1"
From: Ari Suutari <ari.suutari@syncrontech.com>
To: Ruslan Ermilov <ru@FreeBSD.ORG>, Luigi Rizzo <rizzo@icir.org>
Subject: Re: ip_dummynet.c:"*** OUCH! pipe should have been idle!"
Date: Tue, 15 Jan 2002 15:11:18 +0200
X-Mailer: KMail [version 1.3.2]
Cc: chkno@dork.com, freebsd-ipfw@FreeBSD.ORG,
	Brian Somers <brian@FreeBSD.ORG>
References: <20020114141539.A70340@iguana.icir.org> <20020115021839.A74391@iguana.icir.org> <20020115144045.J46269@sunbay.com>
In-Reply-To: <20020115144045.J46269@sunbay.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Sender: owner-freebsd-ipfw@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-ipfw.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-ipfw>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-ipfw>
X-Loop: FreeBSD.ORG

Hi,
> 
> Also CC:ed to Brian Somers (who committed that change) and
> Ari Suutari who originally wrote natd(8).
> 
> 
> Cheers,
> Ruslan (who now wonders if the problem fixed in natd.c,v 1.2 was false).
> 

	If I remember correctly I was just wondering about getting an
	ENOBUFS error when the internet link was a slow one
	(because packets could be arriving from local ethernet
	much faster then a modem link can serve). Maybe I did think
	that waiting with select would be better than just drop the
	packet. Thinking it again it seems that dropping is not
	a bad thing since it would occur also if there were no
	natd running in similar situation.

	The correct fix would have been to silently drop the packet.

	But we have it corrected now :-)

		Ari S.

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-ipfw" in the body of the message