Re: Net::FTP takes a very long time in Passive mode

To be frank, I don't really know what Passive FTP means, or why I can't use regular FTP for this server.

See ikegami's excellent post at FTP Connections and Firewalls.

Examine what is said, not who speaks.

"Efficiency is intelligent laziness." -David Dunham
"Think for yourself!" - Abigail
"Memory, processor, disk in that order on the hardware side. Algorithm, algorithm, algorithm on the code side." - tachyon

Comment on Re: Net::FTP takes a very long time in Passive mode Download Code

Replies are listed 'Best First'.
Re^2: Net::FTP takes a very long time in Passive mode by pg (Canon) on Oct 16, 2004 at 00:53 UTC
In that post, twice the author said listening on a random port, it is correct to a level... Both the user and the server-DTPs have a default data port. The user-process default data port is the same as the control connection port (i.e., U). The server-process default data port is the port adjacent to the control connection port (i.e., L-1). Default Data Connection Ports: All FTP implementations must support use of the default data connection ports, and only the User-PI may initiate the use of non-default ports. Negotiating Non-Default Data Ports: The User-PI may specify a non-default user side data port with the PORT command. The User-PI may request the server side to identify a non-default server side data port with the PASV command.	[reply]
Re^3: Net::FTP takes a very long time in Passive mode by BrowserUk (Patriarch) on Oct 16, 2004 at 01:20 UTC
It would make more sense to post your correction as a reply to the post that it is correcting? Examine what is said, not who speaks. "Efficiency is intelligent laziness." -David Dunham "Think for yourself!" - Abigail "Memory, processor, disk in that order on the hardware side. Algorithm, algorithm, algorithm on the code side." - tachyon	[reply]