Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

AFRINIC TA malfunctions #1204

Closed
massimocandela opened this issue Nov 30, 2023 · 4 comments
Closed

AFRINIC TA malfunctions #1204

massimocandela opened this issue Nov 30, 2023 · 4 comments
Labels
documentation Improvements or additions to documentation

Comments

@massimocandela
Copy link
Member

Are you receiving TA malfunctions for AFRINIC? Those alerts are correct.

See https://lists.afrinic.net/pipermail/dbwg/2023-November/000493.html

@massimocandela massimocandela added the documentation Improvements or additions to documentation label Nov 30, 2023
@massimocandela massimocandela pinned this issue Nov 30, 2023
@Ferine2016
Copy link

How can we filter those alerts?

@discostur
Copy link

Yes, we are seeing the malfunctions ROA from AFRINIC since weeks:

Possible TA malfunction or incomplete VRP file: 29.27% of the ROAs disappeared from afrinic

I think it startet around october 26 ...

@job
Copy link
Contributor

job commented Dec 12, 2023

We've made a number of changes to rpki-client to change the response to detection of issues with inconsistent publications. This means that the issues still are happening, but that the "Possible TA Malfunction" alert will fire less often.

For a full description of the code change see this commit openbsd/src@102443c

Note: the TA still is malfunctioning, but a TA would have to malfunction for multiple consecutive hours before this fires. The rpki-client code changes do not solve the underlaying problems at the TA side.

@massimocandela
Copy link
Member Author

massimocandela commented Feb 12, 2024

BGPalerter v1.33.0 has been released a few days ago. It includes the possibility to specify a tolerance threshold for each TA (see toleranceDeletedRoasTA and toleranceExpiredRoasTA here).
However, to benefit from this new feature you need to generate a new config.yml file, or manually add the tolerance values.

Suggested tolerance values are:

      toleranceDeletedRoasTA:
        ripe: 20
        apnic: 20
        arin: 20
        lacnic: 20
        afrinic: 50
      toleranceExpiredRoasTA:
        ripe: 20
        apnic: 20
        arin: 20
        lacnic: 20
        afrinic: 50

The short format toleranceDeletedRoasTA: 20 (previously supported) is also accepted to retain back compatibility. However, this will apply the same tolerance to all TAs (instead of a higher one for AFRINIC).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

No branches or pull requests

4 participants