After upgrading vsftpd from 2.0.7 to 2.1.0 transfers (download or upload via ssl) will be interrupted after 300s (idle timeout for data), log message "421 Data timeout". It seems that the idle timer is not reset when packets transmitted via ssl. When setting "data_connection_timeout" to a high value the problem does not occur (because timeout never reached). I've tested this behavior with lftp (freebsd) and filezilla (windows), depending on the client the transmission continues (if the client is able reconnect). I'm not sure if this is a general or FreeBSD port specific bug. Fix: Not really a fix, set "data_connection_timeout" (vsfptd.conf) to a high value. How-To-Repeat: Start a down or upload which takes longer then the default idle timeout and watch the logfile.
Responsible Changed From-To: freebsd-ports-bugs->dinoex Assign to maintainer
State Changed From-To: open->feedback
No, this is another problem (or feature), which is different from the bug I've reported (for compatibility reasons (with filezilla) require_ssl_reuse=NO is already set). SSL data connections are working until the timout is reached.
State Changed From-To: feedback->analyzed - Send a mail upstream this might be a general problem.
dinoex 2009-05-30 20:35:59 UTC FreeBSD ports repository Modified files: ftp/vsftpd Makefile distinfo Log: - update to 2.1.2 Bugfix 421 Data timeout PR: 134422 Revision Changes Path 1.36 +1 -1 ports/ftp/vsftpd/Makefile 1.19 +3 -3 ports/ftp/vsftpd/distinfo _______________________________________________ cvs-all@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/cvs-all To unsubscribe, send any mail to "cvs-all-unsubscribe@freebsd.org"
State Changed From-To: analyzed->patched Please test the new version 2.1.2
I made a test with a 1 GB sized testfile, no timeouts anymore. In the changelog of vsftp 2.1.1 the fix is described. - Fix NASTY regression whereby data transfer timeouts would fire incorrectly under SSL transfers. In addition, the transfer rate caps were not working under SSL transfers. Reported by several people.
State Changed From-To: patched->closed Problem fixed with update, thanks.