Re: [ANNOUNCE] Alpha Snapshots of WireGuard for Android and macOS

[Stefan Tatschner <stefan.tatschner@gmail.com>]

Hi Jason,

thanks for your hard work!

On Wed, 2018-05-16 at 00:54 +0200, Jason A. Donenfeld wrote:
> [NEW] WireGuard for Android
> ---------------------------
> You can download the app from the Play Store or from F-Droid. It supports
> adding wg-quick(8)-style .conf files or .zips of them. The app uses the kernel
> module if available, which gives the best performance, stability, and battery
> life, and falls back to the userspace code if it's not available. Download at:
> https://play.google.com/store/apps/details?id=com.wireguard.android

there seems to be sth. weird with the routing rules/tables. The wireguard routes
are not set up properly on my phone.

My wireguard network is 10.80.100.0/24, the wireguard server is 10.80.100.1, the
phone is 10.80.100.27.

On the phone:

lux:/ # ip route
10.80.100.0/24 dev tun0  proto kernel  scope link  src 10.80.100.27 
10.160.151.136/29 dev rmnet_data0  proto kernel  scope link  src 10.160.151.139

lux:/ # ip route get 10.80.100.1
10.80.100.1 via 10.160.151.140 dev rmnet_data0  src 10.160.151.139  uid 0 
    cache

  -> wrong. this routes via the mobile radio device.

lux:/ # ip route flush cache

lux:/ # ip route get 10.80.100.1      
10.80.100.1 via 10.160.151.140 dev rmnet_data0  src 10.160.151.139  uid 0 
    cache

How can I debug this further?


I have an openvpn server on the same box, in another subnet. This works fine on
the phone:

lux:/ # ip route
10.100.40.0/24 dev tun0  proto kernel  scope link  src 10.100.40.2 
10.160.151.136/29 dev rmnet_data0  proto kernel  scope link  src 10.160.151.139 

lux:/ # ip route get 10.80.100.1
10.80.100.1 dev tun0  src 10.100.40.2  uid 0 
    cache 

  -> works, the wireguard subnet is routed via tun0.

Stefan