IP Protocol: Addresses, Forwarding and TTL
The Internet Protocol moves datagrams between networks using addresses and forwarding rules. IP does not promise reliable delivery, ordering or application-level completion.
Updated · Editorial approach and simulation limits
IP addresses guide packets between networks
An IP packet carries source and destination addresses plus fields used for forwarding and interpretation. Routers examine the destination and their routing tables to choose a next hop. The destination address identifies an IP endpoint, not necessarily a specific process; transport-layer ports distinguish many application conversations.
The path is selected hop by hop and can change with routing policy or network conditions. A packet’s source address can be rewritten by NAT, and a middlebox can filter or encapsulate traffic. A trace at one interface shows that observation point, not every transformation along the route.
TTL, protocol and fragmentation fields
IPv4 TTL is reduced as a packet crosses routers to prevent indefinite forwarding loops. It is therefore a hop limit, not an elapsed-time clock. The Protocol field identifies the next header, such as TCP, UDP, ICMP or an encapsulation protocol.
IPv4 fragmentation can split a datagram when path constraints require it, although modern traffic often uses Path MTU Discovery to avoid fragmentation. If fragments are present, a capture tool may need to reassemble them before showing a transport header or application data.
IP is not the same as TCP or IPv6
IP provides best-effort datagram delivery. TCP adds an ordered byte stream and retransmission; UDP provides datagrams without those delivery guarantees. IPv6 is a separate IP version with a different header and extension-header model, not simply a larger IPv4 address field.
IPsec can protect selected IP traffic, while ICMP carries control messages about IP delivery. Protocol Explorer’s IP overview shows a simplified header; use the IPv4 or IPv6 standard that matches the packet you are analyzing.
Explore IP interactively
Follow the matching exchange packet by packet. The animation is a scripted teaching model with illustrative timing, not a capture of your network.
Specification and source
For exact protocol requirements, consult the primary document: RFC 791: Internet Protocol. This page summarizes selected behavior and is not a substitute for the specification.
Related protocol lessons
Browse all network protocols · Read packet headers from the network layer outward