From: Ben <bench@silentmedia.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] HTB: Filtering flat out not working :(
Date: Thu, 28 Feb 2002 23:18:43 +0000 [thread overview]
Message-ID: <marc-lartc-101493837626080@msgid-missing> (raw)
In-Reply-To: <marc-lartc-101486681303617@msgid-missing>
I've seen examples like this, but what I'm not clear on is if the filter
handle has to be the same as the fwmark or if the flowid has to be <class
parent>:<fwmark>. Either way seems not right, but nothing else seems to
make sense, based on the examples I've seen.
On Fri, 1 Mar 2002, Viktor Kemmet wrote:
> # Mark Packets according to destination port number
> iptables -I OUTPUT -t mangle -p udp --destination-port 5003 -j MARK --set-mark 3
> iptables -I OUTPUT -t mangle -p udp --destination-port 5002 -j MARK --set-mark 2
> iptables -I OUTPUT -t mangle -p udp --destination-port 5001 -j MARK --set-mark 1
>
> $TC class change $EGDEV classid 1:1 dsmark mask 0x3 \
> value 0xb8
> #becomes AF11
> $TC class change $EGDEV classid 1:2 dsmark mask 0x3 \
> value 0x28
> #becomes AF21
> $TC class change $EGDEV classid 1:3 dsmark mask 0x3 \
> value 0x48
>
> $TC filter add $EGDEV parent 1:0 protocol ip prio 4 handle 1 fw flowid 1:1
> $TC filter add $EGDEV parent 1:0 protocol ip prio 4 handle 2 fw flowid 1:2
> $TC filter add $EGDEV parent 1:0 protocol ip prio 4 handle 3 fw flowid 1:3
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2002-02-28 23:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-28 3:25 [LARTC] HTB: Filtering flat out not working :( Tim Carr
2002-02-28 8:31 ` EGAL Vincent
2002-02-28 8:54 ` Martin Devera
2002-02-28 14:56 ` Tim Carr
2002-02-28 19:45 ` Tim Carr
2002-02-28 23:05 ` Viktor Kemmet
2002-02-28 23:18 ` Ben [this message]
2002-02-28 23:42 ` Viktor Kemmet
2002-02-28 23:59 ` bert hubert
2002-03-01 7:45 ` 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-101493837626080@msgid-missing \
--to=bench@silentmedia.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.