From owner-freebsd-current@freebsd.org Mon Nov 14 14:12:14 2016 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E5424C400CA for ; Mon, 14 Nov 2016 14:12:14 +0000 (UTC) (envelope-from franco@lastsummer.de) Received: from host64.shmhost.net (host64.kissl.de [213.239.241.64]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id AFAA61FEA for ; Mon, 14 Nov 2016 14:12:14 +0000 (UTC) (envelope-from franco@lastsummer.de) Received: from francos-mbp.homeoffice.local (ipservice-092-217-062-255.092.217.pools.vodafone-ip.de [92.217.62.255]) by host64.shmhost.net (Postfix) with ESMTPSA id 3BF3783917; Mon, 14 Nov 2016 15:12:11 +0100 (CET) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 10.1 \(3251\)) Subject: Re: netpfil with if_output and ip(6)_output From: Franco Fichtner In-Reply-To: <6980420c-a473-232b-5847-9aa4dd8eab66@yandex-team.ru> Date: Mon, 14 Nov 2016 15:12:10 +0100 Cc: freebsd-current Content-Transfer-Encoding: quoted-printable Message-Id: <3E6A1786-613F-4ECF-8302-DB38B0213128@lastsummer.de> References: <2456B7E6-2425-4D86-A02B-33CE1EFEB608@lastsummer.de> <6980420c-a473-232b-5847-9aa4dd8eab66@yandex-team.ru> To: "Andrey V. Elsukov" X-Mailer: Apple Mail (2.3251) X-Virus-Scanned: clamav-milter 0.99.2 at host64.shmhost.net X-Virus-Status: Clean X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Nov 2016 14:12:15 -0000 > On 14 Nov 2016, at 2:36 PM, Andrey V. Elsukov = wrote: >=20 > On 14.11.2016 16:13, Franco Fichtner wrote: >>> void ip6_flush_fwdtag(struct mbuf *m); >>=20 >> This looks reasonable, thank you. How would we proceed with the >> implementation / porting of ipfw to the new framework? >>=20 >=20 > Both ipfw and pf needs some patches. Also the generic *proto*_output > should be modified. Currently I'm busy with IPsec related work, so if > you will do this it will be very cool :) > But if not, I can do some work after 2-3 weeks. I will close the previous review and start on your proposal. Should have something concrete next week. Many thanks, Franco=