Hello,
after upgrade to 25.7, my Frr OSPF3 (v6) instance stops working.
I've noticed during boot and if I type "service frr restart" daemon tells me configuration syntax is wrong after specifing area on interface.
I tested renaming frr.conf in frr.conf.old and regenerate configuration but issue still persist.
Ospf v4 still working fine as usual.
Does somebody noticed same behavior?
There was an frr8 to frr10 upgrade.
Best would be an issue here and how to replicate it.
https://github.com/opnsense/plugins/issues
If its clear whats going on Ill pick it up and fix it soon.
Hi,
The problem is that the script is not adding the area to the interface.
The correct configuration should be:
interface bxe0
...
ipv6 ospf6 area 0.0.0.0
...
exit
https://github.com/opnsense/plugins/commit/3a1d0c4180a 3 weeks ago
It seems for OSPFv2 (IPv4) the built syntax is correct, and operational
root@OPNsense:~ # vtysh
Hello, this is FRRouting (version 10.4).
Copyright 1996-2005 Kunihiro Ishiguro, et al.
OPNsense.localdomain# show ip ospf neighbor
Neighbor ID Pri State Up Time Dead Time Address Interface RXmtL RqstL DBsmL
10.0.0.11 0 Full/DROther 1w1d18h 19.817s 10.0.0.11 vmx0:10.0.0.138 0 0 0
10.0.0.45 0 Full/DROther 1w1d18h 19.818s 10.0.0.45 vmx0:10.0.0.138 0 0 0
10.0.0.105 200 Full/Backup 1w1d18h 19.818s 10.0.0.105 vmx0:10.0.0.138 0 0 0
OPNsense.localdomain# show running-config
Building configuration...
Current configuration:
!
frr version 10.4
frr defaults traditional
hostname OPNsense.localdomain
log syslog notifications
!
interface vmx0
ip ospf area 0.0.0.10
ip ospf authentication message-digest
ip ospf dead-interval 20
ip ospf hello-interval 5
ip ospf message-digest-key 1 md5 nicetry....!
ip ospf priority 254
ip ospf retransmit-interval 4
exit