Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 16 Sep 2004 04:04:08 -0000
From:      Max Laier <max@love2party.net>
To:        pf4freebsd@freelists.org
Cc:        Ryan Verner <xfesty@computeraddictions.com.au>
Subject:   [pf4freebsd] Re: Maturity of this port?
Message-ID:  <200405250756.55875.max@love2party.net>
In-Reply-To: <40B2DAD4.2040005@computeraddictions.com.au>
References:  <40B2DAD4.2040005@computeraddictions.com.au>

next in thread | previous in thread | raw e-mail | index | archive | help

--Boundary-02=_nAusAcwXlEdSxBy
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

On Tuesday 25 May 2004 07:34, Ryan Verner wrote:
> Honestly - how mature is this port?  Is it recommended for production
> use?  How feature rich and stable is it compared to the OpenBSD offering
> - any known bugs?  Is this going to be actively maintained for the
> forseeable future?

Okay, I'll try to address these fairly general questions:
1) As you might have seen (I should really update the homepage) the port is=
=20
now part of the FreeBSD source tree.
2) FreeBSD 5.x is -CURRENT and as such not recommend for production use=20
per-se. However, if you find FreeBSD-5.x reasonably stable in your=20
environment pf will not be the show-stopper. I use 5.x on all my boxes and =
am=20
satisfied, even tracking -CURRENT (with a delay of a week or so) is good fo=
r=20
most application I think.
3) FreeBSD-Current has the same feature-set as OpenBSD 3.4. Everything shou=
ld=20
work as known from OpenBSD. ALTQ is not part of FreeBSD (yet). One major=20
problem with 3.4 however, is the lack of dynamic interface support. This=20
might cause problems with certain mpd setups (when tun0 is destroyed it mig=
ht=20
trigger a panic when pf still has a reference to this interface).
4) An (experimental) import of OpenBSD 3.5 and ALTQ is available from:=20
http://people.freebsd.org/~mlaier/ I run it on two router, my laptop and my=
=20
desktop/development machine without problems, but am still waiting for more=
=20
feedback from other list-users. I can only encourage you to give it a spin,=
 I=20
am very confident that this will match your needs.
5) Daniel Hartmeier accepted a FreeBSD commit-bit to maintain the port on=20
=46reeBSD in addition to myself. We will try to stay in sync with OpenBSD=20
stable and will very likely import more reliability fixes from OpenBSD=20
current than OpenBSD MFC's to its stable branch (as the policy for MFC'ing =
is=20
very strict over there).

Summary:
If you need ALTQ, we don't have a stable solution yet, but you are invited =
to=20
test the patches (which are very close to stable already). If you do not ne=
ed=20
ALTQ you can install FreeBSD-current and have OpenBSD 3.4-STABLE pf.

=2D-=20
Best regards,				| mlaier@freebsd.org
Max Laier				| ICQ #67774661
http://pf4freebsd.love2party.net/	| mlaier@EFnet

--Boundary-02=_nAusAcwXlEdSxBy
Content-Type: application/pgp-signature
Content-Description: signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (FreeBSD)

iD8DBQBAsuAnXyyEoT62BG0RAhrJAJ4oilW8KUFqB7LhPFH2u5YDKCxKAACeMEku
Pi5yjYy8rCT0WHxfDgT/BTo=
=wwoA
-----END PGP SIGNATURE-----

--Boundary-02=_nAusAcwXlEdSxBy--




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200405250756.55875.max>