From owner-freebsd-current@FreeBSD.ORG Mon Apr 15 10:38:13 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id F097E321 for ; Mon, 15 Apr 2013 10:38:13 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from zxy.spb.ru (zxy.spb.ru [195.70.199.98]) by mx1.freebsd.org (Postfix) with ESMTP id B30A2276 for ; Mon, 15 Apr 2013 10:38:13 +0000 (UTC) Received: from slw by zxy.spb.ru with local (Exim 4.69 (FreeBSD)) (envelope-from ) id 1URgnR-0005Xw-2P for freebsd-current@freebsd.org; Mon, 15 Apr 2013 14:38:01 +0400 Date: Mon, 15 Apr 2013 14:38:01 +0400 From: Slawa Olhovchenkov To: freebsd-current@freebsd.org Subject: Re: ipfilter(4) needs maintainer Message-ID: <20130415103801.GA21132@zxy.spb.ru> References: <20130411201805.GD76816@FreeBSD.org> <20130414160648.GD96431@in-addr.com> <36562.1365960622.5652758659450863616@ffe10.ukr.net> <201304150025.07337.Mark.Martinec+freebsd@ijs.si> <951943801.20130415141536@serebryakov.spb.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <951943801.20130415141536@serebryakov.spb.ru> User-Agent: Mutt/1.5.21 (2010-09-15) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: slw@zxy.spb.ru X-SA-Exim-Scanned: No (on zxy.spb.ru); SAEximRunCond expanded to false X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 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, 15 Apr 2013 10:38:14 -0000 On Mon, Apr 15, 2013 at 02:15:36PM +0400, Lev Serebryakov wrote: > >> Yes! This is the most clever thought in this thread. Why we need 3 > >> firewalls? Two packet filters it's excess too. We have two packet filters: > >> one with excellent syntax and functionality but with outdated bandwidth > >> control mechanism (aka ALTQ); another - with nice traffic > >> shaper/prioritization (dummynet)/classification (diffused) but with > >> complicated implementation in not trivial tasks. May be the next step > >> will be discussion about one packet filter in the system?.. > > MM> ... and as far as I can tell none of them is currently usable > MM> on an IPv6-only FreeBSD (like protecting a host with sshguard), > MM> none of them supports stateful NAT64, nor IPv6 prefix translation :( > IPv6 prefix translation?! AGAIN!? FML. I've thought, that IPv6 will > render all that NAT nightmare to void. I hope, IPv6 prefix translation > will not be possible never ever! You disallow anonymization? NAT do anonymisation also.