-
Notifications
You must be signed in to change notification settings - Fork 15
Open
Labels
All vendorsIf something needs to be done for all supported platformsIf something needs to be done for all supported platformsenhancementNew feature or requestNew feature or requestgood first issueGood for newcomersGood for newcomers
Description
It should be possible to configure in peers.yaml the list of routers that should be ignored for a specific peer. This would make it easier to not set up a session to a specific peer.
Now you have to configure in peers.yaml to ignore everything that is on PeeringDB and copy the router IPs and prefix limits from PeeringDB to peers.yaml manually. And you have to keep this up-to-date afterwards. This approach will generate issues somewhere in the future.
Metadata
Metadata
Assignees
Labels
All vendorsIf something needs to be done for all supported platformsIf something needs to be done for all supported platformsenhancementNew feature or requestNew feature or requestgood first issueGood for newcomersGood for newcomers