@romo said in Anyone have a script to rip apart traceroute:

@reid-cooper said in Anyone have a script to rip apart traceroute:

SmokePing

@JaredBusch maybe try using Scapy to get what you want? It can do plotting and graphing and many other things, just have to read through the documentation.

Ex: A simple traceroute to mangolassit from my work computer with a graph.

>>> res, unans = traceroute("mangolassi.it",dport=443,maxttl=20) Begin emission: ****Finished to send 20 packets. **************** Received 20 packets, got 20 answers, remaining 0 packets 104.25.46.32:tcp443 1 189.211.38.162 11 2 200.78.150.113 11 3 200.78.150.49 11 4 148.240.205.13 11 5 213.248.97.166 11 6 213.248.97.166 11 7 62.115.32.214 11 8 104.25.46.32 SA 9 104.25.46.32 SA 10 104.25.46.32 SA 11 104.25.46.32 SA 12 104.25.46.32 SA 13 104.25.46.32 SA 14 104.25.46.32 SA 15 104.25.46.32 SA 16 104.25.46.32 SA 17 104.25.46.32 SA 18 104.25.46.32 SA 19 104.25.46.32 SA 20 104.25.46.32 SA >>> res.graph()

That looks solid.

@travisdh1 I guess I should note that I got a laugh because the route to go from our site in Killbuck, OH to our host in Walla Walla, WA went

Cincinnati, OH Los Angeles, CA Monroe, AR Chicago, IL New York, NY Philadelphia, PA Atlanta, GA Seattle, WA Walla Walla, WA

Nothing like traversing the entire country 3 times to help with latency, right? Even with that, latency only averages 87ms with the Piladelphia -> Atlanta link being the slowest of the bunch.

@DustinB3403 said in Weird TraceRoute Error:

I got timed out at hop 8 along the trace route to 45.63.18.153

That's normal.