astrace / prtraceroute things

This is a two fold message  due to some overlap; first about astrace.
I have done some testing of astrace and found a few problems with it.

1) It or I guess alc doesn't use the ias-int attribute. This makes most
   of the policies wrong at the borders.

2) The "-g" support works on the destination and not first on the gateway
   and then the destination. So its policy decisions are based on the
   wrong destination for half of the trace. 
   See below for "-g" support in prtraceroute.

3) Also, for the legend you seem to use the non-RIPE descriptions for AS 
   names. I guess ALC stores the first one it sees and you are using 
   NIC based data over RIPE for preference.

Plus, from a "personal point of view only" the policy messages returned
seem a little hard to read and currently due to the missing ias-int support are
often wrong. However, as noted these are now different tools so no problems.

Secondly, I have made a few changes to prtraceroute this week and wanted you
to get a chance to look at the pre-release version before the next pride tools
sub release. The main ones are as follows.

1) support of traceroutes "-g" option.

2) support of environment variables for alternate host and port. ala Dales
   suggestion.

3) support in the make for Solaris 2.* support. Solaris has a new 
   value for SOCK_STREAM ;-(.

4) Changes to Makefile for building of the manual.

5) Chages to the manual.

The major one though is the "-g". Just to show this in action.

[mature-tony-123] prtraceroute -l -v -g Amsterdam1.router.surfnet.nl ns0.ja.net
traceroute with AS and policy additions [Apr 27 10:02:15 UTC]

                from AS2122 mature.ripe.net (192.87.45.6)
                via  AS1103 Amsterdam1.router.surfnet.nl (145.41.1.193)
                to   AS 786 ns0.ja.net (193.63.94.20)

 1 AS1104  hef-router.nikhef.nl           192.87.45.80       [D2] 19 3 2 ms
 2 AS1103  Amsterdam1.router.surfnet.nl   192.87.4.18        [E1] 9 4 4 ms
 3 AS1103  Amsterdam2.router.surfnet.nl   145.41.9.130       [I] 6 5 5 ms
 4 AS2043  amsterdam4.empb.net            193.172.4.17       [E1] 15 11 14 ms
 5 AS2043  london4.empb.net               193.172.4.34       [I] 29 35 27 ms
 6 AS 786  janet-ex.london4.empb.net      193.172.27.22      [E1] 35 37 39 ms
 7 AS 786  ns0.ja.net                     193.63.94.20       [I] 32 90 35 ms

AS Path followed:  2122 1104 1103 2043 786

AS2122 = RS Test AS at NCC (TB's box of tricks)
AS1104 = NIKHEF-H
AS1103 = SURFnet IP
AS2043 = European Multiprotocol Backbone
AS 786 = The JANET IP Service

Also, notice the inconsistencies highligthed above in "astrace". 

[mature-tony-129] astrace -l -v -g Amsterdam1.router.surfnet.nl ns0.ja.net
Connected to ALC server
traceroute with AS and policy additions [Apr 27 10:07:55 UTC] 

                from AS3333 mature.ripe.net (192.87.45.6)
                to   AS 786 ns0.ja.net (128.86.1.20)

 1 AS3333  hef-router.nikhef.nl           192.87.45.80    [INT  0      0] 5 2 2
ms
 2 AS1755  Amsterdam1.router.surfnet.nl   192.87.4.18     [!RO -1 !RO -1] 60 5
5 ms
 3 AS1103  Amsterdam2.router.surfnet.nl   145.41.9.130    [!RO -1 !RO -1] 71 99
17 ms
 4 AS2043  amsterdam4.empb.net            193.172.4.17    [!RO -1 EXP  0] 14 10
10 ms
 5 AS2043  london4.empb.net               193.172.4.34    [INT  0      0] 35 29
32 ms
 6 AS2043  janet-ex.london4.empb.net      193.172.27.22   [INT  0      0] 47 36
40 ms
 7 AS 786  ns0.ja.net                     128.86.1.20     [!RO -1 !RO -1] 43 36
49 ms

AS Path followed:  3333 1755 1103 2043 786

AS3333 = RIPE-ASNBLOCK4
AS1755 = EBONE-INTERNAL
AS1103 = SURFNET-AS
AS2043 = EMPB-AS
AS 786 = ULCC-CISCO-AS

If you are intereted in a early look at prtraceroute it is on

ftp.ripe.net:pride/tools/prtraceroute.new.shar


	Regards,
		--Tony.




-------- Logged at  Wed Apr 27 13:46:16 MET DST 1994  ---------