[strongSwan-dev] Info related to Stroke Utility

krishna chaitanya krishnachaitanya.sanapala at gmail.com
Mon Sep 17 08:45:24 CEST 2012

HI Andreas,

I started my work on stroke utility .

Initially I was having some segfaults but was able to resolve them. I was
able to add connections via CLI which was evident from ./stroke statusall .
But I was unable to initiate the added connections.

I started my work by hard-coding the stroke message to a certain extent
later on I will be cleaning up the code.

I have attached the Log files and the modified code. Please help me or
direct me the hack to initiate the connection. I will go ahead.

On Fri, Sep 7, 2012 at 11:28 AM, krishna chaitanya <
krishnachaitanya.sanapala at gmail.com> wrote:

> Hi Andreas,
> Thanks for the reply.
> I don't wanted to spam the dev-community with this mail.
> Let me brief you on what I was doing the couple of months. I have done
> some bench marking on the open source IKEv2 solutions Racoon, OpenIKEv2 and
> IKEv2 along with yours and concluded Strongswan aptly meeting my
> requirements.
> So I have to integrate it with my IPsec Fast Path which is in progress.
> Coming to the CLI part I had few discrepancies :
> I had 3 designs were in my mind since the day I took this task.
> 1. One is to write a wrapper script that would simple update the conf file
> in runtime.
> 2. CLI parsing and invoking the Stroke API. Its currenlty in the state of
> development which is not fully functional. So if I write it for my needs
> and once you  release your stroke CLI utility my code would be useless.
> 3. Developing an RPC model using the same Stroke API which I have gone
> through the Styx plugin. But I was not getting enough support from the
> developer.
> So currently you don't have a full fledged support of the Stroke CLI, I
> would start my design on the lines of Design 2 .
> Coming to the funding part as I see Strongswan Team is doing a beautiful
> job. I will definitely take the proposal to the concerned and will be
> updating you on the prospects. Let be positive.
> Thanks for your support.
> On Thu, Sep 6, 2012 at 10:31 PM, Andreas Steffen <
> andreas.steffen at strongswan.org> wrote:
>> Hi Krishna,
>> we currently don't have any plans to implement a full-fledged stroke
>> command line configuration tool. If someone is willing to do that
>> e.g. along the lines of the obsoleted whack interface but using the
>> stroke_msg structs
>> http://wiki.strongswan.org/projects/strongswan/repository/revisions/master/entry/src/stroke/stroke_msg.h
>> then anyone is invited to contribute to such an interface. Also if some
>> organization is willing to sponsor the development then we would
>> prioritize a stroke command line interface on our todo list.
>> Best regards
>> Andreas
>> On 09/03/2012 10:00 PM, krishna chaitanya wrote:
>> > Hi Team,
>> >
>> > As an user of Strongswan, when could we expect the the complete
>> > development of the stroke utility.
>> >
>> >
>> > Thanks,
>> > Krishna Chaitanya
>> ======================================================================
>> Andreas Steffen                         andreas.steffen at strongswan.org
>> strongSwan - the Linux VPN Solution!                www.strongswan.org
>> Institute for Internet Technologies and Applications
>> University of Applied Sciences Rapperswil
>> CH-8640 Rapperswil (Switzerland)
>> ===========================================================[ITA-HSR]==
> Thanks,
> KC
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.strongswan.org/pipermail/dev/attachments/20120917/10e24bfa/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Stroke_Dev_Logs
Type: application/octet-stream
Size: 2883 bytes
Desc: not available
URL: <http://lists.strongswan.org/pipermail/dev/attachments/20120917/10e24bfa/attachment.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: stroke.c
Type: text/x-csrc
Size: 20689 bytes
Desc: not available
URL: <http://lists.strongswan.org/pipermail/dev/attachments/20120917/10e24bfa/attachment.c>

More information about the Dev mailing list