From: Tom Rymes <trymes@rymes.com>
To: development@lists.ipfire.org
Subject: Re: [PATCH 2/2] ipsec: Silence charon
Date: Wed, 05 Feb 2020 12:16:57 -0500 [thread overview]
Message-ID: <e15e7c20-3867-ae9e-c6a8-d71dc22c887c@rymes.com> (raw)
In-Reply-To: <1A805D74-9F8F-4844-82D7-F3B7FDDC9C3B@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 2438 bytes --]
I have no issue with reducing the amount of verbosity of the current
IPSec logging. It has been helpful in the past when troubleshooting a
new tunnel, but it's not a major deal.
I was just hoping that whatever remaining messages are left after
reducing the verbosity could be directed to /var/log/ipsec instead of
/var/log/messages, as the IPSec messages can clutter up the kernel log,
which can be annoying. We have 20+ tunnels on two different machines, so
it can be quite extensive.
Tom
On 02/05/2020 11:55 AM, Michael Tremer wrote:
> Hi,
>
> Are those logged messages really useful?
>
> I know that there is a ticket open with this matter, but I am not sure if there is any value in the proposed changes.
>
> https://bugzilla.ipfire.org/show_bug.cgi?id=11001
>
> What are you getting from the logs that you won’t get right now?
>
> I have to enable proper debugging every time I want to have a REALLY detailed look. Otherwise the amount of logs are very verbose and it is hard to find things.
>
> Best,
> -Michael
>
>> On 5 Feb 2020, at 15:25, Tom Rymes <trymes(a)rymes.com> wrote:
>>
>> May I suggest that we also move the IPSec logging into its own file? It seems to me that, even with verbosity reduced, having it in /var/log/messages makes it a pain to locate anything else in the kernel log.
>>
>> Tom
>>
>> On 02/05/2020 6:24 AM, Michael Tremer wrote:
>>> Charon has some verbose logging enabled by default. This clutters
>>> the logs a lot.
>>> This patch disables debug logging but still lets charon log important
>>> messages like tunnels that are going up or down.
>>> Signed-off-by: Michael Tremer <michael.tremer(a)ipfire.org>
>>> ---
>>> html/cgi-bin/vpnmain.cgi | 3 +++
>>> 1 file changed, 3 insertions(+)
>>> diff --git a/html/cgi-bin/vpnmain.cgi b/html/cgi-bin/vpnmain.cgi
>>> index b3cd3e51e..d2bc70a27 100644
>>> --- a/html/cgi-bin/vpnmain.cgi
>>> +++ b/html/cgi-bin/vpnmain.cgi
>>> @@ -266,6 +266,9 @@ sub writeipsecfiles {
>>> flock CONF, 2;
>>> flock SECRETS, 2;
>>> print CONF "version 2\n\n";
>>> + print CONF "config setup\n";
>>> + print CONF "\tcharondebug=\"dmn 0, mgr 0, ike 0, chd 0, job 0, cfg 0, knl 0, net 0, asn 0, enc 0, lib 0, esp 0, tls 0, tnc 0, imc 0, imv 0, pts 0\"\n";
>>> + print CONF "\n";
>>> print CONF "conn %default\n";
>>> print CONF "\tkeyingtries=%forever\n";
>>> print CONF "\n";
>
next prev parent reply other threads:[~2020-02-05 17:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-05 11:24 [PATCH 1/2] ipsec: Add script to ensure VPNs are always on Michael Tremer
2020-02-05 11:24 ` [PATCH 2/2] ipsec: Silence charon Michael Tremer
2020-02-05 15:25 ` Tom Rymes
2020-02-05 16:55 ` Michael Tremer
2020-02-05 17:16 ` Tom Rymes [this message]
2020-02-05 15:23 ` [PATCH 1/2] ipsec: Add script to ensure VPNs are always on Tom Rymes
2020-02-05 16:53 ` Michael Tremer
2020-02-05 17:19 ` Tom Rymes
2020-02-05 17:22 ` Michael Tremer
2020-02-05 17:36 ` Tom Rymes
2020-02-06 15:03 ` Michael Tremer
2020-02-06 20:06 ` Tom Rymes
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e15e7c20-3867-ae9e-c6a8-d71dc22c887c@rymes.com \
--to=trymes@rymes.com \
--cc=development@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox