Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Michael Gale <michael.gale@utilitran.com>
To: netfilter@lists.netfilter.org
Subject: Re: FTP passive not working
Date: Tue, 13 Apr 2004 14:20:49 -0600	[thread overview]
Message-ID: <20040413142049.71d5a1ef@mgalepc.utilitran.com> (raw)
In-Reply-To: <20040413140848.32857beb@mgalepc.utilitran.com>


Nevermind --- not sure why it is not working --- I was able to get it to work by
setting a port range for passive on the FTP server and then forwarding the port
range to the FTP server.

Michael.

On Tue, 13 Apr 2004 14:08:48 -0600
Michael Gale <michael.gale@utilitran.com> wrote:

> Hi,
> 
> 	The log files from the LOG target show that the OUT interface for
> 	packets
> coming after the passive command is issue to be the exteranl interface, which
> is wrong since all other commands show the out interface as eth1 the internal
> nic.
> 
> Michael.
> 
> 
> On Tue, 13 Apr 2004 13:43:34 -0600
> Michael Gale <michael.gale@utilitran.com> wrote:
> 
> > Hello again,
> > 
> > 	It seems that on tablerule-36 (custom user chain) the --state RELATED
> > 	does not
> > work ?
> > 
> > If I add a rule allowing all traffic it works ?
> > 
> > Michael.
> > 
> > 
> > On Tue, 13 Apr 2004 13:13:36 -0600
> > Michael Gale <michael.gale@utilitran.com> wrote:
> > 
> > > Hello,
> > > 
> > > 	I have all the iptable modules built into the kernel. I also forgot to
> > > 	add the
> > > for the custom tablerule I have allowed all established and related
> > > connections.
> > > 
> > > Michael.
> > > 
> > > 
> > > On Tue, 13 Apr 2004 19:59:53 +0200
> > > Rob Sterenborg <rob@sterenborg.info> wrote:
> > > 
> > > > On Tue, 2004-04-13 at 19:41, Michael Gale wrote:
> > > > > Hello,
> > > > > 	
> > > > > 	I am having trouble getting a FTP connection to work in passive
> > > > > 	mode from
> > > > > behind a firewall.
> > > > 
> > > > ....
> > > > 
> > > > > So all rules with regards to this IP / PC are under one rule.
> > > > > 
> > > > > This setup is working fine for all connections accept passive FTP --
> > > > > it seems the firewall is not forwarding the related data connection to
> > > > > the internal server.
> > > > 
> > > > Did you load the ip_conntrack_ftp and ip_nat_ftp modules ?
> > > > 
> > > > 
> > > > Gr,
> > > > Rob
> > > > 
> > > > 
> > > > 
> > > > 
> > > > 
> > > > 
> > > > 
> > > 
> > > 
> > > -- 
> > > Michael Gale
> > > Network Administrator
> > > Utilitran Corporation
> > > 
> > > 
> > > 
> > > 
> > > 
> > 
> > 
> > -- 
> > Michael Gale
> > Network Administrator
> > Utilitran Corporation
> > 
> > 
> > 
> > 
> > 
> 
> 
> -- 
> Michael Gale
> Network Administrator
> Utilitran Corporation
> 
> 
> 
> 
> 


-- 
Michael Gale
Network Administrator
Utilitran Corporation


  reply	other threads:[~2004-04-13 20:20 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-13 17:41 FTP passive not working Michael Gale
2004-04-13 17:59 ` Rob Sterenborg
2004-04-13 19:13   ` Michael Gale
2004-04-13 19:43     ` Michael Gale
2004-04-13 20:08       ` Michael Gale
2004-04-13 20:20         ` Michael Gale [this message]
2004-04-13 19:37 ` Antony Stone
2004-04-13 19:47   ` Michael Gale
2004-04-13 20:00     ` Antony Stone

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=20040413142049.71d5a1ef@mgalepc.utilitran.com \
    --to=michael.gale@utilitran.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