Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 28 Jul 1999 12:41:22 +0100
From:      Brian Somers <brian@FreeBSD.org.uk>
To:        Loren Daniel Koss <loren@pciway.com>
Cc:        Brian Somers <brian@Awfulhak.org>, freebsd-questions@FreeBSD.ORG
Subject:   Re: FTP through NATD.. 
Message-ID:  <199907281141.MAA01614@keep.lan.Awfulhak.org>
In-Reply-To: Your message of "Tue, 27 Jul 1999 17:11:03 PDT." <Pine.BSF.4.10.9907271709210.433-100000@unix.pciway.com> 

next in thread | previous in thread | raw e-mail | index | archive | help
Hi,

The only other thing I can think of is that your client may be having 
a problem with the port number from which the back-channel comes.  
You could try the -same_ports switch - it may help, although I belive 
it's the default anyway.

If all else fails, passive mode on the client is probably the best 
thing to aim for :-/

> No, I'm trying to get *in* to a "dodgy" (are you english?) ftp port..
> Actually, I have it exposed to the world as 8002, but internally on my NT
> box it is 6002.  It could very well be 8002 on the internal, but for some
> reason when I tried 6002 on the 216.32.46.218, it failed, so I moved it..
> I Like I said, I can still connect..  I just can't do anything over the
> data connection..  It fails on the PORT command..  What do you think is
> the problem?
> 
> Loren
> 
> On Wed, 28 Jul 1999, Brian Somers wrote:
> 
> > Hmm, I thought you were trying to get *out* to a dodgy ftp port.... I 
> > didn't read your post properly.  You don't need to use passive mode 
> > for this.
> > 
> > Shouldn't your config say something like
> > 
> >   redirect_port tcp 192.168.1.20:6002 216.32.46.218:6002
> > 
> > assuming the incoming packets are addressed to 216.32.46.218 ?  Is 
> > the 8002 below a typo ?
> > 
> > > Okay, I did that and now it just hangs after it connects and tries to do 
> > > a listing of the files.. What should
> > > the NATD.CONF file look like?  I have:
> > > 
> > > redirect_port tcp 192.168.1.20:6002 216.32.46.218:8002
> > > 
> > > It's really weird..
> > > 
> > > Thanks for your help.
> > > 
> > > Loren
> > > 
> > > On Tue, 27 Jul 1999, Brian Somers wrote:
> > > 
> > > > > Brian,
> > > > > do you mean passive mode on the FTP server?  Its a WIN NT box..  Or do you
> > > > > mean passive mode of NATD or something?  Sorry I'm such a newbie..
> > > > 
> > > > Passive mode on the client side.
> > > > 
> > > > Passive mode basically means that the server does not try to open up 
> > > > a second channel back to the client.  The NAT stuff can only handle 
> > > > this sort of thing if it can recognise the ``PORT'' command going out 
> > > > on the original channel (it then prepares itself for the 
> > > > back-connect), but natd only looks for PORT commands on the standard 
> > > > ftp port.
> > > > 
> > > > > On Tue, 27 Jul 1999, Brian Somers wrote:
> > > > > 
> > > > > > 
> > > > > > > I am having a helluva time with this..  I moved the port of my FTP server
> > > > > > > that is behind my FreeBSD box to 6002..  I am able to connect to it from
> > > > > > > the outside just fine, except for doing any LIST, PUT, or GETs..  They get
> > > > > > > me a "INVALID PORT COMMAND"  Does anyone know how to solve this??
> > > > > > 
> > > > > > If you're not using the standard ftp port, you *must* use passive 
> > > > > > mode ftp (otherwise libalias won't detect and fix the port command).
> > > > > > 
> > > > > > Passive mode is enabled in FreeBSD with ``-p''.
> > > > > > 
> > > > > > > Thanks
> > > > > > > Loren
> > > > > > > 
> > > > > > > loren@pciway.com

-- 
Brian <brian@Awfulhak.org>                        <brian@FreeBSD.org>
      <http://www.Awfulhak.org>;                   <brian@OpenBSD.org>
Don't _EVER_ lose your sense of humour !          <brian@FreeBSD.org.uk>




To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199907281141.MAA01614>