Bug 4443
| Summary: | data corruption with ping? | ||
|---|---|---|---|
| Product: | [Retired] Red Hat Raw Hide | Reporter: | sg618lo |
| Component: | netkit-base | Assignee: | Jeff Johnson <jbj> |
| Status: | CLOSED NEXTRELEASE | QA Contact: | |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 1.0 | ||
| 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: | 1999-08-09 20:07:23 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: | |||
A fix for an alpha sizeof(time_t) != 4 problem compared timevals as well as patterns. Long (>1 sec) round trip times caused packets to miscompare. The fix is to not compare the timeval, so this isn't really data corruption. Fixed in netkit-base-0.10-33. |
The ping command of netkit-base-0.10-32 gives output similar to the following one when my isdn device gets under heavy load (i.e. > 5k/sec): wrong data byte #8 should be 0x7c but was 0x7b 7b f3 ae 37 13 19 1 0 8 9 a b c d e f 10 11 12 13 14 15 16 17 18 19 1a 1b 1c 1d 1e 1f 20 21 22 23 24 25 26 27 28 29 2a 2b 2c 2d 2e 2f