LARTC
[Top] [All Lists]

Re: [LARTC] about default filter command

To: Vincent Dautremont <vdautrem@ulb.ac.be>
Subject: Re: [LARTC] about default filter command
From: Georgi Alexandrov <georgi.alexandrov@gmail.com>
Date: Thu, 26 Jul 2007 14:55:12 +0300
Cc: lartc@mailman.ds9a.nl
Delivered-to: sp-com-lists@consult.net
Delivered-to: lartc-list@securepoint.com
Delivered-to: lartc@outpost.ds9a.nl
Dkim-signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:x-enigmail-version:content-type; b=XYX6D7UMYIBaLhr8olWNfXqgnsw3wIwIqwqn8Nxm4ntzVshI8q23gn6JcMe4XUztuPz6S5jDLaWhytdrRq73yvYr7ENB3r0DmZtXBJ8JcDdKUNMyHTYERo2ssSsNLUckTYW4sCLIjCwMra6T2iUkU8Y8JUvUk4zYaItoKBBb1aY=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:x-enigmail-version:content-type; b=AAlyQTCcFFEYG8gECxI8L+M4hpiEgascWOIeCN4FexK7JgQw+Xz6DJwYU2sm3D0EX+Kk6LLsHJMpDILOO99eq5WLqBaqNSQOM92pMzYzIhTX0/ZA3yOyQu/Op+snPpDfdiUrVROdeHyKneeWUdH+wtQrN2VCpBOn4GQFdcs3/GA=
In-reply-to: <5C822E76-E686-499C-B408-90EF00C1494C@ulb.ac.be>
List-archive: <http://mailman.ds9a.nl/pipermail/lartc>
List-help: <mailto:lartc-request@mailman.ds9a.nl?subject=help>
List-id: "Mailinglist of the Linux Advanced Routing &amp; Traffic Control project" <lartc.mailman.ds9a.nl>
List-post: <mailto:lartc@mailman.ds9a.nl>
List-subscribe: <http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc>, <mailto:lartc-request@mailman.ds9a.nl?subject=subscribe>
List-unsubscribe: <http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc>, <mailto:lartc-request@mailman.ds9a.nl?subject=unsubscribe>
References: <5C822E76-E686-499C-B408-90EF00C1494C@ulb.ac.be>
Sender: lartc-bounces@mailman.ds9a.nl
User-agent: Thunderbird 1.5.0.12 (X11/20070604)
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: signature.asc
Description: OpenPGP digital signature

_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
<Prev in Thread] Current Thread [Next in Thread>