Description of problem: The default to passive mode is so strong that ftp client refuses to do port mode even when told to: Version-Release number of selected component (if applicable): ftp-0.17-18 How reproducible: very Steps to Reproduce: ftp -d -v 192.168.50.161 Connected to 192.168.50.161 (192.168.50.161). 220 ATAboy2-00330138 FTP V1.0 ready Name (192.168.50.161:nigel): ADMIN ---> USER XXXX 331 User OK, need password Password: ---> PASS XXXX 230 User logged in ---> SYST 215 UNIX Type: L8 Remote system type is UNIX. Using binary mode to transfer files. ftp> sendport Use of PORT cmds off. ftp> sendport Use of PORT cmds on. ----------------SO we are *definitely* using PORT mode ftp> binary ---> TYPE I 200 TYPE command OK ftp> put ATABoy2f_5030 local: ATABoy2f_5030 remote: ATABoy2f_5030 ftp: setsockopt (ignored): Permission denied ---> PASV ----------------- The fucker just sent a PASV - wheres the PORT ----------------- command???? 500 Unsupported command/option Passive mode refused. ftp> quit ---> QUIT 221 Goodbye See internal commentary Additional info: RH9 also affected.
Duplicated here
Did some more digging - passive and sendport are not exclusive in Berkeley ftp. "passive" turns off passive correctly. I thus don't believe this is a bug.