Skip to content

Latest commit



89 lines (66 loc) · 2.43 KB


File metadata and controls

89 lines (66 loc) · 2.43 KB

Example Scenario

To make it clearer how you can deploy RTRTR, below is an example scenario. This flow may not be entirely realistic, but it intends to show all the different ways you can wire units and targets together using a visual representation and the configuration file needed to accomplish it.

In this example, there is routing infrastructure in a data centre labeled as dc1. To ensure redundancy, it gets Validated ROA Payloads (VRPs) primarily from relying party software running in the eu-west-3 location, using the RTR protocol. There are two backups configured: a validator serving RTR in ap-south-1 and an instance from another vendor offering a feed in JSON format in us-east-2. A unit of the type any is configured to get a feed from all three and, should the first one fail, do a round robin to the next available one.

To make the management of some statically configured routes for this location easy, the slurm unit gets its data from the any unit so only a single file has to be kept up-to-date.

Finally, an http target is configured to get the VRPs without the SLURM exceptions, to be fed into internal tooling and an rtr unit is defined to serve the routing infrastructure.

Example of an RTRTR data flow

Example of an RTRTR data flow

Configuration File

log_level = "debug"
log_target = "stderr"
log_facility = "daemon"
log_file = "/var/log/rtrtr.log"

http-listen = [""]


type = "rtr"
remote = ""

type = "rtr"
remote = ""


type = "json"
uri = ""
refresh = 60


type = "any"
sources = [ "eu-west-3", "ap-south-1", "us-east-2" ]
random = false


type = "slurm"
source = "round-robin"
files = [ "/var/lib/rtrtr/local-expections.json" ]


type = "rtr"
listen = [ "" ]
unit = "static-routes"


type = "http"
path = "/json"
format = "json"
unit = "round-robin"