Mastering Network Fundamentals: OSI Model, IP Addressing, and Protocols Explained

1. Network Layer Division

The ISO introduced the OSI Reference Model in 1978, dividing network communication into seven layers: Physical, Data Link, Network, Transport, Session, Presentation, and Application. The fourth layer provides end‑to‑end transport services, while the top three layers serve user applications.

In addition to the standard OSI model, the TCP/IP suite is often represented as a four‑layer or five‑layer model, with a correspondence diagram illustrating the mapping between the two.

2. OSI Seven‑Layer Model

Using the OSI model as a reference, each layer has its own protocols and responsibilities. The physical layer handles the mechanical and electrical characteristics of the transmission medium. The data link layer ensures reliable delivery over the physical link, using frames, MAC addresses, and devices such as bridges and switches.

The network layer provides logical addressing and routing (e.g., IP, ICMP, ARP). The transport layer offers reliable (TCP) or best‑effort (UDP) transport, handling segmentation, flow control, and error recovery. The session, presentation, and application layers manage sessions, data formatting, encryption, and provide interfaces for applications.

3. IP Address

An IP address consists of a network part (including subnet) and a host part. Different address classes (A, B, C, D, E) define the size of the network and host portions. Special addresses include broadcast, network, loopback (127.0.0.1), and private ranges (10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16).

4. Subnet Mask and Network Segmentation

Subnet masks identify which bits of an IP address belong to the network and which belong to the host. They are 32‑bit binary numbers where a ‘1’ denotes a network bit and a ‘0’ denotes a host bit. Subnetting allows efficient use of address space by borrowing host bits for additional network identifiers.

Typical interview calculations include determining a subnet mask from the required number of subnets or hosts, converting the subnet count to binary, and setting the appropriate bits to ‘1’ in the mask.

5. ARP/RARP Protocol

ARP (Address Resolution Protocol) maps an IP address to a MAC address by broadcasting a request on the local network and receiving a reply. RARP (Reverse ARP) performs the opposite mapping, allowing a host that knows only its MAC address to discover its IP address via a RARP server.

6. Routing Selection Protocol

Common routing protocols include RIP, which uses hop count as its metric, and OSPF, which uses link‑state information such as bandwidth and delay to compute the shortest path.

7. TCP/IP Protocol

TCP provides reliable, connection‑oriented communication with three‑way handshake establishment and four‑way termination, flow control via sliding windows, and retransmission of lost segments. IP handles packet routing without guaranteeing delivery order or reliability.

8. UDP Protocol

UDP is a connection‑less, unreliable transport protocol that includes source and destination ports, length, and checksum fields. It is used by services such as DNS, TFTP, SNMP, and NFS where low latency is preferred over reliability.

9. DNS Protocol

Domain Name System translates human‑readable domain names into IP addresses, enabling users to access resources using friendly names instead of numeric addresses.

10. NAT Protocol

Network Address Translation converts private IP addresses to public ones, conserving address space and providing a layer of security by hiding internal network structure.

11. DHCP Protocol

Dynamic Host Configuration Protocol automatically assigns IP addresses and other network configuration parameters to hosts on a LAN using UDP.

12. HTTP Protocol

HyperText Transfer Protocol is the foundation of data communication on the World Wide Web. Common request methods include GET, POST, PUT, and DELETE, each with distinct semantics regarding safety and idempotence.

13. Example: Accessing www.baidu.com

When a user enters http://www.baidu.com in a browser, the client resolves the domain via DNS, establishes a TCP connection to the server’s IP address on port 80, sends an HTTP request, and receives the response, traversing the OSI layers from application down to physical and back.