ML
    • Recent
    • Categories
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    Anyone have a script to rip apart traceroute

    IT Discussion
    traceroute analytics
    7
    14
    2.2k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • JaredBuschJ
      JaredBusch
      last edited by

      Not a Linux application. Fedora/CentOS specifically.

      I did not specify that, but the traceroute command is a Linux syntax. It is tracert on Windows.

      1 Reply Last reply Reply Quote 1
      • scottalanmillerS
        scottalanmiller
        last edited by

        It's not something that I have seen. I think I understand what you are after, though.

        JaredBuschJ 1 Reply Last reply Reply Quote 0
        • JaredBuschJ
          JaredBusch @scottalanmiller
          last edited by

          @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.

          1 Reply Last reply Reply Quote 1
          • travisdh1T
            travisdh1
            last edited by

            Would mtr Multi Trace Route work for you? Basically traceroute that collects statistics over time.

            JaredBuschJ 1 Reply Last reply Reply Quote 1
            • JaredBuschJ
              JaredBusch @travisdh1
              last edited by

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

              Would mtr Multi Trace Route work for you? Basically traceroute that collects statistics over time.

              Useful for live troubleshooting, but not for historical tracking.

              bigbearB 1 Reply Last reply Reply Quote 0
              • bigbearB
                bigbear @JaredBusch
                last edited by

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

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

                Would mtr Multi 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?

                JaredBuschJ 1 Reply Last reply Reply Quote 0
                • scottalanmillerS
                  scottalanmiller
                  last edited by

                  Not very elegant, but you could make a traceroute.out folder, and have each TR output as a different file in it.

                  1 Reply Last reply Reply Quote 1
                  • JaredBuschJ
                    JaredBusch @bigbear
                    last edited by

                    @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 mtr Multi 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.

                    1 Reply Last reply Reply Quote 0
                    • Reid CooperR
                      Reid Cooper
                      last edited by

                      These guys make several tools, maybe one of them will meet your needs?

                      https://www.oetiker.ch/en/oss/projects/

                      Like SmokePing or RRDtool?

                      JaredBuschJ 1 Reply Last reply Reply Quote 2
                      • JaredBuschJ
                        JaredBusch @Reid Cooper
                        last edited by

                        @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.

                        1 Reply Last reply Reply Quote 0
                        • RomoR
                          Romo
                          last edited by

                          @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()
                          

                          0_1510695286659_scapy_mangolassi-traceroute.png

                          JaredBuschJ 1 Reply Last reply Reply Quote 2
                          • JaredBuschJ
                            JaredBusch @Romo
                            last edited by

                            @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.

                            1 Reply Last reply Reply Quote 1
                            • 1 / 1
                            • First post
                              Last post