Prev: eee pt 2
Next: Upgrading Kernel For First Time.
From: Martin on 24 Jan 2010 13:22 Thanks, with passive mode off the situation seems the same. Actually I do apologise for misleading information in the title of the thread and my original post. I CAN log in, but then when I try to 'ls' it says: 'ls' at 0 [making data connection...] and then after some time: 'ls' at 0 [delaying before reconnect: + seconds counting down] and then it goes back to logging in [ok], making data connection... I also tried: set ssl:verify-certificate off again, with no luck. regards, martin On 01/24/2010 02:06 PM, Helmut Hullen wrote: > Hallo, Martin, > > Du meintest am 24.01.10: > >>>> I can't seem to log in to an ftp account through lftp. Logging in >>>> using just 'ftp' works fine. >>>> When I log in through lftp, it 'hangs' when displaying 'making data >>>> connection'. Is it something to do with ssl or something? > >> Thanks for your reply. My understanding is that the passive mode is >> enabled by default in lftp. Nevertheless, I've tried to set it >> explicitly in /etc/lftp.conf (set ftp:passive-mode on) >> and on the lftp command prompt with no luck, though:( > > And what happens if you set "ftp:passive-mode off"? > > Simple ftp is most times set to "passive off". > > Viele Gruesse > Helmut > > "Ubuntu" - an African word, meaning "Slackware is too hard for me". >
From: Mike Spencer on 25 Jan 2010 00:16
Martin <xtd8865(a)gmail.com> wrote: > Actually I do apologise for misleading information in the title > of the thread and my original post. I CAN log in, but then when I > try to 'ls' it says: > 'ls' at 0 [making data connection...] > and then after some time: > 'ls' at 0 [delaying before reconnect: + seconds counting down] > and then it goes back to logging in [ok], making data connection... Sounds as if you command connection works but the remote host can't open a new connection to your local host for data. I'm supposing that "passive" is off, here, or perhaps the remote host doesn't support PASV protocol command. Are you by any chance runnng iptables? If so, have you failed to issue an iptables command something like this /usr/sbin/iptables -A INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT to permit "related" inbound connections? And if you *do* have such an iptables line, have you modprobed the ipt_state module required to implement the --state switch? Loading the module and adding the command line to /etc/rc.d/rc.local solved a problem with very similar symptoms for me. -- Mike Spencer Nova Scotia, Canada |