Subject: Re: `ifconfig wm3 ip4csum` creates bad cksums via tcpdump
To: None <>
From: Daniel Carosone <>
List: current-users
Date: 05/23/2007 12:38:13
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Tue, May 22, 2007 at 05:24:04PM +0100, Charlie Allom wrote:
> 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?
> does it link down - then link up? could be the cisco switch?

Ah, heh.  I read your description as the commmand taking 34 seconds to
return, rather than for traffic to start flowing again.  Yes, in the
latter case, STP is the obvious (and now confirmed) culprit.

> other systems don't do it with different cards?

It would be nice if wm could avoid resetting the PHY; these other
drivers do (or they're not connected to the same switch?)

Content-Type: application/pgp-signature
Content-Disposition: inline

Version: GnuPG v1.4.7 (NetBSD)