Quote:
Originally Posted by Paul
There is no -m option in windows, so i looked it up for mac
A TTL of 2 isnt going to get you very far, possibly not even off your own network, hence the exceeded messages.
|
That's the point of this test
With a TTL of 2 and two pings going, the 2nd hop starts to acts very weirdly, one of the pings will correctly show TTL exceeded and the other will show timeout, occasionally switching between which is exceeding and which is timing out.
Virgin appear to be dropping the TTL exceeded packets - but only if there are 2 pings hitting that node, if you have a single ping running it works as expected.
I'm actually writing a piece of software to analyse routes, and I've noticed this issue for a long time but ignored it. Tonight I spent quite a while debugging and figuring out what exactly was going on, it however meant that I reorganised part of the software to make it more robust.
