From: David Cannings <lists@edeca.net>
To: netfilter@lists.netfilter.org
Subject: Re: martians and portforwarding to 127.0.0.1
Date: Tue, 20 Apr 2004 17:43:13 +0100 [thread overview]
Message-ID: <200404201743.13848.lists@edeca.net> (raw)
In-Reply-To: <20040420163326.32095.qmail@web40706.mail.yahoo.com>
On Tuesday 20 April 2004 17:33, udo wrote:
> $path_iptables -t nat -A PREROUTING -p tcp -i $ext_if
> -s 0/0 -d $ext_ip --dport 222 -j DNAT --to
> 127.0.0.1:22
> How can I make the sshd (attached to loopback) work
> without `martian destination` messages for packets
> destined for port 22?
Please see my lengthly post about this from last month. Due to the way
the martian checking code in the kernel is written, I do not think this
is possible.
http://lists.netfilter.org/pipermail/netfilter/2004-March/051615.html
Hopefully somebody can prove this wrong, I hope that post helps you.
David
next prev parent reply other threads:[~2004-04-20 16:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-20 16:33 martians and portforwarding to 127.0.0.1 udo
2004-04-20 16:42 ` hello german speaking? marc manthey
2004-04-20 16:59 ` Antony Stone
2004-04-20 16:43 ` David Cannings [this message]
2004-04-20 17:00 ` martians and portforwarding to 127.0.0.1 Antony Stone
2004-04-20 17:20 ` Cedric Blancher
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=200404201743.13848.lists@edeca.net \
--to=lists@edeca.net \
--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