On Tue, Jul 5, 2011 at 2:34 PM, Mick <michaelkintz...@gmail.com> wrote: > On Tuesday 05 Jul 2011 19:42:53 Paul Hartman wrote: >> On Tue, Jul 5, 2011 at 6:58 AM, Mick <michaelkintz...@gmail.com> wrote: >> > 200 Switching to ASCII mode. >> > tnftp: setsockopt SO_DEBUG (ignored): Permission denied >> > ---> EPSV >> > 229 Entering Extended Passive Mode (|||62430|) >> > 229 Entering Extended Passive Mode (|||62430|) >> >> Don't use EPSV, use PASV instead, hopefully that will work. > > I tried defining passive when in the session. It was in passive by default, > so I had to toggle it back on again: > > got remotecwd as `/' > ---> TYPE I > 200 Switching to Binary mode. > ftp> passive > Passive mode: off; fallback to active mode: off. > ftp> passive > Passive mode: on; fallback to active mode: on. > ftp> ls > ---> TYPE A > 200 Switching to ASCII mode. > tnftp: setsockopt SO_DEBUG (ignored): Permission denied > ---> EPSV > 229 Entering Extended Passive Mode (|||9832|) > 229 Entering Extended Passive Mode (|||9832|) > > How can I control it to not go into extended passive? > > PS. The server reports EPSV in its features, so I am not sure why it would not > work with EPSV.
FTP is the bastard protocol from hell. There are more ways it can go wrong than right. :) Firewalls especially love to silently rewrite FTP commands and port mappings. It can be a real PITA to debug. So, even if your client supports EPSV and your server supports EPSV, if firewall/router in-between does not then it could still break things. Even if you wireshark the session on your computer, what you see may not match what's being sent to the remote server, and vice-versa. Standard PASV mode is much more widely supported than EPSV mode, so that's the line of thought that brought me to suggest trying that. I've never used tnftp but from the manpage I googled, it looks like "epsv4 off " is the command to toggle EPSV off.
