From: Ruben Laban <r.laban@ism.nl>
To: netfilter@lists.netfilter.org
Subject: Re: Port forwarding inside local domain
Date: Tue, 21 Aug 2007 08:57:35 +0200 [thread overview]
Message-ID: <200708210857.35915.r.laban@ism.nl> (raw)
In-Reply-To: <20070820191001.GA23822@bart.bertram-scharpf.homelinux.com>
On Monday 20 August 2007, Bertram Scharpf wrote:
> Am Montag, 20. Aug 2007, 16:34:31 +0200 schrieb Ruben Laban:
> > 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
>
> iptables v1.3.5: Can't use -i with POSTROUTING
>
> > 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
>
> Seems it's "... --ctorigdst 192.168.7.33 -j ...".
Two 'stupid' mistakes indeed. Guess I should've reviewed my own posts a little
more.
> Works fine. Thanks!
Glad it worked out for you afterall.
Regards,
--
Ruben
prev parent reply other threads:[~2007-08-21 6:57 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
2007-08-20 19:10 ` Bertram Scharpf
2007-08-21 6:57 ` Ruben Laban [this message]
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=200708210857.35915.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;
as well as URLs for NNTP newsgroup(s).