If I set my TTL in WiFix to 65 when I ping 8.8.8.8 in CMD it returns 63
If I set my TTL in WiFix to 67 when I ping 8.8.8.8 in CMD it returns 65
Which would be correct for tmobile?
WE826 TTL confusion?
Forum rules
Please assure there is not an existing forum and topic related to your post
Please assure there is not an existing forum and topic related to your post
- Didneywhorl
- Posts: 3646
- Joined: Fri Mar 23, 2018 5:37 pm
- Location: USA
- Has thanked: 1370 times
- Been thanked: 764 times
- Contact:
Re: WE826 TTL confusion?
I would guess 65 or 66. Set it and check to see if your data is counting as hotspot data or not. Dont forget the ipv6 'ttl' (HL)
Re: WE826 TTL confusion?
Didneywhorl wrote: Sun Nov 22, 2020 10:31 pm I would guess 65 or 66. Set it and check to see if your data is counting as hotspot data or not. Dont forget the ipv6 'ttl' (HL)
Thanks guys, I will log in and see what it is currently being reported as. I just didn't know what TTL value we are after when I ping google or a website. I currently have it set to 65 in wifix, so when I ping google it is saying ttl=63 in the CMD.
On a different note, when I ping google from my phone on cellular it returns ttl=111. I just don't know what all this means and what each ttl value is recognized as by the carriers.
- Didneywhorl
- Posts: 3646
- Joined: Fri Mar 23, 2018 5:37 pm
- Location: USA
- Has thanked: 1370 times
- Been thanked: 764 times
- Contact:
Re: WE826 TTL confusion?
Is your phone the same carrier as your modem? You can def try setting your ttl to a value above 111. Each time the packet "hops" through a device that routes it to its destination, it goes down by 1. IE TTL of 65 by 65 when it leaves your router, but then go down by one when it passes through your carriers equipment and into the backhaul or fiber line, then down by 1 for each "router" it hits on the way to its destination.
-
- Posts: 11
- Joined: Tue Apr 13, 2021 11:17 pm
- Has thanked: 0
- Been thanked: 0
- Didneywhorl
- Posts: 3646
- Joined: Fri Mar 23, 2018 5:37 pm
- Location: USA
- Has thanked: 1370 times
- Been thanked: 764 times
- Contact:
Re: WE826 TTL confusion?
It depends on the device, but if you are using a device with rooter, you can place the following rules in the firewall-->custom Rules tab, to cover both ip4 and ip6:
Some like to do:# A Hashtag is in place if not using that line.
# Popular TTL values: 64 for Visible. 65 for Verizon, ATT and Tmobile. 117 is sometimes a working TTL for Verizon.
# When changing values, first place # on all the TTL value lines beginning, like this line itself has. Then click Restart Firewall.
# Then change all of the TTL values to what you need and then delete the #s at their lines beginning.
# Then click Restart Firewall. Changes should then be applied properly.
# Start-IP6-TTL-Fix
ip6tables -t mangle -I POSTROUTING -o wwan0 -j HL --hl-set 65
# End-IP6-TTL-Fix
# Start-IP4-TTL-Fix
iptables -t mangle -I POSTROUTING -o wwan0 -j TTL --ttl-set 64
# End-IP4-TTL-Fix
#ipv6ttlfix
ip6tables -t mangle -I POSTROUTING -o wwan0 -j HL --hl-set 66
ip6tables -t mangle -I PREROUTING -i wwan0 -j HL --hl-set 66
#startTTL
iptables -t mangle -I POSTROUTING -o wwan0 -j TTL --ttl-set 66
iptables -t mangle -I PREROUTING -i wwan0 -j TTL --ttl-set 66
#endTTL
The ip6tables mangle rules are for ipv6. Technically its not "TTL" on IPV6, its "HL"