Subject: Re: mtrace 5.1 (was: >10k MBONE routes?)
To: None <>
From: None <>
List: tech-net
Date: 02/13/1997 19:05:51

this concerns mtrace 5.1:

> The best way to track this is to use "mtrace -P 195.221.235"
> (195.221.235 was one of the routes that showed up last week).

It seems that the -P option is a recent addition to mtrace...

vader# mtrace -P 195.221.235
Usage: mtrace [-Mlnps] [-w wait] [-m max_hops] [-q nqueries] [-g gateway]
              [-S statint] [-t ttl] [-r resp_dest] [-i if_addr] source [receiver] [group]
vader# uname -a
NetBSD 1.2B NetBSD 1.2B (VADER) #2: Wed Feb  5 09:31:00 MET 1997 i386

mtrace 5.1 doesn't slide in without trouble either:

vader# make
cc -O   -c mtrace.c
mtrace.c: In function `send_igmp':
mtrace.c:526: `IGMP_MTRACE' undeclared (first use this function)
mtrace.c:526: (Each undeclared identifier is reported only once
mtrace.c:526: for each function it appears in.)
mtrace.c: In function `send_recv':
mtrace.c:977: `IGMP_MTRACE' undeclared (first use this function)
mtrace.c:1129: `IGMP_MTRACE_RESP' undeclared (first use this function)
mtrace.c: In function `passive_mode':
mtrace.c:1276: `IGMP_MTRACE' undeclared (first use this function)
mtrace.c:1277: `IGMP_MTRACE_RESP' undeclared (first use this function)
mtrace.c:1288: warning: unreachable code at beginning of switch statement
mtrace.c: In function `main':
mtrace.c:2372: `IGMP_MTRACE' undeclared (first use this function)
*** Error code 1


Rats!  Is this a porting confusion and/or differing APIs (sigh!),
as I in <netinet/igmp.h> find

#define IGMP_MTRACE_REPLY               0x1e  /* traceroute reply      */
#define IGMP_MTRACE_QUERY               0x1f  /* traceroute query      */

IGMP_MTRACE_RESP=IGMP_MTRACE_REPLY and it compiled, but this
is gross.  To my untrained eye the result looks OK, though:

vader# ./mtrace -P 195.221.235
Mtrace from to via group
Querying full reverse path... 
  0 (
 -1 (  PIM  thresh^ 0  
 -2 (  PIM  thresh^ 0   [default]
Round trip time 28 ms; total ttl of 1 required.

Monitoring path..........................................................

Oh, yes, BTW, the usage message in mtrace 5.1's source code
hasn't been updated with the -P option.

The mtrace source I used was in


- Havard