Wondering if anyone else may have seen/are seeing the same…
This AM have newly setup on two VMware Guests running
Server Setup
openSUSE 13.1 (LXDE)
Fully updated
Install vsftpd and yast2-ftp-server
vsftpd info
Information for package vsftpd:
Repository: Main Repository (OSS)
Name: vsftpd
Version: 3.0.2-10.1.2
Arch: x86_64
Vendor: openSUSE
Installed: Yes
Status: up-to-date
Installed Size: 327.3 KiB
Result:
Connecting through the Localhost interface is the only way FTP is working.
Connecting through the normal network IP address,
- Initially connects no matter what authentication setting is set, then
- Hangs instead of prompting for Username and Password
Of note, there is no file or folder /var/log/vsftpd which I expected
Of note, I find the same behavior if the vsftpd service is stopped
FTP clients tried:
openSUSE 13.1 FTP clients (from another Guest on the same virtual network)
Firefox running on another openSUSE 13.1 client
Windows command line FTP client
Windows IE
(same result all clients)
Using the YAST FTP Server configuration applet, tried the following settings
Verified “Firewall port is open on all interfaces”
Verified in Firewall Settings > Firewall Details the correct network adapter is specified (only one is installed)
PASV enabled/disabled
Authentication Anonymous Only, Authenticated Users Only, Both (all possibilities)
Enable Upload both enabled and disabled
Verified vsftpd is running, a number of different ways, one is using systemctl
systemctl status vsftpd
Preliminary Conclusion:
Could be a couple different issues. First, I’m surprised that vsftpd is not configured to log to file(s) in /var/log/ somewhere. Could this be a broken install?
Because no vsftpd-specific logging file was found, I set logging to the syslog in /etc/vsftpd.conf but no ftp related entries are sent to syslog (var/log/messages)
I find it curious that by simply opening port 20, I see the same result… A connection is accepted without authentication and then just hangs without passing on to requiring FTP authentication. Because this only happens on the external network address but functions correctly on the localhost address, I am speculating that this is where the vsftpd install may be broken, not binding to “all interfaces”
Hoping anyone else can either verify what I’m seeing or can see where I might be going wrong.
BTW - I also tried running yast-ftp-server with pure-ftp instead of vsftp and that also was a failed install, but differently… That is more obvious, it has fundamental problems starting (start succeeds, but status thereafter is “stopped” without explanation).
Thx,
TSU