From owner-freebsd-current@FreeBSD.ORG  Tue Sep  2 16:00:46 2003
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id B0C4216A4BF
	for <freebsd-current@freebsd.org>;
	Tue,  2 Sep 2003 16:00:46 -0700 (PDT)
Received: from franky.speednet.com.au (franky.speednet.com.au [203.57.65.5])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 2BB6643FB1
	for <freebsd-current@freebsd.org>;
	Tue,  2 Sep 2003 16:00:45 -0700 (PDT)
	(envelope-from andyf@speednet.com.au)
Received: from hewey.af.speednet.com.au (hewey.af.speednet.com.au
	[203.38.96.242])h82N0g9c046979;	Wed, 3 Sep 2003 09:00:42 +1000 (EST)
	(envelope-from andyf@speednet.com.au)
Received: from hewey.af.speednet.com.au (hewey.af.speednet.com.au
	[203.38.96.242])h82N0eHT005141;	Wed, 3 Sep 2003 09:00:41 +1000 (EST)
	(envelope-from andyf@speednet.com.au)
Date: Wed, 3 Sep 2003 09:00:40 +1000 (EST)
From: Andy Farkas <andyf@speednet.com.au>
X-X-Sender: andyf@hewey.af.speednet.com.au
To: Seishi Hiragushi <s-hrgsh@lapis.plala.or.jp>
In-Reply-To: <20030902071657.1e94e2b4.s-hrgsh@lapis.plala.or.jp>
Message-ID: <20030903085737.L98839-100000@hewey.af.speednet.com.au>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
cc: freebsd-current@freebsd.org
Subject: Re: current: network collition increase
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Sep 2003 23:00:46 -0000

Seishi Hiragushi wrote:

> I noticed that network collition increase, in log of 7/26.
> Such still a state continues.
> What became like this owing to?
>
> 5.1-CURRENT-20030720 (daily run 7/26):
> Network interface status:
> Name    Mtu Network       Address              Ipkts Ierrs    Opkts Oerrs  Coll
> dc0    1500 <Link#1>      00:90:cc:a2:59:56   383420    27   441061     0 260568
> dc0    1500 192.168.200   *****************   374698     -   431325     -     -
> dc1    1500 <Link#2>      00:c0:ca:10:91:89   190866     0   136617  4124 70128
...
> dc0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
>         inet 192.168.200.1 netmask 0xffffff00 broadcast 192.168.200.255
>         inet6 fe80::2c0:caff:fe10:918c%dc0 prefixlen 64 scopeid 0x1
>         ether 00:c0:ca:10:91:8c
>         media: Ethernet autoselect (100baseTX <full-duplex>)
>         status: active

I am seeing the same thing:

team2# netstat -inr
Name    Mtu Network       Address              Ipkts Ierrs    Opkts Oerrs  Coll
dc0    1500 <Link#1>      00:00:e8:89:b9:66  1205836     0   899804 171173 2909941
dc0    1500 172.22.2/28   172.22.2.12        1205560     -   899768     -     -
lo0   16384 <Link#2>                              52     0       52     0     0
lo0   16384 127           127.0.0.1               52     -       52     -     -
team2#
team2# ifconfig dc0
dc0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        inet 172.22.2.12 netmask 0xfffffff0 broadcast 172.22.2.15
        ether 00:00:e8:89:b9:66
        media: Ethernet autoselect (100baseTX <full-duplex>)
        status: active

Collisions shouldn't happen on a full-duplex link?

--

 :{ andyf@speednet.com.au

        Andy Farkas
    System Administrator
   Speednet Communications
 http://www.speednet.com.au/