From: Andy Furniss <andy.furniss@dsl.pipex.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] problems with u32 fiter
Date: Tue, 08 Feb 2005 02:00:48 +0000 [thread overview]
Message-ID: <42081D50.40603@dsl.pipex.com> (raw)
In-Reply-To: <200502061213.30560.listas@pablodanielrey.com.ar>
listas@pablodanielrey.com.ar wrote:
> hello to all
> i'm trying to set a filter but doesn't want to work.
> i've set ut the qdiscs and the classes like this :
>
> tc qdisc add dev ppp0 root handle 1: htb default 20
> tc class add dev ppp0 parent 1: classid 1:1 htb rate 120kbit
> tc class add dev ppp0 parent 1:1 classid 1:20 htb rate 30kbit ceil 120kbit
> tc class add dev ppp0 parent 1:1 classid 1:21 htb rate 30kbit ceil 120kbit
> tc class add dev ppp0 parent 1:1 classid 1:22 htb rate 30kbit ceil 120kbit
> tc class add dev ppp0 parent 1:1 classid 1:23 htb rate 30kbit ceil 120kbit
> tc qdisc add dev ppp0 parent 1:20 handle 20: prio
> tc qdisc add dev ppp0 parent 1:21 handle 21: prio
> tc qdisc add dev ppp0 parent 1:22 handle 22: prio
> tc qdisc add dev ppp0 parent 1:23 handle 23: prio
>
> but when i try to set up the filters :
>
> tc filter add dev ppp0 parent 1:0 prio 1 u32 match ip src 192.168.0.2 flowid 1:23
> tc filter add dev ppp0 parent 1:0 prio 1 u32 match ip src 192.168.2.2 flowid 1:22
> tc filter add dev ppp0 parent 1:0 prio 1 u32 match ip src 192.168.0.1 flowid 1:21
you need protocol ip before u32 eg.
tc filter add dev ppp0 parent 1:0 protocol ip prio 1 u32 match ip src
192.168.0.2 flowid 1:23
Andy.
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2005-02-08 2:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-06 12:13 [LARTC] problems with u32 fiter listas
2005-02-06 17:55 ` George Alexandru Dragoi
2005-02-08 2:00 ` Andy Furniss [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=42081D50.40603@dsl.pipex.com \
--to=andy.furniss@dsl.pipex.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.