-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
VPN import excludes routes with system AS #17797
Comments
You are missing |
No, this feature is enable, please check this route.
This route not leaked to VRF |
I don't see it in your configuration. |
Yes, I didn't put all the settings.
|
Try putting |
Don't working. This feature works on versions < 10.2
|
Check this topotest as an example: 77857dc. |
This example is a route leak from a default VRF, in this case between two (non-default) VRFs. |
Example output in frr v10.1
|
Just to be on the same page, could you show the debug log when import does not happen? With UPDATE: Confirmed that it works with 10.1, and broken with 10.2. |
Possible to test this patch out #17800? You can grab the .deb packages from here: https://ci1.netdef.org/browse/FRR-PULLREQ3-6852/artifact/shared/Debian-12-%28Bookworm%29-x86_64-Packages/. |
Now working. Thanks for your help.
|
The issue #17607 is closed but the problem persist in 10.2.1 version.
Since version 10.2 we still cannot share the routes that our AS has between the different VRFs.
FRR version:
Package version:
For example: 1.1.1.0/24 in vrf angola
Our prefix announced in external site (remote site): 190.103.176.0/24 in vrf angola
Both prefixes in internal VRF:
Angola configuration:
Internal VRF:
Activate share routes between VRFs.
The shared configuration is minimal and sufficient to be able to test the problem.
The text was updated successfully, but these errors were encountered: