From: Ruben Laban <r.laban@ism.nl>
To: netfilter@lists.netfilter.org
Subject: Re: Port forwarding inside local domain
Date: Mon, 20 Aug 2007 16:34:31 +0200 [thread overview]
Message-ID: <200708201634.31185.r.laban@ism.nl> (raw)
In-Reply-To: <20070820141102.GA19046@bart.bertram-scharpf.homelinux.com>
On Monday 20 August 2007, Bertram Scharpf wrote:
> Hi,
>
> just another question. Let my router be 192.168.7.33 with
> interfaces eth0 and ppp0; then this works perfectly here:
>
> # iptables -t nat -A PREROUTING -i ppp+ -p tcp --dport 80 \
> -j DNAT --to 192.168.7.49:80
>
> However, I want to request from inside my local domain the
> same way. This seems to end in a drop or an infinite loop:
>
> # iptables -t nat -A PREROUTING -d 192.168.7.33 -p tcp --dport 80 \
> -j DNAT --to 192.168.7.49:80
>
> Besides that I want to know what is going wrong here,
You need to 'fix' the reply traffic, by using a rule like:
# iptables -t nat -A POSTROUTING -i eth0 -d 192.168.7.49 -p tcp --dport 80 \
-j SNAT --to 192.168.7.33
With recent kernels this can be done more elegantly by using the conntrack
module:
# iptables -t nat -A POSTROUTING -d 192.168.7.49 -m conntrack --ctorigdst \
192.168.7.49 -j SNAT --to 192.168.7.33
I never used the latter myself due to me working with older kernels mainly.
> I further would like to ask how I could debug this.
tcpdump and/or wireshark is/are your best friend(s).
HTH,
--
Ruben
next prev parent reply other threads:[~2007-08-20 14:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-20 14:11 Port forwarding inside local domain Bertram Scharpf
2007-08-20 14:34 ` Ruben Laban [this message]
2007-08-20 19:10 ` Bertram Scharpf
2007-08-21 6:57 ` Ruben Laban
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=200708201634.31185.r.laban@ism.nl \
--to=r.laban@ism.nl \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox