From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] double rule
Date: Tue, 13 Aug 2002 16:56:56 +0000 [thread overview]
Message-ID: <marc-lartc-102925785909537@msgid-missing> (raw)
In-Reply-To: <marc-lartc-102925336503123@msgid-missing>
On Tuesday 13 August 2002 17:41, Petre Bandac wrote:
> I want to shape the traffic on the http port and further on shape it if the
> destination ip is on some network I specify
>
> however, only the first rule is applied ... why ?
Because you add both rules to the same parent. When one rule is matched, the
packet is put in the destination class and the other rule is never matched.
Atach the second rule to class 1:11 with option "parent 1:11" and it should
work.
Stef
> #http
> $filtru prio 1 u32 match ip sport 80 0xffff flowid 1:11
> #droop :-)
> $filtru prio 1 u32 match ip src x.x.x.x \
> match ip dst x.x.x.0/24 flowid 1:13
>
> where classes are defined earlier as
>
> $tc class add dev eth0 parent 1:1 classid 1:10 \
> htb rate 32kbit ceil 32kbit
>
> $tc class add dev eth0 parent 1:1 classid 1:11 \
> htb rate 64kbit ceil 64kbit
>
> $tc class add dev eth0 parent 1:1 classid 1:12 \
> htb rate 128kbit ceil 160kbit
>
> $tc class add dev eth0 parent 1:1 classid 1:13 \
> htb rate 100kbit ceil 100kbit
>
> and
>
> filtru="$tc filter add dev eth0 protocol ip \
> parent 1:0"
>
>
> thanks in advance,
>
> petre
--
stef.coene@docum.org
"Using Linux as bandwidth manager"
http://www.docum.org/
#lartc @ irc.oftc.net
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2002-08-13 16:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-13 15:41 [LARTC] double rule Petre Bandac
2002-08-13 16:56 ` Stef Coene [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=marc-lartc-102925785909537@msgid-missing \
--to=stef.coene@docum.org \
--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.