plugins: FRR: Can no longer match a prefix-list in a route-map
Important notices Before you add a new report, we ask you kindly to acknowledge the following:
- I have read the contributing guide lines at https://github.com/opnsense/plugins/blob/master/CONTRIBUTING.md
- I have searched the existing issues, open and closed, and I’m convinced that mine is new.
- The title contains the plugin to which this issue belongs
Describe the bug No longer able to do a match ip address prefix-list myprefixlist under route-map. Receive this error in the log, and the running config does not show the match line:
[VAKV3-NMY7B][EC 100663337] error processing configuration change: error [internal inconsistency] event [apply] operation [modify] xpath [/frr-route-map:lib/route-map[name='Redistribution']/entry[sequence='10']/match-condition[condition='ipv4-prefix-list']/rmap-match-condition/list-name]
To Reproduce
Just create a ip prefix-list and try adding a match statement to a route-map
Expected behavior Running Config:
ip prefix-list myprefixlist seq 10 permit 100.64.0.0/10 le 32
route-map Redistribution permit 10
match ip address prefix-list myprefixlist
Screenshots Actual Running Config because of bug:
ip prefix-list myprefixlist seq 10 permit 100.64.0.0/10 le 32
route-map Redistribution permit 10
Missing match statement…
Relevant log files
[VAKV3-NMY7B][EC 100663337] error processing configuration change: error [internal inconsistency] event [apply] operation [modify] xpath [/frr-route-map:lib/route-map[name='Redistribution']/entry[sequence='10']/match-condition[condition='ipv4-prefix-list']/rmap-match-condition/list-name]
Additional context FRR issue also created: https://github.com/FRRouting/frr/issues/14626 Community post with others having issue: https://forum.opnsense.org/index.php?topic=36507.0
Environment OPNsense 23.7.6 OS Version: FreeBSD: 13.2-RELEASE-p3 FRR Version: 8.5.3
About this issue
- Original URL
- State: closed
- Created 8 months ago
- Comments: 18 (8 by maintainers)
Thanks, marking this upstream for now and subscribed to other issue. May have to move this to ports repo where the fix would live under the current assumption.
Cheers, Franco