No. There is no way that dynamic routes can be picked up by automatic outbound NAT.

If they are all privately numbered, you could make an RFC1918 alias (192.168.0.0/16, 172.16.0.0/12, 10.0.0.0/8) and then setup hybrid or manual outbound NAT rules to match that alias as a source.

I pushed a fix for this and a couple other syntax issues I found along the way. Hopefully it behaves properly now, give it a try.

I think you need to be in the Routing and Multi-WAN forum, not the Packages - Traffic Monitoring forum. I know OSPF is a routing protocol… not sure what FRR is, but everything else in your post seems to be about routing, not monitoring traffic on your network.

If your question is about one of the routing protocol packages, then maybe the general Packages forum might also be appropriate.

@jimp:

There is a patch around that will stop routing packages from being restarted which can help in some cases.

Is this patch still compatible with Version 2.4.x.
Seems like some paths/files have been changed.

@mclaborn:

What is the process for installing FRR? Can I just install the package or is there more to it?

(We're fighting bug https://redmine.pfsense.org/issues/6223 with IPSec)

Just install the package and go. If you need md5 authentication, the latest version fixes it.

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.