Date: Thu, 16 Sep 2004 04:03:28 -0000 From: Richard Tector <richardtector@thekeelecentre.com> To: pf4freebsd@freelists.org, Max Laier <max@love2party.net> Subject: [pf4freebsd] Re: pf 3.5 + ALTQ import / Looking for beta testers and altq drivers Message-ID: <1084981332.40ab8054b3e40@webmail.thekeelecentre.com> In-Reply-To: <200405190216.16204.max@love2party.net> References: <200405190216.16204.max@love2party.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Quoting Max Laier <max@love2party.net>: > Hello, >=20 > http://people.freebsd.org/~mlaier/ has an import of the OpenBSD 3.5 pf > sources=20 > (OPENBSD_3_5_BASE, stable imports will follow later). To build this you= need >=20 > a recent -current source tree. Just apply the patch and copy over the o= ther=20 > files. After this you should be ready for a build{world, kernel}. If yo= u do=20 > not want to do a full buildworld, make sure to update (at least) pfctl(= 8) and >=20 > authpf(8). You might also want to update ifconfig(8) and kdump(1). >=20 > This comes bundled with latest ALTQ sources from KAME, providing "pf_mo= de"=20 > only (i.e. no support of /dev/altq). This makes the locking really easy= and=20 > keeps the impact of ALTQ to the tree very small (i.e. no classifier hoo= ks=20 > etc). >=20 > The ALTQ-enabled driver set is very limited at the moment as I'd like t= o=20 > import only well-tested drivers to this patchset anticipating a possibl= e=20 > import into the tree. >=20 > The pf import is a bit different in respect to the interface handling. = As=20 > FreeBSD allows network interfaces to be renamed at runtime I had to int= roduce >=20 > a special group for interfaces that have not yet been seen. Just to exp= lain=20 > what this "notyet" group is all about and what "(placeholder)" means. O= ther=20 > than this, there should be no noticable difference between Open- and > FreeBSD. >=20 > Please test this stuff if you have time/resources at hand and possibly=20 > feedback drivers after a reasonable time of testing. It should be able = to=20 > apply the driver patch from the rofug.ro patchset in most cases, if you= run=20 > into troubles - let me know. >=20 > Note that this is really a BETA patch. It works great for me on two rou= ters, >=20 > my desktop and laptop, but that does not mean anything. It is also miss= ing=20 > some glue in regards to pfsync(4) (which is kinda pointless w/o carp[1]= =20 > anyways) and other minor tweaks that make up a proper import. If you ru= n into >=20 > anything let me know! (w/ or w/o patches to fix it). >=20 > Okay ... this is a bit of a disordered mess, but I think you get the po= int. I >=20 > am in Canada at the moment and will not be very available until monday,= but I >=20 > just had to send this out ... finally. >=20 > [1] There is an old patchset available to import this. Pick up from the= re or >=20 > fund me to finish it ;) >=20 > P.S.: There is also this "jailed.patch". If you have an application for= it,=20 > please give it a try (discription is on the site) and let me know what = you=20 > think about it. >=20 > --=20 > Best regards, | mlaier@freebsd.org > Max Laier | ICQ #67774661 > http://pf4freebsd.love2party.net/ | mlaier@EFnet >=20 >=20 Excellent work with pf, thank you and please keep it up. However, I was wondering if you had any plan to support the ste driver an= y time soon. The routers I run generally have 2 or 3, 4port ethernet cards that = use the ste driver and it would be very helpful to test out performance with = altq on these systems under freebsd. Kind regards, Richard Tector CAPL Ltd. ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1084981332.40ab8054b3e40>