-
Notifications
You must be signed in to change notification settings - Fork 443
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
Api process of a template announce routes to other templates #1005
Comments
Thank you for the report Cédric. Have you tested if things are working as should when the process section is under the neighbour, please? |
I just removed all template and used only neighbors with process inside. something similar to :
Still no luck. |
I remember reading somewhere ages ago - I could be wrong though - that there were some known limitations of API / processes causing cross-neighbor propagation back then, not sure if this still applies. |
In my case similar to. All routes are sent to all peers ignoring the inherited template.
Version:
|
I'm having the same issue with the processes set under the With the desired configuration, I get errors about mismatched address family constantly appearing in the logs. On further investigation, adding both v4/v6 unicast to both BGP sessions, I can confirm that the 'foreign' routes are being passed to the peer. Maybe the configuration is incorrect? The documentation for this feature is terrible. There doesn't seem to be a single example with multiple healthchecks in one configuration. What I have (want) is
With this configuration, routes from both service checks appear at both BGP peers. I am using the Ubuntu 20.04 packages, but did confirm the same behaviour with 4.2.13.
|
I am experiencing a similar issue. All processes are run on all neighbors even when explicitly stating the process names on them. ExaBGP : 4.2.4 |
Thank you @thomas-mangin ! |
You are nice, but I should be sorry as I overlooked this for way too long ... |
** Bug Report **
Describe the bug
I have two templates, one for public IP announce and another one for private IP announce to a different network/interface.
Each templace has an api process that announce specific routes.
But all routes are sent to all peers ignoring the inherited template.
To Reproduce
Use this config (local/remote AS removed...) :
Expected behavior
Routes announced by process dynamic_routes_public should only be announced to neighbor x.x.x.x.
Routes announced by process dynamic_routes_private should only be announced to neighbor y.y.y.y.
Environment (please complete the following information):
Additional context
The text was updated successfully, but these errors were encountered: