[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: ftp bug?



Kenneth Dombrowski said:

> <--- 227 Entering Passive Mode (192,168,0,105,196,230).
> ---- Address returned by PASV seemed to be incorrect and has been fixed
> ---- Connecting data socket to (12.129.206.105) port 50406
> ---> LIST
> Interrupt
> ---> ABOR
>
> it is definitely *trying* to enter passive mode there.. the "Address
> returned by PASV seemed to be incorrect and has been fixed" message may
> be mucking it up though(?)
>
> anyway, the client is set to use it:
>
> kenneth@enlil:~$ lftp
> lftp :~> set -a
> set ftp:passive-mode on
>   (trimmed a million other options...)
>
> What I'm most confused by is mc working, but telnet behaving the same as
> lftp. I've confirmed mc is using passive mode as well. telnet in pasv
> mode:

the remote site, 12.129.206.105, is THAT behind a NAT box? have you
tried lftp on another site?  I tried it on ftp.kernel.org and it
worked fine. try it there to make sure it's not the remote server
causing the problem. Running a FTP server behind a NAT box is
generally a good way to screw up FTP bigtime, since FTP isn't NAT
friendly.

lftp ftp.kernel.org:/pub> get README
---> TYPE I
<--- 200 Type set to I.
---> SIZE README
<--- 213 1963
---> MDTM README
<--- 213 20011004181209
---> PASV
<--- 227 Entering Passive Mode (204,152,189,116,207,80).
---- Connecting data socket to (204.152.189.116) port 53072
---> RETR README
<--- 150 Opening BINARY mode data connection for README (1963 bytes).
<--- 226 Transfer complete.
1963 bytes transferred
lftp ftp.kernel.org:/pub> quit
---> QUIT

nate





Reply to: