IntroductionJust like every other protocol, IP has a place in the OSI model. Because it's such an important protocol and other protocols depend upon it, IP needs to be placed before them in the OSI model. That's why you will find it in Layer 3:
When a computer receives a packet from the network, the computer will first check the destination MAC address of the packet at the Datalink Layer (2). If it passes, it's then passed on to the Network layer.
At the Network layer, it will check the packet to see if the destination IP address matches the computer's IP address. (If the packet is a broadcast, it will pass the network layer anyway.)
From there, the packet is processed as required by the upper layers.
On the other hand, the computer may be generating a packet to send to the network. Then, as the packet travels down the OSI model and reaches the Network layer, the destination and source IP address of this packet are added in the IP header.
The IP headerNow we are going to analyze the Internet protocol header, so you can see the fields it has and where they are placed. In here you will find the destination and source IP address field which is essential to every packet using the protocol.
It's worth noting that the 9th field, which is the "Protocol" field, contains some important information that the computer uses to find out where it must pass the datagram
If you remember, TCP and UDP exist on Layer 4 of the OSI Model, which is the transport layer. When data arrives at a computer and the packet is processed by each layer, it needs to know whereabouts above to pass the data. This protocol field tells the computer to give the remaining data to either the TCP or UDP protocol, which is directly above it.
The destination IP address is another important field which contains the IP address of the destination machine.
The next section talks about the five different classes of IP address.
Click over to Firewall.cx for more articles like this one. You don't have to register or jump through any hoops. All you do is get the networking information you want. Copyright 2004 Firewall.cx.
This was first published in October 2004