-
Bug
-
Resolution: Unresolved
-
Undefined
-
rhel-10.0
-
None
-
frr-10.1-5.el10
-
No
-
Low
-
rhel-sst-cs-net-perf-services
-
ssg_core_services
-
15
-
1
-
False
-
-
None
-
None
-
Pass
-
Automated
-
None
Kind of a hot topic in FRR-10.x was a change that the Upstream did that interpreted the NOPREFIXROUTE flag with interface addresses. This effectively made a problem when running dynamic routing with FRR and using NetworkManager at the same time. When using NetworkManager to add IP addresses on an interface, it will automatically add the noprefixroute flag with the address. This means that a route will be created by the kernel in the link scope but FRR will interpret this differently and will only create local (L) route with /32 prefix. It should also create the connected (C) prefix as well.
I intentionally excluded this behavior from the rebased version of FRR in RHEL-10.0-beta and now that the fix is complete in the Upstream, I would like to replace the 0006-noprefixroute-network-manager.patch with the current implementation that has been merged here:
https://github.com/FRRouting/frr/pull/16300
Reproducer is currently not really working because like I described above, I intentionally left out this change that broke usage with NetworkManager. This would just be a matter of replacing the current patch with the one that has been released after the 10.1 version.
- relates to
-
RHEL-64427 out of sync between FRR and NetworkManager
- New
- links to
-
RHBA-2024:138646 frr bug fix and enhancement update