Then if srvA has an application that somehow forwards the message to srvC, the following headers can be seen: mac-srvB -> mac-rtr3, ip-srvB -> ip-srvC, TTL=64 (arriving at rtr3) Mac-rtr2 -> mac-srvB, ip-srvA -> ip-srvB, TTL=62 (arriving at srvB) Mac-rtr1 -> mac-rtr2, ip-srvA -> ip-srvB, TTL=63 (arriving at rtr2) SrvA -> rtr1 -> rtr2 -> srvB -> rtr3 -> srvCĭifferent systems use different initial TTL values (mostly 64, 128 or 255), for now, assume they all use 64.Ī message from srvA to srvB will have the following headers: mac-srvA -> mac-rtr1, ip-srvA -> ip-srvB, TTL=64 (arriving at rtr1) (You can share traces by uploading the trace to and then paste the link to the trace here) Each of these routers will decrement the IP TTL, but each server will create a new IP packet, with a new TTL value. Between these application layer hops are routers to get the IP packet from one server to the other. I believe the hops you are drawing in your response to are hop at the application layer and not at the IP layer. Undeliverable datagrams to be discarded, and to bound the maximum Less than a second, the TTL must be thought of only as an upperīound on the time a datagram may exist. Seconds, but since every module that processes a datagram mustĭecrease the TTL by at least one even if it process the datagram in Zero, then the datagram must be destroyed. This field indicates the maximum time the datagram is allowed to The IP TTL is a time-to-live at the IP layer to prevent packet destined for an undeliverable address from looping through the network forever.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |