The day my ping took countermeasures
The author recounts a surprising experience with the ping utility after returning from vacation. Upon running ping, they discovered it had implemented countermeasures due to a backward clock adjustment. This led to an exploration of how ping handles erroneous measurements and its historical context.
- ▪The author experienced unexpected behavior from the ping utility after their computer clock was adjusted backward.
- ▪Ping marked erroneous measurements as zero milliseconds, which the author referred to as 'taking countermeasures'.
- ▪Ping was originally developed in 1983 by Mike Muuss for the U.S. Army Ballistic Research Laboratory.
Opening excerpt (first ~120 words) tap to expand
The day my ping took countermeasures2023-07-11Marek Majkowski8 min read Once my holidays had passed, I found myself reluctantly reemerging into the world of the living. I powered on a corporate laptop, scared to check on my email inbox. However, before turning on the browser, obviously, I had to run a ping. Debugging the network is a mandatory first step after a boot, right? As expected, the network was perfectly healthy but what caught me off guard was this message: I was not expecting ping to take countermeasures that early on in a day. Gosh, I wasn't expecting any countermeasures that Monday!Once I got over the initial confusion, I took a deep breath and collected my thoughts. You don't have to be Sherlock Holmes to figure out what has happened.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at The Cloudflare Blog.
Discussion
0 commentsMore from The Cloudflare Blog
