Hi,
Thank you all for the responses, since I was looking for a specific client
implementation (iOS), I am going to test the PIA framework, as kindly
pointed by Rogier.
Gert, since I was also mapping the whole protocol, if PIA framework is
capable of meet my specific requirements then I will use it instead of
creating another lib by my own. Anyway thanks for telling me your point of
view.
Best Regards.
2018-06-06 17:14 GMT-03:00 Rogier Spoor <rogier.sp...@surfnet.nl>:
> Hi all,
>
> > On Tue, Jun 05, 2018 at 05:54:05PM -0300, Rafael Herrera wrote:
> >> We are developing a custom client for OpenVPN 2.4.x and it would be
> nice to
> >> have some support from experienced community developers.
>
> It seems PIA has created an OpenVPN compatible client for iOS which
> could save some time.
> https://github.com/pia-foss/tunnel-apple
>
> This was probably done because you can't release 'regular' OpenVPN 2.x
> or 3.x in the Apple appstore due to a GPL license problem.
>
> The PIA implementation looks pretty nice.
> >> Is there anybody here available to help us with a consultancy regarding
> to
> >> network protocols and its required state machines?
> >
> > David was working on an RFC to document the protocol - no idea if that
> > has progressed to "readable first draft" status already, but it might
> > be a good test for the document.
> >
> > Besides this, I wonder why you're not basing your work on the existing
> > (2.x or 3.x) client, possibly with a new GUI wrapped on top -
> duplicating
> > all the code and logic inside OpenVPN is a fairly big task, especially
> > in the "this is not really very well defined, it just happens to be
> > this way today" areas.
>
> This would certainly be the most preferred way 2 go. Makes no sense to
> have multiple implementations; this will fork the community. However for
> iOS it seems 2.x and 3.x can't be used if you like to release your own
> client in the appstore.
>
> cheers,
> Rogier
> >
> > Also, you'll have to end up following all developments that we do on
> > the 2.x and 3.x clients - like, right now we're working on making the
> > client work in an IPv6-only environment. We test against 2.x and 3.x,
> > but if we break "other implementations that we do not know about", it
> > is not something we can avoid.
> >
> > gert
> >
> >
> >
> > ------------------------------------------------------------
> ------------------
> > Check out the vibrant tech community on one of the world's most
> > engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> >
> >
> >
> > _______________________________________________
> > Openvpn-devel mailing list
> > Openvpn-devel@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/openvpn-devel
> >
>
>
>
--
Rafael de Paula Herrera
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Openvpn-devel mailing list
Openvpn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openvpn-devel
