From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] u32 filter and NAT
Date: Fri, 30 May 2003 12:56:56 +0000 [thread overview]
Message-ID: <marc-lartc-105429948412486@msgid-missing> (raw)
In-Reply-To: <marc-lartc-105421301800663@msgid-missing>
On Thursday 29 May 2003 14:55, Szymon Miotk wrote:
> I want to limit each user in my network to have limited bandwidth (let's
> say 256/128 kbit).
> I use NAT (done with iptables).
> Can I limit users on the outgoing interface using u32 using rules like:
>
> tc filter add dev eth0 parent 1: protocol ip prio 17 u32 match ip src
> 10.10.10.10 flowid 1:10
>
> It seem I made a mistake somewhere or NAT is done before routing and I
> must use iptables mangling.
The src address is indeed rewritten. So you have to mark the packets with
iptables before natting and use that mark with the fw filter.
> BTW what is the maximum for --set-mark ?
Mark is 32 or so, so you can go pretty high.
Stef
--
stef.coene@docum.org
"Using Linux as bandwidth manager"
http://www.docum.org/
#lartc @ irc.oftc.net
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2003-05-30 12:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-29 12:55 [LARTC] u32 filter and NAT Szymon Miotk
2003-05-30 12:56 ` Stef Coene [this message]
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-105429948412486@msgid-missing \
--to=stef.coene@docum.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.