nlnetlabs/ziggy

Ziggy: the RPKI Wayback Machine

Ziggy: the RPKI Wayback Machine

Copyright (c) 2019 NLnet Labs (https://nlnetlabs.nl/)

All rights reserved. Distributed under a 3-clause BSD-style license. For more information, see LICENSE

Dependencies

Ziggy requires Python 3 to run, and has been tested with Python 3.6 on Ubuntu 18.04LTS.

Note that the script also requires the Python dateutil package to be installed. This is available for most distributions as a native package, for example, on an Ubuntu system the following command installs this package:

$ apt install python3-dateutil

Running Ziggy

Configuration file

Ziggy uses a very simple configuration file in JSON format. Currently, the following keys should be defined in the config:

• routinator -- the full path to the routinator executable to run
• routinator-cache -- path to the Routinator repository cache (note: for Routinator version older than 0.6 you should change the value in the sample configuration to ~/.rpki-cache/repository)
• routinator-tals -- path to the Routinator TAL cache
• vrp-out-format -- output format to ask Routinator for
• vrp-out-name -- output filename for VRP data, {} is replaced by the date in ISO notation (e.g. 2018-01-01)
• routinator-log-name -- filename for the log, {} is replaced by the date in ISO notation
• ignore-tals -- a list of repositories for which Ziggy should not generate a TAL, even if a TA certificate is available

A sample file called sample-ziggy.conf is included in the repository.

Running

Running Ziggy is as simple as invoking:

$ ./ziggy.py -c <config-file> -d <date-in-ISO>

Where <date-in-ISO> is the date for which to extract data in ISO notation (e.g. 2018-01-01 for January 1st, 2018).

Ziggy will end by running the Routinator. It shows you the command line it uses to invoke Routinator so you can easily re-run Routinator if you wish to.

ziggy's Issues

ignore-tals attribute in sample ziggy configuration

First of all thanks for this great tool

I was looking in the sample-ziggy.conf and I've noticed that in the ignore-tals attribute you include two tals: "ca.rg.net" and"rpki-repository.nic.ad.jp".

Is there any particular reason why you excluded these TALs in the sample configuration (i.e. do you recommend them being excluded), or it's just an example and you could have added any TAL there?

Warning, found no TA keeps showing up

Greetings,
I am using routinator for some months now, and I would like to retrieve some ROAs from the past. So ziggy seems to be a perfect choice. The problem is that even with a clean installation of routinator and ziggy as shown in your instructions, I keep getting this warning.
"Ziggy is processing data for 2022-01-01
Got https://ftp.ripe.net/rpki/afrinic.tal/2022/01/01/repo.tar.gz
No data found at https://ftp.ripe.net/rpki/apnic-afrinic.tal/2022/01/01/repo.tar.gz
No data found at https://ftp.ripe.net/rpki/apnic-arin.tal/2022/01/01/repo.tar.gz
No data found at https://ftp.ripe.net/rpki/apnic-iana.tal/2022/01/01/repo.tar.gz
No data found at https://ftp.ripe.net/rpki/apnic-lacnic.tal/2022/01/01/repo.tar.gz
No data found at https://ftp.ripe.net/rpki/apnic-ripe.tal/2022/01/01/repo.tar.gz
Got https://ftp.ripe.net/rpki/apnic.tal/2022/01/01/repo.tar.gz
Got https://ftp.ripe.net/rpki/arin.tal/2022/01/01/repo.tar.gz
Got https://ftp.ripe.net/rpki/lacnic.tal/2022/01/01/repo.tar.gz
Got https://ftp.ripe.net/rpki/ripencc.tal/2022/01/01/repo.tar.gz
Cleaning out /home/user/.rpki-cache/repository/rsync ... OK
Cleaning out /home/user/.rpki-cache/tals ... OK
Ziggy is processing /tmp/afrinic.tal.tar.gz ... OK (5078 objects)
Warning, found no TA in /tmp/afrinic.tal.tar.gz
Ziggy is processing /tmp/apnic.tal.tar.gz ... OK (33450 objects)
Warning, found no TA in /tmp/apnic.tal.tar.gz"

and this keeps going resulting that I am not able to use routinator.

My system is Ubuntu 20.4

Regards

Antonis