From owner-freebsd-stable@FreeBSD.ORG  Thu Aug 21 03:03:48 2003
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 6AF9516A4BF
	for <freebsd-stable@freebsd.org>;
	Thu, 21 Aug 2003 03:03:48 -0700 (PDT)
Received: from techno.sub.ru (webmail.sub.ru [213.247.139.22])
	by mx1.FreeBSD.org (Postfix) with SMTP id DBEBF43FBD
	for <freebsd-stable@freebsd.org>;
	Thu, 21 Aug 2003 03:03:46 -0700 (PDT)
	(envelope-from tarkhil@webmail.sub.ru)
Received: (qmail 28875 invoked by uid 0); 21 Aug 2003 10:04:06 -0000
Received: from unknown (HELO tarkhil.over.ru) (213.148.23.65)
  by webmail.sub.ru with SMTP; 21 Aug 2003 10:04:06 -0000
Date: Thu, 21 Aug 2003 14:03:21 +0400
From: Alex Povolotsky <tarkhil@webmail.sub.ru>
To: freebsd-stable@freebsd.org
Message-Id: <20030821140321.3a8a6130.tarkhil@webmail.sub.ru>
In-Reply-To: <D2CFC58E0F8CB443B54BE72201E8916E94C9E1@dehhx005.hbg.de.int.atosorigin.com>
References: <D2CFC58E0F8CB443B54BE72201E8916E94C9E1@dehhx005.hbg.de.int.atosorigin.com>
Organization: sub.ru
X-Mailer: Sylpheed version 0.9.3claws (GTK+ 1.2.10; i386-portbld-freebsd4.6)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Subject: Re: Strange fork-related problem: acutally, virus-related
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Production branch of FreeBSD source code
	<freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
	<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
	<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Aug 2003 10:03:48 -0000

On Wed, 20 Aug 2003 22:07:43 +0200
"Oldach, Helge" <Helge.Oldach@atosorigin.com> wrote:

OH> > 
OH> > Anyway, it should not behave that way.
OH> 
OH> Should it? Worms are known to be a NAT killer on dedicated routing
OH> platforms. I am
OH> facing customers every other day complaining about their Cisco
OH> router performance
OH> which usually turns out to be caused by virii. (In particular these
OH> days.)

It, speaking RFC-like, MUST NOT hang the computer. It MUST issue diagnostics like "NAT state table overflow, disabling NAT for 192.168.0.104", or just "NAT state table overflow" before hanging. I've spend about a workday fighting that problem... 

But I SHOULD ask about it in ipfilter's mailing list...

-- 
Alex.