RE: [suse-security] INFORMATION
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
T=121 -> time to live for packet, in seconds
The ttl (time to live) is hops or routes, not seconds, so a ttl of 121 has that many hops before the packet is discarded. -James -----BEGIN PGP SIGNATURE----- Version: PGPfreeware 7.0.3 for non-commercial use http://www.pgp.com iQA/AwUBO3fOpPfthvTDkNu3EQI4yQCgqFcYNs/7IO4+hAfPSjPl8Ca0SCQAmwVj B2UzZVeeciQsxZPWqrp1hOfo =zjD/ -----END PGP SIGNATURE-----
On Monday 13 August 2001 05:57, James Wilkus wrote: [snip]
T=121 -> time to live for packet, in seconds
The ttl (time to live) is hops or routes, not seconds, so a ttl of 121 has that many hops before the packet is discarded.
-James [snip]
Hi James, Doh! I was thinking of DNS (where ttl is seconds in cache). from 'man ping': The TTL value of an IP packet represents the maximum number of IP routers that the packet can go through before being thrown away. In current practice you can expect each router in the Internet to decrement the TTL field by exactly one. John
On Monday 13 August 2001 05:57, James Wilkus wrote:
The ttl (time to live) is hops or routes, not seconds, so a ttl of 121 has that many hops before the packet is discarded.
Not necessarily. It could be 121 seconds - if one of the routers is waiting for fragments of a fragmented packet for more than one second, the TTL is being count down in seconds. In your case the router would discard the packet after 121 seconds and reply with a ICMP ttl-zero-during-reassembly. Bjoern
participants (3)
-
Bjoern Engels
-
James Wilkus
-
John Pinder