1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
|
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=windows-1252">
<META NAME="Generator" CONTENT="Microsoft Word 97">
<TITLE>MRT User's Guide</TITLE>
</HEAD>
<BODY LINK="#0000ff" VLINK="#800080">
<B><FONT FACE="Arial" SIZE=7><EM><P ALIGN="CENTER"><A NAME="_Toc409238192"><A NAME="_Toc409241003"></P>
<P ALIGN="CENTER"> </P>
<P ALIGN="CENTER"> </P>
<P ALIGN="CENTER">IRRd</P>
<P ALIGN="CENTER">User/Configuration Guide</P>
</B></FONT></EM><I><FONT FACE="Arial" SIZE=6><STRONG><P ALIGN="CENTER">Version 1.4.3 Alpha</P>
</FONT><FONT FACE="Arial" SIZE=4><P ALIGN="CENTER">(Draft 2/27/98 3:46 PM)</P>
</I></FONT><FONT SIZE=7><P> </P>
<P> </P>
<P> </P>
<P> </P>
</FONT></STRONG><B><FONT SIZE=5><P><A NAME="_Toc410609075"><A NAME="_Toc412873690"></A></A>Copyright (c) 1997, 1998</P>
</B></FONT><FONT FACE="Courier" SIZE=3><P> </P>
<P> </P>
<P>The Regents of the University of Michigan ("The Regents") and Merit Network, Inc. All rights reserved.<BR>
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:</P>
<P>1. Redistributions of source code must retain the above <BR>
copyright notice, this list of conditions and the <BR>
following disclaimer.</P>
<P>2. Redistributions in binary form must reproduce the above <BR>
copyright notice, this list of conditions and the <BR>
following disclaimer in the documentation and/or other <BR>
materials provided with the distribution.</P>
<P>3. All advertising materials mentioning features or use of <BR>
this software must display the following acknowledgement:</P><DIR>
<DIR>
<P>This product includes software developed by the University of Michigan, Merit Network, Inc., and their contributors.</P></DIR>
</DIR>
<P>4. Neither the name of the University, Merit Network, nor the<BR>
names of their contributors may be used to endorse or <BR>
promote products derived from this software without <BR>
specific prior written permission.</P>
<P>THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. </P>
</FONT><FONT SIZE=5><STRONG><P>Table of Contents</P>
<P> </P>
</FONT></STRONG><FONT SIZE=2><P></A></A>1. Introduction	</FONT><A HREF="#_Toc413050816">*</A><DIR>
<FONT SIZE=2><P>Document Conventions	</FONT><A HREF="#_Toc413050817">*</A></P>
<FONT SIZE=2><P>Getting Help	</FONT><A HREF="#_Toc413050818">*</A></P>
<FONT SIZE=2><P>Credits	</FONT><A HREF="#_Toc413050819">*</A></P>
<FONT SIZE=2><P>2. Obtaining the IRRd Code	</FONT><A HREF="#_Toc413050820">*</A></P>
<FONT SIZE=2><P>System Requirements	</FONT><A HREF="#_Toc413050821">*</A></P>
<FONT SIZE=2><P>3. Building and Installation Procedure	</FONT><A HREF="#_Toc413050822">*</A></P>
<FONT SIZE=2><P>4. Using IRRd	</FONT><A HREF="#_Toc413050823">*</A></P>
<FONT SIZE=2><P>Getting Started	</FONT><A HREF="#_Toc413050824">*</A></P>
<FONT SIZE=2><P>Synopsis	</FONT><A HREF="#_Toc413050825">*</A></P>
<FONT SIZE=2><P>Options	</FONT><A HREF="#_Toc413050826">*</A></P>
<FONT SIZE=2><P>Description	</FONT><A HREF="#_Toc413050827">*</A></P>
<FONT SIZE=2><P>Interactive Interface	</FONT><A HREF="#_Toc413050828">*</A></P>
<FONT SIZE=2><P>Configuration Commands	</FONT><A HREF="#_Toc413050829">*</A></P>
<FONT SIZE=2><P>Machine/Tool Interface	</FONT><A HREF="#_Toc413050830">*</A></P>
<FONT SIZE=2><P>Related Documents	</FONT><A HREF="#_Toc413050831">*</A></P>
<P> </P></DIR>
<FONT FACE="Courier" SIZE=3> </P>
</FONT><H2><A NAME="_Toc413050816">1. Introduction</A></H2>
<P>IRRd is a streamlined, stand-alone version of the Internet Routing Registry (IRR) database server. When used in conjunction with policy tools such as RtConfig, Roe, and Aoe, the IRRd server allows: </P>
<UL>
<LI>Automated generation of route configuration files and access-lists</LI>
<LI>Internet topology visualization</LI>
<LI>Network trouble-shooting and debugging</LI></UL>
<P>Besides the usual RIPE whois queries, the IRRd Server also provides a protocol for getting information from RIPE-style database files that is not easily (or rapidly) obtainable using the standard RIPE whois queries. These queries can be submitted one-at-a-time via whois, or by establishing a connection to the server, issuing multiple queries, and then closing the connection.</P>
<P>IRRd is currently bundled with the Multi-threaded Routing Toolkit (MRT). a platform for developing and debugging routing protocols and routing code. In addition to IRRd, MRT includes multi-protocol routing daemons, network anyalyzers, routing simulators and routing management tools.,</P>
<H3><A NAME="_Toc413050817">Document Conventions</A></H3>
<P>The following document conventions are used in the <I>IRRd User/Configuration Guide:</P>
<UL>
</I><LI>Commands and keywords are in <B>boldface</B>.</LI>
<LI>User-supplied variables are enclosed in <angle brackets>.</LI>
<LI>Optional elements are shown in [square brackets].</LI>
<LI>Alternative but required keywords are grouped in {braces} and separated by a vertical bar.</LI></UL>
<H3><A NAME="_Toc413050818">Getting Help</A></H3>
<P>The IRRd and MRT development teams are available to answer questions and provide configuration advice. We are also very interested in bug reports, feature requests, and general feedback. Please contact us by sending e-mail to db-admin@ra.net.</P>
<H3><A NAME="_Toc413050819">Credits</A></H3>
<P>IRRd was developed by Gerald Winters, Jake Khuon, and Craig Labovitz of the Internet Engineering Group at Merit.</P>
<P>MRT was originally developed by Merit Network, Inc., under National Science Foundation grant NCR-9318902, "Experimentation with Routing Technology to be Used for Inter-Domain Routing in the Internet." Current MRT research is supported by the National Science Foundation (NCR- 9710176) and a gift from Intel Corporation. The design and ideas behind many of the MRT libraries draws heavily on the architecture pioneered in the GateD routing daemon. </P>
<P> </P>
<STRONG><H2><A NAME="_Toc412284087"><A NAME="_Toc413050820">2. Obtaining the IRRd Code</A></A></H2>
</STRONG><P><A NAME="_Toc409238217">IRRd is currently bundled with the Multi-threaded Routing Toolkit. The IRRd binaries are available from:</P>
<P>	xx</P>
<P>To obtain current copies of the Internet Routing Registry databases, ftp the databases and CURRENT_SERIAL number from the Internet Routing Registry ftp site: </P>
<FONT FACE="Courier New" SIZE=3><P>ftp://ftp.merit.net/routing.arbiter/radb/dbase </P>
</FONT><P>These files stored in the irr_directory file configured in the IRRd config file. By default, /var/spool/IRRd/ is used.</A> (need help here)</P>
<P>For real-time mirroring, you will need to contact the database administrators to obtain the appropriate IP address and port number used for mirroing service. At present, only the RADB, RIPE, and ANS registries support real-time mirroring. For other database, a Perl FTP cronjob client is available. Send email to <A HREF="mailto:db-admin@ra.net">db-admin@ra.net</A> for more information.</P>
<P>Although the binaries are compiled with IPv6 extensions, most of them will run on IPv4-only platforms. Examples of configuration files are found in each tool directory under programs, or in the conf directory in the binary distribution. </P>
<H3><A NAME="_Toc413050821">System Requirements</A></H3>
<P>GCC is recommended but other commercial compilers will also work. </P>
<P>IRRd runs with native POSIX threads (pthreads) on Solaris 2.5 or later. IRRd does not work correctly with the MIT Pthreads library. IRRd is designed to run under threads-capable operating systems, but the code will run on uni-processor systems lacking thread and shared memory support. Without threads, however, the software's performance will be significantly degraded (but may be sufficient for some situations). </P>
<P>Because the IPv6 kernel implementations and API specifications are still in flux, IRRd may not run on the latest IPv6 platforms. On systems running Linux IPv6, IRRd may require the inet6 library, and the code will not compile with glibc-2.x. </P>
<P>We have compiled and tested IRRd and the other MRT tools on the following systems/environments:</P>
<UL>
<LI>Solaris 2.5.1 </LI>
<LI>Linux 2.0.27 and 2.1.63 </LI>
<LI>FreeBSD 2.2.1 & 2.2.2 </LI>
<LI>NetBSD 1.1 and 1.2 </LI>
<LI>SunOS 4.1.3 and 4.1.4 </LI></UL>
<P>MRT provides IPv6 support for: </P>
<UL>
<LI>Solaris IPv6 Release 5.2 (Solaris 2.5.1) </LI>
<LI>Linux IPv6 (2.1.63) </LI>
<LI>INRIA IPv6 (970903, FreeBSD 2.2.2) </LI>
<LI>WIDE IPv6 (hydrangea 970225, BSD/OS 2.1) </LI>
<LI>NRL IPv6 (Sep96, NetBSD 1.2) </LI></UL>
<P>Other users have reported that MRT runs on: </P>
<UL>
<LI>IRIX (version?) </LI></UL>
<H2><A NAME="_Toc412284088"><A NAME="_Toc413050822">3. Building and Installation Procedure</A></A></H2>
<P>This chapter explains how to download, build, and install the IRRd code. We recommend that you use the IRRd binaries, but if desired, source code is also available.</P>
<OL>
<LI>Obtain the source archive and then <B>unzip</B> and <B>untar</B> it. There should be a directory named mrt-<version>.</LI>
<CODE><P>% <B>cd</B> /tmp</P>
<P>% <B>ftp</B> ftp.merit.edu</P>
<P>ftp> <B>cd</B> /net-research/mrt</P>
<P>ftp> <B>get</B> irrd.tar.gz</P>
<P>ftp> <B>quit</P>
</B><PRE>% <B>cd</B> /usr/local/src
% <B>gzip</B> -cd < /tmp/irrd.tar.gz | <B>tar</B> xvf
</CODE>
Change (<B>cd</B>) into that directory and run the shell script <B>make-sym-links.</B> This will create a new directory named src.[platform]. Change into this new directory and run <B>./configure</B>. The make-sym-links script allows the same source directory to build IRRd on multiple platforms. </LI></PRE>
<CODE><P> </P>
<P>% <B>cd</B> /usr/local/src/mrt-<version></P>
<P>% <B>sh</B> <B>make-sym-links</P>
</B><P>% <B>cd</B> src.<platform></P>
<P>% ./<B>configure</P>
</B></CODE><LI>Now run <B>make</B>. After successful compilation, you will have binaries in each of the source directories and src/obj/[platform]/[lib/bin/]. If you don't need all of the MRT tools, delete those you don't need under the directory programs before running configure. If you will not be compiling the code on another platform at a later time, you can change the directory to src and run ./configure without running make-sym-links. </LI>
<CODE><P>% <B>make</P>
</B></CODE><LI>Run make install. By default, binaries and libraries will be installed in /usr/local/[/lib|/bin]. See the the man page for configure if you want to change the default install directory.</LI>
<CODE><PRE>% <B>su</PRE>
</B><P># <B>make</B> <B>install</P>
</B></CODE><LI>IRRd features a telnet user interface. You can optionally specify the port on which the tools listen for telnet connections by adding the following line to /etc/services. Feel free to choose your own port numbers. </LI></OL>
<PRE>
irrd		5673/tcp # MRT IRRd routing registry server</PRE>
<P> </P>
<H2><A NAME="mrt"><A NAME="bgpsim"><A NAME="sbgp"><A NAME="route_btoa"><A NAME="route_atob"><A NAME="netnowd"><A NAME="_Toc409238208"><A NAME="_Toc409241011"><A NAME="IRRd"></H2>
<H2><A NAME="_Toc413050823">4. Using IRRd</A></H2>
<H3><A NAME="_Toc413050824">Getting Started</A></H3>
<P>IRRd can be invoked from the command line, or from the Unix boot/startup script. Below is an example of starting the IRRd routing daemon from the command line:</P><DIR>
<DIR>
<CODE><P>> /usr/local/bin/irrd </P></DIR>
</DIR>
</CODE><P>Once running, IRRd will begin to listen for user telnet connections on the TCP port specified in /etc/services. The daemon may be configured by editing a configuration file, or by invoking the configuration utility from the interactive user telnet interface. Below is an example of telneting to the user interactive interface (UII) port on a machine running IRRd. The "irrtd" number has been configured in /etc/services (see the Installation Manual for more information).</P><DIR>
<DIR>
<CODE><P>>telnet mrt.merit.edu irrd </P>
<P>MRT version 1.4.2 ALPHA January 8, 1998</P>
<P>User Access Verification</P>
<P>[71] password> ***</P>
<P>[71] MRTd></P></DIR>
</DIR>
</CODE><P>If a password is specified in the configuration file, it must be supplied at the password prompt. Initially, IRRd and other MRT programs default to no password access control and restrict user interactive telnet to the loopback address or the interface address of the local machine.</P>
<P>The IRRd user interface supports Unix shell-like redirection (<B>></B> or <B>>></B> <B>filename</B>) for output. To edit a line, emacs-like line editing, including ^a, ^e, ^b, ^f, ^d, ^k, ^u and ^c, is available. To reuse a previous line, the tcsh-line history function is available by typing ^p and ^n.</P>
<H3><A NAME="_Toc409238209"><A NAME="_Toc413050825">Synopsis</A></A></H3>
<P><A NAME="_Toc409238210">irrd [-v] [-f config file]</A> </P>
<H3><A NAME="_Toc409238211"><A NAME="_Toc413050826">Options</A></A></H3>
<B><P>-<FONT SIZE=2>f config_file </P><DIR>
<DIR>
</B><P>Specify the configuration file to use. By default, IRRd looks in /etc/irrd.config. </P></DIR>
</DIR>
<B><DL>
<DT>-v </DT>
</DL>
</B><P>Verbose logging </P>
</FONT><H3><A NAME="_Toc409238212"><A NAME="_Toc413050827">Description</A></A></H3>
<P><A NAME="_Toc409238213">The current version of IRRd supports mirroring and</A> <A NAME="_Toc409238214">updates.</A> <A NAME="_Toc409238215">Interactive telnet connections are on port "irrd" in /etc/services.</A> </P>
<H3><A NAME="_Toc413050828">Interactive Interface</A> </H3>
<P><A NAME="_Toc409238220">IRRd provides an interactive user interface that shows the status of measurement tests and parameters.</A> </P>
<P><A NAME="_Toc409238221">The port number can be specified in the configuration. The default is a number associated with "irrd" or 5675. If a password is specified in the configuration, it must be supplied on login.</A> </P>
<P><A NAME="_Toc409238222">Unix shell-like redirection (or filename) is available for output. To edit a line, emacs-like line editing including ^b, ^f, ^d, ^k, ^u and ^c is available. To reuse a previous line, tcsh-line history function is available by typing ^p and ^n.</A> </P>
<P>The IRRd command language shares many similarities with the language used on Cisco Systems routers. Commands include:</P>
<UL>
<B><LI>show config</B>view the configuration file</LI>
<B><LI>show version</B>show the current version</LI>
<B><LI>show threads</B>show the status of application threads</LI>
<B><LI>config</B>enter configuration mode</LI>
<B><LI>write</B>save volatile memory configuration to disk<B> </LI>
<LI>reboot</B>restart the application</LI>
<B><LI>help</B>shows all commands available</LI>
<B><LI>exit</B>leave the UII interface</LI>
<B><LI>mirror</B>Synchronize database with remote server</LI>
<B><LI>reload</B>Reload an IRR database file</LI>
<B><LI>show database</B>Show database status</LI>
<B><LI>show threads</B>Show status of threads</LI>
<B><LI>show version</B>Show version and uptime</LI>
<B><LI>sync</B>Synchronize IRR diskfiles with memory</LI></UL>
<B><P> </P>
</B><P>Below is an example of a user interactive telnet command to the IRRd daemon:</P>
<P> </P><DIR>
<CODE><P>[47] IRRd> show databases</P>
<P>Database Size (kb) Rt Obj AutNum Obj Serial #</P>
<P>--------- -------- ------ --------- --------</P>
<P> mci 6722.3 40076 435 0</P>
<P> radb 10257.5 42913 1083 19889</P>
<P> ans 58654.5 9067 24 6498</P>
<P> ripe 3823.7 16854 1461 1312991</P>
<P> canet 1027.3 9073 58 0</P>
<P> </P>
<P> </P>
<P>mci mirroring 198.108.0.8</P>
<P>radb mirroring 198.108.0.8</P>
<P>ans mirroring 198.108.0.8</P>
<P>ripe mirroring 198.108.0.8</P>
<P>canet mirroring 198.108.0.8</P>
</CODE><P> </P></DIR>
<H3><A NAME="_Toc413050829">Configuration Commands</A> </H3>
<P>When IRRd is started for the first time and no configuration file exists on disk, the programs will create a default configuration in volatile memory. This configuration may be modified in memory by issuing the "<B>config"</B> command from the UII telnet interface prompt. Modifications to volatile memory may be saved to disk using the "<B>write</B>" command. Modifications not saved to disk will be lost if the application terminates or is rebooted.</P>
<P>Upon startup, IRRd will search for the default configuration file for the application (usually /etc/<application_name.conf>). The user may also override the default configuration file by providing a "-<B>f <filename></B> " flag on the command line of the application.</P>
<U><P>A WARNING </U> Most, but not all, configuration commands may be issued even through the interactive, telnet interface. In this alpha release, the modification of volatile memory occasionally may have unintended side effects. In rare instances, the alteration of some volatile memory setting may crash the application. We recommend most configuration changes be made directly to the configuration file on disk. The program must be restarted, or <B>rebooted</B>, to reread the changed configuration file. Improved support for configuration management will be available with the next release of IRRd.</P>
<H4>No-style commands, such as no ip route .... have not yet been implemented for many configuration commands. Command prefixes can be used for both IPv4 and IPv6 configurations, but IPv6 features may not be available on IPv4-only platforms. </H4>
<P>IRRd supports the following configuration commands:</P>
<B><P>uii</B>configures the user interface (by telnet)</P>
<B><FONT SIZE=2><P>uii_password <string> <access-list number></P><DIR>
<DIR>
<DIR>
<DIR>
</B><P>Sets a password <string> for telnet interface. Note that if a password is not set, access verification will not be performed and interactive user telnet connections will be disabled. If <access-list number> is specified, telnet connections will be restricted to IP addresses allowed by the access list. See the access-list description below for more information.</P></DIR>
</DIR>
</DIR>
</DIR>
<B><P>uii port <number> </P><DIR>
<DIR>
<DIR>
<DIR>
</B><P>Changes the port number with <number> for the telnet interface. The default is the port value specified in /etc/services for the application name. If a /etc/services entry does not exist, the port number assigned to the service defaults to "mrt" or 5674.</P></DIR>
</DIR>
</DIR>
</DIR>
</FONT><B><P>debug</B>controls debug options</P>
<B><FONT SIZE=2><P>debug <flag> [<file> [<size>]]</P><DIR>
<DIR>
<DIR>
<DIR>
</B><P>Logs debug messages specified <flag> to <file>. If the limit is specified with <size>, the file will be truncated after reaching at the limit. If <file> is omitted, stderr will be chosen.</P></DIR>
</DIR>
</DIR>
</DIR>
<PRE> <flag></FONT><B> .... info, norm, trace, parse, packet, state, timer, all
<file> .... filename or "stdout".
		 Some applications also support "syslog"
			
</PRE>
<P>access-list</B>defines a filter</P>
<B><FONT SIZE=2><P>access-list <number> {permit|deny} <prefix> [refine|exact]</P><DIR>
<DIR>
<DIR>
<DIR>
</B><P>Defines an access list <number>, which permits or denies access if the condition is matched. <B>all</B> can be specified as <prefix>. <B>exact</B> will be assumed if neither <B>refine</B> or <B>exact</B> is specified. <B>exact</B> matches only the prefix, while <B>refine</B> matches more specific prefixes, excluding the prefix itself.</P>
<P>Matches are performed in the order in which they appear. At the end of a list with the same number, <B>permit all</B> is assumed.</P></DIR>
</DIR>
</DIR>
</DIR>
</FONT><B><P>!</B>comment and separator</P><DIR>
<DIR>
<FONT SIZE=2><P>Comments can appear at the beginning of a line, or any other place in the line. A comment at the beginning of a line is treated as a separator, which ends a command clause followed by its sub-commands, such as router and interface.</P></DIR>
</DIR>
</FONT><B><P>redirect</B>allows shell-like redirection of output (> or >>).</P><DIR>
<DIR>
<B><FONT SIZE=2><P>redirect</B> <directory></P><DIR>
<DIR>
<P>Allows redirection to files in this directory. Unrestricted redirection was deemed a security problem.</P></DIR>
</DIR>
</DIR>
</DIR>
</FONT><B><P>irr_directory</B>specify the cache directory for database files</P>
<B><FONT SIZE=2><P>irr_directory <path> </P>
</FONT><P>irr_database</B>the database to be included and served by this server</P>
<B><FONT SIZE=2><P>irr_database <name> [mirror_host <hostname> [<port>] [authoritative] </P><DIR>
<DIR>
<DIR>
<DIR>
</B><P>Include a database named <<B>name</B>>.db in the IRR directory in the list of databases provided by the Server. If available, enable automatic mirroring to <B>hostname</B> on the selected <B>port</B> (default is 43). If <B>authoritative</B> keyword is used, updated will be allowed for this database.</P></DIR>
</DIR>
</DIR>
</DIR>
</FONT><B><P><BR>
irr_mirror_interval</B>The interval for obtaining mirror updates</P>
<B><FONT SIZE=2><P>irr_mirror_interval <</B>seconds> <B> </P>
</FONT><P>irr_port</B>The port to listen on for "RAWhoisd" style machine TCP connections</P>
<B><FONT SIZE=2><P>irr_port <</B>port<B>></P>
</B></FONT><P>After editing the configuration file, the user may return to the top-level of the interactive telnet interface by typing a <B>^Z</B> or entering <B>exit</B>. Below is an example of an interactive telnet session using the IRRd configuration mode.</P><DIR>
<DIR>
<P>[example to be supplied]</P>
<P> </P></DIR>
</DIR>
<H3><A NAME="_Toc409238218"><A NAME="_Toc413050830"></A></A>Machine/Tool Interface</A></A></H3>
<P><A NAME="_Toc409238219">RADB-style machine telnet queries are available on the port specified in the configuration file.</A> Although IRRd was designed for use by tools such as RtConfig, peval, and PRtraceroute, it is also extremely useful for compute-intensive queries generated by individuals.</P>
<B><FONT SIZE=2><P>g command</P>
</B></FONT><PRE>	Get routes with specified origin.
	e.g., <B>!gas1234
h command
</B>	Get routes with specified community.
	e.g., <B>!hCOMM_NSFNET
i command with option 1
</B>	Return all lines of as-macro. Recursive lookup available.
	e.g., <B>!iAS-ESNETEU </B>	# non-recursive, don't expand
				# any embedded marcos
	e.g., <B>!iAS-ESNETEU,1</B> 	# expand any embedded AS marcos
<B>man command
</B>	Get the aut-num object with the specied key.
<B>	man,</B>aut-num
<B>	mam,</B>as-macro
<B>	mcm,</B>community
<B>	mmt,</B>maintainer
<B>	eg, !man,as1234
q command
</B>	Quit the IRRd session.
	eg, <B>!q
r command with option l, o, L
</B>	Perform route searches.
	 Default finds exact prefix/len match.
	<B>o </B>- return origin of exact match(es)
	<B>l</B>one-level less specific
<B>	L</B>all less specific
<B>	M</B>all more specific
<B>	</B>e.g.,<B> !r141.211.128/24,l
s command
</B>	Set the sources to the specified list.
	 Default is all sources.
<B>	</B>e.g.<B>, !sradb,ans
	lc - </B>show the currently selected sources
	 e.g.,<B> !s-lc
</PRE>
<FONT SIZE=2><P>u command</P><DIR>
<DIR>
</B><P>Update the database</P></DIR>
</DIR>
</FONT><B><PRE>	!us<database>start update
	 <ADD | DEL> <OBJECT>
	!ueend update
</PRE>
</B><P>IRRd treats each database (i.e., the RADB and the ANS, MCI, and RIPE databases) as a separate object. As a general algorithm, IRRd will scan each database and return an answer from each. However, the <B>!m </B>... commands (i.e., match objects commands) and the <B>!i</B>... command use a slightly different general algorithm.</P>
<P>The <B>!m</B>... commands return immediately after finding an object, even if an identical object exists in another registry. The <B>!m</B> command is used to find a match for an object and will return at most one object. For example,</P>
<FONT FACE="Courier" SIZE=2><P>!man,AS1234</P>
<P>A351</P>
<P>*an: AS1234</P>
<P>*de: Imatran Voima Ltd</P>
<P>*de: IVOWAN</P>
<P>*ai: AS790 100 ANY</P>
<P>*ai: AS1759 100 AS544 OR AS1759</P>
<P>*ao: AS1234 AS1234</P>
<P>*ao: AS1759 AS1234</P>
<P>*ac: TT18-RIPE</P>
<P>*tc: JT35-RIPE</P>
<P>*tc: LK34-RIPE</P>
<P>*tc: KS76-RIPE</P>
<P>*ny: jan.tamlander@ttgroup.fi</P>
<P>*ny: lauri.kumpulainen@ttgroup.fi</P>
<P>*ny: kalevi.sinkko@ttgroup.fi</P>
<P>*mb: DATANET-NOC</P>
<P>*ch: Jarmo.Oksanen@tele.fi 951120</P>
<P>*so: RIPE</P>
<P>C</P>
</FONT><P><BR>
The <B>!i</B> command finds AS macro objects and will recursively expand embedded AS macros when the proper option is specified. For example,</P>
<FONT FACE="Courier" SIZE=2><P>!iAS-ICINET</P>
<P>A24</P>
<P>AS6561 AS7252 AS-LTINET</P>
<P>C</P>
<P>!iAS-ICINET,1</P>
<P>A28</P>
<P>AS6561 AS7252 AS7790 AS7346</P>
<P>C</P>
</FONT><P> </P>
<P>The !i command searches the databases in the order specified by the user and returns when it finds an object. When the <B>,1</B> option is specified to indicate embedded macro expansion, the command will expand embedded macros using the database where the macro was found. The other database sources, as specified by the user, will only be used when a match is not found in the source in which the macro was found.</P>
<P>Therefore in the above sample command <B>!iAS-ICINET,1</B>, assuming the specified search order is RADB, RIPE, MCI, ANS, CANET (Bell Canada), and the embedded macro AS-LTINET is found in the ANS registry, AS-LTINET will be expanded first in the ANS registry, rather than in the RADB.</P>
<P>Below is an example of telneting to the IRRd command port and issuing a command to see all less specific routes:</P><DIR>
<DIR>
<FONT FACE="Courier New" SIZE=2><P>home% telnet irrserver 5006</P>
<P>Trying 198.108.60.133...</P>
<P>Connected to irrserver.</P>
<P>Escape character is '^]'.</P>
</FONT><CODE><P>!r198.108.60.88/32,L</P>
<P>A329</P>
<P>*rt: 198.108.0.0/14</P>
<P>*nh: 192.41.177.181</P>
<P>*as: 3561 237 IGP </P>
<P>*or: AS237</P>
<P>*so: mae_east</P>
<P> </P>
<P>*rt: 198.108.0.0/14</P>
<P>*nh: 198.32.128.129</P>
<P>*as: 3561 237 IGP </P>
<P>*or: AS237</P>
<P>*so: pb</P>
<P> </P>
<P>*rt: 198.108.0.0/14</P>
<P>*nh: 198.32.130.12</P>
<P>*as: 3561 237 IGP </P>
<P>*or: AS237</P>
<P>*so: aads</P></DIR>
</DIR>
</CODE><P></A></A></A></A></A></A></A></P>
<H3><A NAME="_Toc413050831"></H3>
<H3>Related Documents</A></H3><DIR>
<DIR>
<P>Bates, T., E. Gerich, L. Joncheray, J-M. Jouanigot, D. Karrenberg, M. Terpstra, and J. Yu. Representation of IP Routing Policies in a Routing Registry (ripe-81++). ftp://nic.merit.edu/documents/rfc1786.</P>
<P>Colton, R., Ferguson, D. and J. Moy. OSPF for IPv6.<BR>
ftp://nic.merit.edu/documents/internet-drafts/ draft-ietf-ospf-ospfv6-05.txt </P>
<P>Gerich, E., Karrenberg, D., Meyer, D., Terpstra, M. Villamizar, C., Alaettinoglu, C., and T. Bates. Routing Policy Specification Language (RPSL). <BR>
ftp://nic.merit.edu/documents/internet drafts/draft-ietf-rps-rpsl-04.txt,ps. </P>
<P>Malkin, G. and R. Minnear. RIPng for IPv6.<BR>
ftp://nic.merit.edu/documents/rfc2080.</P>
<P>Marques, P.R. and F. Dupont. Use of BGP-4 Multiprotocol Extensions for IPv6 Inter-Domain Routing. <BR>
ftp://nic.merit.edu/documents/internet_drafts/draft-ietf-idr-bgp4-ipv6-00.txt</P>
<P>Moy, J. OSPF Version 2. <BR>
ftp://nic.merit.edu/documents/internet-drafts/draft-ietf-ospf-vers2-02.txt </P>
<P>The RADB and the Internet Routing Registry, <I>in </I>RADB Frequently Asked Questions, http://www.ra.net/RADB.tools.docs/.faq.html.</P>
<P> </P></DIR>
</DIR>
</BODY>
</HTML>
|
