Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
In active FTP the control session is opened Client dynamic port to Server well known port(21). When you initiate a transfer the client opens a dynamic passive port and informs the servers of that port number. The server then connects to the client on that port to shift the data along.
So if your server is on the outside of your NAT its data connection is going to bounce off of the NAT translation table as the NAT device has no knowledge of the passive open port. To make this work the NAT device would need to be able to snoop on the control connection to see what port was agreed on between the client and the server. As far as I know this is not possible, and is what passive FTP was invented to get around anyway.
Hi,
thanks for your replies, baldy3105 you are right about active FTP, but there is a workaround. I did some reading and if you enable these two kernel modules, the computers behind the NAT can create active ftp connections.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.