Fetch certificates and ROAs via rsync
Perform cryptographic validation
Export validated ROAs in CSV, JSON and RPSL format
Add local white list exceptions and overrides (RFC 8416)
Implement the RPKI-RTR protocol for pushing RPKI data to supported routers (RFC 6810)
Exhaustive interoperability and compliance testing
Implement the RRDP protocol for fetching (RFC 8182)
Implement a basic web-based user interface and Command Line Interface
Expose an API
Add the ability to process Internet Routing Registry data
Integration with alerting and monitoring services so that route hijacks, misconfigurations, connectivity and application problems can be flagged.

RPKI

The Resource Public Key Infrastructure provides cryptographically signed statements about the association of Internet routing resources. In particular, it allows the holder of an IP address prefix to publish which AS number will be the origin of BGP route announcements for it.

All of these statements are published in a distributed repository. Routinator will collect these statements into a local copy, validate their signatures, and construct a list of associations between IP address prefixes and AS numbers. It provides this information to routers supporting the RPKI-RTR protocol or can output it in a number of useful formats.

Getting Started

There’s two things you need for Routinator: rsync and Rust and a C toolc… There is three things you need for Routinator: rsync, Rust and a C toolchain. You need rsync because the RPKI repository currently uses rsync as its main means of distribution. You need Rust because that’s what the Routinator has been written in. Some of the cryptographic primitives used by the Routinator require a C toolchain, so you need that, too.

Since this currently is a very early experimental version, we decided not to distribute binary packages just yet. But don’t worry, getting Rust and building packages with it is easy.

rsync

Currently, Routinator requires the rsync executable to be in your path. We are not quite sure which particular version you need at the very least, but whatever is being shipped with current Linux and *BSD distributions and macOS should be fine.

If you don’t have rsync, please head to http://rsync.samba.org/.

Rust

While some system distributions include Rust as system packages, Routinator relies on a relatively new version of Rust, currently 1.29. We therefore suggest to use the canonical Rust installation via a tool called rustup.

To install rustup and Rust, simply do:

curl https://sh.rustup.rs -sSf | sh

or, alternatively, get the file, have a look and then run it manually. Follow the instructions to get rustup and cargo, the rust build tool, into your path.

You can update your Rust installation later by simply running

rustup update

C Toolchain

Some of the libraries Routinator depends on require a C toolchain to be present. Your system probably has some easy way to install the minimum set of packages to build from C sources. If you are unsure, try to run cc on a command line and if there’s a complaint about missing input files, you are probably good to go.

Building and Running

In the directory you cloned this repository to, say

cargo build --release

This will build the whole thing in release mode (or fail, of course). If it succeeds, you can run

cargo run --release

to run the binary that has been built. If this is the first time you’ve been using Routinator, it will create $HOME/.rpki-cache, put the trust anchor locators of the five RIRs there, and then complain that ARIN’s TAL is in fact not really there.

Follow the instructions provided and try again. You can also add additional trust anchors by simple dropping their TAL file in RFC 7730 format into $HOME/.rpki-cache/tals.

Now Routinator will rsync the entire RPKI repository to your machine (which will take a while), validate it and produce a long list of AS numbers and prefixes.

When running, you might get rsync errors, such as from rpki.cnnic.cn. You can ignore these. Certainly, Routinator will.

Note that the --release flag is important as the produced binary is about ten times faster than the one built if you skip that flag.

There is a number of command line options available. You can have cargo pass them to the executable after a double hyphen. For instance, if to find out about them, run

cargo run --release -- -h

The manual page in doc/routinator.1 has detailed information about those options. Read it via

man doc/routinator.1

Feeding a Router with RPKI-RTR

Routinator supports RPKI-RTR as specified in RFC 8210. It will act as an RTR server if you start it with the -r (or --repeat) or -d (--daemon) option. In the latter case it will detach from the terminal and log to syslog while in repeat mode it’ll stay with you.

You can specify the address(es) to listen on via the -l (or --listen) option. If you don’t, it will listen on 127.0.0.1:3323 by default. It will not use the default RTR port of 323 since you need to be root to bind to that port. Also, note that the default address is localhost for security reasons.

So, in order to run Routinator as RTR server listening on port 3323 on both 192.0.2.13 and 2001:0DB8::13 in repeat mode, execute

cargo run --release -- -r -l 192.0.2.13:3323 -l [2001:0DB8::13]:3323

Note that RTR support (like everything else in the Routinator right now) is still experimental and may break in new and creative ways. You might not want to make production routing decision based on it just yet.

Local Exceptions

If you would like to add exceptions to the validated RPKI data in the form of local filters and additions, you can specify this in a file using JSON notation according to the SLURM standard. You can find two example files in /test/slurm. Use the -x option to refer to your file with local exceptions.

When playing with these options, you might find -n useful. It will cause Routinator to skip the rsync-ing of the repository – which should be unnecessary if you re-run in quick succession.

README.md Unescape Escape

🚀 Routinator 3000.