Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Martijn Lievaart <m@rtij.nl>
To: Askar Ali Khan <askarali@gmail.com>
Cc: netfilter@lists.netfilter.org
Subject: Re: ftp access problem
Date: Sat, 24 Jul 2004 14:01:34 +0200	[thread overview]
Message-ID: <41024F9E.1060905@rtij.nl> (raw)
In-Reply-To: <a0f69e5040724044591804e0@mail.gmail.com>

Askar Ali Khan wrote:

>Hi Anthony,
> 
>On Sat, 24 Jul 2004 11:22:16 +0100, Antony Stone
><antony@soft-solutions.co.uk> wrote:
>  
>
>>On Saturday 24 July 2004 11:05 am, Askar Ali Khan wrote:
>>
>>    
>>
>>>Hi
>>>
>>>On my router/firewall which acting i am getting problem while anyone
>>>tries to connect to ftp server he connected successfully however when
>>>he types and command for example "ls" ftp server return error "500
>>>Illegal PORT range rejected"
>>>Everything else is working fine.
>>>      
>>>
>>I see you are doing NAT on this firewall.   Do you have the nat_ftp support
>>module loaded or compiled in to your kernel?
>>
>>Without that module, netfilter will not see the PORT commands in the FTP
>>packets, and will not know what to do with the data connection on port 20
>>associated with the control connection onn port 21.
>>    
>>
>#modprobe nat_ftp
>   modprobe: Can't locate module nat_ftp
>  
>

Try ip_nat_ftp instead. Also, don't bother with port 20. Use a RELATED 
rule to let in the data connections. All this is documented in lots of 
howto's, www.netfilter.org is a good place to start.

HTH,
M4





  reply	other threads:[~2004-07-24 12:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-24 10:05 ftp access problem Askar Ali Khan
2004-07-24 10:22 ` Antony Stone
2004-07-24 11:45   ` Askar Ali Khan
2004-07-24 12:01     ` Martijn Lievaart [this message]
2004-07-24 13:00     ` ro0ot
2004-07-24 13:13     ` Antony Stone
2004-07-24 13:28       ` Jeffrey Laramie

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=41024F9E.1060905@rtij.nl \
    --to=m@rtij.nl \
    --cc=askarali@gmail.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