FRR (FRRouting) package now available for 2.3.4 users

jimp

The FRR package which handles multiple routing protocols is now available for pfSense 2.3.4 users. It is already available for 2.4 and 2.3.5 snapshots and has been working OK there.

Currently the FRR package GUI supports BGP, OSPF, and OSPF6 configured using the GUI or via manual configuration. This package takes the place of both Quagga and OpenBGPD allowing for BGP and OSPF to be used simultaneously.

Note that the package is lacking a majority of its input validation but that is coming shortly.

luckman212

Looks like I'm going to be needing OSPF in a few weeks for a customer install where they have a 2.3.4_p1 SG-4860 running currently. How's the FRR package doing? Has anyone been using it, any major gotchas etc?

jimp

No major gotchas, it runs well. I'd pick it over Quagga for new OSPF deployments right now.

luckman212

Great, will definitely give it a spin & let everyone know how it flies. Thanks

Eric Smid

I succesfully installed FRR.
As far as I can tell now, this solves the "PF_KEY socket: No buffer space available" problem I had with OpenBGPd and IP-SEC.

However I ran into a few things with BGP. I don't know if this is the right place to mention them.
If not, please let me know.

If I define a prefix-list, it doesn't appear in the bgpd.conf, so bgpd can't use it.
If I define a route-map to set a metric, the config line in bgpd.conf, always has the statement "match".

jimp

@Eric:

I succesfully installed FRR.
As far as I can tell now, this solves the "PF_KEY socket: No buffer space available" problem I had with OpenBGPd and IP-SEC.

However I ran into a few things with BGP. I don't know if this is the right place to mention them.
If not, please let me know.

If I define a prefix-list, it doesn't appear in the bgpd.conf, so bgpd can't use it.

If I define a route-map to set a metric, the config line in bgpd.conf, always has the statement "match".

For the first one, we just merged a PR that should help.

For the second, I think I see what the problem is and I'll get a fix in shortly.

jimp

Be on the lookout for FRR 0.0.3 which has a fix for both the prefix-list entries and metric actions in route maps.