I’m having problems with vsftpd on SuSe 11.0. I can ftp from a remote machine, but can’t access the files: for example if I type “ls”, it says “Entering Passive Mode” and eventually times out.
I’ve tried restarting vsftpd, double checked the vsftpd.config, used “modprobe ip_nat_ftp”, making sure vsftpd is listed as an allowed service for firewall, nothing helps.
How familiar are you with the difference(s) between Active and Passive
mode FTP? With Passive mode the FTP server must have a fairly liberal
firewall with regard to its high ports. For example the Wikipedia entry
for FTP is really good and covers this nicely.
For example the following is from a simple test I did:
230 Anonymous access granted, restrictions apply.
Remote system type is UNIX.
Using binary mode to transfer files.
ftp> cd incoming
250 CWD command successful
ftp> binary
200 Type set to I
ftp> put bigfile.big
local: bigfile.big remote: bigfile.big
229 Entering Extended Passive Mode (|||35637|)
150 Opening BINARY mode data connection for bigfile.big
|**********************************|100% 976 MB 41.34 MB/s 00:00 ETA
226 Transfer complete.
1024000000 bytes sent in 00:23 (41.34 MB/s)
So when I typed ‘put bigfile.big’ the server sent my client the number
35637, which is the port on the SERVER side to which I connected. netstat
showed the following:
tcp 0 46416 137.65.120.60:51835 130.57.1.88:35637 ESTABLISHED 26211/ftp
tcp 0 0 137.65.120.60:41694 130.57.1.88:21 ESTABLISHED 26211/ftp
Notice how FTP connected to the number from the server (35637) which had
not previously been open on the server side. As a result the server’s
firewall must either dynamically open that port somehow or must just leave
those potential ports open all the time. If this is not set properly the
symptom you describe happens.
Good luck.
akrishta wrote:
> Hi,
>
> I’m having problems with vsftpd on SuSe 11.0. I can ftp from a remote
> machine, but can’t access the files: for example if I type “ls”, it says
> “Entering Passive Mode” and eventually times out.
>
> I’ve tried restarting vsftpd, double checked the vsftpd.config, used
> “modprobe ip_nat_ftp”, making sure vsftpd is listed as an allowed
> service for firewall, nothing helps.
>
> Any suggestions?
>
> Alisa
>
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
this is for separating out network hosts into individual log files.
destination std {
file ("/var/log/HOSTS/$YEAR-$MONTH/$HOST$FACILITY-$YEAR-$MONTH-$DAY"
owner(root) group(root) perm(0600) dir_perm(0700) create_dirs(yes)); **in was (y/es) /B and i coorrcted it
};
log {
source(src);
destination(std);
};
after saving runing SuSEconfig and restarting syslog-ng
here what i see:
Shutting down syslog services done
Starting syslog servicessyntax error at 237
Parse error reading configuration file, exiting. (line 237)
startproc: exit status of parent of /sbin/syslog-ng: 1
failed
ligne 237 file ("/var/log/HOSTS/$YEAR-$MONTH/$HOST
ligne 238/$FACILITY-$YEAR-$MONTH-$DAY" owner(root) group(root) perm(0600) dir_perm(0700) create_dirs(yes));
what you are using is more correctly named SUSE Linux Enterprise
Server 10 sp2 (aka SLES 10 sp2)
just in case you do not know: you ARE welcome here, but we don’t ‘do’
SLES here…that is done over in forums.novell.com
this it the openSUSE side…they are NOT exactly alike and most folks
here are running openSUSE 11.1 which will eventually result in the
release of SLED/SLES 12
That’s great to hear. Thank-you for posting back your results.
Good luck.
akrishta wrote:
> It’s fixed! This is what I did:
>
> 1) add to the vsftpd.conf file the two lines
> pasv_min_port=30000
> pasv_max_port=30100
>
> 2) Free this range of ports explicitly for the Firewall.
>
> Thanks a lot for pushing me in the right direction
>
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/