From: "Brian J. Murrell" <brian@interlinx.bc.ca>
To: lartc@vger.kernel.org
Subject: [LARTC] inspecting what's going in a class
Date: Mon, 05 Dec 2005 05:52:10 +0000 [thread overview]
Message-ID: <1133761932.15937.58.camel@pc.local> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 695 bytes --]
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.
--
My other computer is your Microsoft Windows server.
Brian J. Murrell
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
[-- Attachment #2: Type: text/plain, Size: 143 bytes --]
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
next reply other threads:[~2005-12-05 5:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-05 5:52 Brian J. Murrell [this message]
2005-12-05 5:59 ` [LARTC] inspecting what's going in a class Jason Boxman
2005-12-05 15:04 ` Ethy H. Brito
2005-12-07 10:43 ` Ethy H. Brito
2005-12-07 15:11 ` gypsy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1133761932.15937.58.camel@pc.local \
--to=brian@interlinx.bc.ca \
--cc=lartc@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.