summaryrefslogtreecommitdiff
path: root/lib/libfrr.c
diff options
context:
space:
mode:
authorPhilippe Guibert <philippe.guibert@6wind.com>2023-02-01 17:28:15 +0100
committerPhilippe Guibert <philippe.guibert@6wind.com>2023-05-09 21:01:08 +0200
commit37a02a8dcb0dcbd46e93307559a2aacb3d1f7681 (patch)
treeba25af6458dfd617493b05b6e41952f2617300e1 /lib/libfrr.c
parentae5a6bc1f6baacb3bd1695615e922ec28bdf9c62 (diff)
topotests: add bgp_vpnv6 test allocation
This test demonstrates that a label is allocated for each ipv6 next-hop. IPv6 test introduces link local ipv6 addresses as next hops, and compared to IPv4, one can have two different next-hops depending if the next-hop is defined by a global address (static route redistributed) or a bgp peer. This test checks that: - The labels are correctly allocated per connected next-hop. - The default label is used for non connected prefixes. - The withdraw operation frees the MPLS entry. - If a recursive route is redistributed by BGP, then the nexthop tracking will find the appropriate nexthop entry, and the associated label will be found out. - When a prefix moves from one peer to one another behind the vrf, then the MPLS switching operation for return traffic is changing the outgoing interface to use. - When the 'label vpn export <value>' MPLS label value is changed, then the modification is propagated to prefixes which use that value. - Also, when unconfiguring the per-nexthop allocation mode, check that the MPLS entries and the VPNv4 entries of r1 are changed accordingly. - Reversely, when re-configuring the per-nexthop allocation mode, check that the allocation mode reuses the other label values. Signed-off-by: Philippe Guibert <philippe.guibert@6wind.com>
Diffstat (limited to 'lib/libfrr.c')
0 files changed, 0 insertions, 0 deletions