[ale] Weird ping stuff
Ken Nagorski
kenn at refriedgeek.com
Thu Jan 24 21:36:27 EST 2002
-------- Original Message --------
Subject: Re: [ale] Weird ping stuff
From: "Ken Nagorski" <kenn at refriedgeek.com>
To: ale at ale.org
To: kenn at refriedgeek.com
Hello - OK. I posted this earlier and I got one response that said
"Broken equipment. Ping even told which piece."
I don't see that in here. I mean, why should I assume that because there
is an error the hardware is broken? After It was good ol' Linas that
said 99.9% of the time hardware isn't the problem. Even if it was broken
equipment how do I know that the router wasn't broken and screwing up
the packet? Does somebody have more information about this? That would
be great.
I mean, if I am missing something please explian... I aint proud, however
I just don't see where this says that a certian piece of hardware is
broken? and if so which one? Couldn't it be a bug in the software
somewhere?
Thank you
Ken
> Hi there,
>
> I noticed that a network that I normally spend a lot of time on in
> Cleveland Ohio was bogged down. I didn't see any massive traffic use.
> They are on DSL that is supossed to be able to max a 321kbs and they
> are averaging out like 2000B/s and like 330B/s in so I thought maybe
> there was problem between there and me. I did a ping and to my suprise
> this is what I got.
> -----------------snip-----------------snip-------------------------------
> PING 216.254.105.101 (216.254.105.101): 56 octets data
> 64 octets from 216.254.105.101: icmp_seq=0 ttl=238 time=1003.6 ms wrong
> data byte #0 should be 0xe1 but was 0xe0e0 25 50 3c 37 a9 7 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 216.254.105.101: icmp_seq=1 ttl=238 time=1016.3 ms wrong
> data byte #0 should be 0xe2 but was 0xe1e1 25 50 3c 9e a3 7 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 216.254.105.101: icmp_seq=2 ttl=238 time=1018.5 ms wrong
> data byte #0 should be 0xe3 but was 0xe2e2 25 50 3c c5 a3 7 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 216.254.105.101: icmp_seq=3 ttl=238 time=1024.8 ms wrong
> data byte #0 should be 0xe4 but was 0xe3e3 25 50 3c 9e a3 7 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
>
> --- 216.254.105.101 ping statistics ---
> 5 packets transmitted, 4 packets received, 20% packet loss
> round-trip min/avg/max = 1003.6/1015.8/1024.8 ms
> kenn at workstation:$
> ---------end---------snip-----------------end-----------snip-------------
>
> But everything is OK when I ping the Flowpoint DSL router. Has anyone
> ever seen this before? I haven't... What would cause that?
>
> Thanks
> Ken
>
> ----------------------------------------------
> But I don't want to go among mad people,
> Alice remarked.
> Oh, you can't help that, said the Cat:
> we're all mad here. I'm mad. You're mad.
> How do you know I'm mad? said Alice.
> You must be, said the Cat,
> or you wouldn't have come here.
>
>
> ---
> This message has been sent through the ALE general discussion list. See
> http://www.ale.org/mailing-lists.shtml for more info. Problems should
> be sent to listmaster at ale dot org.
----------------------------------------------
But I don't want to go among mad people,
Alice remarked.
Oh, you can't help that, said the Cat:
we're all mad here. I'm mad. You're mad.
How do you know I'm mad? said Alice.
You must be, said the Cat,
or you wouldn't have come here.
----------------------------------------------
But I don't want to go among mad people,
Alice remarked.
Oh, you can't help that, said the Cat:
we're all mad here. I'm mad. You're mad.
How do you know I'm mad? said Alice.
You must be, said the Cat,
or you wouldn't have come here.
---
This message has been sent through the ALE general discussion list.
See http://www.ale.org/mailing-lists.shtml for more info. Problems should be
sent to listmaster at ale dot org.
More information about the Ale
mailing list