dc still reporting collisions
Ceri Davies
setantae at submonkey.net
Sat Nov 15 12:27:50 PST 2003
On Fri, Nov 14, 2003 at 11:14:36PM -0800, Jos Backus wrote:
> On Sat, Nov 15, 2003 at 04:52:14PM +1000, Andy Farkas wrote:
> > The dc(4) driver is still reporting collisions on 100 Mbit full-duplex
> > links:
> [snip]
> > > netstat -i
> > Name Mtu Network Address Ipkts Ierrs Opkts Oerrs Coll
> > dc0 1500 <Link#1> 00:00:e8:89:b9:66 26463 0 26737 13253 225301
>
> Fwiw, I'm seeing the same with tx(4):
>
> lizzy:~% ifconfig tx0
> tx0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
> inet 10.0.0.2 netmask 0xffffff00 broadcast 10.0.0.255
> inet 10.0.0.10 netmask 0xffffffff broadcast 10.0.0.10
> ether 00:e0:29:09:e4:1a
> media: Ethernet autoselect (10baseT/UTP)
> status: active
> lizzy:~% netstat -i
> Name Mtu Network Address Ipkts Ierrs Opkts Oerrs Coll
> tx0 1500 <Link#1> 00:e0:29:09:e4:1a 154423 1 118093 0 253
> tx0 1500 10/24 lizzy 159162 - 122841 - -
> tx0 1500 10.0.0.10/32 lizzy-proxy 28 - 28 - -
> lo0 16384 <Link#2> 5347 0 5347 0 0
> lo0 16384 your-net localhost 442 - 442 - -
> lizzy:~%
>
> It's gotten so bad that I can no longer transfer files from a Windows system
> to this FreeBSD system (both are on the same 10BaseT hub). I only rarely used
> to see collisions before, and filetransfers have always worked just fine. Last
> time I know for sure this worked was October 17th.
These probably are actual collisions though. The OP's point is that collisions
are supposed to be impossible on a full duplex link, whereas in your situation
they aren't.
Ceri
--
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-current/attachments/20031115/a63c8704/attachment.bin
More information about the freebsd-current
mailing list