From owner-freebsd-questions@FreeBSD.ORG Fri Jul 4 07:32:04 2003 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 3189C37B401 for ; Fri, 4 Jul 2003 07:32:04 -0700 (PDT) Received: from rwcrmhc11.comcast.net (rwcrmhc11.comcast.net [204.127.198.35]) by mx1.FreeBSD.org (Postfix) with ESMTP id 891FD43FDF for ; Fri, 4 Jul 2003 07:32:03 -0700 (PDT) (envelope-from freebsd-questions-local@be-well.no-ip.com) Received: from be-well.ilk.org (be-well.no-ip.com[24.147.188.198]) by comcast.net (rwcrmhc11) with ESMTP id <20030704143203013009levpe>; Fri, 4 Jul 2003 14:32:03 +0000 Received: from be-well.ilk.org (lowellg.ne.client2.attbi.com [24.147.188.198] (may be forged)) by be-well.ilk.org (8.12.9/8.12.9) with ESMTP id h64EW2ro002762; Fri, 4 Jul 2003 10:32:02 -0400 (EDT) (envelope-from freebsd-questions-local@be-well.no-ip.com) Received: (from lowell@localhost) by be-well.ilk.org (8.12.9/8.12.6/Submit) id h64EW15r002759; Fri, 4 Jul 2003 10:32:01 -0400 (EDT) X-Authentication-Warning: be-well.ilk.org: lowell set sender to freebsd-questions-local@be-well.ilk.org using -f Sender: lowell@be-well.no-ip.com To: "Moriarty" References: <000d01c34002$dc08c3a0$2201040a@aidan> <44u1a5c9ec.fsf@be-well.ilk.org> <006401c340a4$786428b0$2201040a@aidan> From: Lowell Gilbert Date: 04 Jul 2003 10:32:01 -0400 In-Reply-To: <006401c340a4$786428b0$2201040a@aidan> Message-ID: <44znjuqs66.fsf@be-well.ilk.org> Lines: 17 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii cc: freebsd-questions@freebsd.org Subject: Re: Throttled ethernet connection X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: freebsd-questions@freebsd.org List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Jul 2003 14:32:04 -0000 "Moriarty" writes: > I have the ethernet card forced to 100mbit full duplex via rc.conf. The > switch is a Netgear FS108. How would i solve a duplex mismatch? If you've got a duplex mismatch, it's because the switch isn't doing its own autosensing properly. Try forcing the switch to the same settings as those to which you forced the NIC, if you can. If you can't (which I would expect in a device at such a low price), then set different settings on the NIC, or even try letting the card autosense too. Unfortunately, autosensing has always had a few interoperability problems, although they are *much* less common than they were five years ago. [Five years ago was the last time I worked on it myself...] Good luck.