Tuesday, September 22, 2020

Verizon Hotspot - TTL Setting

2020-10-15 New command to try
netsh int ipv4 set glob defaultcurhoplimit=65
netsh int ipv4 set glob defaultcurhoplimit=128
ping -4 localhost

I don't know how long it takes to register the usage but I used the hotspot 10 hours ago and this is the result now:
Next morning the data usage was registered . . . So it didn't work
I'm trying 64 to compensate for the hop from phone to pc

This does not work for me any more.
This seems too simple. 
Verizon checks / verifies a connected device's TTL setting to determine if a hotspot is being used.
Window's default TTL IS 120. Changing to 60 seems to work.

Also try VPN to see if makes a difference
netsh int ipv4 set glob defaultcurhoplimit=65
netsh int ipv6 set glob defaultcurhoplimit=65
(60 didn't work for me this time. Trying 65 because 64 is phone so 65-1=64.)



netsh int ipv4 set glob defaultcurhoplimit=120

open a command prompt as admin
paste the 65 string for Verizon Hotspot
Paste the 120 to restore default

Test the setting 

ping -4 localhost



Curl, Wget, Winget & Powershell Install or Download Commands

After the mess I made in previous posts this summary might be useful.     Thanks PatchMyPC, the great and powerful program downloader and up...