On Wed, 30 May 2001 [EMAIL PROTECTED] wrote:
> Aren't you traveling several rfc1149 links? > > http://www.blug.linux.no/rfc1149/pinglogg.txt ?!? What do U mean ? isn't the ping time measured by storing system time the ICMP ECHO was sent, and comparng it to the system time the reply arrived ? I get it even when pinging my Cisco 1601 router, which is connected directly (I don't care 3com SSII 1100 now) -=Czaj-nick=- > On Wed, May 30, 2001 at 03:24:39PM +0200, Przemyslaw Wegrzyn wrote: > > > > Look at this: > > > > [EMAIL PROTECTED]:~$ ping 156.17.209.1 > > PING 156.17.209.1 (156.17.209.1): 56 data bytes > > 64 bytes from 156.17.209.1: icmp_seq=0 ttl=247 time=5427.7 ms > > 64 bytes from 156.17.209.1: icmp_seq=1 ttl=247 time=23.2 ms > > 64 bytes from 156.17.209.1: icmp_seq=2 ttl=247 time=429492829.5 ms > > ^^^^^^^^^^^^^^^^^^^ > > 64 bytes from 156.17.209.1: icmp_seq=3 ttl=247 time=429492907.1 ms > > 64 bytes from 156.17.209.1: icmp_seq=4 ttl=247 time=16.5 ms > > 64 bytes from 156.17.209.1: icmp_seq=5 ttl=247 time=21.4 ms > > > > What the hell can it be ?!? Every ping comes back in few milisecounds... > > > > We've recently added second CPU to this machine, can it (failed CPU) be > > the reason ? Overall stability is good... > > > > -=Czaj-nick=- > > > > > > > > -- > > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > > -- > HoraPe > --- > Horacio J. Peńa > [EMAIL PROTECTED] > [EMAIL PROTECTED] > [EMAIL PROTECTED] > [EMAIL PROTECTED] > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] >
