IPSEC OSPF opnsense 26.7
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 1.2k
- Forks
- 863
- Avg merge
- 2d 6h
- Merged PRs (30d)
- 10
Description
Important notices
Before you add a new report, we ask you kindly to acknowledge the following:
- I have read the contributing guidelines at https://github.com/opnsense/core/blob/master/CONTRIBUTING.md
- I am convinced that my issue is new after having checked both open and closed issues at https://github.com/opnsense/core/issues?q=is%3Aissue
- AI tools were used to create at least part of the text submitted herewith.
Describe the bug
Hi!
I upgraded to 26.7 and now OSPF in IPSEC dosent work for me.
I have an IPSEC VTI tunnel to a cisco router, the cisco router initiates the connection and the tunnel itself works. Since the update, OSPF just stops working some minutes and then comes back to life.
I see this in the OSPF logs - *** sendmsg in ospf_write failed to 224.0.0.5, id 0, off 0, len 120, interface ipsec10, mtu 1400: Network is unreachable
The network type is Point-to-multipoint and eveything worked before the upgrade.
To Reproduce
Run OSPF over IPSEC VTI in OPNsense version >= 26.7.
Expected behavior
OSPF should form and exchange routes.
Describe alternatives you considered
A clear and concise description of any alternative solutions or workaround you considered.
N/A
Relevant log files
If applicable, information from log files supporting your claim.
Log from FRR
2026-07-16T17:35:38
Error
ospfd
*** sendmsg in ospf_write failed to 224.0.0.5, id 0, off 0, len 120, interface ipsec10, mtu 1400: Network is unreachable
2026-07-16T17:35:38
Notice
ospfd
AdjChg: Nbr 172.28.0.29, NbrIP 172.28.0.21 (default) on ipsec10:172.28.0.20: Exchange -> Full (ExchangeDone)
2026-07-16T17:35:38
Notice
ospfd
AdjChg: Nbr 172.28.0.29, NbrIP 172.28.0.21 (default) on ipsec10:172.28.0.20: Full -> Deleted (InactivityTimer)
2026-07-16T17:34:58
Error
ospfd
*** sendmsg in ospf_write failed to 224.0.0.5, id 0, off 0, len 120, interface ipsec10, mtu 1400: Network is unreachable
2026-07-16T17:34:58
Notice
ospfd
AdjChg: Nbr 172.28.0.29, NbrIP 172.28.0.21 (default) on ipsec10:172.28.0.20: Exchange -> Full (ExchangeDone)
2026-07-16T17:34:58
Notice
ospfd
AdjChg: Nbr 172.28.0.29, NbrIP 172.28.0.21 (default) on ipsec10:172.28.0.20: Full -> Deleted (InactivityTimer)
2026-07-16T17:34:18
Notice
ospfd
AdjChg: Nbr 172.28.0.29, NbrIP 172.28.0.21 (default) on ipsec10:172.28.0.20: Exchange -> Full (ExchangeDone)
2026-07-16T17:34:18
Notice
ospfd
AdjChg: Nbr 172.28.0.29, NbrIP 172.28.0.21 (default) on ipsec10:172.28.0.20: Full -> Deleted (InactivityTimer)
2026-07-16T17:33:38
Error
ospfd
*** sendmsg in ospf_write failed to 224.0.0.5, id 0, off 0, len 120, interface ipsec10, mtu 1400: Network is unreachable
2026-07-16T17:33:38
Notice
ospfd
AdjChg: Nbr 172.28.0.29, NbrIP 172.28.0.21 (default) on ipsec10:172.28.0.20: Exchange -> Full (ExchangeDone)
2026-07-16T17:33:38
Notice
ospfd
AdjChg: Nbr 172.28.0.29, NbrIP 172.28.0.21 (default) on ipsec10:172.28.0.20: Full -> Deleted (InactivityTimer)
2026-07-16T17:32:58
Notice
ospfd
AdjChg: Nbr 172.28.0.29, NbrIP 172.28.0.21 (default) on ipsec10:172.28.0.20: Exchange -> Full (ExchangeDone)
2026-07-16T17:32:58
Notice
ospfd
AdjChg: Nbr 172.28.0.29, NbrIP 172.28.0.21 (default) on ipsec10:172.28.0.20: Full -> Deleted (InactivityTimer)
2026-07-16T17:32:28
Error
ospfd
*** sendmsg in ospf_write failed to 224.0.0.5, id 0, off 0, len 120, interface ipsec10, mtu 1400: Network is unreachable
2026-07-16T17:32:28
Notice
ospfd
AdjChg: Nbr 172.28.0.29, NbrIP 172.28.0.21 (default) on ipsec10:172.28.0.20: Loading -> Full (LoadingDone)
Additional context
Add any other context about the problem here.
Environment
Software version used and hardware type if relevant, e.g.:
OPNsense 26.7
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing OSPF over an IPSEC VTI on OPNsense 26.7 or later, using the FRR ospfd log and the ipsec10 interface details provided. Investigate the repeated “Network is unreachable” errors and adjacency transitions; done means OSPF remains established and exchanges routes without recurring inactivity timeouts.
Written by the indexing model from the issue text.
Assessment
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100