On Wed, 22 Oct 2008 12:13:30 -0700
Jeremy Chadwick <[EMAIL PROTECTED]> wrote:
> Inbound: TCP port 21 (main ftpd daemon)
> Inbound: TCP ports 49152 to 65535(used in FTP passive mode)
> Outbound: TCP port 20 (used in FTP active mode)
>
> Yes, you read that rang
Jeremy Chadwick wrote:
Finally, I recommend if this machine is RELENG_6 or later, that you look
in to using pf(4) instead. You'll thank me later. :-)
Specifically ftp-proxy(8). Makes it almost feasible to support such
an archaic and unfriendly-to-firewalling protocol as FTP and still
retain
Len Conrad <[EMAIL PROTECTED]> writes:
> two machines on the same private network.
>
> ftp 10.0.0.24
> Connected to 10.0.0.24.
> 220 mx1.fairhope.net FTP server (Version 6.00LS) ready.
> Name (10.0.0.24:username):
> 331 Password required for username.
> Password:
> 230 User username logged in.
On Wed, Oct 22, 2008 at 01:58:31PM -0500, Len Conrad wrote:
> two machines on the same private network.
>
> ftp 10.0.0.24
> Connected to 10.0.0.24.
> 220 mx1.fairhope.net FTP server (Version 6.00LS) ready.
> Name (10.0.0.24:username):
> 331 Password required for username.
> Password:
> 230 Use
two machines on the same private network.
ftp 10.0.0.24
Connected to 10.0.0.24.
220 mx1.fairhope.net FTP server (Version 6.00LS) ready.
Name (10.0.0.24:username):
331 Password required for username.
Password:
230 User username logged in.
Remote system type is UNIX.
Using binary mode to transfe
