Subject: kern/35715: Networking broken
To: None <kern-bug-people@netbsd.org, gnats-admin@netbsd.org,>
From: None <ad@netbsd.org>
List: netbsd-bugs
Date: 02/19/2007 18:40:00
>Number:         35715
>Category:       kern
>Synopsis:       Networking broken
>Confidential:   no
>Severity:       serious
>Priority:       high
>Responsible:    kern-bug-people
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Mon Feb 19 18:40:00 +0000 2007
>Originator:     Andrew Doran
>Release:        NetBSD 4.99.11
>Organization:
The NetBSD Project
>Environment:
Architecture: i386
Machine: i386
>Description:
Networking is broken for me with this card:

bge0 at pci4 dev 0 function 0: Broadcom BCM5721 Gigabit Ethernet
bge0: interrupting at ioapic0 pin 16 (irq 5)
bge0: ASIC BCM5751 A1 (0x4101), Ethernet address 00:13:72:3d:ba:4c
bge0: setting short Tx thresholds
brgphy0 at bge0 phy 1: BCM5750 1000BASE-T media interface, rev. 0

bge0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500
        capabilities=3f80<TSO4,IP4CSUM_Rx,IP4CSUM_Tx,TCP4CSUM_Rx,TCP4CSUM_Tx,UDP4CSUM_Rx,UDP4CSUM_Tx>
        enabled=0
        address: 00:13:72:3d:ba:4c
        media: Ethernet autoselect (100baseTX full-duplex,flowcontrol,rxpause,txpause)
        status: active
        inet 192.168.1.200 netmask 0xffffff00 broadcast 192.168.1.255
        inet6 fe80::213:72ff:fe3d:ba4c%bge0 prefixlen 64 scopeid 0x1
>How-To-Repeat:
When trying to connect to other hosts, ARP requests are sent and replied
to, but the affected system does not see the replies properly. Viewed with
tcpdump, the system is seeing junk returned on the link where the ARP reply
should be:

17:08:19.282333 arp who-has 192.168.1.100 tell 192.168.1.200
17:08:19.282565 27:1b:5a:63:08:06 sap 00 > 72:3d:ba:4c:00:90 sap 08 I (s=3,r=2,C) len=42

The Ethernet address of the replying host is 00:90:27:1b:5a:63; it looks
almost like 2 bytes are being dropped off the head of the received packet.

When I patch in the Ethernet address of the target host using arp -s, and
ping it, I see the replies with tcpdump but they are similarly corrupted.
>Fix:
Sorry, no idea.