Re: mtr in nping?

[Toni Ruottu <toni.ruottu () iki fi>]

if you start mtr by commanding "mtr 8.8.8.8", and then press d two
times, mtr will show you a visualization about router responses. I
have included below a screen capture of what it looks like for me.

 1. 192.168.1.1                                    .........1.........2....1...
 2. hoasnet-fe20dd00-1.dhcp.                       .........a..........2.......
 3. hkicredger03-e-7-1.datan                       .........1.........2........
 4. hkicore1-o-3-3-0-0.datan                       >..11.1..2....2.12..31..1..3
 5. hkiasbr2-o-4.datanet.tel                       ....1.2...21.......1..aa....
 6. hls-b1-link.telia.net                          ...1....1.......1....2......
 7. s-bb1-link.telia.net                           211113111111111111111311a1a1
 8. s-b3-link.telia.net                            1113131111111111111111111111
 9. google-ic-130574-s-b3.c.                       33333a333aa333333333a3333333
10. 216.239.43.122                                 333333333ab33333333333333b33
11. 209.85.242.188                                 33333a333a3333333333a3333333
12. 209.85.242.185                                 33333a3aaa333333333a3a33333a
13. 209.85.254.112                                 33333333aa33333333333333a333
14. 209.85.254.126                                 3aaa333?333aa3333a33333a3333
15. google-public-dns-a.goog                       33333333a3333a33333333333333

Scale:  .:7 ms  1:17 ms  2:26 ms  3:48 ms  a:105 ms  b:159 ms  c:253 ms

I think it is possible to do something similar without ncurses, if we
swap the x-axis with y-axis. So we could simply ping each router in a
loop and print the response time symbols to screen one at a time. When
ever we ping the first router again, we need to end the line. Thus
each line would represent one round of pings, and each column a
different router.

 1. 192.168.1.1
 2. hoasnet-fe20dd00-1.dhcp.
 3. hkicredger03-e-7-1.datan
 4. hkicore1-o-3-3-0-0.datan
 5. hkiasbr2-o-4.datanet.tel
 6. hls-b1-link.telia.net
 7. s-bb1-link.telia.net
 8. s-b3-link.telia.net
 9. google-ic-130574-s-b3.c.
 a. 216.239.43.122
 b. 209.85.242.188
 c. 209.85.242.185
 d. 209.85.254.112
 e. 209.85.254.126
 f. google-public-dns-a.goog

Scale:  .:7 ms  1:17 ms  2:26 ms  3:48 ms  a:105 ms  b:159 ms  c:253 ms

123456789abcdef
---------------
...>..213333333
......1133333a3
......1133333a3
...1.11333333a3
...11.113333333
......33a3aa333
...12.113333333
......11333a3?3
.....111333aa3a
1a12..11aaaaa33
....2.11ab33333
....1.1133333a3

We need to figure some way of dealing with new routers that appear
when the route changes. I am not sure how to do that at the moment.
mtr adds new lines to the table. In our case a new line would have
more characters than the previous line. Maybe we could use some
character to point out where the new route was found.

On Fri, Apr 15, 2011 at 12:28 PM, Luis MartinGarcia.
<luis.mgarc () gmail com> wrote:
> Hi, Toni
>
> On 04/14/2011 03:52 PM, Toni Ruottu wrote:
> > Does nping have an mtr mode?
>
> No, it doesn't. It can do --traceroute but not something like mtr.
>
>
> > Would it benefit from one?
>
> That's a good question.  I know mtr could be a nice thing to have but I
> don't know how could we fit it in Nping. We can't implement an
> ncurses-based interface so we'd have to figure out exactly what would
> Nping do if users passed --mtr and how the output would look like.
>
> Do you have something in mind?
>
> Regards,
>
> Luis MartinGarcia.
_______________________________________________
Sent through the nmap-dev mailing list
http://cgi.insecure.org/mailman/listinfo/nmap-dev
Archived at http://seclists.org/nmap-dev/