From owner-freebsd-questions  Tue May 22  8:54:11 2001
Delivered-To: freebsd-questions@freebsd.org
Received: from kt-exchange.edmonton.kanotech.net (edtn016788.hs.telusplanet.net [161.184.241.24])
	by hub.freebsd.org (Postfix) with ESMTP id 83E4E37B424
	for <freebsd-questions@FreeBSD.org>; Tue, 22 May 2001 08:54:07 -0700 (PDT)
	(envelope-from moligny@kanotech.com)
content-class: urn:content-classes:message
Subject: RE: Network Collisions
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 22 May 2001 09:54:06 -0600
Message-ID: <76928F3E231DE4478876350F08358336044A86@kt-exchange.edmonton.kanotech.net>
X-MimeOLE: Produced By Microsoft Exchange V6.0.4417.0
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Network Collisions
Thread-Index: AcDi06Dh2Fe1aNOVSkiZjFyS7viShgAAwjlA
From: "Mike Oligny" <moligny@kanotech.com>
To: "C J Michaels" <cjm2@27in.tv>
Cc: "FreeBSD Questions" <freebsd-questions@FreeBSD.org>
Sender: owner-freebsd-questions@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-questions.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-questions>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-questions>
X-Loop: FreeBSD.ORG

Yours doesn't seem to say half or full duplex.  Take a look at mine.. =20

rl0: flags=3D8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        inet 192.168.1.2 netmask 0xffffff00 broadcast 192.168.1.255
        inet6 fe80::248:54ff:fe6c:2013%rl0 prefixlen 64 scopeid 0x1=20
        ether 00:48:54:6c:20:13=20
        media: autoselect (100baseTX <full-duplex>) status: active
        supported media: autoselect 100baseTX <full-duplex> 100baseTX
10baseT/UTP <full-duplex> 10baseT/UTP 100baseTX <hw-loopback>

Regardless, I would suggest one of three things -- 1) don't worry about
the collisions - they are a normal ethernet phenomenon and occur
whenever two devices on the segment broadcast at exactly the same
moment. 2) Get yourself a switch.  3) Try to find a way to set that NIC
to half duplex.  ifconfig will do it, I believe, but I don't know the
syntax for setting link/media options...

Good luck!

(corrections welcome)

-----Original Message-----
From: C J Michaels [mailto:cjm2@27in.tv]
Sent: Tuesday, May 22, 2001 9:28 AM
To: Mike Oligny
Cc: FreeBSD Questions
Subject: RE: Network Collisions


Mike,

Thanks for the suggestion, that is something I forgot to mention.  I
believe
it is set to half-duplex.  Here is the output of ifconfig, correct me if
I'm
wrong.

Thanks
--Chris


fxp0: flags=3D8943<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        inet 10.0.0.1 netmask 0xffffff00 broadcast 10.0.0.255
        ether 00:90:27:37:22:7f
        media: 100baseTX status: active
        supported media: autoselect 100baseTX <full-duplex> 100baseTX
10baseT/UTP <full-duplex> 10baseT/UTP 100baseTX <hw-loopback>


-----Original Message-----
From: Mike Oligny [mailto:moligny@kanotech.com]
Sent: Tuesday, May 22, 2001 11:19 AM
To: C J Michaels; FreeBSD Questions
Subject: Network Collisions


Just a thought...

Try setting fxp0 to half duplex.  From what I have seen, most cheap hubs
can't deal with full duplex very well.

-----Original Message-----
From: C J Michaels [mailto:cjm2@27in.tv]
Sent: Tuesday, May 22, 2001 8:59 AM
To: FreeBSD Questions
Subject: Errors and Colls with nic


Hi,

I have a FreeBSD 4.3-STABLE box with two network interfaces ed0 and
fxp0.
.
.
.
[snip]


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message