I could have this wrong- but doesn’t the device relying to the ping send back it’s default TTL which varies from OS/mfg. So if this device has a default TTL of 255 and there are no hops between the pinging device and the responding device (otherwise TTL would be less than 255) then why the huge jump down to 64 which is coincidentally another common default TTL value? If there was some route flapping / loop or whatever why exactly 191 extra hops?
I thought maybe there was an IP conflict and I was getting replies from the different devices, but ARP tables are only showing one device on that IP. Or of course I could be completely misunderstanding the whole TTL thing. `S From: Af [mailto:[email protected]] On Behalf Of TJ Trout Sent: Wednesday, November 4, 2015 22:07 To: [email protected] Subject: Re: [AFMUG] TTL flapping link/router somewhere down the line On Wed, Nov 4, 2015 at 10:02 PM, Scott Vander Dussen <[email protected]<mailto:[email protected]>> wrote: Why would the TTL change during a ping sequence? Reply from 10.10.100.5<http://10.10.100.5>: bytes=56 Sequence=1 ttl=64 time=5 ms Reply from 10.10.100.5<http://10.10.100.5>: bytes=56 Sequence=2 ttl=255 time=11 ms Reply from 10.10.100.5<http://10.10.100.5>: bytes=56 Sequence=3 ttl=64 time=3 ms Reply from 10.10.100.5<http://10.10.100.5>: bytes=56 Sequence=4 ttl=64 time=2 ms Reply from 10.10.100.5<http://10.10.100.5>: bytes=56 Sequence=5 ttl=64 time=2 ms
