Carlos E. R. wrote:
The Saturday 2005-12-10 at 08:49 +0100, wavesurf@planet.nl wrote:
¿Could be the router? No because with the susefirewall off it's working.
I meant the double ping.
...
By the way, I just read that "pasive" ftp is dificult to setup in the server firewall, because it needs to open an arbitrary high port on request from the client. This port is unknown before hand, it is different for each new client, and it has to be opened on the fly. The firewall has to keep track of the ftp connection and open the needed port when it is needed.
I have no idea how this is handled by SuSEfirewall nowdays, the doc I read is old.
On the other hand, "Active" is easier on the server side, but more dificult on the client. You might try active.
Active ftp doesn't work well with address translation or firewalls.