From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Brian J. Murrell" Date: Mon, 05 Dec 2005 05:52:10 +0000 Subject: [LARTC] inspecting what's going in a class Message-Id: <1133761932.15937.58.camel@pc.local> MIME-Version: 1 Content-Type: multipart/mixed; boundary="===============0613632594==" List-Id: To: lartc@vger.kernel.org --===============0613632594== Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-aSm5+qh5bvWrDRqttw/b" --=-aSm5+qh5bvWrDRqttw/b Content-Type: text/plain Content-Transfer-Encoding: quoted-printable Well, things seem to be going really well with tbf, prio and sfq. But I'm a nosey bugger. :-) I'd love to be able to audit what's going through each of the prio bands. The super ideal solution would be to be able to attach tcpdump to each band and see what's going through it with the benefit of tcpdump's filtering so that I can examine and filter and so on just like on an interface. This could be of great benefit to tuning classification rules. Short of that even some kind of logging to a socket or something that I can write a tool to examine, etc. Does anything of the sort exist? b. --=20 My other computer is your Microsoft Windows server. Brian J. Murrell --=-aSm5+qh5bvWrDRqttw/b Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQBDk9WKl3EQlGLyuXARAi01AJ9c4ulKyzfxec1XMmGf6H7589wfwgCeKhXq os8GieugTFSyXbrja5QMQXk= =628/ -----END PGP SIGNATURE----- --=-aSm5+qh5bvWrDRqttw/b-- --===============0613632594== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ LARTC mailing list LARTC@mailman.ds9a.nl http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc --===============0613632594==--