From: Andy Furniss <lists@andyfurniss.entadsl.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] tc u32 match !port
Date: Sat, 05 May 2007 21:38:49 +0000 [thread overview]
Message-ID: <463CF969.6080706@andyfurniss.entadsl.com> (raw)
In-Reply-To: <beb91d720705020336u3eaa87bdo25038b72d06dac53@mail.gmail.com>
Salatiel Filho wrote:
> On 5/5/07, Andy Furniss <lists@andyfurniss.entadsl.com> wrote:
>> Salatiel Filho wrote:
>>
>> > Well , i am having a few troubles making this work.
>> > I have some like this in pseudo tc rulez :)
>> > Root class
>> > Class 1 parent ROOT prio 0 filter u32 match sport 80 dst
>> 10.0.0.254
>> > Class 2 paret ROOT prio 0 filter u32 match dport 22
>> > Class 3 parent ROOT prio 7 filter u32 match dst 10.0.0.254
>> > default
>> >
>> > Shouldn't traffic from source port 80 and destination 10.0.0.254 go
>> > through class 1 ?
>> > I can not make a way to this work, traffic to 10.0.0.254 is always
>> > falling in to class 3 :/
>> > Am i missing something ?
>>
>> prio 1 is the top prio for filters 0 ends up much lower.
>>
>> I think two prio 1s should work in order of entry, but I would use 1 and
>> 2 to be sure. I have seen reverse order of entry if you don't use prio
>> at all ...
>>
>> tc -s filter ls dev $DEV parent X:Y
>>
>> should help you see what's going on.
>>
>> Andy.
>>
>>
>>
>>
>
> Changed to this:
>
> tc qdisc add dev imq1 root handle 1: htb default 5 r2q 1
> tc class add dev imq1 parent 1: classid 1:5 htb rate 8kbit ceil 8kbit
> prio 7 quantum 1500 # DEFAULT
>
> tc class add dev imq1 parent 1: classid 1:2 htb rate 1024kbit ceil
> 1024kbit prio 0 quantum 1500
> tc filter add dev imq1 parent 1: protocol ip prio 1 u32 match ip dst
> 192.168.10.1 match ip sport 80 0xffff flowid 1:2 # FROM HTTP DEST TO
> 192.168.10.1
>
> tc class add dev imq1 parent 1: classid 1:3 htb rate 1024kbit ceil
> 1024kbit prio 0 quantum 1500
> tc class add dev imq1 parent 1:3 classid 1:900 htb rate 1024kbit ceil
> 1024kbit prio 7 quantum 1500
> tc filter add dev imq1 parent 1: protocol ip prio 7 u32 match ip dst
> 192.168.10.1 flowid 1:900 # ANY OTHER TRAFFIC TO 192.168.10.1
>
> But all traffic is still flowing to 1:900 :/
Hmm that should work - as long as imq1 hooks in prerouting and after nat
if it goes to 1:900 and not 1:5 I suppose it is seeing the address OK.
This is ingress traffic and you are downloading from an http server?
The way you have set up htb the classes won't share bandwidth.
What does tc -s filter ls dev imq1 show?
Andy.
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
next prev parent reply other threads:[~2007-05-05 21:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-02 10:36 [LARTC] tc u32 match !port Salatiel Filho
2007-05-02 15:20 ` Alejandro Ramos Encinosa
2007-05-03 12:57 ` Andy Furniss
2007-05-05 17:28 ` Salatiel Filho
2007-05-05 18:56 ` Andy Furniss
2007-05-05 19:21 ` Salatiel Filho
2007-05-05 21:38 ` Andy Furniss [this message]
2007-05-06 3:29 ` Salatiel Filho
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=463CF969.6080706@andyfurniss.entadsl.com \
--to=lists@andyfurniss.entadsl.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.