New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can no longer match a prefix-list in a route-map #14626
Comments
Having the same problem as well. I hope this gets put as priority and fixed ASAP. |
Check your version of libyang (dependency of FRR). There's a known issue with libyang 2.1.111. It should work fine if you downgrade it to 2.1.80. |
It would help to know the version of libyang that fixes this or an upstream ticket. Thanks, |
libyang 2.1.128 should fix this, but to my knowledge it was not yet verified by FRR. |
appreciate it, it's pretty easy to test with our users and report back |
I too was bitten by this bug during an upgrade. This combination resolves the prefix list in route maps parse issue. |
Yep it was solved as discussed. I’ve made a patch for FreeBSD ports in their bugzilla for net/libyang2 but it has not been merged so far. |
Describe the bug
No longer able to do a
match ip address prefix-list myprefixlist
underroute-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
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
Result in show run:
ip prefix-list myprefixlist seq 10 permit 100.64.0.0/10 le 32
route-map Redistribution permit 10
Missing match statement...
Versions
FreeBSD: 13.2-RELEASE-p3
8.5.3
Additional context
This is very basic and easily reproducible.
Several people using OPNsense w/ FRR 8.5.3 are seeing same issue: https://github.com/FRRouting/frr/issues/14626
The text was updated successfully, but these errors were encountered: