[SOLVED] Static route not applied after update to 22.1.5

Started by clarknova, April 12, 2022, 09:43:55 PM

Previous topic - Next topic
OPNsense 22.1.5-amd64

This firewall was running 22.1.2_1 until today and statics routes were applied as expected. After upgrading to 22.1.5, one of my many static routes is not active and I haven't been able to determine why not.

In the attached 'configured.png' you can see that 10.31/16 should be routed via 10.16.3.2. But in 'status.png' you see that this network is routed via 172.16.43.9 as a result of a demoted OSPF peer.

I restarted FRR and reapplied the static route configuration, but the problem persists. I checked in System > Routes > Log File but there is nothing in there to indicate a problem. Any idea why this route does not apply while other static routes do?

I rebooted the firewall and I was able to reach it for a short time via this static route, but within a minute or two the static route was removed, or perhaps overwritten by the OSPF route.

Generally I think in most devices that do routing, static should be preferred over ospf.  Did you give ospf a higher "administrative distance" somehow?  Can you share more of your frr config?  Any idea what the old version of frr was before you upgraded?  I assume it got upgraded with the system upgrade.


This is the backup router in a pair, "routerb". The primary "routera" is still running OPNsense 22.1.2_1. Both report FRR version 7.5.1. I've attached both FRR running configs as reported in Routing > Diagnostics > General > Running Configuration.

You'll notice that both config are identical except:

  • hostname
  • cost is manually set to 100 on Wireguard interfaces on routera
  • cost is set to 65535 on all interfaces on routerb due to "CARP Demote" setting (which is set but not visible in the attachements).

After another reboot today this is working as expected. I was able to then update to 22.1.6 and all is well.   :shrug: