From owner-freebsd-questions Wed Apr 22 18:10:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA27221 for freebsd-questions-outgoing; Wed, 22 Apr 1998 18:10:56 -0700 (PDT) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from coal.sentex.ca (coal.sentex.ca [209.112.4.16]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA27158 for ; Thu, 23 Apr 1998 01:10:21 GMT (envelope-from mike@sentex.net) Received: from gravel (ospf-mdt.sentex.net [205.211.164.81]) by coal.sentex.ca (8.8.8/8.8.7) with SMTP id VAA26767; Wed, 22 Apr 1998 21:10:10 -0400 (EDT) (envelope-from mike@sentex.net) Message-Id: <3.0.2.32.19980422205729.029e6320@sentex.net> X-Sender: mdtancsa@sentex.net X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.2 (32) Date: Wed, 22 Apr 1998 20:57:29 -0400 To: Doug White From: Mike Tancsa Subject: Re: How to reset an fxp ethernet interface Cc: questions@FreeBSD.ORG In-Reply-To: References: <199804221920.PAA29587@granite.sentex.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 05:48 PM 4/22/98 -0700, Doug White wrote: >On Wed, 22 Apr 1998, Mike D Tancsa wrote: >Thoughts: > >1. The cable makes all the difference in 100mbit. Crappy cable gets you >crappy performance. Also, bad cabling can trick the hub into downing you >to 10mbit (where 926k/s would be a great xfer rate). > >2. Try forcing the port speed in the hub. Autodetection is still pretty >new and isn't fully reliable. Hi Doug, Thanks for replying. The Hub is permanently set to 100BT Full duplex via dip switch. However, it is quite possible that it is infact 'downgrading' me to 10BaseT without me knowing it, although the LEDs would *seem* to indicate otherwise. The swithcing HUB is an Addtron. Perhaps when the budget permits, we will invest in a better one with monitoring capabilities, but for now I am stuck with it :-( The odd thing about the cable though is that once I reboot the FreeBSD box with the second cable, I am back to my good fast throughput without any interface errors on 200Mbytes of transfer. Then, again when I pull the cable out and plug back in the other, I am back to the same problem of slower throughput. The more I think about it, the more it feels like its the HUB trying to 'compensate', but alas, I cannot control that variable :( Is there anyway to get more stats out of the interface on the FreeBSD end of things that you or anyone knows of ? ---Mike ********************************************************************** Mike Tancsa (mike@sentex.net) * To do is to be -- Nietzsche Sentex Communications Corp, * To be is to do -- Sartre Cambridge, Ontario * Do be do be do -- Sinatra (http://www.sentex.net/~mdtancsa) * To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message