Skip to contentSkip to conversation

HTB --> fw and u32

LARTC raptor 4 participants 6 messages Nov 12, 2003 – Nov 14, 2003

lore
Share & tools
lore

raptor

author
#0 lore raw

hi,

I have the following problem I have to classify packets based on iptables-mark and on u32 filter... My idea was to set

root-------> classX
|------------------> classY

and then in the root to have a filter that on iptables-mark to direct it to classX, and then in classX to setup u32 filters that further classify the packets.
Then in the root put the same u32 filters. So that (pseudo code):

Quoted 1 line

root

if fwmark = 2 then classid classX
else

    u32 filter1 .....  flowid classY-child1
    u32 filter2 ..... flowid classY-child2
    u32 filter3 ..... flowid classY-child3
Quoted 1 line

classX

    u32 filter1 .....  flowid classX-child1
    u32 filter2 ..... flowid classX-child2
    u32 filter3 ..... flowid classX-child3

Now what I read in the LARTC docs :

9.6. Classifying packets with filters
................
You can't filter a packet 'upwards', by the way. Also, with HTB, you should attach all filters to the root!
......

Now this ruins my idea.... My config will not work with filters attached only on ROOT 'cause the filters are the same. The only difference is the fwmark. But on the other hand there is no way to set in one filter both of these mathces..

How to do what I want ?!
aaa and I can't use iptables only solution.. (meanwhile what is the maximum number of the --set-mark values possible and what is the maximum numbers of classes and qdisc i can use).

_______________________________________________
LARTC mailing list / [email protected]
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

#1 lore raw
Quoted 28 lines · raptor

hi,

I have the following problem I have to classify packets based on iptables-mark and on u32 filter... My idea was to set

root-------> classX

|------------------> classY

and then in the root to have a filter that on iptables-mark to direct it to classX, and then in classX to setup u32 filters that further classify the packets.

Then in the root put the same u32 filters. So that (pseudo code):

Quoted 1 line

root

if fwmark = 2 then classid classX
else

    u32 filter1 .....  flowid classY-child1
    u32 filter2 ..... flowid classY-child2
    u32 filter3 ..... flowid classY-child3
Quoted 1 line

classX

    u32 filter1 .....  flowid classX-child1
    u32 filter2 ..... flowid classX-child2
    u32 filter3 ..... flowid classX-child3
Quoted 6 lines

Now what I read in the LARTC docs :

9.6. Classifying packets with filters
................
You can't filter a packet 'upwards', by the way. Also, with HTB, you should attach all filters to the root! ......

You don't have to attach the filters to the root qdisc with htb. So you can implement your idea.

Stef

Signature · 8 lines
[email protected]
 "Using Linux as bandwidth manager"
     http://www.docum.org/
     #lartc @ irc.openprojects.net

_______________________________________________
LARTC mailing list / [email protected]
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
author
#2 lore raw
In reply to raptor
|> Now what I read in the LARTC docs :
|>
|> 9.6. Classifying packets with filters
|> ................
|> You can't filter a packet 'upwards', by the way. Also, with HTB, you should
|> attach all filters to the root! ......
|You don't have to attach the filters to the root qdisc with htb.  So you can 
|implement your idea.

]- so, the LARTC docs are wrong !?

tia
_______________________________________________
LARTC mailing list / [email protected]
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

#3 lore raw
In reply to raptor

Ehlo!

On śro, 2003-11-12 at 09:26, raptor wrote:

<cut/>

Quoted 5 lines

Now what I read in the LARTC docs :

9.6. Classifying packets with filters
................
You can't filter a packet 'upwards', by the way. Also, with HTB, you

should attach all filters to the root!

Quoted 1 line

......

<cut/>

I've noticed that also. Can anyone explain why I should attach all filters to root when using HTB and what could happen if I don't respect that?

BTW, why there's no "reply-to: [email protected]" in header? I think it would be a good idea. Or maybe I did something wrong?

Greetings

Signature · 3 lines
 --== Jacek "Dino" Bilski ==--  --== Registered Linux User #165468 ==--
    --== [email protected] ==--         --== GG# 3484913 ==--
-= 1024D/5B44CFBE   2228 3F73 A678 81C3 4ABE 2617 C77C AE70 5B44 CFBE =-
#4 lore raw
In reply to raptor
Quoted 11 lines · raptor
|> Now what I read in the LARTC docs :
|>
|> 9.6. Classifying packets with filters
|> ................
|> You can't filter a packet 'upwards', by the way. Also, with HTB, you
|> should attach all filters to the root! ......
|
|You don't have to attach the filters to the root qdisc with htb.  So you
| can implement your idea.

]- so, the LARTC docs are wrong !?

Yes.
I sended a patch to the maintainers.

Stef

Signature · 8 lines
[email protected]
 "Using Linux as bandwidth manager"
     http://www.docum.org/
     #lartc @ irc.openprojects.net

_______________________________________________
LARTC mailing list / [email protected]
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
#5 lore raw
In reply to raptor

Stef posted a reply to that, check previous mail,

He also going to inform the maintainers of lartc document to update it.

and again u dont have to attach it to the root qdisc

see my sample script i posted 3 days ago.

K

_________________________________________________________________
Concerned that messages may bounce because your Hotmail account is over limit? Get Hotmail Extra Storage! http://join.msn.com/?PAGEþatures/es

_______________________________________________
LARTC mailing list / [email protected]
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/