Neil Schneider wrote:

In this case the culprit isn't NAT, it's FTP. It's a weird protocol
and it causes no end of grief, not only because of firewalls, but even
routing will cause problems with FTP. So don't blame NAT for the
problems with FTP, blame FTP.

I disagree. There is nothing inherently wrong with FTP. FTP opens a command channel which exchanges commands with the host and when it is time to transfer a file it opens another channel on a negotiated ip/port. Many protocols work this way including the relatively recent (compared to FTP) SIP protocol. It is a perfectly valid way to handle things. NAT breaks the end to end nature of the internet and causes the protocols involved to have to be much more complicated and handle everything within one TCP session.


--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list

Reply via email to