[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#613068: Could not connect, passive socket

--- On Mon, 14/2/11, David Kalnischkies <kalnischkies+debian@gmail.com> wrote:

> Is were some reason for using 0.8.0 version which is
> somewhere between
> hell and purgatory? Squeeze released with for
> example…

I don't know what is happening. I think the version keeps going up and down. I will manually download a version from unstable for installation. However the problem occurs will all versions. I think if a newer archive fails with the "cannot connect", then I get files from Squeeze instead of from Sid (and maybe the reverse happens too.) 

> I guess ftp isn't used too much nowadays
> especially as the http is a multitude better - and easier
> to provide.

I'm not sure. Why do you think http is better? I have always preferred ftp for files.

> Furthermore the ftp method hasn't seen big changes for
> years (~2006) so i can't reproduce your
> problem.

If I keep repeating:

apt-get update
apt-get update
apt-get update

eventually, I get more and more fragments of the update transferred. However, not all repository records will transfer. I'll try and get some screenshots together to demonstrate this.

> A quick skip over the code suggests that you could disable
> the use of passive mode with Acquire::FTP::Passive, but try to force
> the extended passive mode also which is used (or should) be used for
> IPv6 with
> Acquire::FTP::ForceExtended in contrast to the 'simple'
> PASV as IPv4…

Right. I am using IPv4 internally. I have no IPv6 infrastructure here at the moment.

Do I just stick this line in /etc/apt/apt.conf?

Presumably the defaults have changed, which is why this is broken, or is the problem as a result of server side upgrades? (The problem occurs on several Debian mirrors).


Reply to: