From owner-freebsd-net@FreeBSD.ORG Thu Jul 14 03:47:52 2005 Return-Path: X-Original-To: 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 AD03F16A41C for ; Thu, 14 Jul 2005 03:47:52 +0000 (GMT) (envelope-from gnn@neville-neil.com) Received: from mrout2.yahoo.com (mrout2.yahoo.com [216.145.54.172]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7B44343D46 for ; Thu, 14 Jul 2005 03:47:52 +0000 (GMT) (envelope-from gnn@neville-neil.com) Received: from minion.local.neville-neil.com (proxy8.corp.yahoo.com [216.145.48.13]) by mrout2.yahoo.com (8.13.4/8.13.4/y.out) with ESMTP id j6E3kCKl072449; Wed, 13 Jul 2005 20:46:13 -0700 (PDT) Date: Thu, 14 Jul 2005 12:46:11 +0900 Message-ID: From: gnn@freebsd.org To: Jeremie Le Hen In-Reply-To: <20050713130042.GV39292@obiwan.tataz.chchile.org> References: <20050713130042.GV39292@obiwan.tataz.chchile.org> User-Agent: Wanderlust/2.12.2 (99 Luftballons) SEMI/1.14.6 (Maruoka) FLIM/1.14.7 (=?ISO-8859-4?Q?Sanj=F2?=) APEL/10.6 Emacs/21.3.50 (powerpc-apple-darwin8.1.0) MULE/5.0 (SAKAKI) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII Cc: freebsd-net@freebsd.org Subject: Re: Problem with Path MTU Discovery X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Jul 2005 03:47:52 -0000 At Wed, 13 Jul 2005 15:00:42 +0200, Jeremie Le Hen wrote: > > Hi, > > I set a gif(4)-based IPSec tunnel between my network and a friend's one. > This works pretty well, except that Path MTU Discovery doesn't work. > > Quick draw: > MTU: 1500 MTU:1280 MTU:1500 > Comp1 --------- Gate1 -------- Gate2 -----+-- Comp2 > RELENG_5 RELENG_4 RELENG_5 | RELENG_5 > | > +-- Comp3 > RELENG_5 > Can you look at the routing table for each of Comp1 and Comp2 and also use the -W flag to show the path MTU? If there is something wonky in the routing table then TCP will not hear about the MTU change. Thanks, George