Hi Tim,
Thanks for the reply. I have confirmed that the entitlements displayed
in the UI are the same as before the issue, specifically:
ASN: AS59893, AS211591
IPv4: 45.148.76.0/22
IPv6: 2a0f:9400::/29
I'll try and get the CLI output as well.
Chris
On 08/07/2021 13:34, Tim Bruijnzeels wrote:
Hi Christopher,
This is strange indeed. It sounds a bit like your resource entitlements under
RIPE NCC may have changed.
Going with that assumption:
Krill will only allow you to create ROAs for prefixes that you hold on a certificate (or any
certificate under any parent if you have multiple). However if you lose the resource on your
certificate then it can no longer create the signed ROA objects. What is confusing - and I should
prioritise this higher I now realise - is that the UI and API will list your previously configured
"Authorisations" still. These are not actual ROAs but your intent to create ROAs if you
see what I mean. If you get back the resources then the ROA objects will be re-created
automatically. What is missing from the UI though is a clear indication which
"Authorisation" configs would be for space you no longer hold on your certificates.
Can you check the status and resources under each parent?
You can look at the 'parents' tab in the UI, but if you have access to the CLI
then please run:
krillc parents statuses --ca <your-ca>
This gives a little more info than the UI I think. You can also run this
command with --format json to get even more info.
If you prefer you can share your results with [email protected] instead of
this list - of course we would be more than happy to report back when we get
further.
Kind regards,
Tim, on behalf of the NLnet Labs RPKI Team
On 8 Jul 2021, at 21:05, Christopher Munz-Michielin via RPKI
<[email protected]> wrote:
Hi All,
Got a weird issue with Krill and publishing RIPE ROAs. Background: We have been
running Krill with 1 RIPE, 2 ARIN and 1 APNIC parents for the better part of a year
without issue, but yesterday we started receiving reports that all our RIPE ROAs had
been dropped, indeed when I look at
https://jdr.nlnetlabs.nl/#/search/%2Frpki-repo%2Frsync%2Frpki.ripe.net%2Frepository%2FDEFAULT%2F3JsPwPrhyzvSi50Bqvw1Y_2pUdo.cer
<https://jdr.nlnetlabs.nl/#/search/%2Frpki-repo%2Frsync%2Frpki.ripe.net%2Frepository%2FDEFAULT%2F3JsPwPrhyzvSi50Bqvw1Y_2pUdo.cer>
this does appear to be the case.
I have verified all the ROA's exist via the Krill API as well as in the GUI.
So far I have tried restarting Krill, Deleting and re-adding some ROAs, as well
as deleting the delegation from RIPE and re-creating it all to no avail. I'm
at the point where I'm getting ready to blow the whole setup away and rebuild
from scratch, but figured I would reach out here first to see if anyone has a
suggestion to recover from this weird situation.
Version of krill is 0.8.2 on ubuntu 20.04 installed from the package manager.
No other RIR's seem to be effected by this.
--
RPKI mailing list
[email protected]
https://lists.nlnetlabs.nl/mailman/listinfo/rpki
--
RPKI mailing list
[email protected]
https://lists.nlnetlabs.nl/mailman/listinfo/rpki
