Subject: Re: `ifconfig wm3 ip4csum` creates bad cksums via tcpdump
To: None <current-users@netbsd.org>
From: Charlie Allom <charlie@rubberduck.com>
List: current-users
Date: 05/22/2007 17:24:04
--ikeVEW9yuYc//A+q
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Tue, May 22, 2007 at 07:50:34AM +1000, Daniel Carosone wrote:
> On Sat, May 19, 2007 at 07:17:43PM +0100, Charlie Allom wrote:
> > % ifconfig wm3 tcp4csum udp4csum tso4 ip4csum
> > [[wait 34 seconds! poor sockets ]]
>=20
> That seems weird. Can you determine whether this is some kind of name
> resolution problem for, say, 'tcp4sum', or really time spent waiting
> in the driver to set the flags?

other systems don't do it with different cards?

would it matter how much traffic is flowing through it?

does it link down - then link up? could be the cisco switch?


--=20
 hail eris
 http://rubberduck.com/

--ikeVEW9yuYc//A+q
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----

iD8DBQFGUxkgch7Q/D6hJDARAsXDAJ0Sxwl7hPQiBu5JWXNOyITR76PvfwCeN4Mz
7ogLoet/lG6rw0ngev8LW3k=
=JDuD
-----END PGP SIGNATURE-----

--ikeVEW9yuYc//A+q--