Subject: new altq API (was Re: Changing the PHY status reporting)
To: Marcin Jessa <lists@yazzy.org>
From: Jeff Rizzo <riz@NetBSD.org>
List: tech-net
Date: 02/19/2006 09:56:58
This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig720713B4634DBD37E3A206BD
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Marcin Jessa wrote:
> On Sat, 18 Feb 2006 18:55:05 +0000
> "Liam J. Foy" <liamfoy@sepulcrum.org> wrote:
>
> =20
>> Just as a side note, CARP is basically now completely working. The
>> last remaining issues have been resolved now.
>> =20
>
> Is this any related to having working pf with ALTQ support in HEAD ?
> Is anyone working on this?
> I can remember people talking on current@ about creating
> an ALTQ API for ipf and pf.
> =20
No, this is entirely orthogonal to pf+altq. I have some interest in it,
but AFAIK no actual work is being done on a new altq api at the present
time.=20
+j
--------------enig720713B4634DBD37E3A206BD
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iQCVAwUBQ/ixbbOuUtxCgar5AQMgmwP+PQiv7P/jyk5S4+yzzSoOi3L3TXXRQ+23
R8zI5qDgu2kuTTrpVPaWS2k0/pmR0cJr+xyBRXq1ktqI6bbNyCdOAJXFi4CR+AR7
umZrfwftmpWYSqyfWNaanJ2GRqI++/duVQa0u8J1aSsdXaYJTuScGZuG9+ep00cR
UMLG2nO0I8E=
=Xy8R
-----END PGP SIGNATURE-----
--------------enig720713B4634DBD37E3A206BD--