|
Bugzilla – Full Text Bug Listing |
| Summary: | TCP checksums incorrect | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE Linux 10.1 | Reporter: | Dirk Mueller <dmueller> |
| Component: | Kernel | Assignee: | E-mail List <kernel-maintainers> |
| Status: | RESOLVED INVALID | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Normal | ||
| Priority: | P5 - None | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | Other | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: | pcap | ||
|
Description
Dirk Mueller
2005-11-29 16:33:11 UTC
Created attachment 59009 [details]
pcap
0x19da, not 0x19da2. If it really did, you wouldn't be able to do any TCP at all. More likely what you're seeing is a side effect of TSO or TX checksums. The kernel simply doesn't fill in a valid checksum but leaves it to the hardware. On the wire, these packets should look good. hmm, indeed. dumping on the other side doesn't show that. so my actual issue is something different. |