Bug 136618
Summary: | Ethereal reports wrong checksum on outgoing UDP packets | ||||||
---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Tomas Mraz <tmraz> | ||||
Component: | tcpdump | Assignee: | Harald Hoyer <harald> | ||||
Status: | CLOSED DUPLICATE | QA Contact: | |||||
Severity: | medium | Docs Contact: | |||||
Priority: | medium | ||||||
Version: | rawhide | CC: | rvokal | ||||
Target Milestone: | --- | ||||||
Target Release: | --- | ||||||
Hardware: | i386 | ||||||
OS: | Linux | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2006-02-21 19:06:31 UTC | Type: | --- | ||||
Regression: | --- | Mount Type: | --- | ||||
Documentation: | --- | CRM: | |||||
Verified Versions: | Category: | --- | |||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
Cloudforms Team: | --- | Target Upstream Version: | |||||
Embargoed: | |||||||
Attachments: |
|
Description
Tomas Mraz
2004-10-21 08:25:16 UTC
Sorry for the last info: tcpdump actually captures the packets with WRONG checksums too. So the problem lies probably in libpcap? Created attachment 105578 [details]
A very simple program to send UDP packets
Change IP address to host you want to send the packets to.
which NIC? 02:0c.0 Ethernet controller: Intel Corp. 82540EM Gigabit Ethernet Controller (rev 02) Subsystem: Dell Computer Corporation: Unknown device 0151 Flags: bus master, 66Mhz, medium devsel, latency 64, IRQ 9 Memory at fcfe0000 (32-bit, non-prefetchable) I/O ports at df40 [size=64] Capabilities: [dc] Power Management version 2 Capabilities: [e4] PCI-X non-bridge device. Capabilities: [f0] Message Signalled Interrupts: 64bit+ Queue=0/0 Enable- libpcap version 0.8.3, kernel 2.6.8-1.610 some network cards compute the checksum on their own.. maybe a dup of bug #129823 Oh, same NIC... *** This bug has been marked as a duplicate of 129823 *** This is described by ethereal developers - http://www.ethereal.com/faq#q5.14 Changed to 'CLOSED' state since 'RESOLVED' has been deprecated. |