[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20080420.212451.10825959.davem@davemloft.net>
Date: Sun, 20 Apr 2008 21:24:51 -0700 (PDT)
From: David Miller <davem@...emloft.net>
To: herbert@...dor.apana.org.au
Cc: dpn@...merica.net, toralf.foerster@....de, netdev@...r.kernel.org
Subject: Re: tx-checksumming for an Intel Corporation 82540EP Gigabit
Ethernet Controller (Mobile)
From: Herbert Xu <herbert@...dor.apana.org.au>
Date: Mon, 21 Apr 2008 11:57:22 +0800
> Daniel Noe <dpn@...merica.net> wrote:
> >
> > 2) Tell Wireshark not to verify the checksums. See
> > http://wiki.wireshark.org/TCP_Checksum_Verification. This works if you
> > don't really care about the checksums and are looking at other things.
> > If you suspect incorrect checksums, you can always turn off checksum
> > offloading manually.
>
> Better yet fix Wireshark to use the info that the kernel supplies
> and ignore checksums only on those packets generated locally for
> hardware offload.
True.
But every time we say this they keep coming back at us that they can't
change the tcpdump raw dump file format that's been used for
centuries, and naturally it was designed without any extensibility in
mind so there's nowhere to store the checksum indication.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists