Anyone have a script to rip apart traceroute
-
I need to log a bunch of
traceroutecommands over the course of a few days and then subsequently analyze them.Anyone know of a script to do so? Obviously logging to a file is easy. But the normal output is not easily parsed.
-
Could "Ping Plotter" help?
-
Not a Linux application. Fedora/CentOS specifically.
I did not specify that, but the
traceroutecommand is a Linux syntax. It istracerton Windows. -
It's not something that I have seen. I think I understand what you are after, though.
-
@scottalanmiller said in Anyone have a script to rip apart traceroute:
It's not something that I have seen. I think I understand what you are after, though.
It is easy enough to do manually in a spreadsheet. Just annoying.
-
Would
mtrMulti Trace Route work for you? Basically traceroute that collects statistics over time. -
@travisdh1 said in Anyone have a script to rip apart traceroute:
Would
mtrMulti Trace Route work for you? Basically traceroute that collects statistics over time.Useful for live troubleshooting, but not for historical tracking.
-
@jaredbusch said in Anyone have a script to rip apart traceroute:
@travisdh1 said in Anyone have a script to rip apart traceroute:
Would
mtrMulti Trace Route work for you? Basically traceroute that collects statistics over time.Useful for live troubleshooting, but not for historical tracking.
Can think of a dozen BGP tools but I'm guessing you are troubleshooting some upstream issue. Does ping plotter not work for your case?
-
Not very elegant, but you could make a traceroute.out folder, and have each TR output as a different file in it.
-
@bigbear said in Anyone have a script to rip apart traceroute:
@jaredbusch said in Anyone have a script to rip apart traceroute:
@travisdh1 said in Anyone have a script to rip apart traceroute:
Would
mtrMulti Trace Route work for you? Basically traceroute that collects statistics over time.Useful for live troubleshooting, but not for historical tracking.
Can think of a dozen BGP tools but I'm guessing you are troubleshooting some upstream issue. Does ping plotter not work for your case?
No windows available.
-
These guys make several tools, maybe one of them will meet your needs?
https://www.oetiker.ch/en/oss/projects/
Like SmokePing or RRDtool?
-
@reid-cooper said in Anyone have a script to rip apart traceroute:
These guys make several tools, maybe one of them will meet your needs?
https://www.oetiker.ch/en/oss/projects/
Like SmokePing or RRDtool?
RRDTool has two links to Fedora packages but both are dead
There are no good instructions for building from source. There are instructions, but lacking a lot of detail on things such as what are the package dependencies...
SmokePing looks like a graphical ping tool. That is not useful as the destination does not respond to ICMP.
-
@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()
-
@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.
