From: Patrick McHardy <kaber@trash.net>
To: Henrik Nordstrom <hno@marasystems.com>
Cc: Srinivasa Hebbar <sshebbar@yahoo.com>,
netfilter-devel@lists.netfilter.org
Subject: Re: NAT & FORWARDING
Date: Fri, 30 Jan 2004 16:52:06 +0100 [thread overview]
Message-ID: <401A7DA6.2050207@trash.net> (raw)
In-Reply-To: <Pine.LNX.4.44.0401301635121.9279-100000@filer.marasystems.com>
Henrik Nordstrom wrote:
> On Thu, 29 Jan 2004, Srinivasa Hebbar wrote:
>
>
>>I have a situation that if the dest. IP address of the packet is
>>for the local node, then apply NAT rule, otherwise it should simply
>>forward the packet according to the routing table.
>>
>>How can I achieve the above?
>
>
> You need to know which addresses are local. Other than this it is just to
> do it. DNAT is done in PREROUTING and can change the destination freely.
The addrtype match was written out of a similar need, it matches
what routing thinks of an address. It can be found in
patch-o-matic/extra.
Best regards,
Patrick
>
> If you want to be able to NAT sessions initiated by the local node then
> you need to enable NAT of local sessions in the kernel build.
>
> Regards
> Henrik
>
next prev parent reply other threads:[~2004-01-30 15:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-29 14:23 NAT & FORWARDING Srinivasa Hebbar
2004-01-30 0:28 ` John A. Sullivan III
2004-01-30 4:50 ` Srinivasa Hebbar
2004-01-30 5:35 ` John A. Sullivan III
2004-01-31 9:30 ` Henrik Nordstrom
2004-01-30 15:40 ` Henrik Nordstrom
2004-01-30 15:52 ` Patrick McHardy [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-03-15 6:35 NAT & forwarding Alexander Newald
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=401A7DA6.2050207@trash.net \
--to=kaber@trash.net \
--cc=hno@marasystems.com \
--cc=netfilter-devel@lists.netfilter.org \
--cc=sshebbar@yahoo.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 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.