From: Jason Opperisano <opie@817west.com>
To: netfilter@lists.netfilter.org
Subject: Re: FTP Forwarding
Date: Fri, 14 Jan 2005 09:27:30 -0500 [thread overview]
Message-ID: <1105712849.3661.24.camel@hubcap.ljm.dom> (raw)
In-Reply-To: <008c01c4fa2d$92edd930$051ea8c0@floydian>
On Fri, 2005-01-14 at 06:38, Deepak Seshadri wrote:
> iptables -t nat -A PREROUTING -i $EXT_IF -p tcp -s $PublicIPAdd -d
> 202.147.167.99 \
> --dport 21 -j DNAT --to-destination 192.168.0.5
personally--i don't believe in filtering in NAT. nat in NAT, and filter
in FILTER; that's why they're there. it makes the rule set much easier
to troubleshoot, and it saves you time a year from now when you look at
your rules and can't figure out why you can't FTP to that server from
some random IP address, since the FILTER rule is wide open.
-j
--
"Let us all bask in television's warm glowing warming glow."
--The Simpsons
next prev parent reply other threads:[~2005-01-14 14:27 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-28 17:19 FTP Forwarding umar draz
2004-12-28 17:30 ` Jason Opperisano
2005-01-14 8:57 ` Test Mail
2005-01-14 11:38 ` Deepak Seshadri
2005-01-14 14:27 ` Jason Opperisano [this message]
2005-01-14 14:43 ` Deepak Seshadri
2005-01-14 14:23 ` Jason Opperisano
2005-01-17 7:31 ` TestMail
2005-01-18 16:40 ` Jason Opperisano
-- strict thread matches above, loose matches on Subject: below --
2005-01-18 15:49 Hudson Delbert J Contr 61 CS/SCBN
[not found] <FD8F124A387AD6119F7900A0D218B321541403@hslex01.hslbz.local>
2002-11-22 12:02 ` Rob Sterenborg
2002-11-22 13:02 ` Roy Sigurd Karlsbakk
2002-11-22 10:08 Bantam
2002-11-22 10:24 ` Alexey Sheshka
2002-11-22 10:26 ` Alexey Sheshka
2002-11-22 10:31 ` Stewart Thompson
2002-11-22 10:37 ` Wasim Bashir
2002-11-22 11:08 ` Stewart Thompson
2002-11-22 11:47 ` Wasim Bashir
2002-11-22 10:34 ` Rob Sterenborg
2002-11-22 11:53 ` Erdal Mutlu
2002-11-18 9:47 ftp forwarding Wasim Bashir
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=1105712849.3661.24.camel@hubcap.ljm.dom \
--to=opie@817west.com \
--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