Bug 4443 - data corruption with ping?
Summary: data corruption with ping?
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Red Hat Raw Hide
Classification: Retired
Component: netkit-base
Version: 1.0
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Jeff Johnson
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 1999-08-09 15:34 UTC by sg618lo
Modified: 2008-05-01 15:37 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 1999-08-09 20:07:23 UTC

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description sg618lo 1999-08-09 15:34:02 UTC 
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
Comment 1 Jeff Johnson 1999-08-09 20:07:59 UTC 
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.
Note You need to log in before you can comment on or make changes to this bug.