From owner-freebsd-questions@FreeBSD.ORG Sat Dec 11 19:51:04 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 96A5516A4CE for ; Sat, 11 Dec 2004 19:51:04 +0000 (GMT) Received: from pi.codefab.com (pi.codefab.com [199.103.21.227]) by mx1.FreeBSD.org (Postfix) with ESMTP id 472D843D53 for ; Sat, 11 Dec 2004 19:51:04 +0000 (GMT) (envelope-from cswiger@mac.com) Received: from [192.168.1.250] (pool-68-160-207-47.ny325.east.verizon.net [68.160.207.47]) by pi.codefab.com (8.12.11/8.12.11) with ESMTP id iBBJp1TV078556 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 11 Dec 2004 14:51:03 -0500 (EST) Message-ID: <41BB4FA6.3070308@mac.com> Date: Sat, 11 Dec 2004 14:51:02 -0500 From: Chuck Swiger Organization: The Courts of Chaos User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.3) Gecko/20040910 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Gerard Samuel References: <41BB461C.2050603@trini0.org> In-Reply-To: <41BB461C.2050603@trini0.org> X-Enigmail-Version: 0.86.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-questions Subject: Re: sleepy fxp0 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 11 Dec 2004 19:51:04 -0000 Gerard Samuel wrote: [ ... ] > This box currently uses DHCP to get its IP address. > When it boots up, and I log in, and immediately try to > initiate any network activity from this box, it takes about > 2-3 seconds for said network activity to start. > For example, if I were to ping, or startx, it takes > about 2-3 seconds for either ping or startx to actually start. [ ... ] > Is this normal? That sounds more like the puase associated with doing IPv6 versus a IPv4 DNS lookup, assuming it happens when you are trying to ping some remote IP...? You might also be seeing a pause due to ethernet autoselection; if you manually configure the interface and the switch port to manual 100/FD, doing so might also remove a brief pause. [Fixing the speed is impractical for a roaming laptop, but it might be worth trying as a test... ] -- -Chuck