Thanks for this.
I suspect I might have been unclear. The systemd service I'm using is the
one installed by the EPEL package is the traditional charon called using
/usr/libexec/strongswan/starter, not the newer charon-systemd variant.
The service file for this is:
[Unit]
Description=strongSwan I
___
Users mailing list
Users@lists.strongswan.org
https://lists.strongswan.org/mailman/listinfo/users
Hi James,
yes, with systemd and journalctl active you have to remove the
syslog daemon section from strongswan.conf. If you want to change
the defaults of the systemd logging you can do this in a charon.journal
section in strongswan.conf. And I personally prefer an additional
level 0 output going
Out of the box I seem to get every log message from strongswan duplicated,
once logged by "charon", then again by "strongswan" after a delay, e.g.
Oct 10 12:26:32 sapphire charon: 05[ENC] generating INFORMATIONAL_V1
request 1411728704 [ HASH N(DPD) ]
followed later by:
Oct 10 12:29:32 sapphire s
Hi Andreas,
Thanks for the reply. It was very helpful
Regards,
kalyani
-Original Message-
From: Andreas Steffen [mailto:andreas.stef...@strongswan.org]
Sent: Tuesday, October 11, 2016 11:47 PM
To: Kalyani Garigipati (kagarigi)
Cc: users@lists.strongswan.org
Subject: Re: Strongswan AUTH
