From: Arthur Meyer <arthur.meyer@tbz.ch>
To: netfilter@lists.netfilter.org
Subject: Re: Passive FTP Problem in NAT.
Date: Thu, 16 Sep 2004 08:58:18 +0200 [thread overview]
Message-ID: <200409160858.18046.arthur.meyer@tbz.ch> (raw)
In-Reply-To: <84F19A978A20454D96263C93109EE76937CE@telex.atom01.local>
Is the nat-ftp-helper module loades?
insmod ip_nat_ftp
Arthur Meyer
On Wednesday 15 September 2004 16:51, Svavar Örn Eysteinsson 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.
>
> To generate my firewall config I use FwBuilder. I've tried many
> configurations but, I never get the data port to open( e.g. to list a
> directory)
>
> In my configuration I've allowed, and NAT'ed the following services
> to my FTP server located on the DMZ :
>
> FTP = TCP Destination Port : Start : 2121 - End : 2121
> FTP_DATA = TCP Source Port : Start : 20 - End : 20
> Destination : Start : 1024 - End : 65535
>
> I can connect, but cannot list the directories.
>
> p.s. I'm running Proftpd on my FTP server. I have also tried to configure
> the "PassivePorts= 60000 65534" to configure a group of the passive ports.
> But it's the same issue with the directory listening.
>
> Any help would be much appreciated.
>
>
> Best regards to all,
>
> Svavar O
> Reykjavik - Iceland
--
This email was created using 100% recycled electrons.
next prev parent reply other threads:[~2004-09-16 6:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-15 14:51 Passive FTP Problem in NAT Svavar Örn Eysteinsson
2004-09-16 6:58 ` Arthur Meyer [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-09-15 15:13 svavar
2004-09-15 15:39 ` Aleksandar Milivojevic
2004-09-15 15:43 ` 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=200409160858.18046.arthur.meyer@tbz.ch \
--to=arthur.meyer@tbz.ch \
--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