- routing-wg - mailman.ripe.net

hierarchical auth with route objects
by Schmitz＠RUS.Uni-Stuttgart.DE 05 Dec '96

05 Dec '96

Dear colleagues, hierarchical authorization in the RIPE-db as a new feature presented at the last RIPE meeting is not limited to inetnum objects or the domain name space. It is also applicable to route objects. However, it has not yet been implemented for route objects because no consensus was found on how to do it. With this mail I want to start the discussion again. Please note, that this is only the draft of a draft - nothing final. So drop your comments here! In my opinion, route objects are not much different from inetnum objects regarding hierarchical authorization. Both span a certain range of IP addresses and in both cases hierarchical authorization controls definition of IP subranges. Following this reasoning it seems to be simple to implement within the IP prefix tree. However, route objects are not standing alone but are logically linked to AS objects via the origin tag. Applying hierarchical authorization within the IP prefix tree *alone* does allow uncontrolled creation of route objects of differing origin. Therefore, AS objects which match the origin AS of a route object may be considered as parent objects of route objects. I think this is a very useful approach (even though it links different types of objects in one authorization hierarchy). There have been ideas that route objects should only be created if proper address allocation occured. However, it has also been pointed out that it is not a good idea to mix address allocation and routing for several rea- sons, e.g. some registries are pure routing registries and all registries should have the same structure. Moreover, changes in routing might make changes in address registration necessary (and vice versa). There have been some good comments on this topic on the database wg mailing list. Never- theless, if no route objects exist for allocated address space, any AS owner may generate route objects uncontrolled in this registry (creation of objects in one registry which are protected by hierarchical authorization in another is also not covered but this is an entirely different problem). Obviously, there are still some loose ends. But I think that the approach of AS objects as parents of route objects from corresponding origin com- bined with hierarchical authorization within the IP prefix tree is very useful and may be applied here. Shall we go for this? Regards Joachim Schmitz _____________________________________________________________________________ Dr. Joachim Schmitz schmitz(a)noc.dfn.de DFN Network Operation Center Rechenzentrum der Universitaet Stuttgart ++ 711 685 5553 voice Allmandring 30 ++ 711 678 8363 FAX D-70550 Stuttgart FRG (Germany) _____________________________________________________________________________

3 2

final minutes of the routing WG session at RIPE 25
by Schmitz＠RUS.Uni-Stuttgart.DE 02 Nov '96

02 Nov '96

Dear Routing WG members, since there have been no additional comments on the minutes of our session at RIPE 25 I conclude that the minutes are accepted as is. I updated some URLs but there is no other change. The final version of the minutes is appended below. Thanks again to Mike Norris who took them. Regards Joachim -------- RIPE 25, Amsterdam Routing Working Group Report of Meeting, 23rd September 1996 1. Opening and Administrivia Willem van der Scheun, Chairman, presided and welcomed people to the meeting. There were 89 attenders. Mike Norris took minutes. 2. Agenda bashing A draft agenda of business, circulated by the Chairman in the previous week, was agreed. 3. Chairman of the Routing WG Willem announced that his day job prevented him from devoting the time necessary to chairmanship of the WG and that he was standing down. He was pleased to say that Joachim Schmitz would accept his proposal to be Chairman, and this proposal was endorsed by the meeting. Members thanked Willem for his work as Chairman and guidance of the WG. Joachim chaired the remainder of the meeting. 4. Report from the RIPE NCC Daniel Karrenberg said that the RIPE NCC planned to resume its studies of route aggregation. An exercise he had conducted earlier in 1996 and reported to RIPE 24 had revealed plenty of room for improvement. Individual reports to those responsible for over-specific routing had resulted in significant improvements. Since then, however, the aggregation situation had disimproved. Daniel's impression was that some ISPs didn't care or wouldn't take the trouble to correct matters. Further remedial action was needed and the Contributors' Committee supported the NCC in this work. Skilled staff would soon be appointed and they would help ISPs in promoting route aggregation. While neither RIPE nor the NCC could take action against any offenders, the use of peer pressure among the ISPs could be used in a positive manner to improve the position. The meeting encouraged ISPs to supply BGP data to the NCC on request for the purpose of analysing route aggregation. New Action: the NCC would report on route aggregation at RIPE 26. 5. Working Experience with Route Object Editor (ROE) ftp://ftp.ripe.net/ripe/presentations/ripe-m25-jschmitz-work-exp-roe.html Joachim Schmitz reported on his experience with ROE. This was part of the RA Toolset and had been written by Cengiz Alaettinoglu. Its purpose was to view and manipulate route objects and to compare them with operational routes. It worked on routes as objects from Internet routing registries (IRRs) and as determined from routers (by means of input BGP tables). Compiled with C++ in a Tcl/Tk environment, ROE was easy to install. With its GUI it was easy to use. As not all IRRs were aligned in the way they worked, ROE displayed separate route registrations where appropriate. Joachim found it slow in operation, although Cengiz later indicated that this was probably due to network and server performance and not to the ROE program execution. It was also not clear to Joachim whether live or mirrored IRR data was used. He suggested that the program could be improved by allowing more configuration options and greater clarity in some of the messages. This and other feedback should be directed to Cengiz. Overall, he recommended ROE for operational use, particularly for complex routing tasks. 6. Progressive BGP route flap dampening ftp://ftp.ripe.net/ripe/presentations/ripe-m25-tbarber-bgp-damp.html Tony Barber gave a presentation on the strategies used by UUnet-Pipex to reduce the effects of route flapping and to try to prevent router table overflow. These were: - route dampening - prefix filtering - more router memory They had encountered many instabilities from peers and found that many ISPs had not deployed CIDR; this gave rise to more flapping as more routes, and particularly more specific ones, were advertised. Tony explained the parameters used for route dampening on a Cisco router. He had arrived at the following re-use times for various route sizes: /24 and greater ~160 minutes /23 and /22 ~60 minutes /21 and less ~30 minutes He recommended filtering out all prefixes more specific than /24. While route dampening consumed router memory, this was more or less balanced by a reduction in routing CPU cycles. He recommended that if route dampening was to be widely deployed in Europe, consistency was important. In this sense, the Routing WG should agree on guidelines for parameters to be used. In discussion, the following points were made: - aggregation works in reducing router load and route flapping. - route flapping is often a feature of certain autonomous systems rather than a function of prefix length. - much instability was due to configuration changes and errors as distinct from link failures. - making dampening dependent on prefix length could penalise many stable /24s. - it might be useful to discriminate against /24s in the 192.0.0.0/8 block (the swamp). - the focus should be on keeping noise out of the system rather than trying to mitigate against it once in the system. In summary, it was agreed that route dampening was an important topic and that more discussion was needed. 7. Routing Policy analysis tools http://www.isi.edu/ra/Presentations Cengiz Alaettinoglu of ISI presented a review of recent developments and updates in the RA toolset, now at version 3.4.0. The set of front-end tools used a number of back-end libraries, which made program development easier. It required RAWhoisd v3.0 and had been ported to several operating systems. Cengiz gave details of availability (URL = http://www.isi.edu/ra/RAToolSet as official reference or copies also available from ftp://ftp.isi.edu/ra/RAToolSet/RAToolSet-3.4.1.tar.gz or ftp://ftp.ra.net/routing.arbiter/tools/RAToolSet/RAToolSet-3.4.1.tar.gz ) and of the mailing list (ratoolset(a)isi.edu, subscription via robot majordomo(a)isi.edu) The toolset was made available for demonstration purposes to attenders of RIPE 25. RtConfig generated the BGP access list part ofrouter configuration from route objects. It was now used in production by some major network operators. ROE was again shown, with reference to review options before submitting a changed route object. The AS object editor (AOE) was not implemented, though it was on demo at RIPE 25. CIDRAdvisor identifies 'safe' aggregates by route originators as well as aggregates for proxies. Cengiz showed the effects of using various radius values for the distance that aggregation should hold. Summary of Actions ------------------ Action 22.10 on Joachim Schmitz To trigger the discussion on the mailing list of the Routing WG, which focus to choose for a future tool development project and to come to consensus on it Action 24.4 on Joachim Schmitz To investigate the status of the CIDR FAQ and see whether additions are needed, probably by triggering a discussion on the mailing list New action 25.R1 on Daniel Karrenberg/RIPE NCC To report on the results from the route aggregation analysis on the 26th RIPE meeting New action 25.R2 on Joachim Schmitz To coordinate making the presentations at the Routing WG available. This action is already done. Mike Norris 23/9/96 _____________________________________________________________________________ Dr. Joachim Schmitz schmitz(a)noc.dfn.de DFN Network Operation Center Rechenzentrum der Universitaet Stuttgart ++ 711 685 5553 voice Allmandring 30 ++ 711 678 8363 FAX D-70550 Stuttgart FRG (Germany) _____________________________________________________________________________

1 0

RAToolSet 3.4.1 is available for anonymous ftp
by Cengiz Alaettinoglu 16 Oct '96

16 Oct '96

RAToolSet 3.4.1 (contains RtConfig and Route Object Editor in addition to other tools) is now available at http://www.isi.edu/ra/RAToolSet ftp://ftp.isi.edu/ra/RAToolSet The ftp directory also contains binaries for selected architectures. We can make binaries for other systems available upon request. RAToolSet 3.4.1 compiles out of the box for the following systems: SunOS, Solaris, OSF/1, BSDI, FreeBSD, linux, and probably on other systems as well. There is also a mailing list, ratoolset(a)isi.edu. To join, please send a message to majordomo(a)isi.edu with body containing subscribe ratoolset In the upcoming Nanog, there will be demos of these tool. Bug reports, fixes and suggestions for improvements are welcome and appreciated. Cengiz -- Cengiz Alaettinoglu Information Sciences Institute (310) 822-1511 University of Southern California http://www.isi.edu/~cengiz

1 0

draft minutes of the WG session at RIPE 25
by Schmitz＠RUS.Uni-Stuttgart.DE 08 Oct '96

08 Oct '96

Here are the draft minutes of the WG session at RIPE 25. Thanks to Mike Norris for taking them. Comments to the draft minutes are welcome, the final version will be circulated next week. Joachim ------ RIPE 25, Amsterdam Routing Working Group Report of Meeting, 23rd September 1996 1. Opening and Administrivia Willem van der Scheun, Chairman, presided and welcomed people to the meeting. There were 89 attenders. Mike Norris took minutes. 2. Agenda bashing A draft agenda of business, circulated by the Chairman in the previous week, was agreed. 3. Chairman of the Routing WG Willem announced that his day job prevented him from devoting the time necessary to chairmanship of the WG and that he was standing down. He was pleased to say that Joachim Schmitz would accept his proposal to be Chairman, and this proposal was endorsed by the meeting. Members thanked Willem for his work as Chairman and guidance of the WG. Joachim chaired the remainder of the meeting. 4. Report from the RIPE NCC Daniel Karrenberg said that the RIPE NCC planned to resume its studies of route aggregation. An exercise he had conducted earlier in 1996 and reported to RIPE 24 had revealed plenty of room for improvement. Individual reports to those responsible for over-specific routing had resulted in significant improvements. Since then, however, the aggregation situation had disimproved. Daniel's impression was that some ISPs didn't care or wouldn't take the trouble to correct matters. Further remedial action was needed and the Contributors' Committee supported the NCC in this work. Skilled staff would soon be appointed and they would help ISPs in promoting route aggregation. While neither RIPE nor the NCC could take action against any offenders, the use of peer pressure among the ISPs could be used in a positive manner to improve the position. The meeting encouraged ISPs to supply BGP data to the NCC on request for the purpose of analysing route aggregation. New Action: the NCC would report on route aggregation at RIPE 26. 5. Working Experience with Route Object Editor (ROE) ftp://ftp.ripe.net/ripe/presentations/ripe-m25-jschmitz-work-exp-roe.html Joachim Schmitz reported on his experience with ROE. This was part of the RA Toolset and had been written by Cengiz Alaettinoglu. Its purpose was to view and manipulate route objects and to compare them with operational routes. It worked on routes as objects from Internet routing registries (IRRs) and as determined from routers (by means of input BGP tables). Compiled with C++ in a Tcl/Tk environment, ROE was easy to instal. With its GUI it was easy to use. As not all IRRs were aligned in the way they worked, ROE displayed separate route registrations where appropriate. Joachim found it slow in operation, although Cengiz later indicated that this was probably due to network and server performance and not to the ROE program execution. It was also not clear to Joachim whether live or mirrored IRR data was used. He suggested that the program could be improved by allowing more configuration options and greater clarity in some of the messages. This and other feedback should be directed to Cengiz. Overall, he recommended ROE for operational use, particularly for complex routing tasks. 6. Progressive BGP route flap dampening ftp://ftp.ripe.net/ripe/presentations/ripe-m25-tbarber-bgp-damp.html Tony Barber gave a presentation on the strategies used by UUnet-Pipex to reduce the effects of route flapping and to try to prevent router table overflow. These were: - route dampening - prefix filtering - more router memory They had encountered many instabilities from peers and found that many ISPs had not deployed CIDR; this gave rise to more flapping as more routes, and particularly more specific ones, were advertised. Tony explained the parameters used for route dampening on a Cisco router. He had arrived at the following re-use times for various route sizes: /24 and greater ~160 minutes /23 and /22 ~60 minutes /21 and less ~30 minutes He recommended filtering out all prefixes more specific than /24. While route dampening consumed router memory, this was more or less balanced by a reduction in routing CPU cycles. He recommended that if route dampening was to be widely deployed in Europe, consistency was important. In this sense, the Routing WG should agree on guidelines for parameters to be used. In discussion, the following points were made: - aggregation works in reducing router load and route flapping. - route flapping is often a feature of certain autonomous systems rather than a function of prefix length. - much instability was due to configuration changes and errors as distinct from link failures. - making dampening dependent on prefix length could penalise many stable /24s. - it might be useful to discriminate against /24s in the 192.0.0.0/8 block (the swamp). - the focus should be on keeping noise out of the system rather than trying to mitigate against it once in the system. In summary, it was agreed that route dampening was an important topic and that more discussion was needed. 7. Routing Policy analysis tools http://www.isi.edu/ra/Presentations Cengiz Alaettinoglu of ISI presented a review of recent developments and updates in the RA toolset, now at version 3.4.0. The set of front-end tools used a number of back-end libraries, which made program development easier. It required RAWhoisd v3.0 and had been ported to several operating systems. Cengiz gave details of availability (URL = http://www.isi.edu/ra/RAToolSet as official reference or copies also available from ftp://ftp.isi.edu/pub/cengiz/RAToolSet-3.4.0.tar.gz or ftp://ftp.ra.net/routing.arbiter/tools/RAToolSet/RAToolSet-3.4.0.tar.gz ) and of the mailing list (ratoolset(a)isi.edu) The toolset was made available for demonstration purposes to attenders of RIPE 25. RtConfig generated the BGP access list part ofrouter configuration from route objects. It was now used in production by some major network operators. ROE was again shown, with reference to review options before submitting a changed route object. The AS object editor (AOE) was not implemented, though it was on demo at RIPE 25. CIDRAdvisor identifies 'safe' aggregates by route originators as well as aggregates for proxies. Cengiz showed the effects of using various radius values for the distance that aggregation should hold. Summary of Actions ------------------ Action 22.10 on Joachim Schmitz To trigger the discussion on the mailing list of the Routing WG, which focus to choose for a future tool development project and to come to consensus on it Action 24.4 on Joachim Schmitz To investigate the status of the CIDR FAQ and see whether additions are needed, probably by triggering a discussion on the mailing list New action on Daniel Karrenberg/RIPE NCC To report on the results from the route aggregation analysis on the 26th RIPE meeting New action on Joachim Schmitz To coordinate making the presentations at the Routing WG available Mike Norris 23/9/96 _____________________________________________________________________________ Dr. Joachim Schmitz schmitz(a)noc.dfn.de DFN Network Operation Center Rechenzentrum der Universitaet Stuttgart ++ 711 685 5553 voice Allmandring 30 ++ 711 678 8363 FAX D-70550 Stuttgart FRG (Germany) _____________________________________________________________________________

1 0

Short summary of WG session at RIPE25
by Schmitz＠RUS.Uni-Stuttgart.DE 08 Oct '96

08 Oct '96

The following short summary of the WG session at RIPE25 has already been submitted to the RIPE NCC last week. The draft minutes will be circulated this week. Joachim ----- RIPE 25 Short minutes from the Routing WG Meeting 23.9.96 16:00-18:10 89 participants Chairmen: Willem van der Scheun, Joachim Schmitz Scribe: Mike Norris * New chairman Joachim Schmitz (JS395-RIPE), schmitz(a)noc.dfn.de * Presentations Joachim Schmitz, DFN-NOC: Working Experience with ROE Tony Barber, Pipex: Experience with Progressive BGP Route Flap Dampening Cengiz Alaettinoglu, ISI: The RA ToolSet During the RIPE meeting a test installation of the RA ToolSet was accessible to the participants * Actions Action 22.10 on Joachim Schmitz To trigger the discussion on the mailing list of the Routing WG, which focus to choose for a future tool development project and to come to consensus on it Action 24.4 on Joachim Schmitz To investigate the status of the CIDR FAQ and see whether additions are needed, probably by triggering a discussion on the mailing list New action on Daniel Karrenberg/RIPE NCC To report on the results from the route aggregation analysis on the 26th RIPE meeting New action on Joachim Schmitz To coordinate making the presentations at the Routing WG available _____________________________________________________________________________ Dr. Joachim Schmitz schmitz(a)noc.dfn.de DFN Network Operation Center Rechenzentrum der Universitaet Stuttgart ++ 711 685 5553 voice Allmandring 30 ++ 711 678 8363 FAX D-70550 Stuttgart FRG (Germany) _____________________________________________________________________________

1 0

Fwd: Re: mnt-lower attribute not allowed?
by Wilfried Woeber, UniVie/ACOnet 04 Oct '96

04 Oct '96

Dear routing folks ! Just wanted to let you know that we've just started a discussion on how to properly maintain route: objects on the DB-WG list. You're more than welcome to join in on db-wg(a)ripe.net (or we could move the discussion to the routing-wg list :-)! Wilfried. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Subj: Re: mnt-lower attribute not allowed? Hi Steven et.al. ! => => The AS object that matches the origin AS of a route object could be the => parent object of the route object, but then people are still able to put => route objects in with another origin AS which might not be desired by the => owner of the non-portable CIDR address space. Furthermore, a second => hierarchy exists: the IP prefix tree. => => You might want to try to formulate a proposal that is not too => complicated and also addresses the concerns of most people ... = =How about making the inetnum object the parent of the route object? =I think it would make sense to allow the "owner" of the inetnum to create =the route objects.. I'm not convinced that this is the way to go. For two major reasons: - in many environments the routing is handled differently from the address allocation. In particular, where filters or other things are (semi-)automatically derived from objects in the DB, it's certainly not feasable to have the customers ("owner" of the address space) change things without coordination. If they do, it might not reflect reality at all or it might interfere with local logistics. And there's the issue of porting PA address space for a limited amount of time to a different ISP. - I think we should come up with a concept that works as well outside the RIPE-coordinated address space and the central registry concept. I think we should . come up with a solution that works for routing-registries that do not include an address registry in the same DB, . find a solution that works uniformly across all parts of the address space (A, B, C-19[3-5], TWD, et.al.) = You can also keep the owner in the "notify:" field of =the route object, so once you delegate maintenance of the route object to =someone else, you can still keep track of what's happening with it. = =Or does this sound ludicrous? No, it made me think, thus it was a very useful approach :-) I'd favour an approach that is (conceptually) similar to the handling of domain objects - something like an upstream search based on the AS #. Although I haven't a clear picture of how it could work in reality, because the "tree" is certainly less well-defined than in the DNS namespace. Another idea would be to have a registry-pointer in the inetnum objects that identifies a articular regsitry object. This in turn could be used to describe the desired maintainance. We might want to have that linkage anyway? I'm not sure whether that meets David's criteria of "not too complicated and also addresses the concerns of most people" :-) Cheers, Wilfried. -------------------------------------------------------------------------- Wilfried Woeber : e-mail: Woeber(a)CC.UniVie.ac.at Computer Center - ACOnet : Vienna University : Tel: +43 1 4065822 355 Universitaetsstrasse 7 : Fax: +43 1 4065822 170 A-1010 Vienna, Austria, Europe : NIC: WW144 --------------------------------------------------------------------------

1 0

BGP route dampening details
by Tony Barber 03 Oct '96

03 Oct '96

I have put the text of the presentation at the last ripe routing wg at : http://www.pipex.net/people/tonyb/bgp-damp.html fot anyone who is interested. Regards --Tony

1 0

RA tools demo (still) available
by Geert Jan de Groot 30 Sep '96

30 Sep '96

Several people have asked me to keep the machine on which the RA tools were installed would be reachable after the RIPE-meeting. The machine (meeting.ripe.net) will be available for a couple of weeks after the meeting, and the demo account ('rademo', password also rademo) is still operational for those interested. Enjoy, Geert Jan

1 0

RAToolSet
by Cengiz Alaettinoglu 24 Sep '96

24 Sep '96

Hi, RAToolSet can be downloaded from http://www.isi.edu/ra/RAToolSet. Below, I am including the instructions in case some of you may want to try it out next week. My understanding is that the tools will stay installed on meeting.ripe.net (acct name rademo) for a while. Regards. Cengiz -- Cengiz Alaettinoglu Information Sciences Institute (310) 822-1511 University of Southern California http://www.isi.edu/~cengiz ====================================================================== Instructions for RAToolSet Demos ================================ Your feedback on these tools are greatly appreciated. You can download RAToolSet from: ftp.isi.edu:ra/RAToolSet http://www.isi.edu/ra/RAToolSet There is a mailing list ratoolset(a)isi.edu To subscribe, send mail to majordomo(a)isi.edu with body of the message containing "subscribe ratoolset". NOTE: RAToolSet is configured to connect to RAWhoisd running at meeting.ripe.net at port 5045. If you get a connect failed error, RAWhoisd probably is not running anymore. In which case you can connect to whois.ra.net by issuing: unsetenv IRR_HOST unsetenv IRR_PORT To run: 1) cd demo/data NOTE: Most of the executables are in ~cengiz/demo/bin. This directory is already in the PATH of the rademo account. Example data files are in the ~/demo/data directrory. The man pages are in ~demo/man. The MANPATH contains this directory. 2) to generate a config file for a cisco router RtConfig < ornet-gw.ra You may want to examine the file ornet-gw.ra first. This file is used in production to configure one of the routers of Oregon IX (courtesy of Dave Meyer). 3) to generate a route server config file RtConfig -config rsd < rsd.sprint.tmpl rs1.sprint.ra.net is configured using this template file every four hours. You may want to add "-h meeting -p 5055" to speed this up. (see relayd below). 4) roe roe <your-as-number> If you have a cisco bgp dump, you should load it from the file menu. You may want to try "roe AS226", there is a bgp dump file that goes with this AS in file roe_bgp_dump_as226. 5) aoe aoe <your-as-number> If you have a cisco bgp dump, you should load it from the file menu. You may want to try "aoe AS3582", there is a bgp dump file that goes with this AS in file aoe_bgp_dump_as3582. 6) CIDRAdvisor CIDRAdvisor -incl_multihomed AS226 This will not check any policies. Try: CIDRAdvisor -incl_multihomed AS226 -radius -3 to check policies of all ASes 7) peval peval -expand_all 'AS1220 AND AS226' peval will list the multihomed routes between AS1220 and AS226 8) other (9 and 10 below are more interesting) prcheck <your-as-number> pmatch AS3130 cat.isi.edu prpath AS2914 193.85.128.0/24 prtraceroute www.isi.edu we are having problems running prtraceroute on bsdi. 9) relayd is running on meeting.ripe.net on port 5055. All tools above can be run using relayd by issuing the command line options "-h meeting -p 5055". For example: RtConfig -config rsd -h meeting -p 5055 < rsd.sprint.tmpl You will see warning messages saying the data comes from a CACHE. You may also notice certain tools run faster. If you get a connect() failed, most probably somebody rebooted meeting.ripe.net, and relayd is no longer running. You can restart relayd by: relayd -c all-as.db 10) IRRv irrv Rusty's instructions: For a demo the following things can be done: 1. Select "IRR -> AS Peers" menu option and enter as3333. => this expands as3333 2. Find Ebone (as1755) and drag it into the clear 3. Expand Ebone 4. Select "IRR -> Layout -> Gater Peers" => this will collect all of Ebones singly connected peers => around Ebone * at this point you may want expand a few more ases to get the map a bit cluttered to demo the "Gather Nodes" option. following are some suggested expansions 5. Expand as3215 6. Expand as5582 7. Expand UUNet (as175?) => this will cause the uunet icon to turn yellow, indicating no => registered peer info 8. Expand 6708 9. Select "IRR -> Layout -> Group Nodes" && select 3 or 4 levels on the popup => this will group all nodes of degree 3 (or 4) reducing much => clutter. 10. Select RIPE (as3333) and pulldown the 'IRR -> IRR -> Display Autnum" menu. => this will show the '!man,as3333' query results in the text => window. 11. Select RIPE (as3333) and pulldown the 'IRR -> IRR -> Display Routes" menu. => this will show the '!gas3333' query results in the text => window. 12. You can select the 'IRR -> Geographic -> World' to show the geographic ability, although the maps should show as a backdrop, this may produce uninteresting results. *** About exec'ing commands there is an executable script ~eddy/bin/irrv that will change directories to ~eddy/bin and exec tkined. I have symbolic links for: prpath -> ~cengiz/RAToolSet/src/prpath/prpath roe -> ~cengiz/RAToolSet/src/roe/roe prtraceroute -> ~cengiz/demo/bin/prtraceroute that will get executed when the 'IRR -> tools -> ..." gets selected. after executing prtraceroute or prpath using the text log screen and hyper commands, it is safest to quit the log window if you will attempt another exec of prtraceroute or prpath. This is because tkined has a bug that jumbles subsequent hyper link commands.

1 0

Action 24.4: To investigate the status of the CIDR FAQ
by Willem van der Scheun 23 Sep '96

23 Sep '96

The CIDR FAQ is maintained by Hank Nussbacher (hank(a)vm.tau.ac.il or hank(a)ibm.net.il) It's URL is http://www.ibm.net.il/~hank/cidr.html http://www.rain.net/faqs/cidr.faq.html Last version if dated May 1996.

1 0