Am 12.06.18 um 13:17 schrieb Gert Doering:
> Hi,
>
> On Tue, Jun 12, 2018 at 12:14:27PM +0200, Arne Schwabe wrote:
>>> The existing Android code is different from all the other platforms,
>>> as it sends IPv6 info ("IFCONFIG6") *before* IPv4 info.
>>>
>>> Arne, do I have to assume that this is intentional, and your client will
>>> explode if it receives IFCONFIG first and IFCONFIG6 second, or no
>>> IFCONFIG at all?
>>
>> No ifconfig at at all will produce an error since ANdroid itself will
>> not like to have no ifconfig at all. For the Android client it is only
>> important that ifconfig/routes/etc. all happen before opening the tun
>> device.
>>
>> IPv6 only should be fine with my client.
>
> So, to paraphrase this: you will handle IFCONFIG and IFCONFIG6 in
> either order or "just one of them" fine?
>
> I was sort of assuming the code waits for an incoming IFCONFIG and then
> fires up the VPN API with "IFCONFIG and optional IFCONFIG6" - in which
> case, sending IFCONFIG first would have caused "fun effects with IFCONFIG6",
> and "not sending IFCONFIG at all" would cause interesting effects :-)
>
> ... but now I do seem to remember that you collect *all* information
> first (IFCONFIG* and ROUTE*), so it doesn't really matter in which order
> the "core" sends it...
Yeah, I do. At the moment I think I need ifconfig before route but that
is not a bug issue to change that. Only thing that I really need is that
opening TUN happens after everything else because after opening tun
there no more changes possible.
Arne
------------------------------------------------------------------------------
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
