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@xxxxxxxxxxxxxxx
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
