From owner-freebsd-pf@FreeBSD.ORG Thu Sep 16 03:49:21 2004 Return-Path: Delivered-To: freebsd-pf@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 674) id 6AC9916A4D1; Thu, 16 Sep 2004 03:49:21 +0000 (GMT) Delivered-To: mlaier@vampire.homelinux.org Received: (qmail 43259 invoked by uid 1005); 1 Sep 2003 10:47:53 -0000 Delivered-To: max@vampire.homelinux.org Received: (qmail 43256 invoked from network); 1 Sep 2003 10:47:53 -0000 Received: from moutng.kundenserver.de (212.227.126.187) by pd953044d.dip.t-dialin.net with SMTP; 1 Sep 2003 10:47:53 -0000 Received: from [212.227.126.152] (helo=mxng01.kundenserver.de) by moutng.kundenserver.de with esmtp (Exim 3.35 #1) id 19tn74-0001S3-00 for max@vampire.homelinux.org; Mon, 01 Sep 2003 13:44:50 +0200 Received: from [206.53.239.180] (helo=turing.freelists.org) by mxng01.kundenserver.de with esmtp (Exim 3.35 #1) id 19tn6w-0000cy-00 for max@love2party.net; Mon, 01 Sep 2003 13:44:42 +0200 Received: from turing (localhost [127.0.0.1])ESMTP id ABA963909CB; Mon, 1 Sep 2003 06:44:48 -0500 (EST) Received: with ECARTIS (v1.0.0; list pf4freebsd); Mon, 01 Sep 2003 06:44:44 -0500 (EST) Delivered-To: pf4freebsd@freelists.org Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.189])ESMTP id 8A0B3390986 for ; Mon, 1 Sep 2003 06:44:43 -0500 (EST) Received: from [212.227.126.155] (helo=mrelayng.kundenserver.de) by moutng.kundenserver.de with esmtp (Exim 3.35 #1) id 19tn6o-0006XH-00; Mon, 01 Sep 2003 13:44:34 +0200 Received: from [217.83.4.77] (helo=max900) by mrelayng.kundenserver.de with asmtp (Exim 3.35 #1) id 19tn6n-00027l-00; Mon, 01 Sep 2003 13:44:33 +0200 Message-ID: <003f01c3707e$aa035080$01000001@max900> From: "Max Laier" To: References: <20030901024435.GA47671@procyon.firepipe.net> MIME-Version: 1.0 Content-type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1158 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 X-archive-position: 132 X-ecartis-version: Ecartis v1.0.0 Sender: pf4freebsd-bounce@freelists.org Errors-To: pf4freebsd-bounce@freelists.org X-original-sender: max@love2party.net Precedence: normal X-list: pf4freebsd X-UID: 247 X-Length: 4746 X-Mailman-Approved-At: Thu, 16 Sep 2004 03:55:52 +0000 cc: pf4freebsd@freelists.org Subject: [pf4freebsd] Re: What to do with the FreeBSD port security/pf? X-BeenThere: freebsd-pf@freebsd.org X-Mailman-Version: 2.1.1 Reply-To: pf4freebsd@freelists.org List-Id: Technical discussion and general questions about packet filter (pf) List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Date: Thu, 16 Sep 2004 03:49:21 -0000 X-Original-Date: Mon, 1 Sep 2003 13:46:20 +0200 X-List-Received-Date: Thu, 16 Sep 2004 03:49:21 -0000 > [Please Cc: me as I am not subscribed.] > > Hello, > > I understand from several people that the port is using an > outdated version of the pf port (1.0 vs. 1.63). Since this > version is essentially broken, it seems to me that one of two > things should happen: > > 1) Remove the port. > 2) Update the port. Wait! You sliped one or two facts here: 1) Version 1.0 is in fact pf as present in OpenBSD 3.3. So it is what we consider stable. 2) Portrevision 7 brings a fix for an essential problem that has been present since the very first version and was fixed three days ago in OpenBSD, the port and the tarball. 3) As the tarball release is changeing very much, we didn't put it into the portssystem. That would only make sense as a "-devel" port, which needs a active maintainer et al. > I also understand that the pf4freebsd effort is trying to get the > pf code in the base system. That's great, but what about people > who'd like to use it now? The thing is that we provide the tarball release for people who want to use and *test* OpenBSD-Current features. In addition there will be a patchset against FreeBSD-Current for testing as we need comments from you to learn how to bring pf to FreeBSD in case we are allowed. > Such as myself. I could follow the directions at: > > https://solarflux.org/pf/pf+altq-fbsd51.php > > but, hey, why not save everyone else the trouble? I volunteer to > upgrade & commit said upgrade for the pf port. As I stated above 1.63 is much likely to be revised in less then a week resulting in the need of a port update. If you want to build and *maintain* a pf-devel port, be my guest. That would be a great help right now. > Or I'll remove it if you prefer that approach. Or not? No! It's perfectly up2date (in fact OpenBSD-Stable does not have the patch applied, yet so we are ahead). To sum it up: Port 1.0_7 = OpenBSD 3.3 (with the latest patches) Tarball 1.63 = OpenBSD 3.3-Current (what we be released as OpenBSD 3.4 in November) When OpenBSD 3.4 is released we bring a new Port (2.0) or hope to get a chance to get into the base system. > Thanks for your effort, in any case. :) Thank you. Regards, Max