From owner-freebsd-security  Sun Sep  3 13:11: 1 2000
Delivered-To: freebsd-security@freebsd.org
Received: from cairo.anu.edu.au (cairo.anu.edu.au [150.203.224.11])
	by hub.freebsd.org (Postfix) with ESMTP
	id 804E237B424; Sun,  3 Sep 2000 13:10:57 -0700 (PDT)
Received: (from avalon@localhost)
	by cairo.anu.edu.au (8.9.3/8.9.3) id HAA15013;
	Mon, 4 Sep 2000 07:10:46 +1100 (EST)
From: Darren Reed <avalon@coombs.anu.edu.au>
Message-Id: <200009032010.HAA15013@cairo.anu.edu.au>
Subject: Re: ipfw and fragments
To: rwatson@FreeBSD.ORG (Robert Watson)
Date: Mon, 4 Sep 2000 07:10:46 +1100 (Australia/NSW)
Cc: dr@kyx.net (Dragos Ruiu), cjclark@alum.mit.edu,
	cjclark@reflexnet.net (Crist J . Clark),
	billf@chimesnet.com (Bill Fumerola), list@rachinsky.de (Nicolas),
	freebsd-security@FreeBSD.ORG
In-Reply-To: <Pine.NEB.3.96L.1000903094614.69440A-100000@fledge.watson.org> from "Robert Watson" at Sep 03, 2000 09:57:35 AM
X-Mailer: ELM [version 2.5 PL1]
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-security@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

In some mail from Robert Watson, sie said:
[...]
> > Does the same behaviour apply to ipf?
> 
> Darren Reed will be able to best answer this question, and presumably will
> do so.

Damn I'd been not reading this thread at all until your email, Robert :-)

What does IP Filter do with fragments ?

That a packet is a fragment is a filterable atttribute.

You can also tell it to remember "state information" triggered by the
fragment with offset == 0.

It never reassembles and doesn't hold them in a buffer until they're
all received either.

Darren


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