From: Wilson Mak <wilson.mak@digitalview.com>
To: Nick Drage <nickd@metastasis.org.uk>
Cc: netfilter@lists.netfilter.org
Subject: Re: Port Forwarding with iptables
Date: Mon, 23 Aug 2004 11:04:21 +0800 [thread overview]
Message-ID: <41295EB5.50204@digitalview.com> (raw)
In-Reply-To: 20040820101557.GI4818@metastasis.org.uk
Nick Drage wrote:
>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 :)
>
>
>
Yap! I did set this bit to 1. Any other stuffs I missed? That's
absolutely weird. It used to work perfectly with ipchains plus
ipmasqadm. Actually, the packets did forward to the internal server ( I
capture the packets with ethereal), but looks like the response packets
can't get through the NAT box.
Thanks,
Wilson
next prev parent reply other threads:[~2004-08-23 3:04 UTC|newest]
Thread overview: 11+ 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
2004-08-23 3:04 ` Wilson Mak [this message]
2004-08-19 16:39 ` Alejandro Flores
-- strict thread matches above, loose matches on Subject: below --
2004-08-19 11:13 Jason Opperisano
2004-09-01 15:47 Port forwarding " KUCKAERTZ Régis - NVISION
2004-09-02 7:24 Martijn Lievaart
[not found] <200409020414.i824Eh7e032212@xanadu.marasystems.com>
2004-09-02 8:28 ` Henrik Nordstrom
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=41295EB5.50204@digitalview.com \
--to=wilson.mak@digitalview.com \
--cc=netfilter@lists.netfilter.org \
--cc=nickd@metastasis.org.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.