diff options
Diffstat (limited to 'doc/07.RPKI.RP.rpki-rtr.md')
| -rw-r--r-- | doc/07.RPKI.RP.rpki-rtr.md | 19 |
1 files changed, 11 insertions, 8 deletions
diff --git a/doc/07.RPKI.RP.rpki-rtr.md b/doc/07.RPKI.RP.rpki-rtr.md index 017f55ab..59f6fdb0 100644 --- a/doc/07.RPKI.RP.rpki-rtr.md +++ b/doc/07.RPKI.RP.rpki-rtr.md @@ -1,16 +1,15 @@ # rpki-rtr -`rpki-rtr` is an implementation of the ["RPKI-router" protocol -(RFC-6810)](http://www.rfc-editor.org/rfc/rfc6810.txt). +`rpki-rtr` is an implementation of the ["RPKI-router" protocol (RFC-6810)][RFC-6810]. -`rpki-rtr` depends on `rcynic` to collect and validate the RPKI data. `rpki- -rtr`'s's job is to serve up that data in a lightweight format suitable for -routers that want to do prefix origin authentication. +`rpki-rtr` depends on [rcynic][] to collect and validate the RPKI data. +`rpki-rtr`'s's job is to serve up that data in a lightweight format suitable +for routers that want to do prefix origin authentication. To use `rpki-rtr`, you need to do two things beyond just running `rcynic`: - 1. You need to post-process `rcynic`'s output into the data files used by rpki-rtr. The `rcynic-cron` script handles this automatically, so the default installation should already be taking care of this for you. - 2. You need to set up a listener for the `rpki-rtr` server, using the generated data files. The platform-specific packages for FreeBSD, Debian, and Ubuntu automatically set up a plain TCP listener, but you will have to do something on other platforms, or if you're using a transport protocol other than plain TCP. + 1. You need to [post-process `rcynic`'s output][rpki-rtr] into the data files used by rpki-rtr. The `rcynic-cron` script handles this automatically, so the default installation should already be taking care of this for you. + 2. You need to [set up a listener][rpki-rtr] for the `rpki-rtr` server, using the generated data files. The platform-specific packages for FreeBSD, Debian, and Ubuntu automatically set up a plain TCP listener, but you will have to do something on other platforms, or if you're using a transport protocol other than plain TCP. ## Post-processing rcynic's output @@ -117,7 +116,7 @@ required by the protocol specification. `rpki-rtr listener` is a free-standing plain TCP server which just listens on a TCP socket then forks a child process running `rpki-rtr server`. -All of the caveats regarding plain TCP apply to `rpki-rtr listener`. +All of the [caveats regarding plain TCP][rpki-rtr] apply to `rpki-rtr listener`. `rpki-rtr listener` takes one required argument, the TCP port number on which to listen; it also accepts a second argument which specifies the rcynic output @@ -145,3 +144,7 @@ running the rpki-rtr link over an unsecured TCP connection. $ rpki-rtr client tcp <hostname> <port> 2. `rpki-rtr show` will display a text dump of pre-digested data files in the current directory. + +[RFC-6810]: http://www.rfc-editor.org/rfc/rfc6810.txt +[rcynic]: 06.RPKI.RP.rcynic.md +[rpki-rtr]: 07.RPKI.RP.rpki-rtr.md |