From owner-freebsd-net@FreeBSD.ORG  Thu Mar 11 06:09:01 2004
Return-Path: <owner-freebsd-net@FreeBSD.ORG>
Delivered-To: freebsd-net@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 2A8F816A4CF
	for <freebsd-net@freebsd.org>; Thu, 11 Mar 2004 06:09:01 -0800 (PST)
Received: from mailtoaster1.pipeline.ch (mailtoaster1.pipeline.ch
	[62.48.0.70])	by mx1.FreeBSD.org (Postfix) with ESMTP id 6280943D54
	for <freebsd-net@freebsd.org>; Thu, 11 Mar 2004 06:09:00 -0800 (PST)
	(envelope-from andre@freebsd.org)
Received: (qmail 55706 invoked from network); 11 Mar 2004 14:08:56 -0000
Received: from unknown (HELO freebsd.org) ([213.187.67.40])
          (envelope-sender <andre@freebsd.org>)
          by mailtoaster1.pipeline.ch (qmail-ldap-1.03) with SMTP
          for <colin.percival@wadham.ox.ac.uk>; 11 Mar 2004 14:08:56 -0000
Message-ID: <405072E8.9A333E99@freebsd.org>
Date: Thu, 11 Mar 2004 15:08:40 +0100
From: Andre Oppermann <andre@freebsd.org>
X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Colin Percival <colin.percival@wadham.ox.ac.uk>
References: <6.0.1.1.1.20040310231226.03cee598@imap.sfu.ca>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
cc: freebsd-net@freebsd.org
cc: secteam@freebsd.org
Subject: Re: Broadcast storming problem?
X-BeenThere: freebsd-net@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Networking and TCP/IP with FreeBSD <freebsd-net.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-net>
List-Post: <mailto:freebsd-net@freebsd.org>
List-Help: <mailto:freebsd-net-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Mar 2004 14:09:01 -0000

Colin Percival wrote:
> 
> [CC: secteam, since this relates to a recent advisory]
> 
>    In http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/64053 a
> problem is reported as having been introduced by the recent
> TCP reassembly patch.
>    Could someone look into this please?

Reading the description of the problem I find it highly unlikely
that the TCP reassembly changes would have caused this.  The TCP
reassembly code only comes into play when a packet belongs to an
established TCP session.  And it doesn't generate any kind of
packet by itself, it only drops them if there are too many.

The problem in this PR must come from something else in IP stack.
I don't have a clear idea what it can be and I'm at conference
till tomorrow and only have slow modem access.

-- 
Andre