From: Andreas Schwab <schwab@suse.de>
To: "cramerj" <cramerj@intel.com>
Cc: "Andi Kleen" <ak@suse.de>, <jonmason@us.ibm.com>, <netdev@oss.sgi.com>
Subject: Re: Bad UDP checksum with 82540EM
Date: Mon, 09 Feb 2004 01:50:48 +0100 [thread overview]
Message-ID: <jey8rdcbyv.fsf@sykes.suse.de> (raw)
In-Reply-To: <101E0EB68A545748974019DC227C554007CBDD@orsmsx406.jf.intel.com> (cramerj@intel.com's message of "Sun, 8 Feb 2004 15:22:29 -0800")
"cramerj" <cramerj@intel.com> writes:
> Just for clarification...how are you determining a bad checksum? Are
> you using tcpdump/ethereal on those test machines (that you're
> transmitting from), or are you capturing packets on the wire (from some
> other system receiving the packets).
Actually both. I have first noticed the issue because my DHCP clients
didn't accept the answers from the server.
> If the former, then please see the following thread.
>
> http://marc.theaimsgroup.com/?t=107422099800006&r=1&w=2
>
> Is this perhaps the issue you're seeing?
I just double checked, the packets are really going out with a bad
checksum.
Andreas.
--
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux AG, Maxfeldstraße 5, 90409 Nürnberg, Germany
Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next parent reply other threads:[~2004-02-09 0:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <101E0EB68A545748974019DC227C554007CBDD@orsmsx406.jf.intel.com>
2004-02-09 0:50 ` Andreas Schwab [this message]
2004-02-07 13:35 Bad UDP checksum with 82540EM Andreas Schwab
2004-02-07 21:37 ` Jon D Mason
2004-02-07 22:42 ` Andreas Schwab
2004-02-08 6:46 ` Andi Kleen
2004-02-08 13:09 ` Andreas Schwab
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=jey8rdcbyv.fsf@sykes.suse.de \
--to=schwab@suse.de \
--cc=ak@suse.de \
--cc=cramerj@intel.com \
--cc=jonmason@us.ibm.com \
--cc=netdev@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.