1) Most users who connect to the server are stupid and they uses windows FTP-clients which uses passive-mode as default and the users have no idea how to turn it of and I'm tired of explaining.
2) Yes, the server supports passive mode, as I said I could forward ports but rather not if it's not necessary.
3) I'm not trying to imply that either. What I was saying was that ip_conntrack_ftp (and possibly ip_nat_ftp, not sure if it's needed) makes passive connections to the outside possible without opening ports and I thought that it might work the other way around too.
I'll restate my questions:
1) Can ip_conntrack_ftp and/or ip_nat_ftp make a note when a server behind the firewall accepts a PASV command and responds with "227 Entering Passive Mode" and then forward and incomming connection to the specifyed port to the server?
2) Where can I find more information about ip_conntrack_ftp and ip_nat_ftp? I've searched but all I could come up with was the sourcecode, which I have neither the knowledge nor the time to analyze.
Main Topics
Browse All Topics





by: mburdickPosted on 2003-06-18 at 09:30:12ID: 8750578
Couple of thigs here...
1) Is it imperative to support passive-mode clients? If so, why?
2) You mention that you are running a third-party FTP server. Have you verified that the server is compliant with the FTP RFC (RFC959)? Passive-mode clients are really a misnomer. The server is the only component of becoming "passive". If the server doesn't support it, it won't work.
3) The ability to use passive mode on the *inside* and connect to a server on the *outside* does not, and will not, imply that passive mode on an *outside* client can, should, or will work with a server on the *inside*.