From: "John A. Sullivan III" <john.sullivan@nexusmgmt.com>
To: Jason Opperisano <opie@817west.com>
Cc: Netfilter users list <netfilter@lists.netfilter.org>
Subject: Re: Nat before routing decision
Date: Mon, 15 Nov 2004 10:17:31 -0500 [thread overview]
Message-ID: <1100531851.2016.10.camel@localhost> (raw)
In-Reply-To: <1100530284.3405.11.camel@hubcap.ljm.dom>
On Mon, 2004-11-15 at 09:51, Jason Opperisano wrote:
> On Mon, 2004-11-15 at 06:44, thomas.elsaesser@lhsystems.com wrote:
> > Dear all,
> >
> > I need src nat before the packet go to the routing decision.
> > How can i do it.
> >
> > Kind Regards
> >
> > Thomas
>
> well, SNAT is only valid in POSTROUTING of the NAT table. if you need
> to apply alternate routing to a packet and translate it's source, you
> can follow the theory of:
>
> 1) mark packet in PREROUTING of MANGLE
> 2) route based on MARK
> 3) SNAT packet in POSTROUTING of NAT
<snip>
It has been a long time since I worked with it so I don't remember the
details but is the stateless NAT in iproute2 done before routing
decisions? - John
--
John A. Sullivan III
Chief Technology Officer
Nexus Management
+1 207-985-7880
john.sullivan@nexusmgmt.com
---
If you are interested in helping to develop a GPL enterprise class
VPN/Firewall/Security device management console, please visit
http://iscs.sourceforge.net
prev parent reply other threads:[~2004-11-15 15:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-15 11:44 Nat before routing decision thomas.elsaesser
2004-11-15 14:51 ` Jason Opperisano
2004-11-15 15:17 ` John A. Sullivan III [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=1100531851.2016.10.camel@localhost \
--to=john.sullivan@nexusmgmt.com \
--cc=netfilter@lists.netfilter.org \
--cc=opie@817west.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox