Live data from Hacker News

The best ping story I've ever heard

askapache.com

31–40 of 49 posts

Re: The best ping story I've ever heard

#31
Ping fans, be sure to check out bing! Fun stuff and 97.2% accurate (not really)! :)

> Bing is a point-to-point bandwidth measurement tool (hence the 'b'), based on ping. Bing determines the real (raw, as opposed to available or average) throughput on a link by measuring ICMP echo requests roundtrip times for different packet sizes for each end of the link.

http://fgouget.free.fr/bing/bing_src-readme.shtml

Re: The best ping story I've ever heard

#32
post #4

This is a good one too, although not strictly ping related. http://www.ibiblio.org/harris/500milemail.html

There's also this legendary Amazon review, which is strictly ping-related: http://www.amazon.com/review/R2VDKZ4X1F992Q

Good grief, I'd forgotten about that one. Hard to believe it's still up almost 15 years later. A true classic of the Amazon review genre. Who would have thought they would become a cultural repository?

Re: The best ping story I've ever heard

#33
post #18

Is it just my network administrator or do others drop outgoing Ping messages at the corporate firewall? This has cost me and others more time than I would like to admit for some vague "security" reason that he won't or can't explain.

Start with a default-deny policy, the only sensible course. (Google "IP over ICMP".) Note that some sysadmins need to verify external connectivity, so allow ICMP echo reply messages to those IPs (or subnets, more likely). Result: if your machine isn't in one of those blessed ranges, you never get a response to a ping to an outside address. Most users don't complain, because they don't even know what a ping is. So, it…

Blocking ICMP is a questionable practice in my opinion. It generally just complicates troubleshooting for a marginable gain in "security" and some applications even require it for PMTU discovery.

If you're really worried about user tunneling out through various tricks, you'd probably have to block the whole internet and apply a whitelist of trusted destination hosts.

As a heavy ping user, this blockage always bothered me, so I started working on a similar tool to get around this:

https://github.com/silverwind/tcpie

Re: The best ping story I've ever heard

#34
post #20

We once had an Ericsson MSC that only replied to _uneven_ ICMP packets due to some bug. Made it look like there was 50% packet loss on an otherwise perfectly good Cat 5 cable... (edit: ICMP instead of IP)

Checksum issue?

IIRC, there was nothing on the logs and they eventually shipped a fix. I was there when it happened and was called over to have a look.

Re: The best ping story I've ever heard

#35
post #4

This is a good one too, although not strictly ping related. http://www.ibiblio.org/harris/500milemail.html

There's also this legendary Amazon review, which is strictly ping-related: http://www.amazon.com/review/R2VDKZ4X1F992Q

Didn't know that one! The dry humor is f*ing priceless :)

Re: The best ping story I've ever heard

#37
I once recovered a stolen car with ping.

It was 2002 (2003?), and we had just launched Zipcar in New York. Being a naive start-up we had perhaps not the most stringent security measures in place to prevent fraud and theft. Sure enough, a couple of weeks in and one of our cars went missing. Calls to the member went unreturned, and it became clear that the member was not who they claimed to be and had no intention of returning the car.

At the time Zipcar was using the mobile analog CDPD network for vehicle communications, which had a top speed of something like 19.2k/s and cost us around $1/month per KB of data. However, it also had a limited number of data channels, and since it used the old AMPS network broadcast in the 800 - 900 MHz range. I happened to have an amateur radio license and a radio that was able to receive in that band.

Since we were still in contact with the missing car we knew it hadn't been chopped (yet) and I figured we might be able to use some sort of radio direction finding technique to locate the car. My friend and fellow engineer Carl was able to reprogram the firmware of our embedded electronics to tell us which cell tower the car was in contact with, and with that we could look up the FCC id in their database to find the tower's street address.

So my boss Roy and I hopped into his car and drove to Long Island. We drove up to the tower, and I leaned out the window of his minivan with a yagi antenna and my radio (set to scan the 40 or so CDPD channels.) We asked Carl (back in Boston) to start pinging the car. To the radio this sounded like a half-second burst of static, but since it was very regular it was also very easy to identify. Sure enough, after driving around for a few minutes we picked up the signal. pffft pffft pffft

We drove around the tower in a wide circle until the signal was the strongest, got out to scan the area, then used the new bearing to reduce the circle. Eventually we ended up in the parking lot of the Long Island railroad. There in the back corner was our car, luckily unscathed and none the worse for wear.

Ping rocks.

Re: The best ping story I've ever heard

#38
post #36

The linked page appears to be a spammy copy of the original here: http://ftp.arl.army.mil/~mike/ping.html It doesn't correctly credit the real author of ping: http://en.wikipedia.org/wiki/Mike_Muuss

Thank you webmaster@arl.army.mil for seeing that Mike Muuss's pages have been preserved, going on 15 years now.

Interesting note I hadn't read before: "This Web server was one of the first 50 Web servers on the InterNet, making it a pioneer in its own right."

Re: The best ping story I've ever heard

#39
post #31

Ping fans, be sure to check out bing! Fun stuff and 97.2% accurate (not really)! :) > Bing is a point-to-point bandwidth measurement tool (hence the 'b'), based on ping. Bing determines the real (raw, as opposed to available or average) throughput on a link by measuring ICMP echo requests roundtrip times for different packet sizes for each end of the link. http://fgouget.free.fr/bing/bing_src-readme.shtml

This looks pretty ancient (source files dated 1997), and won't compile here. Any maintained version?
Post reply on HN