Route Problem on Galaxy Note 8

pacien / tincapp

Android binding and user interface for the tinc mesh VPN daemon.

https://tincapp.euxane.net

GNU General Public License v3.0

165 stars 31 forks source link

Route Problem on Galaxy Note 8 #77

Closed mshsoft closed 5 years ago

mshsoft commented 5 years ago

Hi all I got it working fairly easily on Galaxy Note 8. But, despite being able to ping both parties, I cannot get any packet to any other destination to get out of the phone. It seems that the Route option in network.conf does not do anything. Yeah, I know that android keeps it somewhere else and I have to see the routes with "ip route list table all" and it does add some entries for tun0, but no traffic destined for any address except the VPN subnet passes through. Strangely, DNS works, I can resolve DNS queries on the phone. I have installed a dns server on the other end, so some packets can go through. But web traffic, etc. , cannot! I have attached the config files and the logs:

Mobile App Config files: network.conf.txt tinc.conf.txt screenshot_20190103-014404_tinc app

host files: appclient1.txt appserver.txt

Traffic at the server side when a web page is requested on the mobile : traffic_at_the_server_side

as you can see, DNS traffic passes through, since the directive in network.conf works, and I have a dns server set up at the other side, but normal traffic cannot be routed.

Routes: routes_on_the_mobile_phone

pacien commented 5 years ago

Hello,

If you want all packets from appclient1 to be routed to appserver, you also need to add a corresponding catch-all Subnet = 0.0.0.0/0 to appserver's host file.

Furthermore, I notice some minor issues in the other files:

appclient1: the prefix length /32 is missing in the Subnet parameter.
tinc.conf: the device parameter is useless on Android.

If further assistance is needed, I invite you to continue over IRC: #tincapp on irc.freenode.net.

mshsoft commented 5 years ago

works like a charm. Thanks buddy