Learn Computer Networking PNETLab - Networking Fundamentals & OSI vs TCP/IP Reference Models

#Introduction

Everything in this series stands on a single foundation: how data moves from one device to another. Before you create VLANs, configure OSPF, or deploy ACLs, you must first understand the role of each network layer. Episode 1 is the conceptual foundation of Learn Computer Networking PNETLab.

In this episode we discuss why computers need networks, the main components that make up a network, and then break down the two most widely used reference models: the seven-layer OSI and the four-layer TCP/IP. We close with the encapsulation and decapsulation process — the mechanism that explains how data is wrapped and unwrapped as it passes through each layer.

#Why Computers Need Networks

#Resource Sharing, Communication, and Data Transfer

Without a network, every computer is an isolated island. Networks enable three main things: resource sharing (sharing printers, file servers, or an internet connection), communication (email, chat, video calls), and data transfer (moving data between devices at scale). These three needs are the reasons a network is built in an office or at home.

#Main Network Components

Every network is made up of three groups of components:

• End Devices: devices that are the source and destination of data, such as PCs, laptops, servers, and printers.
• Intermediate Devices: devices that forward data between networks, such as switches, routers, and access points.
• Network Media: the physical medium over which data travels, such as UTP copper cable, fiber optic, and wireless waves.

You will always encounter these three when assembling topologies in PNETLab: PCs and VPCS are end devices, IOL switches and vIOS Routers are intermediate devices, while the links between nodes are the network media.

#Seven-Layer OSI Reference Model

#From Application Layer to Physical Layer

OSI (Open Systems Interconnection) divides the communication process into seven layers. Each layer only talks to the layers directly above and below it:

• Layer 7 Application: user application interface, for example HTTP and SMTP.
• Layer 6 Presentation: data format, encryption, and compression.
• Layer 5 Session: management of dialog sessions between applications.
• Layer 4 Transport: end-to-end data delivery using TCP or UDP.
• Layer 3 Network: logical addressing and packet routing.
• Layer 2 Data Link: frames, physical MAC addressing, and media access control.
• Layer 1 Physical: bits, electrical voltages, and the physical medium.

This order is easy to remember from the bottom up: Physical, Data Link, Network, Transport, Session, Presentation, Application. The reverse of this order will determine how the encapsulation we discuss later works.

#Four-Layer TCP/IP Reference Model

#Application, Transport, Internet, and Network Access

TCP/IP is the model actually used by the Internet. Its four layers summarize OSI: Application (merging OSI 7, 6, and 5), Transport (OSI 4), Internet (OSI 3), and Network Access (merging OSI 2 and 1).

The important difference between the two is not just the number of layers. OSI is more theoretical and breaks down roles in detail, while TCP/IP is practical and serves as the reference for real implementations. When you read show ip route in episode 9, it is the TCP/IP Internet layer you are observing.

#The Data Encapsulation and Decapsulation Process

#PDU: Data, Segment, Packet, Frame, Bits

As data travels from an application to the medium, each layer adds a header to the data. This process is called encapsulation, and the result of each layer has its own name called the Protocol Data Unit (PDU):

Data      ->  Layer 5-7  ->  Data / Message
Segment   ->  Layer 4    ->  TCP / UDP Header + Data
Packet    ->  Layer 3    ->  IP Header + Segment
Frame     ->  Layer 2    ->  Ethernet Header/Trailer + Packet
Bits      ->  Layer 1    ->  Signal on the physical medium

On the receiving side, the process is reversed: each layer reads its header and strips it off before passing the data up to the layer above. This is called decapsulation. When you capture a frame in Wireshark (episode 0), what you see is the result of complete encapsulation: the Ethernet header, the IP header, and the TCP header wrapping the original data.

#Building Your First Lab in PNETLab

To see encapsulation in action, assemble a simple topology in PNETLab: two PCs connected to a single switch. Here is the node definition in JSON:

{
  "name": "osi-demo",
  "nodes": {
    "1": { "name": "PC1", "template": "VPCS", "x": 50, "y": 100 },
    "2": { "name": "SW1", "template": "IOL-L2", "x": 250, "y": 100 },
    "3": { "name": "PC2", "template": "VPCS", "x": 450, "y": 100 }
  }
}

Once the topology is in place, open PC1's console and run ping 192.168.1.2 toward PC2. Wireshark will show an Ethernet frame containing an ICMP packet — real proof of Layer 2 and Layer 3 encapsulation within a single frame.

#Why Understanding These Models Matters

Understanding the reference models is not just about memorization. When you troubleshoot in episode 20, the top-down or bottom-up approach takes you through the layers one by one: if a website will not open, check Layers 3 and 4 first, then drop down to Layer 2. Classifying problems by layer is what makes troubleshooting systematic instead of guesswork.

#Closing

Key takeaways:

• Networks are built for resource sharing, communication, and data transfer.
• Network components: end devices, intermediate devices, and network media.
• OSI has seven layers; TCP/IP summarizes them into four layers.
• Encapsulation adds a header at every layer; decapsulation removes them.
• The PDU changes form: Data, Segment, Packet, Frame, then Bits.
• A small lab with two PCs and one switch can visualize real encapsulation.

In the next episode, episode 2, we move into the first hands-on practice: Cisco IOS introduction and basic configuration — the structure of Cisco CLI operation modes, naming devices with hostname, securing the console and privileged mode, configuring SSH access, and initial verification commands such as show ip interface brief. Make sure your PNETLab and Cisco Images are ready from episode 0.