Re: Why do I need a software firewall?
Date: Fri, 14 Oct 2005 10:27:04 +0000 (UTC)
In article <E4qdnbbtgcQaWdPeRVnfirstname.lastname@example.org>, "Alun Jones" <email@example.com> writes:
>"Leythos" <firstname.lastname@example.org> wrote in message
>> In article <-eGdnTC-H62FG9PeRVnemail@example.com>, firstname.lastname@example.org
>>> "Leythos" <email@example.com> wrote in message
>>> > You really are a dufus - I never said that NAT didn't impact Active
>>> > FTP,
>>> > not once. I said that NAT doesn't break FTP, never saying anything
>>> > about
>>> > Active or Passive - knowing the anyone that understands the slightest
>>> > about FTP and NAT would already know that you need to use Passive FTP,
>>> > which works fine, so FTP isn't broken at all.
>>> Depending on who's behind the NAT, that is. Passive FTP doesn't work if
>>> it's the server that's behind the NAT. You have to tell the NAT which
>>> to open.
>>> Now, some NATs work fine for passive FTP, because they scan the FTP
>>> channel for PASV commands and the associated responses, and they change
>>> IP address and port described therein. They should also open up the port
>>> mapping from the external port to the internal one. These NATs generally
>>> the same for active FTP transfers, allowing them to work, too.
>>> There are two usual stipulations on this, however:
>>> 1. The FTP control traffic must be on port 21. I've heard rumours that
>>> there are NAT routers that can be configured to look for FTP on other
>>> but never run across such a beast.
>>> 2. The FTP control traffic must be unencrypted.
>> I have 9 FTP servers, some are behind a NAT from a Linksys/D-Link,
>> others behind a FireBox II others behind a FireBox x1000. They all seem
>> to work for us.
FTP is so widely used that I'd think that most NAT devices nowadays would come
with builtin FTP Application Level Gateways to overcome these problems.
Security team leader
>Uh... okay. Does that support or contradict what I said above?
>Or are you just offering up your size for a measuring contest? :-)