From owner-freebsd-net@FreeBSD.ORG Mon Jul 11 18:49:46 2005 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DE7E116A41C for ; Mon, 11 Jul 2005 18:49:46 +0000 (GMT) (envelope-from drgenio@gmail.com) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.193]) by mx1.FreeBSD.org (Postfix) with ESMTP id 783F043D46 for ; Mon, 11 Jul 2005 18:49:46 +0000 (GMT) (envelope-from drgenio@gmail.com) Received: by wproxy.gmail.com with SMTP id 55so969875wri for ; Mon, 11 Jul 2005 11:49:45 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=j432uIa2JYMt0otH6NmuvM9b+TKBcsa7Xf3qLmXfpyBy4r7/0NYyQpIUfbRD1P4m4Va7K/YUUducMTKJNyjx/2bdlEzAv/dM/m77gzTpE4d1ZYZE2yRSWSlIBYxVC/Pka4VgyJEBRzNJ/y+xZ2eIG5HplxO+dY38YimZ4Nr7E4Y= Received: by 10.54.45.1 with SMTP id s1mr4053714wrs; Mon, 11 Jul 2005 11:49:22 -0700 (PDT) Received: by 10.54.3.59 with HTTP; Mon, 11 Jul 2005 11:49:22 -0700 (PDT) Message-ID: <25a1a09905071111492f7b10c4@mail.gmail.com> Date: Mon, 11 Jul 2005 15:49:22 -0300 From: =?ISO-8859-1?Q?Hern=E1n_Freschi?= To: freebsd-net@freebsd.org In-Reply-To: <000301c5863f$e6c59fe0$0200a8c0@satellite> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <000301c5863f$e6c59fe0$0200a8c0@satellite> Subject: Re: two 3C905B's in 5.4 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: =?ISO-8859-1?Q?Hern=E1n_Freschi?= List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Jul 2005 18:49:47 -0000 2005/7/11, dave : > I've got a 5.4 box that's going to be a router. It has two 3C905B car= ds Well I'm not sure if this helps, but I've read that old 3C905's, esp. rev. A have lots of issues, which were solved on Rev. C. 3COM does weird things sometimes, for example, the 3C509 (not 905) don't detect full duplex properly, because they were released before the MDI standard. Try setting it to 10/half, 10/full, 100/half and 100/full and see if they work OK.