Re: ftp passive modem is on by defaut?

> shin> The 1st trial seems to be rejected at, > shin> 500 Illegal PORT range rejected. > shin> and 2nd trial seems to be accepted at, > shin> 200 pcmd command successful. > > This problem was reported at [FreeBSD-users-jp 46521]. It is > Japanese FreeBSD mailing list. > In my experi

Re: ftp passive modem is on by defaut?

On Sun, 6 Feb 2000, Jordan K. Hubbard wrote: > Having passive mode on by default *across the board* is truly the > right thing to do in this day in age and there's no reason not to > default to it now. We've received too many tech support emails (and > phone calls) from people with firewalls who

Re: ftp passive modem is on by defaut?

Having passive mode on by default *across the board* is truly the right thing to do in this day in age and there's no reason not to default to it now. We've received too many tech support emails (and phone calls) from people with firewalls who were confused with the previous default. - Jordan

Re: ftp passive modem is on by defaut?

Hi, >>> Mon, 07 Feb 2000 00:24:09 +0900 $B$N9o$K!V(Bshin$B!W!"$9$J$o$A(B >>> Yoshinobu Inoue <[EMAIL PROTECTED]> $B;a[)$/(B shin> In non passive case, . . . shin> The 1st trial seems to be rejected at, shin> 500 Illegal PORT range rejected. shin> and 2nd trial seems to be accep

Re: ftp passive modem is on by defaut?

> shin> (About EPRT, initiating client retry PORT command next if EPRT > shin> failes, so trying EPRT first will be OK.) > No. In this senario, if server knows EPRT, EPRT request will be > accepted, and will not fail. But, existing NAT box doesn't handle > EPRT request. So, NAT box cannot tre

Re: ftp passive modem is on by defaut?

Hi, >>> Sun, 06 Feb 2000 17:42:14 +0900 $B$N9o$K!V(Bshin$B!W!"$9$J$o$A(B >>> Yoshinobu Inoue <[EMAIL PROTECTED]> $B;a[)$/(B shin> Wmmm, I actually enabled it, but it is causing problems, so shin> should EPSV only allowed for IPv6 at least for several shin> starting 4.x releases? I'm sor

Re: ftp passive modem is on by defaut?

> Since KAME version of ftp/ftpd was merged, ftp speaks EPSV/EPRT as > default not only IPv6 but also IPv4. Currently, existing natd is not > recognize EPRT. So, NAT user may be confuse. Please examine > bin/14305. Wmmm, I actually enabled it, but it is causing problems, so should EPSV only

Re: ftp passive modem is on by defaut?

On Sun, Feb 06, 2000 at 04:06:07AM +0800, Peter Wemm wrote: # Dmitry Valdov wrote: # > Why ftp passive mode is on by default? # > 229 Entering Extended Passive Mode (|||1049|) # > passive Toggle passive mode. If passive mode is turned on (default # >

Re: ftp passive modem is on by defaut?

Hi, > On Sat, 5 Feb 2000 22:09:18 +0300 (MSK) > Dmitry Valdov <[EMAIL PROTECTED]> said: dv> 229 Entering Extended Passive Mode (|||1049|) Since KAME version of ftp/ftpd was merged, ftp speaks EPSV/EPRT as default not only IPv6 but also IPv4. Currently, existi

Re: ftp passive modem is on by defaut?

Dmitry Valdov wrote: > Hello! > > Why ftp passive mode is on by default? > > > > ftp localhost > Connected to localhost. > 220 home.dv.ru FTP server (Version 6.00LS) ready. > Name (localhost:dv): > 331 Password required for dv. > Password: > 230 User dv logged in. > Remote system type is UNIX.

Re: ftp passive modem is on by defaut?

On Sat, Feb 05, 2000 at 10:09:18PM +0300, Dmitry Valdov wrote: > Hello! > > Why ftp passive mode is on by default? Lots of firewall/router filters doesn't allow active ftp ... /Jesper -- Jesper Skriver, jesper(at)skriver(dot)dk - CCIE# 5456 Work:Network manager @ AS3292 (Tele Danmark D

ftp passive modem is on by defaut?

Hello! Why ftp passive mode is on by default? > ftp localhost Connected to localhost. 220 home.dv.ru FTP server (Version 6.00LS) ready. Name (localhost:dv): 331 Password required for dv. Password: 230 User dv logged in. Remote system type is UNIX. Using binary mode to transfer files. ftp> get