cumulus-frr

~cdwertmann/cumulus-frr/+git/trunk:mergify/bp/stable/8.0/pr-9498

Git
lp:~cdwertmann/cumulus-frr/+git/trunk
mergify/bp/stable/8.0/pr-9498

Last commit made on 2021-08-26

Get this branch:: git clone -b mergify/bp/stable/8.0/pr-9498 https://git.launchpad.net/~cdwertmann/cumulus-frr/+git/trunk

Branch merges

Branch information

Name:: mergify/bp/stable/8.0/pr-9498

Repository:: lp:~cdwertmann/cumulus-frr/+git/trunk

Recent commits

013575f... by Igor Ryzhov <email address hidden> on 2021-08-26

bgpd: fix update-source for ipv6

There's no IPv6 LL address on loopback/vrf interfaces. So if the user
configures update-source, the session is never going to be established.

Signed-off-by: Igor Ryzhov <email address hidden>
(cherry picked from commit 2ebb354c415590dc28b07ab18b6d8f16c4f7b6aa)

7ed45c9... by Donald Sharp <email address hidden> on 2021-08-26

Merge pull request #9186 from FRRouting/mergify/bp/stable/8.0/pr-8637

Pim vrf acl fixes (backport #8637)

589a1e8... by Mark Stapp <email address hidden> on 2021-08-24

Merge pull request #9424 from FRRouting/mergify/bp/stable/8.0/pr-9385

bgpd: fix segfault when re-adding "match evpn default-route" rule (backport #9385)

1aa59a0... by Donatas Abraitis <email address hidden> on 2021-08-24

Merge pull request #9459 from FRRouting/mergify/bp/stable/8.0/pr-9426

bgpd: imported evpn rt5 routes copy igpmetric (backport #9426)

ce1fb82... by Philippe Guibert on 2021-08-17

bgpd: imported evpn rt5 routes copy igpmetric

when doing BGP over an IGP platform, the expectation is that
the path calculation for a given prefix takes into account the
igpmetric given by IGP.
This is true with prefixes obtained in a given BGP instance where
peering occurs. For instance, ipv4 unicast entries or l2vpn evpn
entries work this way. The igpmetric is obtained through nexthop
tracking, like below:

south-vm# show bgp nexthop
Current BGP nexthop cache:
1.1.1.1 valid [IGP metric 10], #paths 1, peer 1.1.1.1
2.2.2.2 valid [IGP metric 20], #paths 1, peer 2.2.2.2

The igp metric is taken into account when doing best path
selection, and only the entry with lowest igp wins.

[..]
*>i[5]:[0]:[32]:[5.5.5.5]
                    1.1.1.1 0 100 0 ?
                    RT:65400:268435556 ET:8 Rmac:2e:22:6c:67:bb:73
* i 2.2.2.2 0 100 0 ?
                    RT:65400:268435556 ET:8 Rmac:f2:d3:68:4e:f4:ed

however, for imported EVPN RT5 entries, the igpmetric was not
copied from the parent path info. Fix it. In this way, the
imported route entries use the igpmetric of the parent pi.

Signed-off-by: Philippe Guibert <philippe.guibert@6wind.com>
(cherry picked from commit 56c70d87149ebdf9f399a882b3ecd1cec4e84b76)

e01cebf... by David Lamparter <email address hidden> on 2021-05-18

pimd: fix PtP address handling

When we have a "192.0.2.1 peer 192.0.2.2/32" address on an interface, we
need to (a) recognize the local address as being on the link for our own
packets, and (b) do the IGMP socket lookup with the proper local address
rather than the peer prefix.

Fixes: efe6f18 ("pimd: fix IGMP receive handling")
Cc: Nathan Bahr <email address hidden>
Signed-off-by: David Lamparter <email address hidden>
(cherry picked from commit a2810d30256e8de250b9e0fdc274fc4852c7877c)

86c6c84... by Martin Winter on 2021-05-04