Le Lundi 13 Mars 2006 16:12, Carlos E. R. a écrit :
The Monday 2006-03-13 at 11:36 +0100, Matthias Titeux wrote:
If i connect to the computer using sftp (through ssh2), it is working. The problem seems to start after the connection to the server when it entered into the passive mode.
I'm in lazy mode now, so I don't remember which is which; in passive mode the server side firewall is problematic, and in active mode it is the client side firewall which is problematic - or the other way round, I'd have to check, but I wont right now ;-)
And, in recent SuSE versions, this should be handled transparently by the ftp conntrack module.
nimrodel:~ # lsmod | grep conntrack ip_conntrack_ftp 73616 1 ip_nat_ftp ip_conntrack 45624 4 ipt_state,ip_nat_ftp,iptable_nat,ip_conntrack_ftp
Perhaps declaring the ftp port by name instead of number will make the trick, dunno.
This hapens with 2 different computer running opensuse (1 x86_64 and 1 i386). I don't understand the changes between SuSe 9.2 and opensuse in Susefirewall which impair the ftp transfer.
There is no opensuse distro. I suppose you mean suse 10.0 oss.
-- Cheers, Carlos Robinson
Thanks Carlos, Yes I meant SuSE 10.0 oss, sorry for the confusion. I tried to declare ftp instead of port 20 and 21 in Susefirewall (both TCP and UDP) on both the server and the client (2 SuSE 10.0 oss computers). The problem still there ! What is funny is when I tried from A Mac OS X computer (GO> Connect to server> ftp://my-ip-/my-name/) I was able to list the directory !!! I did not specify sftp, but maybe OS X is using it by default.... I Keep trying... Regards Matthias -- ___________________________________________________ Matthias Titeux, PhD Departement de génétique des maladies epithéliums INSERM U563 - CPTP Pavillon Lefebvre, 5ème étage CHU Purpan 31059 Toulouse cedex 03 __________________________________________________