From owner-freebsd-questions Wed Apr 22 22:17:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA05541 for freebsd-questions-outgoing; Wed, 22 Apr 1998 22:17:02 -0700 (PDT) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA05516 for ; Wed, 22 Apr 1998 22:16:56 -0700 (PDT) (envelope-from root@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id WAA17888; Wed, 22 Apr 1998 22:15:12 -0700 (PDT) Message-Id: <199804230515.WAA17888@implode.root.com> To: Mike Tancsa cc: questions@FreeBSD.ORG Subject: Re: How to reset an fxp ethernet interface In-reply-to: Your message of "Wed, 22 Apr 1998 20:57:29 EDT." <3.0.2.32.19980422205729.029e6320@sentex.net> From: David Greenman Reply-To: dg@root.com Date: Wed, 22 Apr 1998 22:15:12 -0700 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Is there anyway to get more stats out of the interface on the FreeBSD end >of things that you or anyone knows of ? The only thing you can find out currently is what mode the card is set to - auto or forced 10/100 half/full. When it is set to auto, the hardware does the negotiation and FreeBSD doesn't know about it. In the auto case it would be possible to add additional code that asks the hardware what mode it is currently in, but even with that, we don't have an established way of reporting that information. It sounds to me like the hardware isn't negotiating the duplex properly. The PHY (physical interface) will default to half duplex if the negotiation fails. If the switch is hard configured for full duplex, then you'd have a problem. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message