Strange ping echo, what does it mean?

Every time I ping a workstation over a PPP connection while I am
simultaneously downloading something with FTP I get the following
output:

64 octets from 134.169.34.18: icmp_seq=589 ttl=60 time=1133.8 ms
wrong data byte #0 should be 0xe4 but was 0xe3e3 5e 2f 40 c1 8b c 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

It only happens when there is a load on the connection, it does not have
to be FTP. It could be SMTP, or HTTP, or whatever.

It looks as if IP packets are being returned in a broken state, but then
I would have thought that it must follow that ALL IP packets should be
affected, yet the files I download with FTP, or the email I send while
this is happening are all error free.

As soon as the load goes, i.e., as soon as the download has finished,
the ping echo reverts to the correct one.

Any insight anybody>

Oh, and this happens with _many_ kernels, and with several versions of
the PPP software.

Cheers,
Mike

--
Sorry, after years of fighting spam, I've given in. I changed
my email address, and don't want to reveal it to spammers. I
understand any wrath therby incurred, but I'm no longer in any
position to continue the fight.

Mike Dowling wrote:

> Every time I ping a workstation over a PPP connection while I am
> simultaneously downloading something with FTP I get the following
> output:
>
> 64 octets from 134.169.34.18: icmp_seq=589 ttl=60 time=1133.8 ms
> wrong data byte #0 should be 0xe4 but was 0xe3e3 5e 2f 40 c1 8b c 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

Some versions of ping have a bug that causes "wrong data byte" error
messages to appear when the reply takes > 1 second.

http://twiki.org/cgi-bin/view/Wikile...ngDataByte0Bug