Date: Tue, 1 Jun 1999 18:50:35 -0400 From: Nathan Dorfman <nathan@rtfm.net> To: John Polstra <jdp@polstra.com> Cc: dwhite@resnet.uoregon.edu, current@FreeBSD.ORG Subject: Re: FTP passive mode - a new default? Message-ID: <19990601185035.A11288@rtfm.net> In-Reply-To: <199905280446.VAA06342@vashon.polstra.com>; from John Polstra on Thu, May 27, 1999 at 09:46:51PM -0700 References: <Pine.BSF.4.03.9905271100280.16577-100000@resnet.uoregon.edu> <199905280446.VAA06342@vashon.polstra.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, May 27, 1999 at 09:46:51PM -0700, John Polstra wrote: > In article <Pine.BSF.4.03.9905271100280.16577-100000@resnet.uoregon.edu>, > Doug White <dwhite@resnet.uoregon.edu> wrote: > > > I second the suggestion to 'autoprobe' PASV support, and revert to active > > mode (w/ an appropriate msg) if PASV is refused. > > That won't be a good solution in practice. When passive mode doesn't > work, it's almost always because a firewall on the server side is > blocking the incoming data connection. The client doesn't see a > refusal; its connect() call just times out. The trouble is, the > timeout takes a long time (on the order of a minute or more). Certain shareware lose95 FTP servers don't know how to do passive mode. The NetBSD ftp client uses passive mode by default, but will send a PORT if the PASV is unsuccessful. > John > -- > John Polstra jdp@polstra.com > John D. Polstra & Co., Inc. Seattle, Washington USA > "Self-interest is the aphrodisiac of belief." -- James V. DeLong -- Nathan Dorfman <nathan@rtfm.net> The statements and opinions in my Unix Admin @ Frontline Communications public posts are mine, not FCC's. "The light at the end of the tunnel is the headlight of an approaching train." --/usr/games/fortune To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19990601185035.A11288>