TTL shows 242 hops, settting is at 64

[hupptacular]

« SpeedGuide.net TCP Analyzer Results »
Tested on: 2018.11.30 18:51
IP address: 68.0.xxx.xxx
Client OS/browser: Windows 10 (Chrome 64.0.3282.140)

TCP options string: 020405b40103030e01010402
MSS: 1460
MTU: 1500
TCP Window: 262144 (not multiple of MSS)
RWIN Scaling: 14 bits (2^14=16384)
Unscaled RWIN : 16
Recommended RWINs: 64240, 128480, 256960, 513920, 1027840
BDP limit (200ms): 10486kbps (1311KBytes/s)
BDP limit (500ms): 4194kbps (524KBytes/s)
MTU Discovery: ON
TTL: 242
Timestamps: OFF
SACKs: ON
IP ToS: 00000000 (0)




---setting confirmed in regedit, 64 [decimal]

[Philip]

The TCP Analyzer simply reads what your TCP packets sent to our server advertise. Seems that something is overriding the regedit setting. Either way, it is not a huge issue, TTL only comes into play in the presence of packet loss (it would take a bit longer to consider the packet as "lost" and retransmit it).