Talk:Time to live
From Wikipedia, the free encyclopedia
This article (or an earlier version of it) contains material from FOLDOC, used with permission.
This is a ridiculously dense and inaccessible encyclopedia article. Don't rely so heavily on jargon and at least hyperlink those terms you will not define. —Preceding unsigned comment added by 24.250.140.74 (talk) 05:24, 7 March 2008 (UTC)
a "stub resolver"... this article is somewhat helpfull, but i have no idea what a stub resolver is, so it should be either explained further here or a hyerlink to some other article.
also, it is well known that routers reduce the TTL by on. However, do hubs, switches, bridges, and more importantly repeaters have any effect on the TTL? —Preceding unsigned comment added by 74.130.106.12 (talk) 00:49, 18 January 2008 (UTC)
[edit] Removed Table
I've removed the table in the "Time to live of IP datagrams" section for the following reasons:
- The TTL field in the IP header is never used in this way. It could never be used in this way, because network topology is a very uncertain factor, and varying all the time. The TTL field is only there to keep stray data packets from surviving.
- The hop counts in the table are way to high, even the remotest outskirts of the internet can be reached in 30 or 35 hops.
Modern operating systems set the initial TTL field to a fixed value.
I've pasted the text I removed below. Jaho 21:53, 17 March 2007 (UTC)
The arbitrary values below represent how long the packet should live with respect to the given TTL value. The numbers are a rough estimate and are dependent on the number of routers in your network.
- 0 is restricted to the same host
- 1 is restricted to the same subnet
- 32 is restricted to the same site
- 64 is restricted to the same region
- 128 is restricted to the same continent
- 255 is unrestricted
