From owner-freebsd-bugs Fri Jan 23 09:30:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA21579 for freebsd-bugs-outgoing; Fri, 23 Jan 1998 09:30:02 -0800 (PST) (envelope-from owner-freebsd-bugs@FreeBSD.ORG) Received: (from gnats@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA21555; Fri, 23 Jan 1998 09:30:01 -0800 (PST) (envelope-from gnats) Date: Fri, 23 Jan 1998 09:30:01 -0800 (PST) Message-Id: <199801231730.JAA21555@hub.freebsd.org> To: freebsd-bugs Cc: From: Stefan `Sec` Zehl Subject: Re: misc/5539: ftp problems with ftp.freebsd.org ? "Transfer aborted. Data connection closed" Reply-To: Stefan `Sec` Zehl Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR misc/5539; it has been noted by GNATS. From: Stefan `Sec` Zehl To: Bill Fenner Cc: FreeBSD-gnats-submit@freebsd.org Subject: Re: misc/5539: ftp problems with ftp.freebsd.org ? "Transfer aborted. Data connection closed" Date: Fri, 23 Jan 1998 18:20:15 +0100 On Wed, Jan 21, 1998 at 10:10:32AM -0800, Bill Fenner wrote: > There are two strange things about that tcpdump: > 1. There are a lot of retransmitted packets. It looks like there's a lot > of loss between you and ftp.freebsd.org . What does "ping" say? --- wcarchive.cdrom.com ping statistics --- 100 packets transmitted, 67 packets received, 33% packet loss round-trip min/avg/max/stddev = 388.462/656.853/2237.680/393.681 ms > 2. The connection was closed cleanly by your end, implying that ncftp > was the one that closed the connection. Does ncftp have a timeout? > Have you tried setting it larger? I tried it again with "fetch" and it worked that time, so i suspect some problem in ncftp :) - thanks for your help, keep up that good work. CU, Sec -- Eighty megabytes and continuosly swapping Escape Meta Alt Control Shift Emacs makes all computers slow -- So better go to http://www.math.fu-berlin.de/~guckes/vim/