5 ms·
I found out that setting the IP TTL of my machine to 65 usually bypasses most tethering checks in most ISPs. Like T-Mobile has a special case where they allow
by gopalv 12y ago
I found out that setting the IP TTL of my machine to 65 usually bypasses most tethering checks in most ISPs.
Like T-Mobile has a special case where they allow :443 from tethered hosts, while disallowing :80.
That disappears when the TTL is 65.
- chimeracoder 12y agoDo you do this on your laptop, or on your phone? I know that (older versions of) Cyanogenmod would set the TTL of packets to be (2^n + 1) for this exact reason, but it happened on the phone. Also, FWIW, I have T-mobile and haven't experienced issues tethering on my stock Nexus 5. I'm curious why some customers are experiencing these and not others.
- toomuchtodo 12y agoOn a Galaxy Nexus on T-Mobile in Chicago; they subvert my :80 requests to a "you should be paying for tethering" portal.
- gopalv 12y agoI set that on the laptop actually - android's TTL is 64, so +1 hop is 65. I'm sure they could filter that if I upgraded my phone & the tether got a different gateway host (like in the blog).
- Groxx 12y agoOn my Nexus 4 it worked fine for a few months, but then they started blocking it (I used it lightly during my commute, probably <1gb monthly, I have the $30 5gb-fast/unlimited-slow plan). Give it time, it'll probably happen to you too.