I've read other threads in earlier versions of OPNSense that have seemed to broadly fall into;
- make sure strongswan is running (it is)
- bug with syslog-ng crashing, make sure it's running (it is)
- bug with saving tunnel settings causing log settings to actually silently be overwritten to "basic", re-save advanced page with desired logging settings (already tried this, plus I would expect "basic" to still show service restarts, nothing is showing at all, even with every log category set to "highest")
I realised the system wasn't running the latest opnsense so I upgraded it, and the behaviour has persisted with OPNsense 23.1.7_3-amd64
Does anyone have any other ideas on what can cause the IPSEC logs to be completely blank and where I might start troubleshooting this?
Logging generally is working; openvpn logs are working, for example.
I have just noticed that when I restart strongswan, the General log adds the following:
2023-05-22T16:00:51 Notice daemon 00[LIB] no files found matching '/usr/local/etc/strongswan.opnsense.d/*.conf'
This seems... undesirable (and this despite having a P1 and a P2 configured).
How would I go about correcting this, assuming this is *not* expected behaviour?
...ok, so I guess this is my fault, because the default log view seems to be "Warning" messages only and I forgot to check other priorities.... which I only remembered *after* I went and dug around on the console and found /var/log/ipsec/latest.log did indeed have entries after all ::)