current-users: Re: What's happening here? (NFS)

Subject: Re: What's happening here? (NFS)
To: None <tech-kern@netbsd.org, current-users@netbsd.org>
From: Patrick Welche <prlw1@newn.cam.ac.uk>
List: current-users
Date: 03/17/2005 17:22:45

On Thu, Mar 17, 2005 at 03:22:09PM +0100, Reinoud Zandijk wrote:
> On `heethoofdje' :
> 
> ex0: flags=8b63<UP,BROADCAST,NOTRAILERS,RUNNING,PROMISC,ALLMULTI,SIMPLEX,MULTICAST> mtu 1500
>         capabilities=7<IP4CSUM,TCP4CSUM,UDP4CSUM>
>         enabled=7<IP4CSUM,TCP4CSUM,UDP4CSUM>
>         address: 00:11:2f:52:44:7c
>         media: Ethernet autoselect (100baseTX full-duplex)
>         status: active
>         inet 192.168.0.140 netmask 0xffffff00 broadcast 192.168.0.255
>         inet6 fe80::211:2fff:fe52:447c%ex0 prefixlen 64 scopeid 0x1
>         inet6 2001:7b8:341::3 prefixlen 64
> 
> 
> 15:00:32.903993 IP (tos 0x0, ttl  64, id 61608, offset 0, flags [+], length: 1500, bad cksum 0 (->e289)!) heethoofdje.kasbah.2541100127 > rangerover.kasbah.nfs: 1472 write [|nfs]


Just a "me too".. Also on ex0, with h/w csumming enabled:

17:16:13.805723 IP (tos 0x10, ttl  64, id 41336, offset 0, flags [DF], length: 52, bad cksum 0 (->f8f0)!) 131.111.204.180.65215 > 131.111.204.183.22: . [bad tcp cksum a071 (->38f)!] ack 2560 win 33580 <nop,nop,timestamp 4600 4600>


lots of packets with bad cksum..

However, with h/w checksums turned off, all OK according to tcpdump.
(Running current/i386 of yesterday)

Cheers,

Patrick