All of lore.kernel.org
 help / color / mirror / Atom feed
From: svavar@atom01.is
To: netfilter@lists.netfilter.org
Subject: Passive FTP Problem in NAT.
Date: Wed, 15 Sep 2004 15:13:24 +0000 (GMT)	[thread overview]
Message-ID: <1095261204.9082@wormhole.atom.is> (raw)

[-- Attachment #1: Type: text/plain, Size: 1217 bytes --]

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

             reply	other threads:[~2004-09-15 15:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-15 15:13 svavar [this message]
2004-09-15 15:39 ` Passive FTP Problem in NAT Aleksandar Milivojevic
2004-09-15 15:43 ` Jason Opperisano
  -- 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=1095261204.9082@wormhole.atom.is \
    --to=svavar@atom01.is \
    --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 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.