From: "Peter V. Saveliev" <peet@altlinux.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] trouble when using IPMARK module
Date: Mon, 24 Sep 2007 12:17:20 +0000 [thread overview]
Message-ID: <200709241617.20483.peet@altlinux.org> (raw)
In-Reply-To: <0JOV0014XDDSON@mail.fudan.edu.cn>
В сообщении от Monday 24 September 2007 15:07:28 yang,fang написал(а):
> Hello,
>
>
>
> I am trying to use iptables together with tc
>
> I need to use IPMARK module of iptables, but I got a strange error after I
> run 'iptables -t mangle -A POSTROUTING -o eth0 -j IPMARK --addr=dst
> --and-mask=0xffff --or-mask=0x1000'
>
> The command is copied from iptables manual itself (of course interface
> changed)
>
> I only got " iptables v1.3.5: Unknown arg `--addr=dst'
>
<skip />
I think, your iptables just does not have IPMARK extension, which was cleaned
from pom tree. You can check it with shell command:
$ ls -l /lib/iptables/ | grep IPMARK || echo no IPMARK found
If you still want to have separate buckets for every destination IP and do not
want to build iptables extension by yourself, you can use tc filter with
hashing.
I have a ip/tc management tool, which can build such solutions with simple
configs like that:
!
egress htb
rate 100Mbit
!
class-factory 10.0.0.0/24
rate 64Kbit
class-factory 10.0.1.0/24
rate 128Kbit
But I wrote no English documentation yet. If there is need for such tool and
there will be anyone to proofread very-bad-English docs, I can try to write
it.
--
Peter V. Saveliev
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
next prev parent reply other threads:[~2007-09-24 12:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-24 11:07 [LARTC] trouble when using IPMARK module yang,fang
2007-09-24 12:17 ` Peter V. Saveliev [this message]
2007-09-24 13:44 ` Mohan Sundaram
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=200709241617.20483.peet@altlinux.org \
--to=peet@altlinux.org \
--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.