Yeah I was merely referring to the trivial warning of the ifconfig mismatch. It's not exactly a problem but it just sort of made me aware of such thing as /31 subnet and noticed the bug on Linux. That's why I never opened an issue on ics-openvpn. ________________________________ From: Arne Schwabe <a...@rfc2549.org> Sent: Tuesday, November 5, 2019 12:28:25 AM To: Gert Doering <g...@greenie.muc.de> Cc: openvpn-devel@lists.sourceforge.net <openvpn-devel@lists.sourceforge.net> Subject: Re: [Openvpn-devel] [PATCH] tun/iproute2: support 31-bit ipv4 prefix (RFC 3021)
>> Yeah the removal of the p2p topology was one of the reasons. It's >> actually the fact that ics-openvpn doesn't really parse point-to-point >> ifconfig that made me aware of this. > > I wasn't aware of that, but since Arne is reading here, maybe he can > comment on it. It's possible that the Android VPN API just does not > permit p2p mode, but wants a subnet. > > Arne, any idea if /31 works on Android? Yes. But Android is special here anyway. It always wants a subnet mask but the mask can be also be 255.255.255.255. And you also don't have a gateway address and Android also does not set a route to the tun interface (On Android 4.4+). So basically you always operate in p2p mode and emulate other modes by adding routes to the tun interface. Arne
_______________________________________________ Openvpn-devel mailing list Openvpn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openvpn-devel