From: Martin Devera <devik@cdi.cz>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] A tc htb/iptables rate control script for ADSL
Date: Wed, 17 Apr 2002 16:09:53 +0000 [thread overview]
Message-ID: <marc-lartc-101905989016864@msgid-missing> (raw)
In-Reply-To: <marc-lartc-101900137903338@msgid-missing>
> Is this documented anywhere? How/why does it work?
I don't think so (docs). But yes it is fw's feature. I found it
in cls_fw.c code - it is commented/described here.
> I gather that the mark is interpreted as 16 bits of parent and 16 bits
> of class. But you couldn't you also have said something like this?
> iptables -t mangle -A to-dsl -p tcp --dport 80 -j MARK --set-mark 0x10010
> /sbin/tc filter add dev ppp0 parent 1: protocol ip prio 1
> handle 10 fw classid 1:20
> ** ****
> Would that just not work?
No. The trick above works ONLY when mark = qdisc:classid AND fw filter
has NO children (no classid terms).
devik
_______________________________________________
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-04-17 16:09 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-16 23:50 [LARTC] A tc htb/iptables rate control script for ADSL alex
2002-04-17 8:34 ` Martin Devera
2002-04-17 9:07 ` Alex Bennee
2002-04-17 9:33 ` Martin Devera
2002-04-17 12:46 ` Stef Coene
2002-04-17 12:54 ` Martin Devera
2002-04-17 13:10 ` Stef Coene
2002-04-17 13:43 ` Alex Bennee
2002-04-17 13:46 ` Martin Devera
2002-04-17 13:50 ` Stef Coene
2002-04-17 15:57 ` Don Cohen
2002-04-17 16:03 ` Martin Devera
2002-04-17 16:09 ` Martin Devera [this message]
2002-04-17 16:42 ` Jonas Lindqvist
2002-04-17 21:25 ` Nils Lichtenfeld
2002-04-17 21:27 ` Martin Devera
2002-04-17 21:30 ` Nils Lichtenfeld
2002-04-17 21:48 ` Nils Lichtenfeld
2002-04-19 8:32 ` Martin Devera
2002-04-26 13:31 ` Nils Lichtenfeld
2002-04-26 14:43 ` Martin Devera
2002-04-27 16:05 ` Nils Lichtenfeld
2002-04-27 16:06 ` Martin Devera
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-101905989016864@msgid-missing \
--to=devik@cdi.cz \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox