Subject: Re: hardware checksum with wm nics
To: None <6bone@6bone.informatik.uni-leipzig.de>
From: Quentin Garnier <cube@cubidou.net>
List: tech-net
Date: 07/24/2007 21:37:23
--yr6OvWOSyJed8q4v
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Tue, Jul 24, 2007 at 09:31:37PM +0200, 6bone@6bone.informatik.uni-leipzi=
g.de wrote:
[...]
> bash-3.2# tcpdump -vpni wm0 port 22
> tcpdump: listening on wm0, link-type EN10MB (Ethernet), capture size 96=
=20
> bytes
> 15:11:16.469732 IP (tos 0x10, ttl 64, id 32065, offset 0, flags [DF],=20
> length: 292, bad cksum 0 (->741a)!) 139.18.25.35.22 > 139.18.25.33.65436:=
=20
> P 946513:946753(240) ack 1008 win 33580 <nop,nop,timestamp 22 22>
>=20
> I think the problem only occurs with outgoing packets.
Maybe I'm missing something with the way that thing is supposed to work,
but if the system let the NIC do the checksum calculation, why do you
expect anything but 0 in that field in tcpdump output _on the host_?
--=20
Quentin Garnier - cube@cubidou.net - cube@NetBSD.org
"You could have made it, spitting out benchmarks
Owe it to yourself not to fail"
Amplifico, Spitting Out Benchmarks, Hometakes Vol. 2, 2005.
--yr6OvWOSyJed8q4v
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (NetBSD)
iQEVAwUBRqZU89goQloHrPnoAQJzaAf/T3RYCQ8m5kn4gCWr61L0C7MkKTtKrxVv
w1GJOX7TFPWRlE/tXZLM+lwXKFjfkLa/rQuHWoI+fSNWe1p/U4cRK96f5XVnkOiP
i2urkNZZ7QmotLTZlDmA32TVmPvgyM5Fdfe+EEPgV6xTq5K0Hz/i/exFpSaa/D5L
9oFzhqSrUgjf4k1419bD0xIbf7O5iAS6UKSgQeZtb3xzxYVU2cqAFF/xrIZKXuDT
i0X7pUIQd4P6bICxqWzpyWqo/7UekA+fazHrZP+cQYU+P1tJDS0kVZiFf7XpGvWw
lBHKaMsQnX77RRS4NQYchVkgrbvuWIChBhhOBt+QyyK+WXdft6qorw==
=cVVA
-----END PGP SIGNATURE-----
--yr6OvWOSyJed8q4v--