From: Flemming Frandsen <ff@nrvissing.net>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] tc filter add ... fw returns RTNETLINK answers:
Date: Fri, 13 Jan 2006 21:45:49 +0000 [thread overview]
Message-ID: <43C81F8D.2010703@nrvissing.net> (raw)
In-Reply-To: <43C429E5.3070007@nrvissing.net>
Jody Shumaker wrote:
> I have never seen anything coming from the mark unless you specify it.
I have.
> I'm honestly not really sure how setting a mark of 0x14806 can
> automatically set it to go to flowid 1:4806.
Because someone wrote it to do that, a mark of 0xdadface will map to
flowid dad:face.
> I'm fairly sure you need
> either a CLASSIFY target, or a tc filter to use the mark to put it in a
> specific classid. Is there something I'm missing here?
I'm pretty sure you are, I have it working here at my end.
The CLASSIFY target of iptables is something I have overlooked, it looks
like it does exactly the same thing except with a slightly different and
less obscure syntax.
I'll change my script to use CLASSIFY in stead, it seems a lot nicer.
> I'm curious
> because you said it's working as it is right now, and would like to know
> if there's something I'm just not familiar with. This then makes me
> wonder, what do you want this command to do? If its erroring an dnot
> doing anything, but as you claim everything is working correctly... then
> what do you need this for?
First the error, it was because I had "handle 1" in there, just like
Andy said.
The trick is that this:
iptables -t mangle -A to-dsl -s $subnet -j MARK --set-mark $mark
... sets a mark that this:
tc filter add dev $uplink parent 1: protocol ip prio 1 fw
... uses to hit this directly:
tc class add dev $uplink parent 1:1 classid $class htb \
ceil $userUpCeil rate $userUpRate burst 15k prio 10
Without any inbetween duplication of information, but so does CLASSIFY,
so I'll just use that later on, thanks.
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
next prev parent reply other threads:[~2006-01-13 21:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-10 21:40 [LARTC] tc filter add ... fw returns RTNETLINK answers: Invalid Flemming Frandsen
2006-01-10 22:21 ` Muthukumar S
2006-01-10 23:19 ` Flemming Frandsen
2006-01-11 0:51 ` Andy Furniss
2006-01-11 0:52 ` Andy Furniss
2006-01-11 11:55 ` [LARTC] tc filter add ... fw returns RTNETLINK answers: Flemming Frandsen
2006-01-12 0:23 ` Andy Furniss
2006-01-13 21:45 ` Flemming Frandsen [this message]
2006-01-13 23:04 ` Jody Shumaker
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=43C81F8D.2010703@nrvissing.net \
--to=ff@nrvissing.net \
--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.