All of lore.kernel.org
 help / color / mirror / Atom feed
* [LARTC] about default filter command
@ 2007-07-24  1:36 Vincent Dautremont
  2007-07-26 11:55 ` Georgi Alexandrov
  2007-07-27 10:30 ` Andy Furniss
  0 siblings, 2 replies; 3+ messages in thread
From: Vincent Dautremont @ 2007-07-24  1:36 UTC (permalink / raw)
  To: lartc


[-- Attachment #1.1: Type: text/plain, Size: 1472 bytes --]

Hi,
here I have another newcomer question :-)
in the section 9.6.1 of this how too
http://tldp.org/HOWTO/Adv-Routing-HOWTO/lartc.qdisc.filters.html
we can read commands about filters :
------------------------------------------

# tc filter add dev eth0 protocol ip parent 10: prio 1 u32 match \
   ip dport 22 0xffff flowid 10:1
# tc filter add dev eth0 protocol ip parent 10: prio 1 u32 match \
   ip sport 80 0xffff flowid 10:1
# tc filter add dev eth0 protocol ip parent 10: prio 2 flowid 10:2
What does this say? It says: attach to eth0, node 10: a priority 1  
u32 filter that matches on IP destination port 22 *exactly* and send  
it to band 10:1. And it then repeats the same for source port 80. The  
last command says that anything unmatched so far should go to band  
10:2, the next-highest priority.

------------------------------------------

i try to do this at home as i want my ssh traffic prioritary to other  
traffic but the problem is with the last command ! it simply don't  
work. The last command that says default trafic goes to prio 2  
doesn't work

# tc filter add dev eth0 protocol ip parent 10: prio 2 flowid 10:2

just give me the error: "Unknown filter flowid, hence option 1:2 is  
unparsable"

So I don't get what do I must do in order to say that the default  
trafic goes on priority 2 of the prio filter

is this how too always valid with the current version of tc ? did i  
do something wrong ?

Thank you for your help.



Vincent.


[-- Attachment #1.2: Type: text/html, Size: 4142 bytes --]

[-- Attachment #2: Type: text/plain, Size: 143 bytes --]

_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [LARTC] about default filter command
  2007-07-24  1:36 [LARTC] about default filter command Vincent Dautremont
@ 2007-07-26 11:55 ` Georgi Alexandrov
  2007-07-27 10:30 ` Andy Furniss
  1 sibling, 0 replies; 3+ messages in thread
From: Georgi Alexandrov @ 2007-07-26 11:55 UTC (permalink / raw)
  To: lartc


[-- Attachment #1.1: Type: text/plain, Size: 1792 bytes --]

Vincent Dautremont wrote:
> Hi,
> here I have another newcomer question :-)
> in the section 9.6.1 of this how too 
> http://tldp.org/HOWTO/Adv-Routing-HOWTO/lartc.qdisc.filters.html
> we can read commands about filters :
> ------------------------------------------
> 
> # tc filter add dev eth0 protocol ip parent 10: prio 1 u32 match \ 
>   ip dport 22 0xffff flowid 10:1
> # tc filter add dev eth0 protocol ip parent 10: prio 1 u32 match \
>   ip sport 80 0xffff flowid 10:1
> # tc filter add dev eth0 protocol ip parent 10: prio 2 flowid 10:2
> 
> What does this say? It says: attach to eth0, node 10: a priority 1 u32
> filter that matches on IP destination port 22 *exactly* and send it to
> band 10:1. And it then repeats the same for source port 80. The last
> command says that anything unmatched so far should go to band 10:2, the
> next-highest priority.
> 
> ------------------------------------------
> 
> i try to do this at home as i want my ssh traffic prioritary to other
> traffic but the problem is with the last command ! it simply don't work.
> The last command that says default trafic goes to prio 2 doesn't work
> 
> # tc filter add dev eth0 protocol ip parent 10: prio 2 flowid 10:2
> 
> just give me the error: "Unknown filter flowid, hence option 1:2 is
> unparsable"
> 
> So I don't get what do I must do in order to say that the default trafic
> goes on priority 2 of the prio filter
> 
> is this how too always valid with the current version of tc ? did i do
> something wrong ?
> 
> Thank you for your help.
<snip>

You should have posted *all* your tc rules.

-- 
regards,
Georgi Alexandrov

key server - pgp.mit.edu :: key id - 0x37B4B3EE
Key fingerprint = E429 BF93 FA67 44E9 B7D4  F89E F990 01C1 37B4 B3EE


[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

[-- Attachment #2: Type: text/plain, Size: 143 bytes --]

_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [LARTC] about default filter command
  2007-07-24  1:36 [LARTC] about default filter command Vincent Dautremont
  2007-07-26 11:55 ` Georgi Alexandrov
@ 2007-07-27 10:30 ` Andy Furniss
  1 sibling, 0 replies; 3+ messages in thread
From: Andy Furniss @ 2007-07-27 10:30 UTC (permalink / raw)
  To: lartc

Vincent Dautremont wrote:


> # tc filter add dev eth0 protocol ip parent 10: prio 2 flowid 10:2
> 
> just give me the error: "Unknown filter flowid, hence option 1:2 is 
> unparsable"

I am not sure if that ever worked or not - I use

tc filter add dev eth0 protocol ip parent 10: prio 2 u32 match u32 0 0 
flowid 10:2

which should catch all unclassified ip traffic.

When you put prio on root there is often a further buffer that has to 
fill before anything happens. Also arp goes to 1:2 unless you filter it 
elsewhere.

Andy.


_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2007-07-27 10:30 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2007-07-24  1:36 [LARTC] about default filter command Vincent Dautremont
2007-07-26 11:55 ` Georgi Alexandrov
2007-07-27 10:30 ` Andy Furniss

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.