[2407] in linux-net channel archive
PING returning incorrect times
daemon@ATHENA.MIT.EDU (Perry F Nguyen)
Mon Apr 8 15:27:14 1996
Date: Mon, 8 Apr 1996 11:26:30 -0700 (PDT)
From: Perry F Nguyen <pfnguyen@netcom22.netcom.com>
Reply-To: pfnguyen@netcom.com
To: linux-net@vger.rutgers.edu
-----BEGIN PGP SIGNED MESSAGE-----
Ever since I've installed a network card into my box and hooked it
up to a Sun 3/60, I've gotten some bogus ping times when I try.
Although, I've never seen this happen before, because I've never had
the chance or need to use ping (SLiRP user here).
The config is a 486DX2/66 linked to a 3/60 using an NE2000 clone Ether16
LAN card, and going over thinnet 10base2.
[11 : 0] ~> ping sun3xterm1
PING sun3xterm1 (10.0.2.5): 56 data bytes
64 bytes from 10.0.2.5: icmp_seq=0 ttl=255 time=2.6 ms
64 bytes from 10.0.2.5: icmp_seq=1 ttl=255 time=2.6 ms
64 bytes from 10.0.2.5: icmp_seq=2 ttl=255 time=2.6 ms
64 bytes from 10.0.2.5: icmp_seq=3 ttl=255 time=-44.-2 ms
64 bytes from 10.0.2.5: icmp_seq=4 ttl=255 time=-26.0 ms
64 bytes from 10.0.2.5: icmp_seq=5 ttl=255 time=-45.-1 ms
64 bytes from 10.0.2.5: icmp_seq=6 ttl=255 time=2.6 ms
64 bytes from 10.0.2.5: icmp_seq=7 ttl=255 time=2.6 ms
- --- sun3xterm1 ping statistics ---
8 packets transmitted, 8 packets received, 0% packet loss
round-trip min/avg/max = -45.-1/53687078.4/2.6 ms
[12 : 0] ~> uname -a
Linux Viet 1.3.85 #1 Mon Apr 8 09:38:46 PDT 1996 i486
[13 : 0] ~> su -
Password:
# ping -f sun3xterm1
PING sun3xterm1 (10.0.2.5): 56 data bytes
.
- --- sun3xterm1 ping statistics ---
43809 packets transmitted, 43808 packets received, 0% packet loss
round-trip min/avg/max = -54.-3/4.8/275.2 ms
Obviously, the above is very incorrect.
Perhaps it could be the result of a bad system clock on the Sun's side?
I have nothing to use to set the system clock, no rdate command.
But I'm sure ICMP pings don't work that way, do they? They send a time
string to another host and it just pongs it back, no?
Well, if anybody knows the reason to the madness here, I'd appreciate
any replies on why this occurs or if I have a missetup problem around
somewhere.
Oh yeah, this has been occurring since the 1.3.75 release until now,
or so.
- --
| pfnguyen@netcom.com - ftp://ftp.netcom.com/pub/pf/pfn | TCP/IP Networking, |
| 1024/0D97E00D 1995/01/01 Perry "Huy" Francis Nguyen | Unix Systems Admin, |
| CE 62 F2 01 33 87 9D 89 - BC 53 8D 11 F9 A0 DE 8F | and Consulting. |
| FTP, finger or mail with subject PGPKEY for PGP Key | Applications Devel. |
-----BEGIN PGP SIGNATURE-----
Version: 2.6.2
iQCVAwUBMWlaKy2IFwkNl+ANAQGhlgP7Bhbseu/F8Jhz3Rexh4QqJPJqcT9XOnP6
XwrrId43bpHbMDVLHJQZoP9a81OUCFpVMuCIW1G4W0DjdOMoRZ70YN5wAqmvei7N
AQtvmIwrvI7uNm7R6oFD254+72l98xjJZOJhPvfDQvYXyfWO9DNEgLUiWQJn6Va0
Hk5TflzNy48=
=wi/A
-----END PGP SIGNATURE-----
