I have another question or maybe a feature request.
I did some digging in this forum, found a lot of posts about "Passive mode replying with different IP than the server IP", I also know that we have a setting in Filezilla Client.
Connection > FTP > Passive mode,
"Use the serveris external IP address instead"
It is lucky that we have this option, many issues could be solved by this, but does anyone meet a case like following?
A FTPES server (IIS 7.5 on Windows Server 2008 R2), it's IP is 192.168.1.2, only 1 NIC.
The public IP of this server is 210.13.xx.xx, we have firewall and F5 BIG-IP device, NAT is handled by F5.
Due to some reason, the server administrator set the “External IP Address of Firewall” to "210.13.xx.xx" in IIS.
Now the internet clients can connect to the FTP smoothly, but internal clients (inside our corporation) couldn't get directory listing, because internal client get passive mode reply with "Public IP" too, so they can't connect to it.
Under this condition, the settings I mentioned above didn't work, i.e., it only works when server reply with internal IP.
Leaving aside the server side issues, It's better that Filezilla client can change any IP replied in passive mode which is not same as the IP (you connected) to the server IP, no matter what it is.
In other word, Even if you connect to internal IP, but server reply with public IP, Filezilla also change the public IP to internal IP.