From: Erich Weiler <weiler@soe.ucsc.edu>
To: Pascal Hambourg <pascal.mail@plouf.fr.eu.org>
Cc: netfilter@vger.kernel.org
Subject: Re: IPTABLES port forwarding woes
Date: Fri, 30 May 2008 08:17:45 -0700 [thread overview]
Message-ID: <48401A99.70408@soe.ucsc.edu> (raw)
In-Reply-To: <4840124D.2000303@plouf.fr.eu.org>
Hmmm.. Follow up question to this. How would the outgoing connection
back to the internet find it's way back to the remote internet host, if
the source address was re-written to machine 1 when in came in to begin
with? Wouldn't the original remote internet source address be lost in
all the translation?
Thanks for your insight by the way!
-erich
Pascal Hambourg wrote:
> Erich Weiler a écrit :
>>
>> Ah, I forgot to mention, machine 2 is on a private network that is not
>> routed in any way. So, there is no default gateway for machine 2...
>> That's why I was thinking the source port would have to be re-written
>> internally such that machine 2 would know to send it back through
>> machine 1 and then on to the internet... ?
>
> Then indeed you need to SNAT the forwarded connection. Also make sure
> that machine 1 has IP forwarding enabled.
> --
> To unsubscribe from this list: send the line "unsubscribe netfilter" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2008-05-30 15:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-30 14:02 IPTABLES port forwarding woes Erich Weiler
2008-05-30 14:42 ` Pascal Hambourg
2008-05-30 15:17 ` Erich Weiler [this message]
2008-05-30 19:11 ` Pascal Hambourg
2008-05-30 21:06 ` Erich Weiler
-- strict thread matches above, loose matches on Subject: below --
2008-05-30 13:24 Erich Weiler
2008-05-30 13:53 ` Pascal Hambourg
2008-05-30 13:15 Erich Weiler
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=48401A99.70408@soe.ucsc.edu \
--to=weiler@soe.ucsc.edu \
--cc=netfilter@vger.kernel.org \
--cc=pascal.mail@plouf.fr.eu.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