[horseman]

Originally Posted by Ignitionnet

You only see the outbound path with a Command Prompt traceroute. It's the return path that's having issues.

I'd recommend a look at http://www.thinkbroadband.com/tools/traceroute.html

Cheers but actually it's not a CLI TR, its an extract from LFT Path Analyser 2.7 on OSX 10.11.2 with raw sockets enabled courtesy of Vostrom (Van Jacobson eat your heart out! )


https://www.dropbox.com/s/aohv91v7zp...26.34.png?dl=0

EDIT: but as usual your statement is totally correct as being an experienced "man-of-the-world" you've also found that not all CLITR's are useful!