From: Nick Drage <nickd@metastasis.org.uk>
To: netfilter@lists.netfilter.org
Subject: Re: Port Forwarding with iptables
Date: Fri, 20 Aug 2004 11:15:57 +0100 [thread overview]
Message-ID: <20040820101557.GI4818@metastasis.org.uk> (raw)
In-Reply-To: <4125CD2E.7000108@digitalview.com>
On Fri, Aug 20, 2004 at 06:06:38PM +0800, Wilson Mak wrote:
> Nick Drage wrote:
Excuse the short answer...
> Thanks for all who help on this issue. I mis-type the rule here. Yes
> you guys are right, the rule should be: -d 10.1.0.12. But still it
> doesn't work. Do I need to enable something in the kernel when using
> Port-Forwarding?
Try:
echo 1 > /proc/sys/net/ipv4/ip_forward
If you google for that you should find an explanation :)
--
"I think a church with a lightning rod shows a decided lack of confidence"
next prev parent reply other threads:[~2004-08-20 10:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-19 10:57 Port Forwarding with iptables Wilson Mak
2004-08-19 11:15 ` George Alexandru Dragoi
2004-08-19 11:22 ` Nick Drage
2004-08-20 10:06 ` Wilson Mak
2004-08-20 10:15 ` Nick Drage [this message]
2004-08-23 3:04 ` Wilson Mak
2004-08-19 16:39 ` Alejandro Flores
-- strict thread matches above, loose matches on Subject: below --
2004-08-19 11:13 Jason Opperisano
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=20040820101557.GI4818@metastasis.org.uk \
--to=nickd@metastasis.org.uk \
--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