From: Jakob Praher <jpraher@yahoo.de>
To: netfilter@lists.netfilter.org
Subject: portforwarding and masquerding - possible?
Date: 21 Nov 2002 17:16:30 +0100 [thread overview]
Message-ID: <1037895394.1302.15.camel@jaques2> (raw)
hi all,
first of all: iptables is really great.
please email me to this address: jpraher@yahoo.de, since I am not a
member of this list.
I have the following scenario:
* firewall
* internal web server
the firewall has the public address of the server and forwards only port
80 to the server on the internal address.
now for the internal server, I still want to be able to download things
from the web, so I decided to do masquerading for ther internal server.
but somehow the internal server can't connect to external sites, that
means it does not receive any answers. (this might be, as I have a tight
forwarding policy between the nets )
my questions are:
* is there a problem when doing DNAT and SNAT for the same host?
* is the following right:
the firewalls forward chain gets the SNATTED request as an internal one
(since SNAT happends at postrouting ? ) - but how does it get the
results back, does the POSTROUTING change the incoming (the answer to an
SNATted ) packet before it get's in the forward queue?
to illustrate it:
outgoing packet:
dest addr: a.b.c.d
source addr: 10.1.1.100
1) forward
nothing changed (routing deciscion is made with 10.1.1.100)
2) postrouting
dest addr: a.b.c.d
source addr: MASQUERADED
incoming request
source addr: a.b.c.d
dest addr: MASQUERADED
*** when is it written back to 10.1.1.100 ** ?
*** does the forward quere see MASQUERADED or 10.1.1.100 ***
this is important for me, as I have to know what I should allow in the
forward chain to allow MASQUERADING ...
thanks
-- Jakob
reply other threads:[~2002-11-21 16:16 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1037895394.1302.15.camel@jaques2 \
--to=jpraher@yahoo.de \
--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.