From: Tom Yan Date: Tue, 5 Nov 2019 03:08:36 +0000 Message-ID: References: <20191103053148.18059-1-tom.ty89@...277...> <20191103182443.GC40538@...1296...> <20191103183351.GD40538@...1296...> <20191103204613.GE40538@...1296...>, In-Reply-To: Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_BN7PR04MB52517BB2179BE30E03B775CAFD7E0BN7PR04MB5251namp_" MIME-Version: 1.0 Subject: Re: [Openvpn-devel] [PATCH] tun/iproute2: support 31-bit ipv4 prefix (RFC 3021) List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Gert Doering , Arne Schwabe Cc: "openvpn-devel@lists.sourceforge.net" --_000_BN7PR04MB52517BB2179BE30E03B775CAFD7E0BN7PR04MB5251namp_ Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable 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 thin= g as /31 subnet and noticed the bug on Linux. That's why I never opened an = issue on ics-openvpn. ________________________________ From: Arne Schwabe Sent: Tuesday, November 5, 2019 12:28:25 AM To: Gert Doering Cc: openvpn-devel@lists.sourceforge.net Subject: Re: [Openvpn-devel] [PATCH] tun/iproute2: support 31-bit ipv4 pref= ix (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 --_000_BN7PR04MB52517BB2179BE30E03B775CAFD7E0BN7PR04MB5251namp_ Content-Type: text/html; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable
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 thin= g as /31 subnet and noticed the bug on Linux. That's why I never opened an = issue on ics-openvpn.

From: Arne Schwabe <ar= ne@...1227...>
Sent: Tuesday, November 5, 2019 12:28:25 AM
To: Gert Doering <gert@...1296...>
Cc: openvpn-devel@lists.sourceforge.net <openvpn-devel@...1439...= ceforge.net>
Subject: Re: [Openvpn-devel] [PATCH] tun/iproute2: support 31-bit ip= v4 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-p= oint
>> 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 mod= e
and emulate other modes by adding routes to the tun interface.

Arne

--_000_BN7PR04MB52517BB2179BE30E03B775CAFD7E0BN7PR04MB5251namp_--