Skip to content

Conversation

mergify[bot]
Copy link

@mergify mergify bot commented Feb 4, 2025

When peering with an EVPN device from other vendor, FRR acting as route reflector is not able to read nor transmit the label value.

Actually, EVPN AD routes completely ignore the label value in the code, whereas in some functionalities like evpn-vpws, it is authorised to carry and propagate label value.

Fix this by handling the label value.


This is an automatic backport of pull request #17985 done by Mergify.

When peering with an EVPN device from other vendor, FRR acting as route
reflector is not able to read nor transmit the label value.

Actually, EVPN AD routes completely ignore the label value in the code,
whereas in some functionalities like evpn-vpws, it is authorised to
carry and propagate label value.

Fix this by handling the label value.

Signed-off-by: Philippe Guibert <philippe.guibert@6wind.com>
(cherry picked from commit 1cefe94)
@riw777 riw777 merged commit 567c6d6 into stable/10.2 Feb 4, 2025
13 of 15 checks passed
@Jafaral Jafaral deleted the mergify/bp/stable/10.2/pr-17985 branch February 26, 2025 16:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants