Community
Participate
Working Groups
+++ This bug was initially created as a clone of Bug #264943 +++ FTP requires using passive mode for any client that is behind a NAT, since the externally visible IP address will be different in this case than the one seen on the local host -- see bug 264943 for details. I can't at the moment see any reason for not enabling passive mode, and in fact all other FTP clients I know do use passive by default, so RSE should use passive mode by default as well.
Will need to work with the Community on whether we can change the default in 3.1.1
Bulk update of target milestones to 3.2
Bulk move of deferred feature requests to 3.4
This is finally implemented for TM 3.5 (Kepler) RC1: https://git.eclipse.org/c/tm/org.eclipse.tm.git/commit/?id=03f94f01c9181a95562628a88cb1d26c583d46c0 This should be added to the new & noteworthy.
See also bug 174772 for some history
*** Bug 174772 has been marked as a duplicate of this bug. ***
Created attachment 231075 [details] Screenshot of Filezilla Client 3.7.0.1 Settings I've checked some other Open Source FTP clients, and found that FileZilla client also uses passive mode by default (and recommends doing so). FileZilla also has some "fallback" mechanisms and recommends using "the other mode" in case passive mode fails. It also keeps a list of "succesful transfers" vs "failed transfers". I still think we should stick to passive mode as the new default in RSE. For bug 408223 (and probably other issues we may find during testing) we should look for better error handling.
I've checked a couple of commercial clients and they default to passive mode as well. This change makes perfect sense.