Subject: Re: If_sip and FA311 checksum error
To: None <netbsd-bugs@netbsd.org>
From: Jeff Arenberg <jeffa9999@yahoo.com>
List: netbsd-bugs
Date: 12/27/2001 02:12:27
Well, I took the FA311 out of the NetBSD box and put it into a Dell machine,
installed the driver and it works perfectly well there.  I ran ipconfig /all
and found the MAC number matches the value below, so that wasn't the issue.
I took the Ethernet card from the Dell and put it in to the NetBSD box and
it uses the tlp driver.  At first I had a similar problem with no network
access, then I changed the IP number for the ifconfig.tlp0 to a different
number than before and that magically fixed the problem!!  I suppose I
should swap the FA311 card back again to test, but its working now so I
shouldn't break it again!

Bottom line, swapping cards/drivers and keeping the same IP number causes
some problem somewhere.  Better informed people should test that out.

Thanks,
Jeff

> I put a brand new NetGear FA311 10/100 Ethernet board in a working 1.5.2
> i386 NetBSD box (replacing a D-Link 530/TX card), using the generic kernel
> and with /etc/ifconfig.sip0 installed and I get the following from dmesg:
> 
> sip0 at pci0 dev 9 function 0: NatSemi DP83815 10/100 Ethernet
> sip0: interrupting at irq 10
> sip0: Checksum (bf) mismatch (7f)sip0: Ethernet address 00:02:e3:18:ab:98
> ukphy0 at sip0 phy 0: Generic IEEE 802.3u media interface
> 
> The Checksum error seems to be very serious.  I'm guessing the MAC address
> is being read incorrectly.
> 
> Ifconfig sip0 reports:
> 
> sip0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
>       address: 00:02:e3:18:ab:98
>       media: Ethernet autoselect (100baseTX full-duplex)
>       status: active
>       inet 192.168.0.11 netmask 0xffffff00 broadcast 192.168.0.255
>       inet6 fe80::202:e3ff:fe18:ab98%sip0 prefixlen 64 scopeid 0x1
> 
> I have link and activity lights and I can ping the board in a loop, but all
> other net access is down.  A tcpdump reports problems with arp which makes
> sense if the MAC is wrong.  I've also tried the 12/21/2001 current i386
> kernel with the same results.
> 
> Before I brave the return line at Fry's can anyone suggest a solution?
> 
> Thanks,
> Jeff
> 
> 
> _________________________________________________________
> Do You Yahoo!?
> Get your free @yahoo.com address at http://mail.yahoo.com


_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com