Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Tom - 2Ergo Technical Support <tom.stockton@2ergo.com>
To: netfilter@lists.netfilter.org
Subject: illegal ftp port request / ip_nat_ftp
Date: Fri, 25 Feb 2005 11:01:02 +0000	[thread overview]
Message-ID: <1109329262.1686.16.camel@bobby> (raw)

Hi there,

I'm seeing some funny behaviour on one of my debian woody firewalls.  It
manifests itself when making an active ftp connection from a Snatted
client behind the firewall with the following error

ftp> ls
501 Illegal PORT command
ftp: bind: Address already in use

I have the ip_nat_ftp and ip_conntrack_ftp modules loaded and the
following version of iptables

ii  iptables              1.2.6a-5              IP packet filter administration tools for 2.4.4+ kernels

The firewall is running a custom 2.4.26 kernel.  I also have exactly the
same kernel and version of iptables running on another firewall, however
this does not display the same problems.

I have run ethereal to see what is going on and it appears that the
firewall is modifying the PORT command and sending too many parameters.

ie.

seen on the inside interface of the firewall:

PORT 192,168,1,2,179,133

which is ok

however when seen on the outside interface it appears as:

PORT 10,1,1,2,179,133,133

which has a superfluous '133' parameter

192,168,1,2 - private ip address
10,1,1,2 - public ip address


Any tips / advice / suggestions much appreciated.

Regards

Tom

-- 
Tom - 2Ergo Technical Support <tom.stockton@2ergo.com>



                 reply	other threads:[~2005-02-25 11:01 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1109329262.1686.16.camel@bobby \
    --to=tom.stockton@2ergo.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