From: "Jet" <yenjet.chan@eglobal.com.my>
To: Cedric Blancher <blancher@cartel-securite.fr>
Cc: netfilter@lists.samba.org
Subject: Re: IP alias and NAT
Date: Wed, 29 Jan 2003 12:04:14 +0800 [thread overview]
Message-ID: <006c01c2c74b$7f1b37c0$0bc8c80a@dolphin> (raw)
In-Reply-To: 1043672915.15779.16.camel@elendil.intranet.cartel-securite.net
Hi,
>
> To get packets NATed as you want them to, they have to reach PREROUTING
> chain on the firewall. That means when access router wants to forward
> theses packets, it must get an ARP reply for their destination IP. If
> NATed IPs were not aliased on firewall, then nobody would answer access
> router's ARP requests, and connections would not get established.
>
I don't totally agree on this. How about POST ROUTING?
>
> The only thing you have to keep in mind is that packets you want to NAT
> have to reach the firewall. As they're not destined to, you have to
> force them a bit ;)
>
Can anyone explain why we don't have to do the same for POSTROUTING?
- Jet
next prev parent reply other threads:[~2003-01-29 4:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-27 11:31 IP alias and NAT Jet
2003-01-27 13:08 ` Cedric Blancher
2003-01-29 4:04 ` Jet [this message]
2003-01-30 2:04 ` Joel Newkirk
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='006c01c2c74b$7f1b37c0$0bc8c80a@dolphin' \
--to=yenjet.chan@eglobal.com.my \
--cc=blancher@cartel-securite.fr \
--cc=netfilter@lists.samba.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox