From: Andy Furniss <andy.furniss@dsl.pipex.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Filter question
Date: Fri, 07 Jan 2005 19:59:13 +0000 [thread overview]
Message-ID: <41DEEA11.2070802@dsl.pipex.com> (raw)
In-Reply-To: <41DE8ED1.2090409@pobox.com>
Andre Correa wrote:
>
> Hi guys, I may not have made myself clear in my last message so I'll try
> it easy this time. Maybe someone can send me some help.
>
> I'm trying something like this:
>
>
> # root stuff
> tc qdisc add dev eth0 root handle 1: htb default 2
> tc class add dev eth0 parent 1: classid 1:1 htb rate 50000kbit
> # default class
> tc class add dev eth0 parent 1: classid 1:2 htb rate 2000kbit
>
> # root class for my "garanteed bandwidth" service
> tc class add dev eth0 parent 1: classid 1:3 htb rate 10Mbit
>
> # class for a 1Mbit shared bandwidth
> tc class add dev eth0 parent 1:3 classid 1:1024 htb rate 1Mbit
> # qdisc used to _make my life easier scripting classes numbers_
> tc qdisc add dev eth0 parent 1:1024 handle 1024: htb default 250
> # default class for this second qdisc
> tc class add dev eth0 parent 1024: classid 1024:250 htb rate 32kbit
>
> # each customer gets the following class and filter
> tc class add dev eth0 parent 1024: classid 1024:1 htb rate 256kbit
> tc filter add dev eth0 parent 1: protocol ip prio 1 u32 match ip dst
> xxx.xxx.xxx.xxx/yy flowid 1024:1
>
> # another customer...
> tc class add dev eth0 parent 1024: classid 1024:2 htb rate 256kbit
> tc filter add dev eth0 parent 1: protocol ip prio 1 u32 match ip dst
> www.www.www.www/zzz flowid 1024:2
>
>
> My problem is that this filters are created but they don't send traffic
> to the expected class. All traffic is going to 1:2 (default class). Can
> somebody tell me why?
>
> I apreciate any help, I'm in trouble with this...
>
> tks in advance.
>
> Andre
You've created a double htb like in the simulation example on deviks'
page. You need to filter from the top of the first htb to the second
then filter from there.
Below works for me
Andy.
# root stuff
tc qdisc add dev eth0 root handle 1: htb default 2
tc class add dev eth0 parent 1: classid 1:1 htb rate 50000kbit
# default class
tc class add dev eth0 parent 1: classid 1:2 htb rate 2000kbit
# root class for my "garanteed bandwidth" service
tc class add dev eth0 parent 1: classid 1:3 htb rate 10Mbit
# class for a 1Mbit shared bandwidth
tc class add dev eth0 parent 1:3 classid 1:1024 htb rate 1Mbit
# qdisc used to _make my life easier scripting classes numbers_
tc qdisc add dev eth0 parent 1:1024 handle 1024: htb default 250
# default class for this second qdisc
tc class add dev eth0 parent 1024: classid 1024:250 htb rate 32kbit
tc filter add dev eth0 parent 1: protocol ip prio 1 u32 match ip dst
192.168.0.1 flowid 1:1024
tc filter add dev eth0 parent 1: protocol ip prio 1 u32 match ip dst
192.168.0.2 flowid 1:1024
# each customer gets the following class and filter
tc class add dev eth0 parent 1024: classid 1024:1 htb rate 256kbit
tc filter add dev eth0 parent 1024: protocol ip prio 1 u32 match ip dst
192.168.0.1 flowid 1024:1
# another customer...
tc class add dev eth0 parent 1024: classid 1024:2 htb rate 256kbit
tc filter add dev eth0 parent 1024: protocol ip prio 1 u32 match ip dst
192.168.0.2 flowid 1024:2
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2005-01-07 19:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-07 13:29 [LARTC] Filter question Andre Correa
2005-01-07 19:50 ` Andy Furniss
2005-01-07 19:59 ` Andy Furniss [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-12-06 6:10 Victor Dario Martinez
2002-12-06 16:28 ` Andrea Rossato
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=41DEEA11.2070802@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.