[strongSwan-dev] Info on the Starter and Stroke

[krishna chaitanya]

Thanks Very much for the Info Martin.

Could you please just throw some light on the Conftest and backend manager
modules.


 backend <http://fossies.org/dox/strongswan-5.0.0/group__backend.html>
backend_manager<http://fossies.org/dox/strongswan-5.0.0/group__backend__manager.html>
 child_cfg <http://fossies.org/dox/strongswan-5.0.0/group__child__cfg.html>
ike_cfg <http://fossies.org/dox/strongswan-5.0.0/group__ike__cfg.html>
peer_cfg <http://fossies.org/dox/strongswan-5.0.0/group__peer__cfg.html>
proposal <http://fossies.org/dox/strongswan-5.0.0/group__proposal.html>
traffic_selector<http://fossies.org/dox/strongswan-5.0.0/group__traffic__selector.html>
On Thu, Aug 9, 2012 at 7:02 PM, Martin Willi <martin at strongswan.org> wrote:

> Hi,
>
> > I could see the int starter_start_charon (starter_config_t *cfg, bool
> > no_fork, *) is loading the configuration
>
> invokecharon.c actually just spawns the charon process and passes a few
> arguments from global ipsec.conf settings.
>
> > but what I don't understand is starterstroke.c which is having the
> > same functionality of loading the configurations into the charon.
>
> starterstroke.c passes the connection definitions from your ipsec.conf.
> It uses the Unix socket created by the "stroke" libcharon plugin to pass
> over connection definitions to the daemon.
>

> > I could see in the documentation is the stroke is yet to be developed
> > just like Whack.
>
> The stroke utility under src/stroke doesn't handle configuration
> add/removal. It has some stubs for these operations, but they are not
> very functional. It is mainly used to issue "ipsec up/down/status"
> commands. Configuration management is done via starter.
>
> Regards
> Martin
>
>
> Thanks,
KC
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.strongswan.org/pipermail/dev/attachments/20120810/0761a8d1/attachment.html>