From owner-freebsd-stable Sat May 22 3:39:38 1999 Delivered-To: freebsd-stable@freebsd.org Received: from calumet.infoteam.com (calumet.infoteam.com [207.246.83.3]) by hub.freebsd.org (Postfix) with ESMTP id A24B314E7F for ; Sat, 22 May 1999 03:39:35 -0700 (PDT) (envelope-from kmartin@infoteam.com) Received: (from kmartin@localhost) by calumet.infoteam.com (8.8.8/8.8.8) id GAA05331; Sat, 22 May 1999 06:39:32 -0400 (EDT) (envelope-from kmartin) Date: Sat, 22 May 1999 06:39:32 -0400 From: Kenn Martin To: Tom Cc: freebsd-stable@freebsd.org Subject: Re: Debugging a stalled connection Message-ID: <19990522063932.A5273@infoteam.com> References: <19990520163439.B15580@infoteam.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: ; from Tom on Thu, May 20, 1999 at 04:57:13PM -0700 Organization: InfoTeam Corp, Lexington X-Phone: 1 606 335 7233 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, May 20, 1999 at 04:57:13PM -0700, Tom wrote: > On Thu, 20 May 1999, Kenn Martin wrote: > > > I have a number of machines running 3.2-STABLE with no problem, except one, > > an "old" Pentium 200. It has an Intel PRO/100+ Server Adapter (fxp0), two > > IDE disks, and 1 IDE CDROM drive (dmesg below). This also was happening > > in later builds of 3.1-STABLE. > > > > Large transfers, such as an NFS-mount installworld or a ftp get of a file > > over approx 1MB, will stall regularly and indefinately. > > > > No other operation appears to be affected and I can start another ssh > > session with the "stalled" machine. > > > > How should I go about debugging this problem? > > "netstat -i" will give you interface error counts. > > "netstat" will the status of all network connections. > > Check everything between the stalled machine and the client. This > includes routers, switches, hubs, and cabling. Check error counters on > all intervening equipment. I've done all of this with no success. One fast ethernet switch between the 2, 3.2-STABLE systems. No errors reported anywhere, other than occasionally from NFS (server not responding) on the client "problem" machine. > Try switching MTU path discovery off. Misconfigured routers will break > MTU discovery. Turn off TCP extensions. Broken routers and clients will > not handle TCP extensions properly. Is this with "mtu 0" on the ifconfig command? Putting it in rc.conf doesn't seem to work. TCP extensions are off (the default). thanks, kenn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message