-
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
bgpd: fix for the validity and the presence of prefixes in the BGP VPN table. #17370
base: master
Are you sure you want to change the base?
Conversation
106e889
to
fdd3c21
Compare
fdd3c21
to
ad5959e
Compare
ad5959e
to
0a4f3e1
Compare
b4c2e9b
to
dc3a481
Compare
ci:rerun |
1 similar comment
ci:rerun |
bgpd/bgp_mplsvpn.c
Outdated
|
||
if (attrhash_cmp(bpi->attr, new_attr) && labelssame && | ||
!CHECK_FLAG(bpi->flags, BGP_PATH_REMOVED) && | ||
!!leak_update_nexthop_valid(to_bgp, bn, new_attr, afi, safi, source_bpi, bpi, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: leak_update_nexthop_valid() is already bool, no need for !!
.
ci:rerun |
dc3a481
to
c821483
Compare
This pull request has conflicts, please resolve those before we can evaluate the pull request. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looks good
conflicts need to be resolved and @ton31337 's comment addressed before we can push ... |
They are the same value. Signed-off-by: Louis Scalbert <[email protected]>
Mark a nexthop as invalid if the origin VRF is unusable, either because it does not exist or its interface is down. Signed-off-by: Louis Scalbert <[email protected]>
When leak_update() rechecks an existing path, it considers nothing to update if the attributes and labels are not changed. However, it does not take into account the nexthop validity. Perform a leak update if the nexthop validity has changed. Signed-off-by: Louis Scalbert <[email protected]>
Do not leak if origin vrf is not usable Signed-off-by: Louis Scalbert <[email protected]>
Update route_leak_basic tests. The routes with an unusable nexthop VRF are no more present in the RIB. Signed-off-by: Louis Scalbert <[email protected]>
The bgp_bmp test is failing because r2 lacks the vrf1 VRF, which prevents it from exporting VPN prefixes from the configured vrf1 BGP instance. Previous versions allowed the export of static BGP prefixes from a non-existent VRF, so the test passed under those conditions. Add a vrf1 VRF on r2. Fixes: d748544 ("topotests: add basic bgp bmp test") Signed-off-by: Louis Scalbert <[email protected]>
Check bgp vpn table in bgp_vpnv4_route_leak_basic Signed-off-by: Louis Scalbert <[email protected]>
In bgp_vpnv4_route_leak_basic, remove and add back the static prefix 172.16.3.0/24 on VRF DONNA. Before the previous fixes, the 172.16.3.0/24 prefix re-appeared when it was added back in the VPN table but it was marked as invalid. Signed-off-by: Louis Scalbert <[email protected]>
c821483
to
7712a51
Compare
Fix for the validity and the presence of prefixes in the BGP VPN table.
See individial commit logs