Subject: Again: AT-2700FX (maybe others also) - netstat -i output strangeness
To: None <netbsd-users@netbsd.org>
From: Michael Kukat <michael@unixiron.org>
List: netbsd-users
Date: 05/09/2003 22:55:20
Hello again,
ever seen something like this?
# netstat -ni
Name Mtu Network Address Ipkts Ierrs Opkts Oerrs Colls
pcn0 1500 <Link> 00:a0:d2:2f:29:07 237301 0 0 12018 0
pcn0 1500 fe80::/64 fe80::2a0:d2ff:fe 237301 0 0 12018 0
pcn0 1500 192.168.177 192.168.177.200 237301 0 0 12018 0
pcn1 1500 <Link> 00:60:b0:5c:42:96 11 0 2 0 0
pcn1 1500 fe80::/64 fe80::260:b0ff:fe 11 0 2 0 0
pcn1 1500 192.168.20 192.168.20.1 11 0 2 0 0
lo0 33220 <Link> 40 0 40 0 0
lo0 33220 fe80::/64 fe80::1 40 0 40 0 0
lo0 33220 ::1/128 ::1 40 0 40 0 0
lo0 33220 127 127.0.0.1 40 0 40 0 0
where: pcn0 = PCI AMD PCnet 10/100 (AT-2700FX), pcn1 = PCI AMD PCnet 10MBit
(HP Vectra builtin adapter), lo0 should be known.
Look ar Opkts and Oerrs and compare between the adapters... What is going on
here? pcn0 id fiber, so quite error-free, and the network works fine and with
good performance. And how can we produce 12018 errors in 0 packets? :)
The wrong counter counted up?
dmesg excerpts:
pcn0 at pci0 dev 6 function 0: AMD PCnet-PCI Ethernet
pcn0: Am79c972 PCnet-FAST+ rev 6, Ethernet address 00:a0:d2:2f:29:07
pcn0: interrupting at irq 9
lxtphy0 at pcn0 phy 1: LXT970 10/100 media interface, rev. 3
lxtphy0: 100baseFX, 100baseFX-FDX, 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
pcn1 at pci0 dev 11 function 0: AMD PCnet-PCI Ethernet
pcn1: Am79c970A PCnet-PCI II rev 6, Ethernet address 00:60:b0:5c:42:96
pcn1: interrupting at irq 9
pcn1: 10base5, 10base5-FDX, 10baseT, 10baseT-FDX, auto, auto-FDX
...Michael
--
http://www.unixiron.org/ Home Powered by: (Net|Open|Free)BSD IRIX NonStop-UX
Solaris AIX HP-UX Tru64 MUNIX Ultrix VMS SINIX Dolphin_Unix OpenStep MacOS A/UX