From owner-freebsd-security Thu Oct 18 2:19:44 2001 Delivered-To: freebsd-security@freebsd.org Received: from mine.kame.net (kame195.kame.net [203.178.141.195]) by hub.freebsd.org (Postfix) with ESMTP id C69C037B407 for ; Thu, 18 Oct 2001 02:19:41 -0700 (PDT) Received: from localhost ([3ffe:501:4819:cafe:260:1dff:fe21:f766]) by mine.kame.net (8.11.1/3.7W) with ESMTP id f9I9TdH00573; Thu, 18 Oct 2001 18:29:39 +0900 (JST) To: tariq_rashid@lineone.net Cc: freebsd-security@freebsd.org Subject: Re: MTU and KAME ipsec In-Reply-To: Your message of "Thu, 18 Oct 2001 10:04:45 +0100" References: X-Mailer: Cue version 0.6 (010810-1737/sakane) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Message-Id: <20011018181931X.sakane@kame.net> Date: Thu, 18 Oct 2001 18:19:31 +0900 From: Shoichi Sakane X-Dispatcher: imput version 20000228(IM140) Lines: 6 Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org > how does the kame ipsec in freebsd 4.4 handle the network interface MTU? > is it automatically set to the correct "discovered value" or must it be statically set? it doesn't do special things. it's not different from when the kernel sends the normal packet. in ipsec case, it just takes ipsec headers length from interface's mtu. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message