From: Jason Boxman <jasonb@edseek.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] inspecting what's going in a class
Date: Mon, 05 Dec 2005 05:59:46 +0000 [thread overview]
Message-ID: <200512050059.46480.jasonb@edseek.com> (raw)
In-Reply-To: <1133761932.15937.58.camel@pc.local>
On Monday 05 December 2005 00:52, Brian J. Murrell wrote:
> 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?
I think something was just mentioned earlier in the day / night:
On Sunday 04 December 2005 19:23, Piotr Chytla wrote:
> On Thu, Dec 01, 2005 at 06:45:42PM +0100, Andreas Unterkircher wrote:
> > Good suggestion to use ulog for this. So I could dump the exactly
> > traffic which would run through a class (CLASSIFY)
> > to analyze and extract the necessary data to draw the graphs. So I do
> > not have to parse my class (IP or MAC) out of a
> > full tcpdump stream.
> >
> > Sadly not possible with tc-filter. But perhaps I could do this for tc
> > with Vincent Perrier's sch_spy module.
>
> sch_log is also good for this:
>
> http://kernel.umbrella.ro/net/sch_log/v0.4/sch_log-0.4.tar.gz
>
> /pch
--
Jason Boxman
http://edseek.com/ - Linux and FOSS stuff
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
next prev parent reply other threads:[~2005-12-05 5:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-05 5:52 [LARTC] inspecting what's going in a class Brian J. Murrell
2005-12-05 5:59 ` Jason Boxman [this message]
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=200512050059.46480.jasonb@edseek.com \
--to=jasonb@edseek.com \
--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.