From owner-freebsd-current@FreeBSD.ORG Thu Apr 19 10:03:37 2007 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 3D50916A400 for ; Thu, 19 Apr 2007 10:03:37 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.freebsd.org (Postfix) with ESMTP id D97E013C457 for ; Thu, 19 Apr 2007 10:03:36 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id 5C8CD470F6; Thu, 19 Apr 2007 06:03:36 -0400 (EDT) Date: Thu, 19 Apr 2007 11:03:36 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Krassimir Slavchev In-Reply-To: <46272B99.9090100@bulinfo.net> Message-ID: <20070419105902.L2913@fledge.watson.org> References: <46272B99.9090100@bulinfo.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-current@freebsd.org Subject: Re: network problems? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 19 Apr 2007 10:03:37 -0000 On Thu, 19 Apr 2007, Krassimir Slavchev wrote: > The problem is when I try to access ftp servers, the connection stalls > randomly. Also I can't do cvsup and fetch. This happens only with machines > running -current and when the traffic is passed through router based on > FreeBSD 4.4. One of the test machines is my notebook which have installed > 7.0-CURRENT (from today) and 5.4-STABLE and I see this problem only with > -current. > > Is there any new features in -current tcp stack which may be incompatible > with FreeBSD 4.x? No, not in principle, and ideally also not in practice. Sounds like a bit more diagnosis is needed, though. The first thing we should try to determine if this is a problem with a device driver, the network stack, or applications. If you run ping on one terminal to the local router, does it experience problems at the same time as other applications? I.e., does ftp stallage align with ping stallage? Are there any console messages suggesting driver problems, such as messages about interrupts, timeouts, and so on? If you run "vmstat -i", is there any device with an extraordinarily high interrupt rate (second column over 10000 or so)? Could you try doing your network tests directly with the local router and avoid using the wide area network? This would help avoid having wide area issues affect your testing, and also demonstrate whether or not you can reproduce it in a purely local setup (much easier to debug). Robert N M Watson Computer Laboratory University of Cambridge