3 ms·
It's interesting that ICMP ECHO_REQUEST and ECHO_REPLY predate the ping program. But indeed they are defined by http://tools.ietf.org/html/rfc792 http://tools.
by js2 14y ago
It's interesting that ICMP ECHO_REQUEST and ECHO_REPLY predate the ping program. But indeed they are defined by http://tools.ietf.org/html/rfc792 http://tools.ietf.org/html/rfc792 from Sep 1981. I guess that Unix hosts were already replying to ECHO_REQUESTs even though this isn't prescribed till http://tools.ietf.org/html/rfc1122#page-42 http://tools.ietf.org/html/rfc1122#page-42 from 1989. But I wonder what was sending ECHO_REQUEST before ping? The only other standard use of these packets I know of today is DHCP servers before handing out a lease to ensure a host isn't already using a given IP.
Phil Dykstra added ICMP Record Route support to PING, but in those early days few routers processed them
It must have been a narrow window in time when routers respected this option. My Internet career goes back to 1995 and I've never known a router to do so.
I was insanely jealous when Van Jacobson of LBL used my kernel ICMP support to write TRACEROUTE, by realizing that he could get ICMP Time-to-Live Exceeded messages when pinging by modulating the IP time to life (TTL) field. I wish I had thought of that! :-)
Asking a candidate to figure out how traceroute works is one of my interview questions, but if the author of ping didn't think of it, maybe I should drop the question. :)
The real traceroute uses UDP datagrams because routers aren't supposed to generate ICMP error messages for ICMP messages.
The Windows version I believe uses ICMP by default, and the Unix version, these days, can be asked to. I had always heard that routers do reply to ICMP, but at a lower priority.