-
Notifications
You must be signed in to change notification settings - Fork 684
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
v3 API ignores Global ApplyPolicy configuration #2814
Comments
Policy in gobgp.StartBgpRequest will be ignored if I remember correctly. You could work around like the following:
|
@fujita Thanks! If configuring a policy is not supported during startup, would you be open to a pull request to delete Or adding an error on startup if it's populated? |
I prefer to add an error because I don't want to change the API without the major version updated. |
Hi,
I am working with an existing GoBGP integration that uses the "v3 API", via a direct Go import. I am attempting to configure a default import policy over the API similar to the example shown in https://github.com/osrg/gobgp/blob/master/docs/sources/policy.md#42-attach-policy-to-route-server-client.
I am not seeing the expected result. This configuration should reject all announced BGP paths toward the GoBGP instance, yet they continue to be accepted and imported.
In #1768 (comment), I see another person reported the same issue with the V3 API on an old, closed, issue.
My code is as follows:
In the output below, I am observing the accepted/imported routes from the GoBGP instance using a custom CLI tool. This is a route that was announced to a remote FRR instance and then advertised into this GoBGP instance. It should have been rejected.
The text was updated successfully, but these errors were encountered: