From: Andreas Klauer <Andreas.Klauer@metamorpher.de>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] u32 and iptables do not work together
Date: Sat, 08 Apr 2006 13:37:54 +0000 [thread overview]
Message-ID: <20060408133754.GA26568@EIS> (raw)
In-Reply-To: <4436AEB8.1070300@cnett.com.br>
On Sat, Apr 08, 2006 at 03:18:01PM +0200, Piotr Chytla wrote:
> On Sat, Apr 08, 2006 at 08:21:40AM -0300, Nataniel Klug wrote:
> > I think it worked fine... This is my new script (below the text). I just
> > dont know how can I know if this traffic is relly going to the class I
> > send it... hehehehe... I am marking Skype packages using L7-Filter like
> > this:
> >
> If you want to see packets in class you can use sch_log, quite good
> module, you must attach it to class and you will see every packet
> in this class in tcpdump.
Or, without additional software, and a bit less of information,
you could just have a look at the tc statistics. In case of mixed
classes you can temporarily create an extra class for the packets
you want to test filters on.
If packets go into this class and it's the same number as are marked
by iptables, the classification works.
Regards
Andreas Klauer
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
next prev parent reply other threads:[~2006-04-08 13:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-07 18:26 [LARTC] u32 and iptables do not work together Nataniel Klug
2006-04-07 18:45 ` Andreas Klauer
2006-04-07 19:09 ` Nataniel Klug
2006-04-07 19:54 ` Evgeni Gechev
2006-04-07 21:10 ` Jody Shumaker
2006-04-08 10:03 ` Piotr Chytla
2006-04-08 11:21 ` Nataniel Klug
2006-04-08 13:18 ` Piotr Chytla
2006-04-08 13:37 ` Andreas Klauer [this message]
2006-04-10 16:23 ` Nataniel Klug
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=20060408133754.GA26568@EIS \
--to=andreas.klauer@metamorpher.de \
--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.