Hide Forgot
Some FTP servers don't like when clients use different IPs for the control and data connections. This patch adds the "-m" switch to allow for "ftp" to always use the same source IP for both channels. Patch from Anthony Golia <anthony.golia@morganstanley.com>
Created attachment 120307 [details] netkit-ftp-0.17-multihome.patch
Is somewhere an 'anonymous' FTP server (don't like when clients use different IPs for the control and data connections) to test this feature ? Or should I ask <anthony.golia@morganstanley.com> ?
Don't know the specifics on the FTP servers that would behave this way.
There was a small bug in the patch above (it does not close 'data'-socket-descriptor if bind() fails, socket() is OK and 'multihome'==TRUE. Fixed in netkit-ftp-0.17-data.patch and my 'new' netkit-ftp-0.17-multihome.patch ). According to the orignal patch: 'multihome' is default. It seems to work. Tested in: devel-i386 (client) <-> RHEL-4-x86_64 (server) PS (to comment #6): I have no access to zappa (144.203.221.27). -------------------------------------- ftp 144.203.221.27 ftp: connect: Connection refused ftp> -------------------------------------- It would be nice to test it (using FTP servers which don't like when clients use different IPs for the control and data connections).
Fixed in devel (ftp-0.17 Release 32.1).
Created attachment 133238 [details] fixed multihome patch
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on the solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2007-0177.html