From owner-freebsd-stable Tue Aug 18 10:11:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA18898 for freebsd-stable-outgoing; Tue, 18 Aug 1998 10:11:15 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from pop.uniserve.com (pop.uniserve.com [204.244.156.3]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id KAA18890 for ; Tue, 18 Aug 1998 10:11:13 -0700 (PDT) (envelope-from tom@uniserve.com) Received: from shell.uniserve.ca [204.244.186.218] by pop.uniserve.com with smtp (Exim 1.82 #4) id 0z8pHE-0000dq-00; Tue, 18 Aug 1998 10:10:32 -0700 Date: Tue, 18 Aug 1998 10:10:30 -0700 (PDT) From: Tom X-Sender: tom@shell.uniserve.ca To: Vadim Belman cc: "freebsd-stable@FreeBSD.ORG" Subject: Re: Intel EtherExpress Pro 10/100B network collisions In-Reply-To: <199808181036.MAA28563@plab.ku.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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" Also, some 3COM switches have some propietary flow options that are only supported by 3COM cards. Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message