Hmm btw, not sure you are talking about the same thing, but at least my device the "proto kernel scope link" subnet route is added for the tun. While I can ping the "peer" out-of-the-box with /31 subnet and the subnet topology, with p2p topology and 255.255.255.255 mask, I need to add route in ics-openvpn for its peer before I can ping it. (The server is configured with topology and ifconfig corresponds to the client's in both tests.)
On Tue, 5 Nov 2019 at 01:01, Arne Schwabe <a...@rfc2549.org> wrote: > > >> 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 _______________________________________________ Openvpn-devel mailing list Openvpn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openvpn-devel
