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.

Sign up for GitHub

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

Jump to bottom

After route synchronization, a change in policy does not cause a change in routes, but actual routers would respond accordingly #2821

Open
blackbutton opened this issue Jun 24, 2024 · 0 comments
Open

After route synchronization, a change in policy does not cause a change in routes, but actual routers would respond accordingly #2821

blackbutton opened this issue Jun 24, 2024 · 0 comments

Comments

@blackbutton
Copy link

For example, one AS announces the prefix 97.16.10.0/24 to another AS for synchronization, and after synchronization is complete, the announcing AS adds a policy to reject the prefix 97.16.10.0/24. After the policy is published, the other AS still has the prefix. Does GOBGP not support this feature?
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@blackbutton