OPNsense Forum

English Forums => 26.7, 26.10 Series => Topic started by: Monviech (Cedrik) on October 06, 2026, 05:06:18 PM

Title: frr plugin 2.0 was released in 26.7.7
Post by: Monviech (Cedrik) on October 06, 2026, 05:06:18 PM
I cleaned a lot of stuff up in the frr plugin. The change is planned for 26.7.7

I tested it all in my own test environment, but if somebody who also uses BGP/OSPF/OSPFv3 peering and has some basic development knowledge (aka how to build an opnsense plugin from master, deploy it, and report issues) it would be nice to get some feedback before pushing this out.

Please, test it if you can, its a lot of changes but less so feature wise, mostly corrections.

https://github.com/opnsense/plugins/blob/master/net/frr/pkg-descr

Check out the 2.0 changelog and the migration notes (there are a few migrations happening automatically).

Thank you for any help (and if not brace for impact on community at some point regardless :D)

TESTING STEPS (since I was PMed, I also post them here):

You can stay on the current community edition.

Just do the following in an ssh shell with root rights:

# opnsense-code plugins
# cd /usr/plugins/net/frr
# git checkout master
# make upgrade

Now your plugin will be upgraded to 2.0 and migrations will run. If any errors with the migrations happen please tell me. You most likely don't need a reboot, but for testing could be a good idea.

Rolling back to the normal version, better do a VM snapshot, or use the OPNsense ZFS snapshot.
Otherwise, you can use configuration history to roll back the config.xml and also just remove the os-frr-devel-2.0 plugin in the GUI in firmware plugins and then reinstall the previous version from there as well.

Thank you.

EDIT:

Its released now.

Title: Re: frr plugin 2.0 was released in 26.7.7
Post by: br_opnsense on October 16, 2026, 09:28:36 AM
Hi,

I am having issues after the latest update.

I have several dozen OSPF clients. Before the update, they were configured only using the "Interfaces" tab, where the Area was also entered. Under "General", I also set some interfaces to "Passive".

After the update, OSPF no longer works:

- The passive interfaces are not transferred (this is not critical).

- In the "Interfaces" menu, the old Area still shows up in the Areas column. However, when I click "Edit", the Area disappears and shows only an empty drop-down menu.

If I manually create the Area with the type "normal" and assign it to the interfaces, everything works normally again.
I tried to create the Area before the update, but stub and nssa do not work in my environment and "normal" isn't available.

Is it possible to fix this issue in the update process?
Title: Re: frr plugin 2.0 was released in 26.7.7
Post by: Monviech (Cedrik) on October 16, 2026, 09:42:28 AM
I need the migration log to know what went wrong.

I recently fixed this reported issue:
https://github.com/opnsense/plugins/issues/5787

This will be hotfixed today most likely.

If you have a different issue I have to know, though if you already manually reworked your config now to make it working, well, you have to roll back in the configuration history to the point before the changes and run the migration script again.

/usr/local/opnsense/mvc/script/run_migrations.php
Title: Re: frr plugin 2.0 was released in 26.7.7
Post by: br_opnsense on October 19, 2026, 08:48:51 AM
I tried today another appliance. Still failes. Migration output:

[OPNsense\Quagga\OSPF:interfaces.interface.12acf5f9-e33e-4482-8092-fa1035437f35.interfacename] Option [] not in list.{openvpn}
[OPNsense\Quagga\OSPF:interfaces.interface.e840ea08-c93f-4993-858b-0415c64a79a1.interfacename] Option [] not in list.{wireguard}
Model OPNsense\Quagga\OSPF can't be saved, skip ( OPNsense\Base\ValidationException: [OPNsense\Quagga\OSPF:interfaces.interface.12acf5f9-e33e-4482-8092-fa1035437f35.interfacename] Option [] not in list.{openvpn}
[OPNsense\Quagga\OSPF:interfaces.interface.e840ea08-c93f-4993-858b-0415c64a79a1.interfacename] Option [] not in list.{wireguard}
 in /usr/local/opnsense/mvc/app/models/OPNsense/Base/BaseModel.php:821
Stack trace:
#0 /usr/local/opnsense/mvc/app/models/OPNsense/Base/BaseModel.php(946): OPNsense\Base\BaseModel->serializeToConfig()
#1 /usr/local/opnsense/mvc/script/run_migrations.php(69): OPNsense\Base\BaseModel->runMigrations()
#2 {main} )
Failed OPNsense\Quagga\OSPF from 1.1.0 to 1.1.5
Title: Re: frr plugin 2.0 was released in 26.7.7
Post by: Monviech (Cedrik) on October 19, 2026, 09:55:16 AM
It's still the group interface validation issue.

I thought I fixed that and we updated the plugin version.

I will test this myself to see if I missed anything.

For now, remove the "wireguard" and "openvpn" group interfaces from the Passive Interfaces and the OSPF interfaces and rerun the migration.

Rerun the migration from the command line like this:
# pluginctl -m
Title: Re: frr plugin 2.0 was released in 26.7.7
Post by: Monviech (Cedrik) on October 19, 2026, 11:23:36 AM
Since I expect more people to run into this lets make it a bit more forgiving:

https://github.com/opnsense/plugins/commit/150ff2ab0fb256d0d242e4fc96a60af7f04e9398
Title: Re: frr plugin 2.0 was released in 26.7.7
Post by: hharry on October 19, 2026, 01:56:28 PM
nice work Monviech, i recently upgraded a fairly simple BGP ( using prefix list with route maps ) enabled opnsense instance to 27.7.7, and it all went smoothly.

I have another opnsense 26.7.5, OSPF enabled instance, i haven't upgraded yet...
frr sure is a great project, i use it extensively professionally...
Title: Re: frr plugin 2.0 was released in 26.7.7
Post by: Flocki on October 20, 2026, 02:54:46 PM
Hi,

I have a small issue (not sure if this is new with the update, since I have not used the previous version):

For both OSPF and OSPFv3 under the "Interface"/"depend on CARP" section not all my CARP addresses show up. I have setup 13 CARP addresses, but only 9 show up in the drop-down.

Florian
Title: Re: frr plugin 2.0 was released in 26.7.7
Post by: Monviech (Cedrik) on October 20, 2026, 02:58:39 PM
Hello Florian,

this setting has not been touched, so it might be something new or specific to your configuration.

Did you try the search already in the dropdown selectpicker? Did you apply the VIP configuration and reboot the OPNsense completely one time? Maybe its some cache thing.

If this should be investigated please open an issue with some more info here:

https://github.com/opnsense/plugins/issues

Thank you.
Title: Re: frr plugin 2.0 was released in 26.7.7
Post by: Flocki on October 20, 2026, 03:33:28 PM
Hi,

I think I figures out, what the "specific" thing is. several of my CARP addresses look identical, as they are link-local IPv6 addresses "fe80::1", however they are on different Interfaces(VLANs). Thus the drop-down seems to assume they are the same and only shows one entry.

Should I open an issue with those added details?
Title: Re: frr plugin 2.0 was released in 26.7.7
Post by: Monviech (Cedrik) on October 20, 2026, 05:20:08 PM
Sounds like a core issue to me, better go there:

https://github.com/opnsense/core

I would imagine you have the same issue e.g in the wireguard instance selectpicker where its also using the same depend on carp logic.
Title: Re: frr plugin 2.0 was released in 26.7.7
Post by: br_opnsense on October 21, 2026, 09:31:26 PM
Quote from: Monviech (Cedrik) on October 19, 2026, 11:23:36 AMSince I expect more people to run into this lets make it a bit more forgiving:

https://github.com/opnsense/plugins/commit/150ff2ab0fb256d0d242e4fc96a60af7f04e9398

Just for the notes: it still does not work, until i remove the group interfaces from the passive interfaces before the update.
I am updating from 26.1 to 26.7. At least i can prepare the settings now on every appliance und then run the update via cli.
Thanks.
Title: Re: frr plugin 2.0 was released in 26.7.7
Post by: hharry on October 22, 2026, 02:45:39 PM
i found one issue with the new plug in

I have OSPF enabled on LAN interface only, and after the upgrade, there are new automatic generated inbound permit rules on my WAN interface for OSPF, when OSPF is not enabled on WAN interface.

To workaround this issue, i disabled Routing:General:Firewall Rules, which removed the unwanted WAN automatic generated OSPF rules, on a OSPF disabled interface.

The behavior is different and better for BGP, after the upgrade, there are new automatic generated inbound permit BGP rules, applied  ONLY on BGP enabled interfaces.
Title: Re: frr plugin 2.0 was released in 26.7.7
Post by: Monviech (Cedrik) on October 22, 2026, 03:56:37 PM
Yeah the new firewall rules are intentionally broad when activated, one size fits all. If you don't like that, it's indeed better to create manual rules.

But I don't understand why BGP would be added only to certain interfaces, the code here adds it as floating rule as well...?

https://github.com/opnsense/plugins/blob/e4578ae667349c7300cd61a01677399ab6e389cc/net/frr/src/etc/inc/plugins.inc.d/frr.inc#L273

No interface in any of these rules.