> Complete ping response:
> PING 206.245.176.211 (206.245.176.211): 56 octets data
> 64 octets from 206.245.176.211: icmp_seq=0 ttl=122 time=1099.4 ms
> wrong data byte #0 should be 0x59 but was 0x5858 ff 79 3d 79 6b a 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
> 64 octets from 206.245.176.211: icmp_seq=1 ttl=122 time=268.4 ms
> 64 octets from 206.245.176.211: icmp_seq=2 ttl=122 time=283.4 ms
> 64 octets from 206.245.176.211: icmp_seq=3 ttl=122 time=251.6 ms>
> In the above case, the wrong data byte occurred for only one of the
> pings -- in other cases it occurs for 2, 3, or 4 (all of the) pings,
> but usually (always?) for the earliest pings rather than the last
> pings.
It appears, without the benefit of running a sniffer on your network,
that some of your ICMP packets are getting munged while traversing the
network. If this happens only occassionally, it might not be a big deal
but if you see a lot of this, you might be looking at a bad TCP/IP stack
implementation on your machine or some other machine/router between you
and your ISP.
Try installing and using Ethereal for a better understanding of what is
actually taking place on the network. It is a good sniffer, and comes in
mandrake rpm binary or source.
drjung
--
J. Craig Woods
UNIX/NT Network/System Administration
http://www.trismegistus.net/resume.html
Character is built upon the debris of despair --Emerson
Want to buy your Pack or Services from MandrakeSoft?
Go to http://www.mandrakestore.com
