From: Patrick McHardy <kaber@trash.net>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Screening packets within tc-classes
Date: Thu, 01 Dec 2005 11:23:06 +0000 [thread overview]
Message-ID: <438EDD1A.8080709@trash.net> (raw)
In-Reply-To: <20051130.Dqk.80373300@egroupware.netshadow.at>
Andreas Unterkircher wrote:
> Hello list,
>
> I'm currently a bit planless so perhaps someone here could give me a point in
> the right direction.
>
> History: I wrote a shaper web tool (http://shaper.netshadow.at) and now got
> several feature requests if it would be possible to graph "what's going on"
> (this mean per IP address, tcp/udp ports or protocols) in a specific chain. A
> chain represents a specific tc-class. Packets get into this chains via
> tc-filter or iptables MARK.
>
> Currently I'm drawing graphs with data got from the dequeuing counters via tc
> -s class show dev ${IF}. Not the best way - I know - but it was enough till
> yet.
>
> Now the question is - is it possible to get direct access to network packets
> that flow through a specifc tc-class?
>
> I was thinking about iptables and dumping the MARK-value via libpcap. But I
> don't think that this will work because the pcap-filter is attached to the
> device itself before the iptables rules (like the restore-mark) are acting. So
> I guess libpcap will not see this.
No it won't, but its not able to use the netfilter mark anyway. One way
would be to use the ipt action combined with the ULOG target and send
packets to userspace that way.
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
next prev parent reply other threads:[~2005-12-01 11:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-30 10:05 [LARTC] Screening packets within tc-classes Andreas Unterkircher
2005-12-01 11:23 ` Patrick McHardy [this message]
2005-12-01 17:45 ` Andreas Unterkircher
2005-12-02 8:54 ` Patrick McHardy
2005-12-05 0:23 ` Piotr Chytla
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=438EDD1A.8080709@trash.net \
--to=kaber@trash.net \
--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.