From owner-freebsd-net@FreeBSD.ORG Tue Aug 21 14:31:28 2007 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1BE9916A41A for ; Tue, 21 Aug 2007 14:31:28 +0000 (UTC) (envelope-from dhartmei@insomnia.benzedrine.cx) Received: from insomnia.benzedrine.cx (insomnia.benzedrine.cx [IPv6:2001:6f8:1098::2]) by mx1.freebsd.org (Postfix) with ESMTP id B486913C483 for ; Tue, 21 Aug 2007 14:31:27 +0000 (UTC) (envelope-from dhartmei@insomnia.benzedrine.cx) Received: from insomnia.benzedrine.cx (localhost.benzedrine.cx [127.0.0.1]) by insomnia.benzedrine.cx (8.14.1/8.13.4) with ESMTP id l7LEVQT1026877 (version=TLSv1/SSLv3 cipher=DHE-DSS-AES256-SHA bits=256 verify=NO); Tue, 21 Aug 2007 16:31:26 +0200 (MEST) Received: (from dhartmei@localhost) by insomnia.benzedrine.cx (8.14.1/8.12.10/Submit) id l7LEVQIw021411; Tue, 21 Aug 2007 16:31:26 +0200 (MEST) Date: Tue, 21 Aug 2007 16:31:26 +0200 From: Daniel Hartmeier To: Jacek Zapala Message-ID: <20070821143125.GB32421@insomnia.benzedrine.cx> References: <200708211010.l7LAA6V7082258@freefall.freebsd.org> <20070821121118.GF27160@insomnia.benzedrine.cx> <1187703472.22531.4.camel@localhost.localdomain> <20070821135048.GA32421@insomnia.benzedrine.cx> <1187705811.30269.5.camel@localhost.localdomain> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1187705811.30269.5.camel@localhost.localdomain> User-Agent: Mutt/1.5.12-2006-07-14 Cc: freebsd-net@freebsd.org Subject: Re: kern/115413: [ipv6] ipv6 pmtu not working 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: Tue, 21 Aug 2007 14:31:28 -0000 On Tue, Aug 21, 2007 at 04:16:51PM +0200, Jacek Zapala wrote: > I have disabled this on sending side (FreeBSD) and it started to work! Ah, so it's related to window scaling. Headaches again ;) Is the following a correct view of your setup: src ---- $int_if pf $ext_if ---- router ---- dst Where client src connects to server dst, and you create the state entry when the initial TCP SYN goes out $ext_if on the firewall? The ICMPv6 is coming in on $ext_if, in the reverse direction, relative to the initial TCP SYN? And the router is between pf and dst, on the $ext_if side? Daniel