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

IRRdb filters: use "AS<n>" in case of an empty AS-SET from PeeringDB #15

Closed
pierky opened this issue Oct 15, 2017 · 1 comment
Closed

Comments

@pierky
Copy link
Owner

pierky commented Oct 15, 2017

This issue is used to track the problem raised by @job with #14.

When no AS-SETs are configured for a client nor for its ASN, the AS-SET from the PeeringDB record can be used to build IRR-based filters. Until now, if the AS-SET fetched from PeeringDB is empty/non-existent, also the resulting filter is empty.

@pierky pierky closed this as completed in 9b05e3a Oct 15, 2017
@pierky
Copy link
Owner Author

pierky commented Oct 15, 2017

With v0.12.3, the ASn macro is always considered when building IRRdb-based filters, so even in the case of empty/non-existent AS-SETs fetched from PeeringDB an attempt is made by expanding the ASN autnum object itself.

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

No branches or pull requests

1 participant