Hey dude,
On Sat, 2006-08-05 at 17:17 +, Dark Dude wrote:
It seems that setting up an up to date firewall (e.g. iptables or SuSE
firewall), breaks the ability of midnight commander to ftp properly.
Is the FTP connection tracking module loaded? What's the output of
$ /sbin/lsmod | grep
Hello,
On Sat, 5 Aug 2006, Dark Dude wrote:
It seems that setting up an up to date firewall (e.g. iptables or SuSE
firewall), breaks the ability of midnight commander to ftp properly. Even if
someone turns off the passive mode in VirtualFS settings, still the ftp ends
broken (no files or
Case #1, SuSE 10.0 + vsftpd.
220 (vsFTPd 2.0.3)
MC -- remote_is_amiga = 0
USER cdaemon
331 Please specify the password.
PASS Password not logged
230 Login successful.
PWD
257 /backup/cdaemon
PORT 82,103,131,117,184,164
200 PORT command successful. Consider using PASV.
TYPE A
200 Switching to
Hello,
What happens when you use passive mode ?
On Sun, 6 Aug 2006, Dark Dude wrote:
Case #1, SuSE 10.0 + vsftpd.
[...]
PORT 82,103,131,117,184,164
200 PORT command successful. Consider using PASV.
Case #2, CentOS 4.3 + proftpd.
[...]
PORT 88,198,36,130,23,131
200 PORT command successful
Hello all,
It seems that setting up an up to date firewall (e.g. iptables or SuSE
firewall), breaks the ability of midnight commander to ftp properly. Even if
someone turns off the passive mode in VirtualFS settings, still the ftp ends
broken (no files or dirs are shown into the related window).
