Build #902

FreeRangeRouting Protocol Suite

Build: #902 was successful Changes by Philippe Guibert

Build result summary

Details

Completed
Duration
91 minutes
Labels
version=frr-3_0-rc1-3259-gc1a00387git=https_//github_com/frrouting/frr_gitbuildurl=https_//ci1_netdef_org/browse/frr-frr-902branch=master
Revision
c1a003878246ccc84ab5986558ca959f4545f738 c1a003878246ccc84ab5986558ca959f4545f738
Total tests
3895
Successful since
#868 ()

Code commits

Author Commit Message Commit date
Philippe Guibert Philippe Guibert c1a003878246ccc84ab5986558ca959f4545f738 c1a003878246ccc84ab5986558ca959f4545f738 Merge pull request #1806 from vivek-cumulus/evpn-ipv6-tenant-routing
*: EVPN symmetric routing for IPv6 tenant routes
vivek <vivek@cumulusnetworks.com> vivek <vivek@cumulusnetworks.com> 4e262455a252c700f81df75fb8107d112062bba8 m 4e262455a252c700f81df75fb8107d112062bba8 Merge branch 'master' of https://github.com/frrouting/frr into evpn-ipv6-tenant-routing
Conflicts:
        bgpd/bgp_evpn.c
vivek <vivek@cumulusnetworks.com> vivek <vivek@cumulusnetworks.com> bfd498f0dab9a1937c6036cd35ed020b64a69e8f m bfd498f0dab9a1937c6036cd35ed020b64a69e8f Merge branch 'master' of https://github.com/frrouting/frr into evpn-ipv6-tenant-routing
Conflicts:
        zebra/zserv.c
vivek <vivek@cumulusnetworks.com> vivek <vivek@cumulusnetworks.com> 558283638bb50ff24ea28bab89c1bb4c89ccc3dd m 558283638bb50ff24ea28bab89c1bb4c89ccc3dd lib, zebra: Fix warnings
Signed-off-by: Vivek Venkatraman <vivek@cumulusnetworks.com>
vivek <vivek@cumulusnetworks.com> vivek <vivek@cumulusnetworks.com> 1ec31309bb056e4492ebf50a12e8bb29a9c4b29a m 1ec31309bb056e4492ebf50a12e8bb29a9c4b29a *: EVPN symmetric routing for IPv6 tenant routes
Implement support for EVPN symmetric routing for IPv6 routes. The next hop
for EVPN routes is the IP address of the remote VTEP which is only an IPv4
address. This means that for IPv6 symmetric routing, there will be IPv6
destinations with IPv4 next hops. To make this work, the IPv4 next hops are
converted into IPv4-mapped IPv6 addresses.

As part of support, ensure that "L3" route-targets are not announced with
IPv6 link-local addresses so that they won't be installed in the routing
table.

Signed-off-by: Vivek Venkatraman vivek@cumulusnetworks.com
Reviewed-by: Mitesh Kanjariya mitesh@cumulusnetworks.com
Reviewed-by: Donald Sharp sharpd@cumulusnetworks.com