From owner-freebsd-questions@FreeBSD.ORG Sat Dec 11 21:31:51 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 42ABF16A4CE for ; Sat, 11 Dec 2004 21:31:51 +0000 (GMT) Received: from sccrmhc11.comcast.net (sccrmhc11.comcast.net [204.127.202.55]) by mx1.FreeBSD.org (Postfix) with ESMTP id C3A5E43D41 for ; Sat, 11 Dec 2004 21:31:50 +0000 (GMT) (envelope-from fbsd-questions@trini0.org) Received: from hivemind.trini0.org (trini0.org[65.34.205.195]) by comcast.net (sccrmhc11) with ESMTP id <2004121121314801100evn36e>; Sat, 11 Dec 2004 21:31:48 +0000 Received: from [192.168.0.16] (gladiator.trini0.org [192.168.0.16]) by hivemind.trini0.org (Postfix) with ESMTP id 5DE2160C6; Sat, 11 Dec 2004 16:31:47 -0500 (EST) Message-ID: <41BB6745.7090906@trini0.org> Date: Sat, 11 Dec 2004 16:31:49 -0500 From: Gerard Samuel User-Agent: Mozilla Thunderbird 0.9 (X11/20041114) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Chuck Swiger References: <41BB461C.2050603@trini0.org> <41BB4FA6.3070308@mac.com> In-Reply-To: <41BB4FA6.3070308@mac.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-questions Subject: [Solved] 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 21:31:51 -0000 Chuck Swiger wrote: > 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... ] Well you pushed me in the right direction to solve this. Looking over the man pages for ifconfig and rc.conf, here is what I did. 1. Figure out what media options are available for the card $ ifconfig -m fxp0 fxp0: flags=8843 mtu 1500 options=8 capability list: =8 inet 192.168.0.16 netmask 0xffffff00 broadcast 192.168.0.255 ether 00:80:29:65:e2:96 media: Ethernet autoselect (100baseTX ) status: active supported media: media autoselect media 100baseTX mediaopt full-duplex media 100baseTX media 10baseT/UTP mediaopt full-duplex media 10baseT/UTP media 100baseTX mediaopt hw-loopback 2. According to the rc.conf man page, I added a file /etc/start_if.fxp0 with -> ifconfig fxp0 media 100baseTX mediaopt full-duplex To manually set media and media options at bootup. Thats it. I rebooted, and the network is available immediately at bootup, instead of waiting a few seconds to auto configure. Thanks