MRTPolicy

MRTPolicy applies RIPE-181 import or export MRTPolicy for a specified AUT-NUM object to a stream of MRT routing messages. MRTPolicy ouputs a modified stream of MRT routing messages containing RIPE-181 preferences for each route in the input stream. Routes not specifically allowed by policy have a negative preference.

MRTPolicy can be used to apply either import (the policy expressed by an AUT-NUM objects as_in lines) or export policy.

By default, MRTPolicy will query the default database (radb.ra.net) to obtain the AUT-NUM object specified on the command line.

Synopsis

mrtpolicy [-v] [-i input_file] [-o output_file] [-p policy_file] [-s database_server] [-r process_name] [-w process_name] (export | import) autnum AS

OPTIONS

-i
Name of input file containing binary MRT routing messages. An argument 'stdin' will read from standard input (this is the default).

-o
Name of binary output file. An argument of 'stdout' will write to standard output (this is the default).

-v
Verbose mode. Print all tracing and error messages to stdout.

-s
Name of database server to query for specified AUT-NUM object

-p
Name of file containing RIPE-181 policy
-l
Logfile name. By default, ripe181 writes trace information to /tmp/ripe181.log


Example

Apply AS690 RIPE-181 import (as_in) policy to an MRT route stream containing routes sent in BGP updates from peer AS237:
> mrtpolicy -i input_routes -o out import 690 237

BUGS

Lots -- this is an ALPHA release after all!

AUTHOR

Craig Labovitz, Merit Network, Inc.