Date: Tue, 18 Aug 1998 17:36:16 -0700 (PDT) From: Tom <tom@uniserve.com> To: stephen farrell <stephen@farrell.org> Cc: Vadim Belman <voland@plab.ku.dk>, "freebsd-stable@FreeBSD.ORG" <freebsd-stable@FreeBSD.ORG> Subject: Re: Intel EtherExpress Pro 10/100B network collisions Message-ID: <Pine.BSF.3.96.980818173231.12677D-100000@shell.uniserve.ca> In-Reply-To: <87af51bz66.fsf@couatl.uchicago.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On 18 Aug 1998, stephen farrell wrote: > Tom <tom@uniserve.com> writes: > > > On Tue, 18 Aug 1998, Vadim Belman wrote: > > > > ... > > > Surprisingly, we found that Intel board produces a _huge_ > > > number of network collisions, almost for every output > > > packet. > > ... > > > We have 3COM switches installed in our location. > > > > > > Did anyone experience the same or similar problem with > > > cards in question? > > > > Yes, this will hapen if the card isn't configured with the same duplex > > mode as the switch port it is plugged in. You might just need to do a > > "ifconfig fxp0 mediaopt full-duplex" > > Note that full-duplex can also SLOW your network down. I don't Yes, this setting must match the setting on your port on your switch. If you don't have a switch, it MUST be set to half-duplex. > understand this, and am too looking for answers. However, I switched > a 100+ to full-duplex and went from 10Mbps -> 10bps transfer rates to > a sparc/sol2.5 box on 10baseT LAN (though connections off the LAN were > normal). Clearly some care needs to be taken in how to configure this > card. You probably have your card connected to a hub. This means that you MUST use half-duplex. > -- > > Steve Farrell Tom Systems Support Uniserve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.96.980818173231.12677D-100000>