From: Andy Furniss <andy.furniss@dsl.pipex.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] QoS and CLASSIFY
Date: Tue, 31 May 2005 21:30:03 +0000 [thread overview]
Message-ID: <429CD75B.8090004@dsl.pipex.com> (raw)
In-Reply-To: <1117539035.17943.35.camel@pauloric.intranet>
Paulo Ricardo Bruck wrote:
> Hi Guys
>
> After googling a little I couldn't find the correct answer..
>
> When I use :
> tc filter add dev eth0 parent 1:0 protocol ip prio 1 u32 match ip dst
> 192.168.0.11 flowid 1:30 , I can shape traffic to 1:30.( works like a
> charm)
>
> Now instead tc filter I would like to use CLASSIFY as below:
>
> iptables -t mangle -A POSTROUTING -o eth0 -d 192.168.0.5 -j CLASSIFY
> --set-class 1:30
>
> but when I comment tc filter and include iptables -t mangle..CLASSIFY
> nothing works.
>
> Where Am I wrong??
Your rules look OK and a quick test based on them works for me.
You need a recent kernel with classify selected and recent iptables.
I notice you modprobe some stuff - I use modules but don't need to
modprobe anything, this is what autoloads -
sch_sfq 5184 2
sch_htb 15488 1
ipt_CLASSIFY 2176 2
iptable_mangle 2496 1
ip_tables 19728 2 ipt_CLASSIFY,iptable_mangle
You can check counters with
iptables -L POSTROUTING -vnt mangle
tc -s qdisc ls dev eth0
tc -s class ls dev eth0
Andy.
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
prev parent reply other threads:[~2005-05-31 21:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-31 11:30 [LARTC] QoS and CLASSIFY Paulo Ricardo Bruck
2005-05-31 21:30 ` Andy Furniss [this message]
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=429CD75B.8090004@dsl.pipex.com \
--to=andy.furniss@dsl.pipex.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.