PDA

View Full Version : [SOLVED] ftp and passive mode



nerdy_kid
October 30th, 2010, 01:14 PM
I need to get a ftp server going on my server, but am running into some trouble. I spent all last night googling and tried all the suggestions I encountered but none worked.

ftp passive works over LAN.
it does not work over the internet. I can login, but as soon as I try to utilize the data port, I get:


Passive mode on.
ftp> ls
227 Entering Passive Mode (192,168,1,2,118,151).
ftp: connect: Connection timed out

I am assuming that it is a port forwarding issue. Also, notice the IP address in message 227 is a LAN IP -- 192.168.1.2. I have tried changing "pasv_address" in the config file to point to my external IP but that just breaks the ftp totally. It won't even work over lan anymore. It just throws the same error, except with my external IP instead of my LAN IP.



WHAT I HAVE DONE.

I have disabled the system firewall.
I have forwarded ports 21 and ports 30000 - 30999.

and here is my vsftpd.conf:




# Example config file /etc/vsftpd.conf
#
# The default compiled in settings are fairly paranoid. This sample file
# loosens things up a bit, to make the ftp daemon more usable.
# Please see vsftpd.conf.5 for all compiled in defaults.
#
# READ THIS: This example file is NOT an exhaustive list of vsftpd options.
# Please read the vsftpd.conf.5 manual page to get a full idea of vsftpd's
# capabilities.
#
#
# Run standalone? vsftpd can run either from an inetd or as a standalone
# daemon started from an initscript.
listen=YES
#
# Run standalone with IPv6?
# Like the listen parameter, except vsftpd will listen on an IPv6 socket
# instead of an IPv4 one. This parameter and the listen parameter are mutually
# exclusive.
#listen_ipv6=YES
#
# Allow anonymous FTP? (Disabled by default)
anonymous_enable=NO
#
# Uncomment this to allow local users to log in.
local_enable=YES
#
# Uncomment this to enable any form of FTP write command.
write_enable=YES
#
# Default umask for local users is 077. You may wish to change this to 022,
# if your users expect that (022 is used by most other ftpd's)
#local_umask=022
#
# Uncomment this to allow the anonymous FTP user to upload files. This only
# has an effect if the above global write enable is activated. Also, you will
# obviously need to create a directory writable by the FTP user.
#anon_upload_enable=YES
#
# Uncomment this if you want the anonymous FTP user to be able to create
# new directories.
#anon_mkdir_write_enable=YES
#
# Activate directory messages - messages given to remote users when they
# go into a certain directory.
#dirmessage_enable=YES
#
# If enabled, vsftpd will display directory listings with the time
# in your local time zone. The default is to display GMT. The
# times returned by the MDTM FTP command are also affected by this
# option.
use_localtime=YES
#
# Activate logging of uploads/downloads.
xferlog_enable=YES
#
# Make sure PORT transfer connections originate from port 20 (ftp-data).
connect_from_port_20=YES
#
# If you want, you can arrange for uploaded anonymous files to be owned by
# a different user. Note! Using "root" for uploaded files is not
# recommended!
#chown_uploads=YES
#chown_username=whoever
#
# You may override where the log file goes if you like. The default is shown
# below.
#xferlog_file=/var/log/vsftpd.log
#
# If you want, you can have your log file in standard ftpd xferlog format.
# Note that the default log file location is /var/log/xferlog in this case.
#xferlog_std_format=YES
#
# You may change the default value for timing out an idle session.
#idle_session_timeout=600
#
# You may change the default value for timing out a data connection.
#data_connection_timeout=120
#
# It is recommended that you define on your system a unique user which the
# ftp server can use as a totally isolated and unprivileged user.
#nopriv_user=ftpsecure
#
# Enable this and the server will recognise asynchronous ABOR requests. Not
# recommended for security (the code is non-trivial). Not enabling it,
# however, may confuse older FTP clients.
#async_abor_enable=YES
#
# By default the server will pretend to allow ASCII mode but in fact ignore
# the request. Turn on the below options to have the server actually do ASCII
# mangling on files when in ASCII mode.
# Beware that on some FTP servers, ASCII support allows a denial of service
# attack (DoS) via the command "SIZE /big/file" in ASCII mode. vsftpd
# predicted this attack and has always been safe, reporting the size of the
# raw file.
# ASCII mangling is a horrible feature of the protocol.
#ascii_upload_enable=YES
#ascii_download_enable=YES
#
# You may fully customise the login banner string:
#ftpd_banner=Welcome to blah FTP service.
#
# You may specify a file of disallowed anonymous e-mail addresses. Apparently
# useful for combatting certain DoS attacks.
#deny_email_enable=YES
# (default follows)
#banned_email_file=/etc/vsftpd.banned_emails
#
# You may restrict local users to their home directories. See the FAQ for
# the possible risks in this before using chroot_local_user or
# chroot_list_enable below.
#chroot_local_user=YES
#
# You may specify an explicit list of local users to chroot() to their home
# directory. If chroot_local_user is YES, then this list becomes a list of
# users to NOT chroot().
chroot_local_user=YES
chroot_list_enable=YES
# (default follows)
chroot_list_file=/etc/vsftpd.chroot_list
#
# You may activate the "-R" option to the builtin ls. This is disabled by
# default to avoid remote users being able to cause excessive I/O on large
# sites. However, some broken FTP clients such as "ncftp" and "mirror" assume
# the presence of the "-R" option, so there is a strong case for enabling it.
#ls_recurse_enable=YES
#
# Debian customization
#
# Some of vsftpd's settings don't fit the Debian filesystem layout by
# default. These settings are more Debian-friendly.
#
# This option should be the name of a directory which is empty. Also, the
# directory should not be writable by the ftp user. This directory is used
# as a secure chroot() jail at times vsftpd does not require filesystem
# access.
secure_chroot_dir=/var/run/vsftpd/empty
#
# This string is the name of the PAM service vsftpd will use.
pam_service_name=vsftpd
#
# This option specifies the location of the RSA certificate to use for SSL
# encrypted connections.
rsa_cert_file=/etc/ssl/private/vsftpd.pem

userlist_deny=NO
userlist_enable=YES
userlist_file=/etc/vsftp.allowed_users


pasv_enable=YES

#pasv_promiscuous=YES
#pasv_address=EXTERNAL_IP


#ssl_enable=YES
#allow_anon_ssl=YES
#force_local_data_ssl=YES
#force_local_logins_ssl=YES
#ssl_tlsv1=YES
#ssl_sslv2=YES
#ssl_sslv3=YES
# Filezilla uses port 21 if you don't set any port
# in Servertype "FTPES - FTP over explicit TLS/SSL"
# Port 990 is the default used for FTPS protocol.
# Uncomment it if you want/have to use port 990.



# Show hidden files and the "." and ".." folders.
# Useful to not write over hidden files:
#force_dot_files=YES

# Hide the info about the owner (user and group) of the files.
hide_ids=YES

# Connection limit for each IP:
max_per_ip=15

# Maximum number of clients:
max_clients=25

pasv_min_port=30000
pasv_max_port=30999


What am I doing wrong?
I greatly appreciate any help!

elico
October 30th, 2010, 05:24 PM
instead port forwarding try to put the host in dmz which means every contact with your external IP address will forwarded to the DMZ host IP.

this is a very common problem by the way..

psusi
October 30th, 2010, 06:08 PM
You need to fill in the pasv_address field with your real IP address and have the router forward the ports.

nerdy_kid
October 30th, 2010, 09:46 PM
You need to fill in the pasv_address field with your real IP address and have the router forward the ports.

I already tried that, with the min to max pasv port range forwarded.




instead port forwarding try to put the host in dmz which means every contact with your external IP address will forwarded to the DMZ host IP.

this is a very common problem by the way..


So basically forward all the ports to my server?
I suppose I could do that, but I was hoping to avoid that as I have other computers on the LAN. Maybe I will try for testing purposes at least.
As soon as I get this evil thing configured properly, I am gonna put up a nice howto for all the noobs like myself who try setting one of these things up lol

nerdy_kid
October 30th, 2010, 11:57 PM
ok I got it, I had accidentally reenabled ufw and that was blocking it :oops:

but now it is fixed and working great! :D thanks guys!