Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
First Last Prev Next    This bug is not in your last search results.
Bug 4443 - data corruption with ping?
data corruption with ping?
Status: CLOSED NEXTRELEASE
Product: Red Hat Raw Hide
Classification: Retired
Component: netkit-base (Show other bugs)
1.0
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Jeff Johnson
:
Depends On:
Blocks:
  Show dependency tree / graph
 
Reported: 1999-08-09 11:34 EDT by sg618lo
Modified: 2008-05-01 11:37 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 1999-08-09 16:07:23 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

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

  None (edit)
Description sg618lo 1999-08-09 11:34:02 EDT 
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 16:07:59 EDT 
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.
First Last Prev Next    This bug is not in your last search results.