Usb multi tethering

[FunnyDevs]

Hello! I have rooted devices and i would like to connect them in tethering with pc (bypassing Android gateway and ip hardcoding ).
Could i use your app to do that?

[worstperson]

Without the tproxy stuff, it should work fine for controlling IPv4 gateway and subnet. IPv6 would be much tougher. If you like, I can post a branch with only this feature.

[FunnyDevs]

Ok, thank you so much :)

[worstperson]

Try this:
https://github.com/worstperson/TetherTPROXY/tree/notproxy
I added an apk at the base of the project.

[FunnyDevs]

I have tried: the ip isn't the one i choose, on Windows 11 i have this info

Ethernet card Ethernet 8:

Connection-specific DNS suffix:
Local IPv6 address relative to the connection . : fe80::7106:12aa:686d:83ce%10
IPv4 address auto configuration : 169.254.131.206
Subnet mask . . . . . . . . . . . . . : 255.255.0.0
Default gateway . . . . . . . . . :

the device hasn't an external connection with a sim, it uses the usb tethering connection only as a method to communicate with PC.

[worstperson]

That tells me dnsmasq is not getting loaded properly. Is this Android x86 by chance?

Any device info would help and "logcat | grep tethertproxy" after starting the tether and service and waiting a minute. Thanks for reporting back.

[worstperson]

Sorry, the command should be "logcat | grep -i tethertproxy". On my devices, the output looks like this:

03-30 16:48:07.130  8911  8911 I TetherTPROXY: Recieved TETHER_STATE_CHANGED broadcast
03-30 16:48:07.130  8911  8911 I TetherTPROXY: Tether restore callback already scheduled
03-30 16:48:12.242  8911  8911 I TetherTPROXY: Setting IP address
03-30 16:48:12.270  8911  8911 I TetherTPROXY: Setting route
03-30 16:48:12.302  8911  8911 I TetherTPROXY: 200 0 success
03-30 16:48:12.303  8911  8911 D SHELL_IN: rm /data/user/0/com.worstperson.tethertproxy/files/dnsmasq.leases
03-30 16:48:12.320  8911  8911 D SHELL_IN: rm /data/user/0/com.worstperson.tethertproxy/files/dnsmasq.pid
03-30 16:48:12.337  8911  8911 D SHELL_IN: /data/user/0/com.worstperson.tethertproxy/files/dnsmasq.arm64-v8a --interface=rndis0 --keep-in-foreground --no-resolv --no-poll --domain-needed --bogus-priv --dhcp-authoritative --port=5353 --dhcp-alternate-port=6767,68 --dhcp-range=10.0.0.10,10.0.0.99,1h --dhcp-option=option:dns-server,10.0.0.1 --server=8.8.8.8 --server=8.8.4.4 --dhcp-leasefile=/data/user/0/com.worstperson.tethertproxy/files/dnsmasq.leases --pid-file=/data/user/0/com.worstperson.tethertproxy/files/dnsmasq.pid &
03-30 16:48:17.348  8911  8911 D SHELL_IN: [ -f /data/user/0/com.worstperson.tethertproxy/files/dnsmasq.pid ]
03-30 16:48:17.352  8911  8911 D SHELL_IN: cat /data/user/0/com.worstperson.tethertproxy/files/dnsmasq.pid
03-30 16:48:47.419  8911  8911 D SHELL_IN: [ -f /data/user/0/com.worstperson.tethertproxy/files/dnsmasq.pid ]
03-30 16:48:47.424  8911  8911 D SHELL_IN: cat /data/user/0/com.worstperson.tethertproxy/files/dnsmasq.pid

Other useful commands are "logcat | grep -i dnsmasq" to get messages from dnsmasq and "logcat | grep -i shell_" to get information from the root shell.

[FunnyDevs]

This is the message when usb tethering is disabled

01-02 16:56:16.681  3232  3232 I TetherTPROXY: Recieved TETHER_STATE_CHANGED broadcast
01-02 16:56:16.681  3232  3232 I TetherTPROXY: Tether restore callback already scheduled
01-02 16:56:16.713   397   433 I BufferQueueProducer: [Toast#0](this:0x78105c1800,id:70,api:1,p:3232,c:397) connect(P): api=1 producer=(3232:com.worstperson.tethertproxy) producerControlledByApp=true
01-02 16:56:21.687  3232  3232 I TetherTPROXY: Tethering is not active

And this when it's active

01-02 16:58:17.224  3232  3232 I TetherTPROXY: Recieved TETHER_STATE_CHANGED broadcast
01-02 16:58:17.225  3232  3232 I TetherTPROXY: Tether restore callback already scheduled
01-02 16:58:17.247   397   434 I BufferQueueProducer: [Toast#1](this:0x7810582800,id:86,api:1,p:3232,c:397) connect(P): api=1 producer=(3232:com.worstperson.tethertproxy) producerControlledByApp=true
01-02 16:58:22.201  3232  3232 I TetherTPROXY: Tether is already applied...

The devices is arm64

[worstperson]

It looks like how I am parsing the dns bind or routing table is insufficient. This is mostly kernel dependent, but could also be effected by device configuration I suppose. I really hate to bother you again, but can I have you start a regular tether and run these commands through adb or terminal app:

su
cat /proc/net/tcp
cat /proc/net/route

It looks like this on my devices:

ocean:/ # cat /proc/net/tcp                                                                                                                                           
  sl  local_address rem_address   st tx_queue rx_queue tr tm->when retrnsmt   uid  timeout inode                                                     
   0: 0100007F:0035 00000000:0000 0A 00000000:00000000 00:00000000 00000000  1052        0 1452984 1 0000000000000000 99 0 0 10 0                    
   1: 4D69A8C0:0035 00000000:0000 0A 00000000:00000000 00:00000000 00000000  1052        0 1452982 1 0000000000000000 99 0 0 10 0                    
ocean:/ # cat /proc/net/route                                                                                                                                         
Iface   Destination     Gateway         Flags   RefCnt  Use     Metric  Mask            MTU     Window  IRTT                                                       
wlan0   0069A8C0        00000000        0001    0       0       0       00FFFFFF        0       0       0 

The app matches local_address to Destination to get the Iface(wlan0 in this case).

[worstperson]

I uploaded a new test commit that parses netstat and iproute2 output instead, fair change it might address the issue.

[FunnyDevs]

for /proc/net/tcp

sl  local_address rem_address   st tx_queue rx_queue tr tm->when retrnsmt   uid  timeout inode

 0: 0100007F:0035 00000000:0000 0A 00000000:00000000 00:00000000 00000000  9999        0 56414 1 0000000000000000 100 0 0 10 0
 1: 812AA8C0:0035 00000000:0000 0A 00000000:00000000 00:00000000 00000000  9999        0 56412 1 0000000000000000 100 0 0 10 0
 2: 0100007F:C517 0100007F:D10D 01 00000000:00000000 00:00000000 00000000  2000        0 63857 1 0000000000000000 20 6 0 10 -1
 3: 0100007F:B287 0100007F:D10E 01 00000000:00000000 00:00000000 00000000  2000        0 64711 1 0000000000000000 20 4 0 10 -1

and for /proc/net/route

Iface   Destination     Gateway         Flags   RefCnt  Use     Metric  Mask            MTU    W
        IRTT
rndis0  002AA8C0        00000000        0001    0       0       0       00FFFFFF        0      0
        0

This is with simple tethering, without activating your app. Should i give you the results even activating your service?

[worstperson]

Does your phone's shell provide awk? It's the only possible issue I see. I can build with busybox if needed.