From: George Lefter <george.lefter@it-solutions.ro>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] why all goes to default!!
Date: Tue, 18 Nov 2003 16:35:35 +0000 [thread overview]
Message-ID: <marc-lartc-106917347423606@msgid-missing> (raw)
In-Reply-To: <marc-lartc-106917209721515@msgid-missing>
Hi,
I had a similar problem. My conclusion was that u32 match ip dst does
not work in 2.4.22.
Do you use 2.4.22? If so, try upgrade to 2.4.23-rc1 if you can..
raptor wrote:
>Hi,
>
>I have config like this ,... but all traffic goes to the default class 1:4, WHY ?
>What I' doing wrong... filters are attached to the root !
>
>tc qdisc add dev eth0 handle 1:0 root htb default 4
>
> tc class add dev eth0 parent 1:0 classid 1:4 htb rate 55kbit ceil 55kbit prio 7 <--default class
>
> tc class add dev eth0 parent 1:0 classid 1:1 htb rate 20Mbit
> tc qdisc add dev eth0 handle 2:0 parent 1:1 htb
>
> tc class add dev eth0 parent 2:0 classid 2:3 htb rate 30kbit ceil 30kbit
> tc qdisc add dev eth0 handle 3:0 parent 2:3 sfq
> tc filter add dev eth0 parent 1:0 protocol ip prio 2 u32 match ip dst x.x.x.X classid 2:3
>
> tc class add dev eth0 parent 2:0 classid 2:5 htb rate 30kbit ceil 30kbit
> tc qdisc add dev eth0 handle 4:0 parent 2:5 sfq
> tc filter add dev eth0 parent 1:0 protocol ip prio 2 u32 match ip dst x.x.x.X classid 2:5
> tc filter add dev eth0 parent 1:0 protocol ip prio 2 u32 match ip dst x.x.x.X classid 2:5
>
>...... and many like this
>_______________________________________________
>LARTC mailing list / LARTC@mailman.ds9a.nl
>http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
>
>
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2003-11-18 16:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-18 15:43 [LARTC] why all goes to default!! raptor
2003-11-18 16:35 ` George Lefter [this message]
2003-11-18 18:34 ` Chijioke Kalu
2003-11-18 21:15 ` raptor
2003-11-19 8:18 ` Cezar Atanasiu
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=marc-lartc-106917347423606@msgid-missing \
--to=george.lefter@it-solutions.ro \
--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.