Job Snijders
Job Snijders
So we were not reading the RFC carefully enough all this time? I guess this mitigates the problem I outlined to some degree?
@cjeker can you rebase?
please feel free to make a pull-request!
@cjeker can you rebase?
Yes, `rtrdump` (at least on the `master` branch) downgrades: ``` $ ./dist/rtrdump-v0.5.1-62-g9416292-linux-x86_64 INFO[0000] Connecting with plain to 127.0.0.1:8282 INFO[0000] Downgrading to version 1 $ jq -c '.metadata' output.json {"vrps":599727,"aspas":0,"bgpsec_pubkeys":0} ```
Can you use one of these? https://packages.debian.org/search?keywords=stayrtr&searchon=names&suite=all§ion=all
The recipe to make the Debian package is available here: https://salsa.debian.org/md/stayrtr
@ties sorry for the late response - you still want this?
I've tagged our current master as v0.3.0 - a prerelease. I am down for going through a full cycle, and then tagging the result that as a v1.0.0 for production...
What version of StayRTR are you running? Are you using `rpki-client`? What operating systems are in play? Are the two RTR servers located in similar places in the network topology...