From owner-freebsd-bugs  Thu Nov  4  1: 6:34 1999
Delivered-To: freebsd-bugs@freebsd.org
Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21])
	by hub.freebsd.org (Postfix) with ESMTP
	id 801D014C9C; Thu,  4 Nov 1999 01:06:32 -0800 (PST)
	(envelope-from ru@FreeBSD.org)
Received: (from ru@localhost)
	by freefall.freebsd.org (8.9.3/8.9.2) id BAA51676;
	Thu, 4 Nov 1999 01:06:32 -0800 (PST)
	(envelope-from ru@FreeBSD.org)
Date: Thu, 4 Nov 1999 01:06:32 -0800 (PST)
From: <ru@FreeBSD.org>
Message-Id: <199911040906.BAA51676@freefall.freebsd.org>
To: rfg@monkeys.com, ru@FreeBSD.org, freebsd-bugs@FreeBSD.org
Subject: Re: kern/14688: kernel firewall code doesn't log port #'s for `Fragment's
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

Synopsis: kernel firewall code doesn't log port #'s for `Fragment's

State-Changed-From-To: open->closed
State-Changed-By: ru
State-Changed-When: Thu Nov 4 00:57:27 PST 1999
State-Changed-Why: 
This is because source and destination port numbers are part of the
corresponding protocol header (TCP or UDP), not an IP header, and
are only available in the first IP fragment (with a zero offset).

Please refer to RFC791, RFC793 and RFC1858 for further details.


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