From: Frank v Waveren <fvw.lartc@var.cx>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] filters not doing anything?
Date: Sat, 19 Apr 2003 22:38:04 +0000 [thread overview]
Message-ID: <marc-lartc-105079198018915@msgid-missing> (raw)
In-Reply-To: <marc-lartc-105078585814903@msgid-missing>
On Sat, Apr 19, 2003 at 10:55:53PM +0200, Frank v Waveren wrote:
> tc filter add dev eth1 protocol ip parent 1: prio 2 u32 match u8 0 0x0 at 0 flowid 3:
Perhaps of interest:
Replacing the filter line with:
tc filter add dev $DEV protocol ip parent 1: prio 2 u32 match u8 0 0x0 at 0 flowid 1:1
tc filter add dev $DEV protocol ip parent 1:1 prio 2 u32 match u8 0 0x0 at 0 flowid 2:
will convince the packet to trickle down to 2:.
Adding
tc filter add dev $DEV protocol ip parent 2: prio 2 u32 match u8 0 0x0 at 0 flowid 3:
will not get it down to 3: however.
Also, adding just
tc filter add dev $DEV protocol ip parent 1: prio 2 u32 match u8 0 0x0 at 0 flowid 2:
will _not_ get it down to 2:.
I think this has gotten to the point where kernel versions are
interesting, I'm running 2.4.21-pre5-ac3.
--
Frank v Waveren Fingerprint: 21A7 C7F3
fvw@[var.cx|stack.nl|chello.nl] ICQ#10074100 1FF3 47FF 545C CB53
Public key: hkp://wwwkeys.pgp.net/fvw@var.cx 7BD9 09C0 3AC1 6DF2
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2003-04-19 22:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-19 20:55 [LARTC] filters not doing anything? Frank v Waveren
2003-04-19 22:38 ` Frank v Waveren [this message]
2003-04-20 21:44 ` Stef Coene
2003-04-20 21:56 ` Frank v Waveren
2003-04-20 21:59 ` Stef Coene
2003-04-20 22:12 ` Frank v Waveren
2003-04-21 9:20 ` Stef Coene
2003-04-21 14:04 ` Frank v Waveren
2003-04-21 19:33 ` Stef Coene
2003-04-21 20:19 ` Frank v Waveren
2003-04-22 14:41 ` Stef Coene
2003-04-22 17:25 ` Frank v Waveren
2003-04-22 17:55 ` Stef Coene
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=marc-lartc-105079198018915@msgid-missing \
--to=fvw.lartc@var.cx \
--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.