pfSense » pfSense Packages

Marcos M wrote:

The current frr package version is 7.5.1_3 - frr 7.5.1 was released on 2021-03-07 https://github.com/FRRouting/frr/releases/tag/frr-7.5.1

The ports tree now includes frr8 with many fixes and enhancements. Upgrading likely requires updates to the pfSense GUI as well. Alternatively, packages for both frr7 and frr8 could be made available.

This version of FRR is very obsolete because it does not have the option to redistribute the default route to ipv6

Tested in 23.09 by running:

pkg delete -f frr7 frr7-pythontools
pkg install -f frr8 frr8-pythontools

The config tested OSPF, BGP peers with multiple neighbors, AS Paths, Access Lists, Prefix Lists, Route Maps, and BFD. After re-saving all GUI pages, the generated raw config was the same. I looked over the release notes since FRR 7.5.1 to 8.5.2 and didn't notice anything that would prevent an in-place upgrade from working as-is. One thing did stand out:

Ignore end when parsing frr.conf. If frr.conf has end inside the config, BGP peering starts only after 10 minutes. This is because parsing the end keyword stopped hooks from reaching the end of the configuration and BGP thoughts the configuration is not ready.

I tested again after applying the following patch to remove end from the config file, and did not find any issues:

diff --git a/net/pfSense-pkg-frr/files/usr/local/pkg/frr.inc b/net/pfSense-pkg-frr/files/usr/local/pkg/frr.inc
index e802a02a75b5..f8c7cd6cb2a5 100644
--- a/net/pfSense-pkg-frr/files/usr/local/pkg/frr.inc
+++ b/net/pfSense-pkg-frr/files/usr/local/pkg/frr.inc
@@ -830,7 +830,6 @@ function frr_generate_config_integrated() {

         $integratedconffile .= "line vty\n";
         $integratedconffile .= "!\n";
-        $integratedconffile .= "end\n";

         /* Remove sample configuration files */
         array_map('unlink', glob("{$frr_config_base}/*.sample*"));

FRR 9.0.1 is added and working

23.09-BETA (amd64)
built on Thu Oct 12 23:00:00 PDT 2023
FreeBSD 14.0-CURRENT