On Thu, 2017-11-23 at 13:26 +0100, Yves-Alexis Perez wrote: > I don't think libstrongswan is the right package, since indeed counters is a > libcharon plugin. Maybe it should move to the strongswan-libcharon package and > we should have a dependency from strongswan-starter and strongswan-swanctl to > strongswan-libcharon, but right now that's not needed so I'm not sure I want > that.
Actually I was a bit confused too: it's a libcharon plugin which should then be loaded by a relevant charon process. For stroke plugin, this is /usr/lib/ipsec/charon, in your case, for strongswan-swanctl, it is /usr/sbin/charon-systemd from the charon-systemd package. The swanctl command is just talking (via vici) to the charon-systemd binary. And charon-systemd packages already depends on strongswan-libcharon, so it should be fine to move the counters plugin there, I think. Does that make sense to you? Regards, -- Yves-Alexis
signature.asc
Description: This is a digitally signed message part
