Great job Franco!
Looking good so far! :)
Since upgrade to 20.1.4 we are having issues with strongswan U5.8.3/K11.2-RELEASE-p18-HBSD. Here is the output of the log file:
Apr 16 18:13:24 opnsense charon: 10[DMN] <con2-000|6> thread 10 received 11
Apr 16 18:13:24 opnsense charon: 10[LIB] <con2-000|6> dumping 2 stack frame addresses:
Apr 16 18:13:24 opnsense charon: 10[LIB] <con2-000|6> /lib/libthr.so.3 @ 0x00000462e6228000 (pthread_sigmask+0x536) [0x00000462e6236976]
Apr 16 18:13:25 opnsense charon: 10[LIB] <con2-000|6> -> ??:0
Apr 16 18:13:25 opnsense charon: 10[LIB] <con2-000|6> /lib/libthr.so.3 @ 0x00000462e6228000 (pthread_getspecific+0xe12) [0x00000462e6235ee2]
Apr 16 18:13:25 opnsense charon: 10[LIB] <con2-000|6> -> ??:0
Apr 16 18:13:25 opnsense charon: 10[DMN] <con2-000|6> killing ourself, received critical signal
The GUI and strongswan process becomes unresponsive after this error. we can't even restart or stop it. The only way out to get atleast the GUI working:
1. Desactivate all ipsec tunnels (it will keep on loading until you perform step 2)
2. Via ssh kill all ipsec processes
This action only helps to get the GUI. For strongswan to work again a system reboot is needed.
Last version on which it was working:
opnsense: 20.1
strongswan: U5.8.2/K11.2-RELEASE-p16-HBSD
Please don't hijack general topics for specific reports...
Have you done a health audit yet? Have you tried to reinstall the "base" and "strongswan" package?
5.8.3 was working for me (LibreSSL), currently testing 5.8.4 and that looks ok too.
Cheers,
Franco