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

Add feature to disallow user-specified ASNs from downstreams #50

Open
forkwhilefork opened this issue Jul 28, 2021 · 3 comments
Open

Add feature to disallow user-specified ASNs from downstreams #50

forkwhilefork opened this issue Jul 28, 2021 · 3 comments

Comments

@forkwhilefork
Copy link
Owner

Customers should never announce routes from tier1s. If they do, it's probably a leak. This may also be true of peers... though I might be able to peer with e.g. 6939, so maybe that should be configurable.

@forkwhilefork
Copy link
Owner Author

This should implement a new function which can be used in filters that's very similar to has_bogon_asn() but uses a different constant list of ASNs. That list will be configurable by the user.

@forkwhilefork
Copy link
Owner Author

This is blocked by #37.

@forkwhilefork forkwhilefork changed the title Disallow tier1 ASNs from downstreams Add feature to disallow user-specified ASNs from downstreams Aug 12, 2021
@forkwhilefork
Copy link
Owner Author

This is partially implemented. There's a static constant that lists transit ASNs that should not be allowed. There is not a way to change this in the config file though.

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

No branches or pull requests

1 participant