FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > CentOS > CentOS

 
 
LinkBack Thread Tools
 
Old 08-13-2011, 05:56 PM
Tim Dunphy
 
Default can't list directories in ftp

Hello again, Barry

Yes interestingly enough that seemed to do it for the local test. This is odd, because I remember setting up another ProFTPd server with this directive and never ran into this issue.

Nevertheless, once I commented out the MasqueradeAddress directive it works locally.

[root@LCENT05:~] #/usr/bin/ftp localhost
Connected to localhost (127.0.0.1).
220 FTP Server ready.
Name (localhost:root): bluethundr
331 Password required for bluethundr
Password:
230 User bluethundr logged in
Remote system type is UNIX.
Using binary mode to transfer files.
ftp> ls
227 Entering Passive Mode (127,0,0,1,253,20).
150 Opening ASCII mode data connection for file list
-rw-r--r-- 1 apache apache 36834 Mar 11 2010 Copying
-rw-r--r-- 1 apache apache 266 Jul 9 10:30 How to install Piwik.html
-rw-r--r-- 1 root apache 1189469 Dec 20 2010 Illustration.ai
-rw-r--r-- 1 root apache 236524 Dec 20 2010 Illustration.jpg
-rw-r--r-- 1 root apache 230915 Dec 20 2010 Illustration.pdf
-rw-r--r-- 1 root apache 1206524 Dec 20 2010 Illustration_path.ai
-rw-r--r-- 1 root apache 2176338 Dec 20 2010 Illustration_path.eps

Which is nice! But when I try to connect remotely this is what occurs:

Response: 230 User bluethundr logged in
Command: OPTS UTF8 ON
Response: 200 UTF8 set to on
Status: Connected
Status: Retrieving directory listing...
Command: PWD
Response: 257 "/" is the current directory
Command: TYPE I
Response: 200 Type set to I
Command: PASV
Response: 227 Entering Passive Mode (192,168,1,48,251,255).
Status: Server sent passive reply with unroutable address. Using server address instead.
Command: MLSD
Error: Connection timed out
Error: Failed to retrieve directory listing

So remotely it's still having difficulty listing the directory. Here's a snippet from the logs. I've included a longer section of the logs in case this sheds any light on the issue.

Seriously thanks for your help here, it's greatly appreciated!

Aug 13 12:45:44 LCENT05 proftpd[3095] 192.168.1.48 (xx.xxx.xxx.xxx[xx.xxx.xxx.xxx]): USER bluethundr: Login successful.
Aug 13 12:45:44 LCENT05 proftpd[3095] 192.168.1.48 (xx.xxx.xxx.xxx[xx.xxx.xxx.xxx]): dispatching PRE_CMD command 'OPTS UTF8 ON' to mod_tls
Aug 13 12:45:44 LCENT05 proftpd[3095] 192.168.1.48 (xx.xxx.xxx.xxx[xx.xxx.xxx.xxx]): dispatching PRE_CMD command 'OPTS UTF8 ON' to mod_core
Aug 13 12:45:44 LCENT05 proftpd[3095] 192.168.1.48 (xx.xxx.xxx.xxx[xx.xxx.xxx.xxx]): dispatching PRE_CMD command 'OPTS UTF8 ON' to mod_core
Aug 13 12:45:44 LCENT05 proftpd[3095] 192.168.1.48 (xx.xxx.xxx.xxx[xx.xxx.xxx.xxx]): dispatching CMD command 'OPTS UTF8 ON' to mod_core
Aug 13 12:45:44 LCENT05 proftpd[3095] 192.168.1.48 (xx.xxx.xxx.xxx[xx.xxx.xxx.xxx]): dispatching PRE_CMD command 'OPTS_UTF8 ON' to mod_tls
Aug 13 12:45:44 LCENT05 proftpd[3095] 192.168.1.48 (xx.xxx.xxx.xxx[xx.xxx.xxx.xxx]): dispatching PRE_CMD command 'OPTS_UTF8 ON' to mod_core
Aug 13 12:45:44 LCENT05 proftpd[3095] 192.168.1.48 (xx.xxx.xxx.xxx[xx.xxx.xxx.xxx]): dispatching PRE_CMD command 'OPTS_UTF8 ON' to mod_core
Aug 13 12:45:44 LCENT05 proftpd[3095] 192.168.1.48 (xx.xxx.xxx.xxx[xx.xxx.xxx.xxx]): dispatching CMD command 'OPTS_UTF8 ON' to mod_lang
Aug 13 12:45:44 LCENT05 proftpd[3095] 192.168.1.48 (xx.xxx.xxx.xxx[xx.xxx.xxx.xxx]): dispatching LOG_CMD command 'OPTS_UTF8 ON' to mod_log
Aug 13 12:45:44 LCENT05 proftpd[3095] 192.168.1.48 (xx.xxx.xxx.xxx[xx.xxx.xxx.xxx]): dispatching LOG_CMD command 'OPTS UTF8 ON' to mod_log
Aug 13 12:45:45 LCENT05 proftpd[3095] 192.168.1.48 (xx.xxx.xxx.xxx[xx.xxx.xxx.xxx]): dispatching PRE_CMD command 'PWD' to mod_tls
Aug 13 12:45:45 LCENT05 proftpd[3095] 192.168.1.48 (xx.xxx.xxx.xxx[xx.xxx.xxx.xxx]): dispatching PRE_CMD command 'PWD' to mod_core
Aug 13 12:45:45 LCENT05 proftpd[3095] 192.168.1.48 (xx.xxx.xxx.xxx[xx.xxx.xxx.xxx]): dispatching PRE_CMD command 'PWD' to mod_core
Aug 13 12:45:45 LCENT05 proftpd[3095] 192.168.1.48 (xx.xxx.xxx.xxx[xx.xxx.xxx.xxx]): dispatching CMD command 'PWD' to mod_core
Aug 13 12:45:45 LCENT05 proftpd[3095] 192.168.1.48 (xx.xxx.xxx.xxx[xx.xxx.xxx.xxx]): in dir_check_full(): path = '/', fullpath = '/'.
Aug 13 12:45:45 LCENT05 proftpd[3095] 192.168.1.48 (xx.xxx.xxx.xxx[xx.xxx.xxx.xxx]): dispatching LOG_CMD command 'PWD' to mod_log
Aug 13 12:45:45 LCENT05 proftpd[3095] 192.168.1.48 (xx.xxx.xxx.xxx[xx.xxx.xxx.xxx]): dispatching PRE_CMD command 'TYPE I' to mod_tls
Aug 13 12:45:45 LCENT05 proftpd[3095] 192.168.1.48 (xx.xxx.xxx.xxx[xx.xxx.xxx.xxx]): dispatching PRE_CMD command 'TYPE I' to mod_core
Aug 13 12:45:45 LCENT05 proftpd[3095] 192.168.1.48 (xx.xxx.xxx.xxx[xx.xxx.xxx.xxx]): dispatching PRE_CMD command 'TYPE I' to mod_core
Aug 13 12:45:45 LCENT05 proftpd[3095] 192.168.1.48 (xx.xxx.xxx.xxx[xx.xxx.xxx.xxx]): dispatching CMD command 'TYPE I' to mod_xfer
Aug 13 12:45:45 LCENT05 proftpd[3095] 192.168.1.48 (xx.xxx.xxx.xxx[xx.xxx.xxx.xxx]): dispatching LOG_CMD command 'TYPE I' to mod_log
Aug 13 12:45:45 LCENT05 proftpd[3095] 192.168.1.48 (xx.xxx.xxx.xxx[xx.xxx.xxx.xxx]): dispatching PRE_CMD command 'PASV' to mod_tls
Aug 13 12:45:45 LCENT05 proftpd[3095] 192.168.1.48 (xx.xxx.xxx.xxx[xx.xxx.xxx.xxx]): dispatching PRE_CMD command 'PASV' to mod_core
Aug 13 12:45:45 LCENT05 proftpd[3095] 192.168.1.48 (xx.xxx.xxx.xxx[xx.xxx.xxx.xxx]): dispatching PRE_CMD command 'PASV' to mod_core
Aug 13 12:45:45 LCENT05 proftpd[3095] 192.168.1.48 (xx.xxx.xxx.xxx[xx.xxx.xxx.xxx]): dispatching CMD command 'PASV' to mod_core
Aug 13 12:45:45 LCENT05 proftpd[3095] 192.168.1.48 (xx.xxx.xxx.xxx[xx.xxx.xxx.xxx]): in dir_check_full(): path = '/', fullpath = '/'.
Aug 13 12:45:45 LCENT05 proftpd[3095] 192.168.1.48 (xx.xxx.xxx.xxx[xx.xxx.xxx.xxx]): Entering Passive Mode (192,168,1,48,255,131).
Aug 13 12:45:45 LCENT05 proftpd[3095] 192.168.1.48 (xx.xxx.xxx.xxx[xx.xxx.xxx.xxx]): dispatching LOG_CMD command 'PASV' to mod_log
Aug 13 12:45:45 LCENT05 proftpd[3095] 192.168.1.48 (xx.xxx.xxx.xxx[xx.xxx.xxx.xxx]): dispatching PRE_CMD command 'MLSD' to mod_tls
Aug 13 12:45:45 LCENT05 proftpd[3095] 192.168.1.48 (xx.xxx.xxx.xxx[xx.xxx.xxx.xxx]): dispatching PRE_CMD command 'MLSD' to mod_core
Aug 13 12:45:45 LCENT05 proftpd[3095] 192.168.1.48 (xx.xxx.xxx.xxx[xx.xxx.xxx.xxx]): dispatching PRE_CMD command 'MLSD' to mod_core
Aug 13 12:45:45 LCENT05 proftpd[3095] 192.168.1.48 (xx.xxx.xxx.xxx[xx.xxx.xxx.xxx]): dispatching CMD command 'MLSD' to mod_facts
Aug 13 12:45:45 LCENT05 proftpd[3095] 192.168.1.48 (xx.xxx.xxx.xxx[xx.xxx.xxx.xxx]): in dir_check_full(): path = '/', fullpath = '/'.


----- Original Message -----
From: "Barry Brimer" <lists@brimer.org>
To: "CentOS mailing list" <centos@centos.org>
Sent: Saturday, August 13, 2011 1:32:03 PM
Subject: Re: [CentOS] can't list directories in ftp

> Sorry for all the questions today. But I am trying to wrap up this ftp business and still having some issues. I appreciate your input.
>
> SELinux is temporarily disabled (until I can work this all out) and I am now able to log into the FTP server.

<snip>

> This is what my proftpd config is looking like at the moment.

<snip>

> # Masqurade Address
> MasqueradeAddress xx.xxx.xxx.xxx

<snip>

I'm betting that your MasqueradeAddress is the issue. This is great when
you are behind a NATing firewall, but for localhost testing, it could be
your issue.

Try commenting out your MasqueradeAddress line and it should create the
connection back through the IP address you connected from instead of
forcing the one in your MasqueradeAddress. When you want to test the real
setup, put it back in.

Barry
_______________________________________________
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
_______________________________________________
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
 
Old 08-13-2011, 06:07 PM
Barry Brimer
 
Default can't list directories in ftp

> Hello again, Barry
>
> Yes interestingly enough that seemed to do it for the local test. This is odd, because I remember setting up another ProFTPd server with this directive and never ran into this issue.
>
> Nevertheless, once I commented out the MasqueradeAddress directive it works locally.

<snip>

> 227 Entering Passive Mode (127,0,0,1,253,20).

<snip>

> Which is nice! But when I try to connect remotely this is what occurs:

<snip>

> Response: 227 Entering Passive Mode (192,168,1,48,251,255).

> Seriously thanks for your help here, it's greatly appreciated!

You're welcome.

Look above where I've left in the "Entering Passive Mode" line. This is
the address that is being used to send the connection back through. As
expected with localhost, it used 127.0.0.1, remotely, it used
192.168.1.48. That is not going to work if you are being NATed somewhere
using a different (public) IP address. That is where the
MasqueradeAddress comes into play. Of course this only applies to
*passive* ftp connections. Active FTP connections would be unaffected.
By any chance when you tested and this worked in the past could you have
been testing with active ftp?

Barry
_______________________________________________
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
 
Old 08-13-2011, 06:19 PM
Keith Roberts
 
Default can't list directories in ftp

On Sat, 13 Aug 2011, Tim Dunphy wrote:

> To: CentOS mailing list <centos@centos.org>
> From: Tim Dunphy <bluethundr@jokefire.com>
> Subject: Re: [CentOS] can't list directories in ftp
>
> Hello again, Barry
>
> Yes interestingly enough that seemed to do it for the
> local test. This is odd, because I remember setting up
> another ProFTPd server with this directive and never ran
> into this issue.
>
> Nevertheless, once I commented out the MasqueradeAddress
> directive it works locally.

I've NEVER had any problems with proftpd for myself, running
on Centos 5.6 - it's always worked out of the box for me.

I use gFTP to login to my main machine from my laptops, even
logged in from a Vista laptop to my Centos 5.6 machine via
ftp, using WinSCP.

I have created 2 directories under my normal user acount,
and just login using a GUI client like gFTP, and that takes
me to my home directory. I use ~/FTP-OUT for placing files I
want to get things from, and another directory called
~/ftp-in for moving things to the main Centos machine. The
ftp port is opened in my custom firewall to machines on the
LAN side only. Works fine for me.

I know it's lazy, but if I can't be bothered to get up and
walk to the main machine, I can always login via ssh to move
things around on the main Centos box while I'm on the laptop

HTH

Keith Roberts

-----------------------------------------------------------------
Websites:
http://www.karsites.net
http://www.php-debuggers.net
http://www.raised-from-the-dead.org.uk

All email addresses are challenge-response protected with
TMDA [http://tmda.net]
-----------------------------------------------------------------
_______________________________________________
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
 
Old 08-13-2011, 06:19 PM
John R Pierce
 
Default can't list directories in ftp

On 08/13/11 11:07 AM, Barry Brimer wrote:
>> Response: 227 Entering Passive Mode (192,168,1,48,251,255).
>> > Seriously thanks for your help here, it's greatly appreciated!
> You're welcome.
>
> Look above where I've left in the "Entering Passive Mode" line. This is
> the address that is being used to send the connection back through. As
> expected with localhost, it used 127.0.0.1, remotely, it used
> 192.168.1.48. That is not going to work if you are being NATed somewhere
> using a different (public) IP address. That is where the
> MasqueradeAddress comes into play. Of course this only applies to
> *passive* ftp connections. Active FTP connections would be unaffected.
> By any chance when you tested and this worked in the past could you have
> been testing with active ftp?

FTP servers behind NAT are a pain in the butt, you have to support
passive, as its the CLIENT that decides which mode to use.

if you load the ip connection tracker FTP module in your NAT (assuming
its a linux system), then it will monitor the FTP port for these PORT
commands and munge them on the fly to be correct, then your ftp server
works inside or outside (you don't use the MasqueradeAddress in this mode)


--
john r pierce N 37, W 122
santa cruz ca mid-left coast

_______________________________________________
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
 

Thread Tools




All times are GMT. The time now is 02:10 AM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org