From: Jason Opperisano <opie@817west.com>
To: netfilter@lists.netfilter.org
Subject: Re: Passive FTP Problem in NAT.
Date: Wed, 15 Sep 2004 11:43:50 -0400 [thread overview]
Message-ID: <1095263030.1899.70.camel@wolfpack.ljm.dom> (raw)
In-Reply-To: <1095261204.9082@wormhole.atom.is>
On Wed, 2004-09-15 at 11:13, svavar@atom01.is wrote:
> Hi.
>
> Could someone help me or give me advice regarding NAT on a FTP server located in my DMZ.
>
> This is my setup :
>
> My Firewall(Linux 2.4.22-1) :
> |
> - eth0 = Public Interface (x.x.x.66 / 26 )
> |
> - eth1 = DMZ Interface (172.16.100.254 / 24 )
> |
> - eth2 = My Internal Network ( 192.168.1.1 / 24 )
>
>
> I have a FTP server located on my DMZ Network. The server is listening on a non-standard ftp port. It listens on port : 2121.
bingo. the standard modprobe commands won't work in your situation.
try:
modprobe ip_conntrack_ftp ports=21,2121
modprobe ip_nat_ftp ports=21,2121
to force the helper to watch your specific port.
-j
--
Jason Opperisano <opie@817west.com>
next prev parent reply other threads:[~2004-09-15 15:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-15 15:13 Passive FTP Problem in NAT svavar
2004-09-15 15:39 ` Aleksandar Milivojevic
2004-09-15 15:43 ` Jason Opperisano [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-09-15 14:51 Svavar Örn Eysteinsson
2004-09-16 6:58 ` Arthur Meyer
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=1095263030.1899.70.camel@wolfpack.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