[OnePlus 8 Pro  ROMs, Kernels, Recoveries, & Other ] shootind5nukes:
I'm still on 2.5.1 because I'm loading a large backup. When I'm finished will upgrade to 2.6.0. Showing you the steps here. This is the iptables rules after I changed the ttl to 67 on wlan0. And ifconfig of wlan0 to show it is the correct interface.

Rules:

:/data/data/com.termux/files/home # iptables -t mangle -vnL PREROUTING

Chain PREROUTING (policy ACCEPT 178 packets, 61344 bytes)

pkts bytes target prot opt in out source destination

146 59744 TTL all -- wlan0 * 0.0.0.0/0 0.0.0.0/0 TTL set to 67

10514 11M TTL all -- wlan0 * 0.0.0.0/0 0.0.0.0/0 TTL set to 67

:/data/data/com.termux/files/home # iptables -t mangle -vnL POSTROUTING

Chain POSTROUTING (policy ACCEPT 49 packets, 3116 bytes)

pkts bytes target prot opt in out source destination

18 1670 TTL all -- * wlan0 0.0.0.0/0 0.0.0.0/0 TTL set to 67

7088 872K TTL all -- * wlan0 0.0.0.0/0 0.0.0.0/0 TTL set to 67

7105 876K TTL all -- * wlan0 0.0.0.0/0 0.0.0.0/0 TTL set to 67

ifconfig wlan0 output:

wlan0 Link encap:Ethernet HWaddr *REMOVED* Driver cnss_pci

inet addr:192.168.1.44 Bcast:192.168.1.255 Mask:255.255.255.0

inet6 addr: *REMOVED* Scope: Link

UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

RX packets:3222652 errors:0 dropped:15 overruns:0 frame:0

TX packets:21189103 errors:0 dropped:219 overruns:0 carrier:0

collisions:0 txqueuelen:3000

RX bytes:797778144 TX bytes:30489615620

After that going to ping this device from. Another device inside my network. When pinging device the ping return should include a ttl of 67.

Just did that, can't copy and paste results but returned a ttl of 64 still. Will do the test again but change rmnet_data2 to 67 see if I can get the ping to return 67. Standby.

Rebooting will come back and edit this message.

Changed rmnet_data2 and still returned 64, which is the default for Android. Even though the rules I added say 67. I'm very curious as to why that didn't work. It works well at changing rmnet_data2 which hides tethering but can't seem to change the wifi ttl. The only use for that I can see anyways is making the wlan0 ttl of 65 so once it makes the next hop to another phone with Hotspot on would make tethering from the device in question hide its own tethering because after the hop through the Hotspot the ttl would decrease by one making its ttl 64 as it leaves the device doing the Hotspot thus making its tethering seem like it came from the Hotspot device which would cause the carrier to think the data being used isn't Hotspot data but actually data from the device itself so it wouldn't be counted towards tethering data.

---------- Post added at 09:32 AM ---------- Previous post was at 09:06 AM ----------

Hell yeah. Upgraded to 2.6.0. Changed ttl of wlan0 to 67(while wifi was in use don't know if that matters but thought I'd mention it) . When pinged it returned 67. It works on 2.6.0 but not 2.5.1. You're good at what you do buddy. Hope this helped you in any sort of way.

If you wanna do something very cool, don't know if you can, but you should add this into your kernel. Make the rmnet_data2 ttl in and out 64. Then make the wlan0 ttl in and out 65. That would be very cool. Maybe label that kernel for Hotspot tethering and people who want that could download it. Right now I use ex kernel manager to load a script on startup to change the rmnet_data2 but I bet you could do something inside the kernel to do it already.