It can't work.

[Zibri]

This solution can't work because there is no TTL-SET in iptables on android.

iptables v1.8.7 (legacy): unknown option "--ttl-set"

moreover, setting TTL to 65 might work but is incorrect. TTL should be just increaded by 1.

My solution:
I patch the kernel so TTL is not decreased when forwarding.
As of now only a few phones are supported, but it works perfectly:
https://github.com/Zibri/ttl_fix/releases/tag/V3

[kushpr]

As you said most phones require a patched or custom kernel for this to work. Our kernels do bring the option for ttl-set but by factory its on N. So again all devices are supported just need a custom or patched kernel.

…

On Sat, Dec 17, 2022, 5:22 AM Zibri ***@***.***> wrote: This solution can't work because there is no TTL-SET in iptables on android. iptables v1.8.7 (legacy): unknown option "--ttl-set" moreover, setting TTL to 65 might work but is incorrect. TTL should be just increaded by 1. My solution: I patch the kernel so TTL is not decreased when forwarding. As of now only a few phones are supported, but it works perfectly: https://github.com/Zibri/ttl_fix/releases/tag/V3 — Reply to this email directly, view it on GitHub <#2>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AVMKV5ZBGX3ENFWWFKO5PJDWNWA4VANCNFSM6AAAAAATB3E4AY> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[Zibri]

As you said most phones require a patched or custom kernel for this to work. Our kernels do bring the option for ttl-set but by factory its on N. So again all devices are supported just need a custom or patched kernel.

Even with a custom kernel, is preferred to remove the TTL decrease from ip_forward.c than leave it and then add 1 to incoming TTL... imho.

[kushpr]

Correct. Theres actually a few ways to go about it you could edit the kernel modules or simply just go tru iptable rules or netfilters theres so many ways to do this workaround

…

On Mon, Dec 26, 2022, 7:12 AM Zibri ***@***.***> wrote: As you said most phones require a patched or custom kernel for this to work. Our kernels do bring the option for ttl-set but by factory its on N. So again all devices are supported just need a custom or patched kernel. Even with a custom kernel, is preferred to remove the TTL decrease from ip_forward.c than leave it and then add 1 to incoming TTL... imho. — Reply to this email directly, view it on GitHub <#2 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AVMKV52TFM3KOG5WXQGBIV3WPF4TLANCNFSM6AAAAAATB3E4AY> . You are receiving this because you commented.Message ID: ***@***.***>