主动FTP与被动FTP-权威解释(国外英语资料).doc

主动FTP与被动FTP-权威解释(国外英语资料)Active FTP and passive FTP - authoritative explanationopeningOne of the most common challenges in dealing with firewalls and other network connectivity issues is the difference between active FTP and passive FTP and how to support them perfectly. Fortunately, this article can help you clear some of the confusion over how to support FTP in a firewall environment.This article may not like the title says it is an authoritative explanation, but Ive heard a lot of good feedback, saw this article cited in many places, know a lot of people think it is very useful. Although Ive been looking for ways to improve, if you find somewhere that isnt clear enough and needs more explanation, please let me know! Recent changes are examples of commands in active FTP and passive FTP sessions. Examples of these conversations should help to better understand the problem. The example also provides a great illustration to explain the steps of the FTP session. Now, the question begins...basisFTP is a TCP based service that does not support UDP. What is different is that FTP USES two ports, a data port and a command port (also called the control port). Typically these two ports are the 21-command port and the 20-data port. But when we found that different data ports in the (FTP) approach were not always 20, confusion arose.Active FTPThe active way of FTP is this: the client connects to the FTP servers command port from an arbitrary non-privileged port (N 1024), which is the 21 port. The client then listens for port N + 1 and sends the FTP command port N + 1 to the FTP server. The server then connects to the client specified data port (N + 1) from its own data port (20).For the firewall ahead of the FTP server, the following communication must be allowed to support active FTP:Port 21 on any port to the FTP server (the client initialization of the connection S -c)Port 21 port of FTP server to port greater than 1024 (server response client control port s- C)Port 20 port