Re: TTL=Time To Lie?
well if network admins thought they could hide 'bad acting' by mucking with probe packets, I bet they would...
Anyway.l I think it's a good idea to run probes like this during peak periods just to know how the network is doing, maybe re-route things around bottlenecks, do some load balancing and so on.
The 'traceroute' algorithm uses something like this already, but it's based on the number of hops and the receipt of a control packet that tells you that you exceeded the number of hops. In this case the packet is just being dropped altogether when TTL is exceeded, so if it's not somehow indicating that it was dropped, the process becomes a bit more difficult to track.
Still, I'd like to see some 'standard POSIX tool' that could do this, at any rate. Let's see if it can become a new internet standard.
Oh and one more thing, with respect to the article: Verizon throttling bandwidth of firefighters - it was in their contract, unfortunately (and I blame both sides for that). Cellular contracts with data caps and throttling (if you go over the cap) have been around throughout the so-called 'net neutrality' regulation period from the FCC. So nothing changed at all, with respect to FCC de-regulation. Connecting the 'net neutrality' de-reg at the FCC with Verizon's data plan throttling practice is FUD, at best. Come on, El Reg, you can do better than THAT!