>Today I've found an interesting case, looking at why the new nessus distfile
>was not uploaded to ftp.netbsd.org: it seems that ftp.nessus.org doesn't
>accept passive ftp because of a firewall rule:
>227 Entering Passive Mode (199,181,107,23,146,207)
>200 PORT command successful.
><some delay here>
>425 Can't build data connection: No route to host.
>
>Active mode works fine. If someone wants to look at our ftp client and fix
>this case ...

in case i missed it somewhere...what's the reason for ftp using
passive mode by default now?  it's not wrong...it's just disarming (as
in, counter to the last ten years of my experience using ftp).

-- 
|-----< "CODE WARRIOR" >-----|
codewarrior@daemon.org             * "ah!  i see you have the internet
twofsonet@graffiti.com (Andrew Brown)                that goes *ping*!"
andrew@crossbar.com       * "information is power -- share the wealth."