[BACK]Return to FORMATS CVS log [TXT] [DIR] Up to [ELWIX - Embedded LightWeight unIX -] / embedaddon / mtr

Diff for /embedaddon/mtr/FORMATS between versions 1.1.1.1 and 1.1.1.4

version 1.1.1.1, 2013/07/21 23:43:42 version 1.1.1.4, 2023/09/27 11:18:58
Line 6  gui-library with a setuid program. Line 6  gui-library with a setuid program.
   
 The split format is:  The split format is:
   
<pos> <host> <loss%> <rcvd pckts> <sent pckts> <best> <avg> <worst> <pos> <host> <loss%> <rcvd pckts> <sent pckts> <best> <avg> <worst>
   
   
 The "raw" format is:  The "raw" format is:
   
hostline|pingline|dnsline|timestamplinehostline|xmitline|pingline|dnsline|timestampline|mplsline
   
 hostline:  hostline:
 h <pos> <host IP>  h <pos> <host IP>
   
   xmitline:
   x <pos> <seqnum>
   
 pingline:  pingline:
p <pos> <pingtime (ms)>p <pos> <pingtime (ms)> <seqnum>
   
dnsline: dnsline:
 d <pos> <hostname>  d <pos> <hostname>
   
 timestampline:  timestampline:
 t <pos> <pingtime> <timestamp>  t <pos> <pingtime> <timestamp>
   
   mplsline:
   m <pos> <label> <traffic_class> <bottom_stack> <ttl>
   
 Timestampline is not  yet implemented. Need to find out how to do  Timestampline is not  yet implemented. Need to find out how to do
 ICMP timestamping first. :-)  ICMP timestamping first. :-)
Line 32  ICMP timestamping first. :-) Line 37  ICMP timestamping first. :-)
   
 Someone suggested to put the following text here. As to context: Some  Someone suggested to put the following text here. As to context: Some
 people are wondering why mtr sometimes reports hosts beyond the  people are wondering why mtr sometimes reports hosts beyond the
destination host. destination host.
   
   
 The FINAL host will occasionally be mentioned at position n, n+1, n+2  The FINAL host will occasionally be mentioned at position n, n+1, n+2
Line 52  reply. So in the example above, we'd see a reply from  Line 57  reply. So in the example above, we'd see a reply from 
 position 4, then we'd send out 5-9 (and because the max-host is now at  position 4, then we'd send out 5-9 (and because the max-host is now at
 9, we'll send them out at 1s/9 = 111ms intervals). When the reply from  9, we'll send them out at 1s/9 = 111ms intervals). When the reply from
 host 9 comes back, we'll start probing for host 10-15 (at about 60ms  host 9 comes back, we'll start probing for host 10-15 (at about 60ms
intervals). But suppose the network delay upto host 9 is already 200msintervals). But suppose the network delay up to host 9 is already 200ms
 and suppose our destination host is at position 11. Then by the time  and suppose our destination host is at position 11. Then by the time
 the packet from host 11 comes back, we'll already have sent probe  the packet from host 11 comes back, we'll already have sent probe
 packets for position 12, 13, and 14! Those will come back as  packets for position 12, 13, and 14! Those will come back as
Line 97  h 15 152.63.50.89 Line 102  h 15 152.63.50.89
 h 16 152.179.99.218  h 16 152.179.99.218
 h 17 152.179.99.218  h 17 152.179.99.218
 h 18 152.179.99.218  h 18 152.179.99.218
   
Removed from v.1.1.1.1  
changed lines
  Added in v.1.1.1.4

FreeBSD-CVSweb <freebsd-cvsweb@FreeBSD.org>