Large ftp downloads hanging

When trying to download large (> 5MB) files some transfers just hang
reproducibly.

I tried different servers, different clients and different Linux versions
(2.4 and 2.6) on different computers to no avail.
The transfer just hangs on certain files at a specific size, this is
reproducible.
Transferring the same file using a Windows XP ftp client on the same
computer in the same environment works without a problem.
Example file:
ftp://ftp.suse.com/pub/suse/i386/9.1....1-20.i586.rpm
hangs after 5729680 bytes.

Anyone having any ideas?

Kai

Kai Stuke wrote:
> When trying to download large (> 5MB) files some transfers just hang
> reproducibly.
>
> I tried different servers, different clients and different Linux versions
> (2.4 and 2.6) on different computers to no avail.
> The transfer just hangs on certain files at a specific size, this is
> reproducible.
> Transferring the same file using a Windows XP ftp client on the same
> computer in the same environment works without a problem.
> Example file:
> ftp://ftp.suse.com/pub/suse/i386/9.1....1-20.i586.rpm
> hangs after 5729680 bytes.
>
> Anyone having any ideas?
>
> Kai

You'd better post not that file, but some logs, for example, do this:
wget ftp://remote-host/remote-file.rpm

and post here what wget says when he transfer falls.

Kai Stuke <(E-Mail Removed)> wrote:
> When trying to download large (> 5MB) files some transfers just hang
> reproducibly.

> I tried different servers, different clients and different Linux versions
> (2.4 and 2.6) on different computers to no avail.
> The transfer just hangs on certain files at a specific size, this is
> reproducible.
> Transferring the same file using a Windows XP ftp client on the same
> computer in the same environment works without a problem.

What "environment?"

> Example file:
> ftp://ftp.suse.com/pub/suse/i386/9.1....1-20.i586.rpm
> hangs after 5729680 bytes.

> Anyone having any ideas?

Hangs that occur after a particular number of bytes are downloaded,
and which are reproducible, suggest to me a PPP "environment" where
an XOFF byte (13h) is encountered and not accounted for in the ACCM
map (pppd asyncmap) translation - usually the result of a broken ISP
ACCM implementation, or an improperly initialized modem.

If you are using PPP and the ISP the problem then the probability
is high that adding the pppd option "asyncmap a0000" will serve as
a workaround fix.

--
Clifford Kite Email: "echo xvgr_yvahk-(E-Mail Removed)|rot13"
PPP-Q&A links, downloads: http://ckite.no-ip.net/