Feature #7007
closed
Change default IPsec/strongswan log levels
100%
Description
It is usually beneficial to set IKE SA, IKE Child SA, and Configuration Backend to logging level "Diag" when troubleshooting IPsec issues. Propose changing these to be the default settings with all others staying at level "Control."
Updated by Kill Bill about 8 years ago
Any attempts on tweaks useful for debugging here are completely useless while IPsec log is being flooding with tons of utter junk.
Time Process PID Message Dec 12 20:50:57 charon 13[NET] <con4|20> sending packet: from 188.xx.xx.xx[500] to 94.xx.xx.xx[500] (57 bytes) Dec 12 20:50:57 charon 13[ENC] <con4|20> generating INFORMATIONAL response 416 [ ] Dec 12 20:50:57 charon 13[ENC] <con4|20> parsed INFORMATIONAL request 416 [ ] Dec 12 20:50:57 charon 13[NET] <con4|20> received packet: from 94.xx.xx.xx[500] to 188.xx.xx.xx[500] (57 bytes)
100+ lines of the above shit in 5 minutes. At default logging levels. Awesome. I certainly object to increasing loglevels of anything here until the crap it muted.
Updated by Jim Pingle about 8 years ago
- Target version set to 2.4.0
Those are a different story entirely and unrelated to this at all. See #4227 (If you set "Networking" and "Message Encoding" to audit or silent it may be able to stop those from being logged)
The log areas in question on this ticket are what we always recommend for IPsec troubleshooting anyhow, it only increases the log verboseness during negotiation and it shows much more useful information about the encryption/authentication/traffic selector exchanges.
Updated by Jim Thompson almost 8 years ago
- Assignee set to Jim Pingle
assigned to Pingle for resolution.
Updated by Jim Pingle almost 8 years ago
- Status changed from New to Feedback
- % Done changed from 0 to 100
Applied in changeset e470f72139ed54972465e653e27536687ce58b23.