We are exhilarated to announce the latest release of the Routinator, version 0.2.0 ‘Instant Gezellig.’
Routinator is an RPKI relying party software that collects and validates statements made in the Resource Public Key Infrastructure (RPKI) about allowed route origins and provides them to routers and curious researchers alike.
This release both cleans up the initial release and prepares for new features to come. Most importantly, we decided to change command line handling and switched to the ever popular model of requesting actions via sub-commands. You can now request a list of the validated ROA payload (aka VRP) via the vrps command and start the RTR server via rtrd.
Instead of repeating options over and over again, you can now put them into a config file. You can either explicitly pick a file via the -c option or keep .routinator.conf in your home directory. The config file can contain all global options and the additional options for the RTR server. It is a TOML file. A complete example is available in the source repository.
Another change is that we adjusted the output formats for the vrps command to be even closer to those used by the RIPE NCC Validator by adding trust anchor information. On top of that, Job Snijders contributed a new output that makes it easier to use Routinator with OpenBGPD.
Finally, deployment is now ever so much easier thanks to the Dockerfile contributed by David Monosov. If you are using Docker, you can now get Routinator from the Docker Hub simply by:
docker pull nlnetlabs/routinator
If you have Routinator installed from cargo.io, you can upgrade to the latest release via:
cargo install --force routinator