From: "Akos Szalkai" <szalkai@2fkft.com>
To: netfilter@lists.netfilter.org
Subject: mangle after nat in the postrouting chain
Date: Fri, 28 Nov 2003 18:33:50 +0100 [thread overview]
Message-ID: <20031128173350.GJ5232@2fkft.com> (raw)
Hello,
is there any kind of patch (or even consideration to create one) for
packet mangling in the POSTROUTING chain after NAT? (At least as far as
I see, right now it's mangle first, then NAT.) I can also see the
advantages of mangle before NAT, so perhaps the ideal solution would be
mangling twice on the POSTROUTING chain, if it is possible.
The situation where I would find mangling after NAT very handy is the
following. I have two independent internet connections, and a few NAT
rules which eventually decide the source address of the outgoing packet.
And only now, knowing the source address is it possible to route the
packet correctly. Since we are way after routing here, only mangle
could help.
Please correct me if I am not understanding things correctly.
Akos
--
Akos Szalkai <szalkai@2f.hu>
IT Consultant, CISA
2F 2000 Szamitastechnikai es Szolgaltato Kft.
Tel: (+36-1)-4887700 Fax: (+36-1)-4887709 WWW: http://www.2f.hu/
next reply other threads:[~2003-11-28 17:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-28 17:33 Akos Szalkai [this message]
2003-11-28 17:55 ` mangle after nat in the postrouting chain Jeffrey Laramie
-- strict thread matches above, loose matches on Subject: below --
2003-11-28 17:50 Daniel Chemko
2003-11-28 18:13 ` Akos Szalkai
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=20031128173350.GJ5232@2fkft.com \
--to=szalkai@2fkft.com \
--cc=netfilter@lists.netfilter.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.