You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm attempting to use FRR as a route reflector for our EVPN/MPLS/ISIS-SR network.
It seems to be losing the label for type 1 circuits and sending 1048575 instead (binary 11111111111111111111).
Set up EVPN-MPLS VPWS circuit on equipment with BGP peering and confirm functionality.
Add FRR as route reflector and remove peering. The VPWS no long functions because the devices receive the wrong remote labels.
Expected behavior
Correct labels are sent.
Actual behavior
Labels are sent as 1048575
Additional context
Unclear if this is related to #7292
I have a packet capture with some moderately sensitive data (ASN) in it I can provide access to.
Checklist
I have searched the open issues for this bug.
I have not included sensitive information in this report.
The text was updated successfully, but these errors were encountered:
Description
I'm attempting to use FRR as a route reflector for our EVPN/MPLS/ISIS-SR network.
It seems to be losing the label for type 1 circuits and sending 1048575 instead (binary 11111111111111111111).
Update received by FRR:
Update sent by FRR:
Version
How to reproduce
Set up EVPN-MPLS VPWS circuit on equipment with BGP peering and confirm functionality.
Add FRR as route reflector and remove peering. The VPWS no long functions because the devices receive the wrong remote labels.
Expected behavior
Correct labels are sent.
Actual behavior
Labels are sent as 1048575
Additional context
Unclear if this is related to #7292
I have a packet capture with some moderately sensitive data (ASN) in it I can provide access to.
Checklist
The text was updated successfully, but these errors were encountered: