> > > for broader testing gets interesting. If Linux gets support quickly, I'm > able > to test this out pretty soonish in a limited prod environment. > > I might start with Linux first since, as you rightly point out, more people can use/test it. Worth mentioning: you need third party implementation of SCTP on Windows and Mac OS X so this might be a significant hurdle for adoption on these platforms :-(
> Some practical details. General info about the development process can be > found here: > <https://community.openvpn.net/openvpn/wiki/DeveloperDocumentation>, > including > git repositories. > > Thanks, will read it. > So what I'm saying, please base your stuff on JJO's branch > now, but be sure your changes can be merged against the feat_ipv6_payload > branch too. As I'm the one going to do the merges, I'm going to be noisy > if > it doesn't go smooth ;-) > > Yes, I'll try JJO's branch first, see if I can make it work on FreeBSD and Linux Cheers, Olivier > And just let me state that, if someone got time to do a real overhaul of > socket.c, that would really be beneficial. That source file is confusing > at > best to read. However, we do have some source documentation patches is the > wild somewhere, waiting to go in soonish too - which I'd like to see go > into > the 2.3 cycle. So - there's a little coordination needed to be done here > with > such an overhaul too. > > > kind regards, > > David Sommerseth > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.10 (GNU/Linux) > Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/ > > iEYEARECAAYFAk1o6G0ACgkQDC186MBRfrrnPACgg5MNumXBR0McuTEip6/c76lY > BacAoIANCG/ZGas/yhiGEbw4U7xqDYeI > =PMoQ > -----END PGP SIGNATURE----- > -- “If you know what you're doing, three layers is enough; if you don't, even seventeen levels won't help”. ~ Padlipsky
