On Thu, Mar 24, 2016 at 06:46:31PM +0100, Jaakov wrote:
On 23.03.2016 19:25, Jaakov wrote:
I'll check and report here. Sorry if it will take a while.
So let me first report the relevant tail of the output of
aptitude -vvvv
in the original, non-anonymous form with ftp mirrors:
[
...
Holen: 1088 ftp://ftp.debian.org/debian jessie-proposed-updates/main
Translation-en [67,9 kB]
Ign ftp://ftp.debian.org/debian jessie-proposed-updates/main Translation-en
Holen: 1089 ftp://ftp.debian.org/debian jessie-backports/non-free amd64
Packages [20,7 kB]
Feh ftp://ftp.debian.org/debian jessie-backports/non-free amd64 Packages
PORT-Befehl konnte nicht gesendet werden. [IP: 130.89.148.12 21]
Holen: 1090 ftp://ftp.debian.org/debian jessie-backports/non-free i386
Packages [19,0 kB]
Feh ftp://ftp.debian.org/debian jessie-backports/non-free i386 Packages
PORT-Befehl konnte nicht gesendet werden. [IP: 130.89.148.12 21]
2.473 kB wurden in 7 min 3 s heruntergeladen (5.840 B/s)
W: The repository 'ftp://ftp.debian.org/debian jessie-proposed-updates
Release' does not have a Release file.
W: The repository 'ftp://ftp.debian.org/debian jessie-backports Release'
does not have a Release file.
W: Herunterladen von ftp://ftp.debian.org/debian/dists/jessie-backports/non-free/binary-amd64/Packages
fehlgeschlagen: PORT-Befehl konnte nicht gesendet werden. [IP: 130.89.148.12
21]
W: Herunterladen von ftp://ftp.debian.org/debian/dists/jessie-backports/non-free/binary-i386/Packages
fehlgeschlagen: PORT-Befehl konnte nicht gesendet werden. [IP: 130.89.148.12
21]
E: Einige Indexdateien konnten nicht heruntergeladen werden. Sie wurden
ignoriert oder alte an ihrer Stelle benutzt.
Aktueller Status: 0 (+0) broken, 0 (+0) upgradable, 37946 (+0) new.
]
It occurred today, on Thu 24 March, at around 18:30 -- 18:40.
Any questions so far? If for few days no reply will occur, I'll switch from
ftp to http and recheck.
There are no questions. The TCP protocol cannot deal with changing
IP addresses. Changing IP address breaks *every* application (except
possibly some UDP based protocols that can deal with loss and changing
IPs..., something like mosh).
Some might fallback to reconnecting transparently, but I think most
don't (especially downloads in web browsers don't or didn't last I
checked).
This is *not* a working internet connection.
That said, there is *no* reason to use the ftp method. It is
*dead*. Do *not* use it. Do use http, instead.
The http method might transparently reconnect, but in the general
case: a connection that reconnects more often than a few hours (that
is, during transfer) is not supported.