"Cannot bind a port" error when using active FTP with 2.9.1; regression from 2.7.0b #193
Description
I'm getting the error Cannot bind a port: Cannot assign requested address when connecting to a local vsftpd via active connection. This worked in older versions.
I searched and found a related issue: #149
The advice of "just use passive" is a bit disingenuous. gFTP certainly appears to support active FTP; the checkbox is presumably there for a reason. If active FTP support has been removed entirely, then the UI (and documentation) should reflect that.
Connection log from 2.7.0b (no error):
Successfully changed local directory to /home/ltsmash/Downloads
Looking up 192.168.0.30
Trying 192.168.0.30:43756
Connected to 192.168.0.30:43756
220 (vsFTPd 3.0.3)
USER ltsmash
331 Please specify the password.
PASS xxxx
230 Login successful.
SYST
215 UNIX Type: L8
TYPE I
200 Switching to Binary mode.
CWD /home/ltsmash
250 Directory successfully changed.
PWD
257 "/home/ltsmash" is the current directory
Loading directory listing /home/ltsmash from server (LC_TIME=en_CA.UTF-8)
PORT 192,168,0,5,224,123
200 PORT command successful. Consider using PASV.
LIST -aL
150 Here comes the directory listing.
226 Directory send OK.
Log from 2.9.1 (error):
Successfully changed local directory to /home/ltsmash/Downloads
Looking up 192.168.0.30
Trying 192.168.0.30:43756
Connected to 192.168.0.30:43756
220 (vsFTPd 3.0.3)
USER ltsmash
331 Please specify the password.
PASS xxxx
230 Login successful.
FEAT
SYST
215 UNIX Type: L8
TYPE I
200 Switching to Binary mode.
CWD /home/ltsmash
250 Directory successfully changed.
PWD
257 "/home/ltsmash" is the current directory
Loading directory listing /home/ltsmash from server (LC_TIME=en_CA.UTF-8)
Cannot bind a port: Cannot assign requested address
Disconnecting from site 192.168.0.30
I've downgraded back to 2.8.0b for now.