Tunnel with default route: no access to local network.

[Chris56]

When a tunnel defines a default route, i.e. AllowedIPs = 0.0.0.0/0 The access to the local network is not possible anymore. This is different on Linux desktop and at least the tunnel packets themselves MUST run throuch the local net. No way to reach the local resources

Smartphone (please complete the following information):

• Device: any
• Android Version: serveral, e.g.13
• App Version [e.g. 3.3.3] 3.6.0
• Backend: [e.g. Kernel, Userspace]

To Reproduce Just define a default route in conf file.

Expected behavior Apart from the default route throght the tunnel an additional route to the local network.

[zaneschepke]

Hello! Please see the FAQ for how to resolve this.

In the near future, I'm looking to add settings to the config screen to exclude private IPs from the tunnel w/custom ranges, but (for now) the directions in the FAQ are the best way to resolve this.

[Chris56]

Thanks for your reply. I used this as an awkward workaround before. But apart from splitting 0.0.0.0/0 into a lengthy list: every time the android device moves to another local network, you will have to change the config. However, the config file should be agnostic of the network the device happens to be in. The (quite simple) Linux solution is creating a different routing table for the new default route, which is only being used, in case there is no local route defined for the particular destination ip: "ip -4 rule add table main suppress_prefixlength 0"