pfSense » pfSense Packages

I can confirm this behavior, the Frr keeps the neighbor config until the restart of the service

tested on

23.09-DEVELOPMENT (amd64)
built on Thu Sep 07 06:05:43 UTC 2023
FreeBSD 14.0-ALPHA2

Looks like that's an upstream bug in the frr9 or frr9-pythontools port(s).

The script at /usr/local/sbin/frr-reload is looking for /usr/local/lib/frr/frr-reload.py

: more /usr/local/sbin/frr-reload
#!/bin/sh

if test -e /usr/local/lib/frr/frr-reload.py; then
   exec /usr/local/lib/frr/frr-reload.py --reload /var/etc/frr/frr.conf
fi
>&2 echo "Please install frr9-pythontools package. Required for reload" 
exit 1

However the frr9-pythontools pkg is placing the script in /usr/local/sbin/frr-reload.py:

: pkg info -l frr9-pythontools-9.0.1
frr9-pythontools-9.0.1:
        /usr/local/sbin/frr-reload.py
        /usr/local/sbin/generate_support_bundle.py
        /usr/local/share/licenses/frr9-pythontools-9.0.1/GPLv2
        /usr/local/share/licenses/frr9-pythontools-9.0.1/LICENSE
        /usr/local/share/licenses/frr9-pythontools-9.0.1/catalog.mk
        /var/etc/frr/support_bundle_commands.conf

And since the two don't match (/usr/local/sbin/frr-reload.py != /usr/local/lib/frr/frr-reload.py), it doesn't work.

So then the question is... Which one is wrong? Is the script looking in the wrong place, or is the frr9-pythontools port putting it in the wrong place?

The symlink is OK as a temporary workaround but that isn't something we would commit to the package. It needs to be addressed upstream in either the frr9 or frr9-pythontools port, and then we can bring the fix in from there.

We are looking into it here. Christian said he sees the issue in port and is looking into a fix.

The upstream fix was merged/picked and should be in package repositories for 23.09 and 2.7.1