From: Andy Furniss <andy.furniss@dsl.pipex.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] IPTables script
Date: Thu, 12 May 2005 20:18:48 +0000 [thread overview]
Message-ID: <4283BA28.3080509@dsl.pipex.com> (raw)
In-Reply-To: <200505121414.56363.lartc-337@ccp.com.au>
Lee Sanders wrote:
>>Ok I thought you were trying to match src addresses, and that would be a
>>problem because of masquerading ;)
>>
>
> yep.
>
So you need to use addresses before nat - just mark them in iptables
postrouting like.
iptables -t mangle -A POSTROUTING --src 192.168.0.2 -j MARK --set-mark 32
then filter them with tc something like -
tc filter add dev $UPIF parent 1:0 prio 4 protocol ip handle 32 fw
flowid 1:32
> On this, can anyone help with: http://lartc.org/howto/lartc.adv-filter.html
>
> 12.1.3. Specific selectors
>
> The following table contains a list of all specific selectors the author of
> this section has found in the tc program source code. They simply make your
> life easier and increase readability of your filter's configuration.
>
> FIXME: table placeholder - the table is in separate file ,,selector.html''
> FIXME: it's also still in Polish :-(
> FIXME: must be sgml'ized
>
> I'm quite happy to read polish to get at the list they are offering.
They may well be outdated now anyway - there is work going on currently
with tc eg. ematches - just not many docs yet.
Andy.
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
prev parent reply other threads:[~2005-05-12 20:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-12 6:14 [LARTC] IPTables script Lee Sanders
2005-05-12 7:40 ` Sylvain BERTRAND
2005-05-12 8:31 ` Alexander Samad
2005-05-12 8:38 ` Sylvain BERTRAND
2005-05-12 8:52 ` Lee Sanders
2005-05-12 9:10 ` Sylvain BERTRAND
2005-05-12 10:42 ` Lee Sanders
2005-05-12 10:47 ` Sylvain BERTRAND
2005-05-12 20:18 ` Andy Furniss [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=4283BA28.3080509@dsl.pipex.com \
--to=andy.furniss@dsl.pipex.com \
--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.