Since there's not official fix, I created this manual patch: --- a/usr/local/pkg/frr/inc/frr_ospf.inc +++ b/usr/local/pkg/frr/inc/frr_ospf.inc @@ -211,10 +211,6 @@ if (!empty($conf['passive'])) { $passive_interfaces[] = $realif; } - list($interface_ip, $interface_subnet, $subnet) = frr_get_interfaceinfo($conf['interface']); - if (empty($interface_ip)) { - continue; - } $area = (strlen($conf['interfacearea']) > 0) ? $conf['interfacearea'] : $frr_ospfd_conf['defaultarea']; $frr_integrated_config['interfaces'][$realif] .= " ip ospf area {$area}\n"; }

now need update to frr10.7

@netblues thanks for working this out. I filed this issue in redmine and opened a pull request for the code. Applied it to 7 firewalls with 26.03.1, works flawlessly now. Adjacency after reconnection of a spoke or the hub takes a few seconds now https://redmine.pfsense.org/issues/16978

@jimp I'm definitely eager to test that package update, but after the latest system update to 25.11.1 from 25.11, (which I did in the hope it would the OPFv3 issue) my long-working IPsec VTI setup quit passing usable traffic. This obviously not the right topic for that subject. I will post it where it belongs once I get time to collect more useful diagnostic information than I have now. ETA: VTI IPsec VPN seems to be working normally again! IPv4 OSPF is working, and I can now rebuild my IPv6 routes on OPFv3. I am pretty stoked! Thanks to everyone involved in getting that package update published.

[image: 1770496773678-8946c0b5-7b3e-40c5-8211-64fc13857050-image.png] https://redmine.pfsense.org/issues/12760 https://redmine.pfsense.org/issues/14652 This might be the issue but can someone please confirm?

Yes, a forced restart of the FRR service can restore functionality; sometimes, two forced restarts are required to get it working again. They are remote BGP connections made via VPN tunnels. BGP neighbor is 2602:fed:7020:a::2, remote AS 39703, local AS 65105, external link Local Role: undefined Remote Role: undefined Description: FMT VP Hostname: changeme BGP version 4, remote router ID 0.0.0.0, local router ID 10.50.1.254 BGP state = Idle Last read 01:46:26, Last write 01:46:23 Hold time is 180 seconds, keepalive interval is 25 seconds Configured hold time is 180 seconds, keepalive interval is 25 seconds Configured tcp-mss is 0, synced tcp-mss is 0 Configured conditional advertisements interval is 60 seconds Graceful restart information: Local GR Mode: Disable* Remote GR Mode: NotApplicable R bit: False N bit: False Timers: Configured Restart Time(sec): 120 Received Restart Time(sec): 120 Configured LLGR Stale Path Time(sec): 0 Message statistics: Inq depth is 0 Outq depth is 0 Sent Rcvd Opens: 3 3 Notifications: 59 0 Updates: 3 567673 Keepalives: 1919 799 Route Refresh: 0 0 Capability: 0 0 Total: 1984 568475 Prefix statistics: Inbound filtered: 0 AS-PATH loop: 0 Originator loop: 0 Cluster loop: 0 Invalid next-hop: 0 Withdrawn: 0 Attributes discarded: 0 Minimum time between advertisement runs is 10 seconds Update delay timer is 20 seconds (remaining: 0) Update source is 2602:fed:7020:a::3 For address family: IPv6 Unicast Not part of any update group Inbound soft reconfiguration allowed NEXT_HOP is always this router Community attribute sent to this neighbor(all) Outbound path policy configured Outgoing update prefix filter list is *myv6out 0 accepted prefixes Connections established 1; dropped 1 Last reset 01:45:58, Notification sent (Neighbor Events Error/Unspecific) Message received that caused BGP to send a NOTIFICATION: FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF 00690104 9B4900B4 1781205A 4C020601 04000200 01020202 00020246 00020641 0400009B 49020206 00020645 04000201 0302074C 05000201 0000020C 490A0863 68616E67 656D6500 02044002 40780209 47070002 01800000 00 External BGP neighbor may be up to 1 hops away. Local host: 2602:fed:7020:a::3, Local port: 19658 Foreign host: 2602:fed:7020:a::2, Foreign port: 179 Nexthop: 0.0.0.0 Nexthop global: 2602:fed:7020:a::3 Nexthop local: :: BGP connection: shared network BGP Connect Retry Timer in Seconds: 300 Next start timer due in 64 seconds Peer Authentication Enabled Read thread: off Write thread: off FD used: -1

This one has been tricky still not sure what to try. Any ideas?

@div444 i'm finding the same - did you find a solution or did reverting fix it? Hoping there is a patch fix or something to get it working! Rather not rollback if i can avoid it

@michmoor said in BGP convergence with BFD working smoothly with the settings below.: Redmine has been updated to reflect the testing done by @mcury so there is official guidance regarding treating this set up with dynamic routing. Glad to see that.. They even tested with HA.. Thanks @marcosm for testing.

Did you resolve this I seem to be running into this issue as well.

@pwabrat Sorry for the delayed reply, the issue resolved by Route Redistribution in pfSense Kernel Routes of "Extended_LAN" [image: 1740053295339-cbabfeed-7467-45d0-b3dc-5d8a06e8bdd8-image.png] Thank you for the support.