*BSD News Article 91018


Return to BSD News archive

Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!msunews!news.mtu.edu!newsxfer.itd.umich.edu!newsxfer3.itd.umich.edu!howland.erols.net!worldnet.att.net!cbgw2.lucent.com!nntphub.cb.lucent.com!news
From: Bernhard Suter <suter@dnrc.bell-labs.com>
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: 100BaseT ?
Date: Thu, 13 Mar 1997 22:09:11 -0500
Organization: Lucent Bell Labs - Holmdel
Lines: 15
Message-ID: <3328C157.41C67EA6@dnrc.bell-labs.com>
NNTP-Posting-Host: machiavelli.dnrc.bell-labs.com
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Mailer: Mozilla 3.01Gold (X11; I; FreeBSD 2.1.5-RELEASE i386)
Xref: euryale.cc.adfa.oz.au comp.unix.bsd.freebsd.misc:37045

Is anybody using 100BaseT ethernet with FreeBSD? Some of the supported
ethernet cards are 10/100 (fxp0 - Intel EtherExpress Pro/100, de0 - DEC
DC21140, vx0 - 3Com 3c590). Shouldn't they autonegotiate to 100BaseT
when connected to a 100BaseT network? I have tried to connect two
FreeBSD 2.1.5 machines with Intel and DEC chip based cards with an
ethernet X-wire - the 100 LED goes on but packets cannot be transmitted
without errors. (seems like some PHY config problem in the driver...)

Is it correct that fast ethernet hosts should only use the "standard"
IEEE 802.2 encapsulation (RFC 1042) and not the classical Ethernet
ecapsulation (RFC 894)? Is this beeing observed by other OS? As far as I
can see, the Ethernet sublayer in FreeBSD only supports the RFC 894
style encapsulation for IP. If this is a problem are there any fixes?

Bernhard