Comment 1 for bug 130682

Revision history for this message
Carsten Menke (carsten-menke) wrote :

Bug could be closed,

I was faced by set of obscurities leading to this behavior. In fact it was the router. Maybe we can have this bug as a reference here so that other people who stumble about the same thing find it.

I'm using a Bintec R232bw Router, the Router can do statefull firewalling, but what is not mentioned in the docs is, that this router does not also do related connection tracking but also modifies the FTP Protocol that it rewrites the Address in the PASV response. However the route does not seem to suppport the EPSV mode, so when I used my command line client, which issued a EPSV command the packets came unmodified throug and the passive mode worked.

However the browser and Filezilla use the PASV command which in turn has been modified by the Router as well as for the port and address part. Additionally I had of course a Port Forwarding on the Router forwarding the defined passive port range to the Server.

This all together leaded to this result. The sad thing is, if I would have done this without any knowledge how FTP works I would be done in 1 minute, as the Bintec R232bw just needs a Portforwarding on Port 21 and one rule allowing port 21 in and you're all done, as the rest is done by the router's magic