Hi, On Thu, May 10, 2012 at 09:00:05AM +0200, Adriaan de Jong wrote: > That would be another option. In the model we were using (which might be > different), the order is as follows: > > 1. openvpn is started > 2. openvpn opens a socket to the remote host > 2. openvpn establishes the control channel across this socket > 3. openvpn passes socket and control channel data (IP, routing, DNS, etc) > through the management interface to the android app > 4. android app passes these to the VPNService and receives an opened tun > 5. android app passes the tun to openvpn > 6. openvpn proceeds as usual
This looks very reasonable to me.
(As for the patch itself, I had no time to go through it yet, sorry)
Changing the build environment to build a shared library out of openvpn
is something I do not fully understand yet, though - and don't view
a particular useful goal right now.
gert
--
USENET is *not* the non-clickable part of WWW!
//www.muc.de/~gert/
Gert Doering - Munich, Germany g...@greenie.muc.de
fax: +49-89-35655025 g...@net.informatik.tu-muenchen.de
pgpdrmmRXkF6D.pgp
Description: PGP signature
