From owner-freebsd-net@FreeBSD.ORG Sun Nov 9 13:30:58 2014 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 73B0476E; Sun, 9 Nov 2014 13:30:58 +0000 (UTC) Received: from olymp.kibab.com (olymp6.kibab.com [IPv6:2a01:4f8:160:84c1::2]) by mx1.freebsd.org (Postfix) with ESMTP id 37706A57; Sun, 9 Nov 2014 13:30:57 +0000 (UTC) DKIM-Filter: OpenDKIM Filter v2.8.3 olymp.kibab.com 70D397590E DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=bakulin.de; s=default; t=1415539855; bh=oDNrXQvjDG5gV569jUq/U+BApNzj5+wCnJxhCGL1Mik=; h=Date:From:To:CC:Subject:References:In-Reply-To; b=FjjXgUy+BqcGLlZybNMm0CWQ0dUmqmoBjkrnlUSTUD173BDOMal95BtGZNi+hxVpk m7OMfY7VLO7rvEKf3+uX2RWiwFbzIFnIcUxzp2cPv+ATC78L6ZGrsLPGesNh2yU93S 8H65y5R+qaCmtoWHM29SvXFsV989Jjw2ctqdMOug= Message-ID: <545F6C8F.6010700@bakulin.de> Date: Sun, 09 Nov 2014 14:30:55 +0100 From: Ilya Bakulin MIME-Version: 1.0 To: Kristof Provost Subject: Re: Checksumming outgoing packets in PF vs in ip[6]_output References: <1415210423.3394438.187470637.21CD8D3D@webmail.messagingengine.com> <9355b23f1a07008eca61f16ebd828d0b@mail.bakulin.de> <20141107133101.GF2044@vega.codepro.be> In-Reply-To: <20141107133101.GF2044@vega.codepro.be> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org, Mark Felder X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 09 Nov 2014 13:30:58 -0000 On 07.11.14, 14:31, Kristof Provost wrote: > On 2014-11-05 19:11:55 (+0100), Ilya Bakulin wrote: >> On 2014-11-05 19:00, Mark Felder wrote: >>> Now if we could only stamp out the bug with ipv6 fragment and pf I'd be >>> a happy, happy daemon. :-) >> This is somewhat more complex problem, I'll take a look as the time >> allows. >> > I've been playing with it too. I have a patch which seems to be working, > but it currently drops the distinction between PFRULE_FRAGCROP and > PFRULE_FRAGDROP. OpenBSD dropped that a while ago, but I figured FreeBSD > wouldn't want user-visible changes. > > I've been meaning to look at that some more but ... ENOTIME. > It's tentatively planned as a project for Chaos Congress (end of > December), but no promises. > > If you like I can probably dig up the (non-clean) patches for you. > > Regards, > Kristof > Yes, please do it, would be interesting to look at your code! -- Regards, Ilya Bakulin