Important notices
Before you add a new report, we ask you kindly to acknowledge the following:
Is your feature request related to a problem? Please describe.
In my network, I need to redistribute routes from other protocols (e.g., OSPF or static) into BGP using FRR within OPNsense. However, the current FRR plugin lacks a "redistribution map" option, which prevents me from applying fine-grained control over which routes are redistributed. Without this, all routes from a protocol are redistributed indiscriminately, leading to unwanted routes in BGP or requiring manual CLI tweaks that don’t persist through the GUI.
Describe the solution you'd like
I’d like the FRR plugin to add a "Redistribution Map" field in the BGP configuration section of the OPNsense GUI (under Routing > BGP). This field would allow users to specify a route-map (e.g., route-map MY_MAP) to filter or modify routes during redistribution. In FRR terms, this would map to the configuration command:
redistribute route-map MY_MAP
Where could be ospf, static, connected, etc. The route-map itself could be defined in the existing "Route Maps" tab of the FRR plugin, ensuring consistency with current functionality.
This might be accomplished in the same way it does in the Routing -> OSPF allowing a user to define route redistribution map for OSPF (although it might be better to uses separate route maps for each type of redistribution as it is done in pfSense plugin).
Describe alternatives you've considered
Manual CLI Configuration: I can edit /usr/local/etc/frr/frr.conf manually to add redistribute ospf route-map MY_MAP, but this gets overwritten by the GUI on config sync or reboot.
Prefix Lists: While prefix lists in the BGP neighbor settings can filter outbound updates, they don’t apply to the redistribution process itself and are less flexible than route-maps.
External Workaround: Running FRR outside OPNsense is an option, but it defeats the purpose of using the integrated plugin.
Additional context
Files attached:
Examples of route map fields in ospf and the corresponding solution for pfSense
Important notices
Before you add a new report, we ask you kindly to acknowledge the following:
Is your feature request related to a problem? Please describe.
In my network, I need to redistribute routes from other protocols (e.g., OSPF or static) into BGP using FRR within OPNsense. However, the current FRR plugin lacks a "redistribution map" option, which prevents me from applying fine-grained control over which routes are redistributed. Without this, all routes from a protocol are redistributed indiscriminately, leading to unwanted routes in BGP or requiring manual CLI tweaks that don’t persist through the GUI.
Describe the solution you'd like
I’d like the FRR plugin to add a "Redistribution Map" field in the BGP configuration section of the OPNsense GUI (under Routing > BGP). This field would allow users to specify a route-map (e.g., route-map MY_MAP) to filter or modify routes during redistribution. In FRR terms, this would map to the configuration command:
redistribute route-map MY_MAP
Where could be ospf, static, connected, etc. The route-map itself could be defined in the existing "Route Maps" tab of the FRR plugin, ensuring consistency with current functionality.
This might be accomplished in the same way it does in the Routing -> OSPF allowing a user to define route redistribution map for OSPF (although it might be better to uses separate route maps for each type of redistribution as it is done in pfSense plugin).
Describe alternatives you've considered
Manual CLI Configuration: I can edit /usr/local/etc/frr/frr.conf manually to add redistribute ospf route-map MY_MAP, but this gets overwritten by the GUI on config sync or reboot.
Prefix Lists: While prefix lists in the BGP neighbor settings can filter outbound updates, they don’t apply to the redistribution process itself and are less flexible than route-maps.
External Workaround: Running FRR outside OPNsense is an option, but it defeats the purpose of using the integrated plugin.
Additional context
Files attached:
Examples of route map fields in ospf and the corresponding solution for pfSense