Network Connectivity 🖧🖇️: Understanding the TCP/IP Language 💻↔️💻

Understanding the Model That Moves Data Across the Internet 💻🌐🔁

In the previous article, we explored the key networking devices—such as routers, switches, and access points—and the basic rules (protocols) that enable devices to communicate across a network. Those concepts set the stage for understanding how TCP/IP actually works behind the scenes. 👉 Devices & Rules Behind Communication

Every computer protocol created over the years has one common purpose: ➡️ to ensure successful communication between two devices. But communication requires structure. In the 1970s, theoretical networking models were introduced to bring order to these tasks.

One of the most important among them was created by the U.S. Department of Defense (DoD) — and it became the foundation for modern networking.

The DoD Model — The Foundation of TCP/IP 🧱 🪖

TCP/IP (Transmission Control Protocol / Internet Protocol) is the main protocol suite used on the Internet today. Although it is named after its two most famous protocols (TCP and IP), the suite actually contains dozens of protocols working together. TCP/IP is structured using the four layers of the DoD model:

• Process / Application Layer
• Host-to-Host Layer
• Internet Layer
• Network Access Layer

You can think of TCP/IP like a puzzle—you need one piece from each layer for communication to work. Most TCP/IP protocols sit in the Process/Application layer, because that’s where everyday software communicates.

The Four Layers Explained 📚

Process / Application Layer

This is where the apps you use every day live — websites, email software, file transfer tools, etc. Some common examples:

• HTTP — HyperText Transfer Protocol. Used for browsing websites.
• HTTPS — HyperText Transfer Protocol Secure. Secure version of HTTP; encrypts data so your passwords and card numbers stay safe.
• FTP — File Transfer Protocol. Used for downloading/uploading files.
  • Example: When a website sends you to a link starting with ftp:// to download drivers or software.
• POP3 — Post Office Protocol version 3. Used to receive email (downloads emails to your device).
• IMAP — Internet Message Access Protocol. Also used to receive email, but keeps mail synced across devices (Gmail, Outlook app, phone, etc.).
• SMTP — Simple Mail Transfer Protocol. Used to send email.

Real-World Example 🔍

• When you check Gmail on your phone → it uses IMAP.
• When you send an email → your email app uses SMTP.
• When you open amazon.com → the browser uses HTTPS behind the scenes.

Host-to-Host Layer

This layer has only two protocols:

• TCP — Transmission Control Protocol. Reliable, connection-oriented. Ensures all data is delivered correctly. Example: Watching Netflix, transferring money online, sending an email.
• UDP — User Datagram Protocol. Fast but not guaranteed. Example: Zoom calls, online gaming, live sports streaming — speed matters more than perfection.

Most applications use one of these two depending on the task.

Internet Layer

The most important protocol here:

• IP — Internet Protocol. The backbone of everything. It defines how devices address and route information.

Other helpers:

• ICMP — Internet Control Message Protocol. Used for diagnostics. Example: When you use ping, you’re actually using ICMP.
• ARP — Address Resolution Protocol. Helps match IP addresses to MAC addresses inside a local network.

Network Access Layer

This layer does not have specific protocols. Instead, it describes how your device physically accesses the network. Examples include:

• Ethernet
• Wi-Fi
• Cellular data
• Fiber
• DSL

This is the “cables and signals” part of networking.

Basic Networking Services & Protocols 🌟 📜

If you have used the internet even once, you have already used many of these protocols — without even noticing. Here’s how:

HTTPS — Secure Web Browsing 🔒

Websites using HTTPS have addresses starting with: https://

Modern browsers hide this for simplicity, but it’s still there. HTTP, the older version, did not encrypt data, so HTTPS replaced it for safety.

Real-World Example. When you enter your password or credit card on Amazon, HTTPS encrypts it during transmission so attackers cannot see it.

FTP — Downloading Files 📥

Some websites redirect you to a download server that starts with: ftp://

That’s because FTP is explicitly designed for transferring files.

• You might install an FTP client (like FileZilla).
• The software uses the FTP protocol to communicate with FTP servers.

Email Protocols — How Email Actually Works 📧 @

There are three major players:

• POP3 – Receives email (downloads it). Older email apps use POP3 to download messages onto the device.
• IMAP – Receives email (keeps everything synced). Gmail, Outlook, iCloud, and most modern providers use IMAP.
• SMTP – Sends email. Any email you send uses SMTP behind the scenes.

Example. Your email app might say:

• Incoming mail server: imap.gmail.com
• Outgoing mail server: smtp.gmail.com

These are literally the protocols being used.

Simple Way to Understand This ❀

Most basic network services use a protocol with the same name:

• “FTP software” → uses FTP protocol
• “POP3 mail server” → uses POP3 protocol
• “SMTP server” → uses SMTP protocol

The service name equals the protocol name.

Understanding IP Addressing — How Devices Get Their Identity on a Network 🏷️💻

To communicate on a TCP/IP network, every device needs its own unique address, called an IP address. Any device with an IP address is called a host. This includes:

• desktops
• laptops
• smartphones
• printers
• servers
• routers

➡️ If it has an IP address, it’s a host.

📌 Note: When People Say “IP Address,” They Usually Mean IPv4. Unless someone specifically says IPv6, always assume they are talking about IPv4.

What Is an IP Address? 📬

An IP address is:

• a 32-bit hierarchical address
• used to identify a device on a network uniquely
• usually written in dotted decimal format, such as: 192.168.10.55

Each number (192, 168, 10, 55) is:

• 8 bits
• 1 byte
• also called an octet

Here is the same address written in binary:

The Binary Version of 192.168.10.55

• 192 → 11000000
• 168 → 10101000
• 10 → 00001010
• 55 → 00110111

So the full binary IP address is: 11000000.10101000.00001010.00110111

As you can see, dotted decimal is much easier for humans to read and write.

Why IP Addresses Are “Hierarchical”

IP addresses are not flat—they have structure. This structure allows:

• Organizing networks.
• grouping devices.
• Routing traffic across different networks (including the internet)

A Simple Analogy: Your Street Address 🏡

Here’s a random example address: 1451 Random example Road, Apt 3B, Charlotte, NC 91201, USA

The postal system uses a hierarchy:

• USA → narrows down the country
• North Carolina → narrows down the state
• Charlotte → city
• Random example Road → street
• 1451, Apt 3B → exact destination

If addresses were “flat” (e.g., every house in the country was just numbered randomly), the postal service would break down. There would be no logical grouping, and finding anything would be nearly impossible.

IP addressing works the same way 🔄

The first part of the IP address identifies the network, and the second part identifies the specific host within that network.

Without this structure:

• Routers couldn’t forward packets
• The internet couldn’t scale
• Communication across millions of networks would be chaotic

Two Parts of Every IP Address ☯️🌓

Each IP address contains:

• Network ID → identifies the network
• Host ID → identifies the device on that network

Example: For the IP 192.168.10.55 with subnet mask 255.255.255.0:

• Network ID: 192.168.10
• Host ID: 55

The Network ID always comes first, but the number of bits used for Network vs Host can vary, depending on the subnet mask.

Understanding Network ID vs Host ID 📝

Why is this confusing? Because the split between Network and Host is not fixed. It depends on the subnet mask, not just the IP address.

Let’s break it down: Think of the IP Address as a Full Phone Number

For example: 📞 +1 (700) 555-1234

Breakdown:

• +1 → Country
• 700 → Area code
• 555 → Exchange
• 1234 → Line number (unique phone)

In IP addressing:

• Network ID = area code + exchange (group)
• Host ID = line number (unique device)
• The subnet mask tells the computer where to split the number.

What Is a Subnet Mask? 🧮

A subnet mask looks like an IP address: 255.255.255.0

• Each 255 means all bits are 1 → this portion belongs to the Network ID.
• Binary of 255: 11111111

So:

Subnet Mask	Meaning
255	All 8 bits belong to Network ID
0	All 8 bits belong to Host ID

Example: 192.168.10.55 with Subnet Mask 255.255.255.0 📘

Subnet mask:

• 255 → Network
• 255 → Network
• 255 → Network
• 0 → Host

So:

• Network portion: 192.168.10
• Host portion: 55

This means:

• All devices on the 192.168.10.x network belongs together
• Each device must have a unique host ID (1–254)

Important Rules for IP Addressing 📏

• ✔ All host addresses on a network must be unique
• ✔ All network addresses must also be unique in a routed environment
• ✔ The Network ID cannot be all 0s
• ✔ The Host ID cannot be all 0s (“this network”)
• ✔ The Host ID cannot be all 1s (“broadcast”)
• ✔ The broadcast address means: send this to every device on the network

How Computers Use IP Addresses to Communicate 📡

Case 1: Sending to a device on the same network 🟰

If Computer A wants to message Computer B on 192.168.10.x, and both have the same Network ID, it simply sends the message directly on the wire or Wi-Fi. No router needed.

Case 2: Sending to a device on a different network 🚪

If Computer A wants to reach

• a device on 192.168.20.x,
• or anything on the internet

It sees the Network ID is different, so it sends the packet to the Default gateway (your router)

Your router is the door from your local network to the outside world.

Summary ⭐

• IP addresses uniquely identify devices
• They have a network part and a host part
• The subnet mask decides where the split occurs
• Computers use this split to determine whether to send data:
  • directly to another device, or
  • to the router (default gateway)

Understanding TCP/IP Ports — How Computers Pick the Right Service 🛎️✅

Knowing the correct IP address helps a device identify which host it needs to communicate with. But that’s only half of the story.

To communicate with the correct application or service on that host, TCP/IP needs something more: Ports (or port numbers)

A port is an additional identifier that tells the operating system which application the incoming data belongs to.

Ports = The “Channels” of Networking ⚓

A device uses:

• The IP address to find the correct host
• The port number to find the correct service or application inside that host

Simple Analogy: Cable or Satellite TV 📺

Think of your IP address as your home address. The cable company needs your home address to send TV signals to you.

But inside your home, which channel do you want to watch?

• If you want National Geographic, you might tune to Channel 200.
• If you want sports, you tune to another channel.
• If you want news, yet another.

These channels = ports.

Real Networking Example

If a computer wants to ask something through HTTPS, it must talk to: Port 443, because that is the port reserved for secure web communication.

If it tried to use port 80, the server would treat it as regular HTTP instead.

What Is a Socket? 🎛️

TCP/IP applications combine:

• IP address
• Port number

This combination is called a socket. – Example socket: 192.168.10.55:443

This means: “Talk to the device at 192.168.10.55 on port 443.”

How Many Ports Are There? 🔢

There are 65,536 ports, numbered: 0 — 65,535. They fall into three categories:

• Well-Known Ports (0–1023). Assigned to commonly used services. Examples:
  • 80 – HTTP
  • 443 – HTTPS
  • 25 – SMTP

• Registered Ports (1024–49151). Used by vendors or software developers for their applications.

• Dynamic / Private Ports (49152–65535). Available for temporary or custom use

Common TCP/IP Ports 📘

Service	Protocol	Port Number
Web browsing (not secure)	HTTP	80
Secure web browsing	HTTPS	443
File transfer	FTP	21
Email (sending)	SMTP	25
Email (receiving – POP3)	POP3	110
Email (receiving – IMAP4)	IMAP4	143

This table helps beginners clearly connect each service to its port.

Quick Notes to Remember

These three terms often get mixed up, so here’s a simple explanation:

IP Address 📃

• Logical address
• Can be changed
• Identifies a device on the network

MAC Address ⌨

• Physical address burned into the network card
• Cannot be changed
• Identifies the hardware itself

Ports ⚓

• Like TV channels
• Identify specific services on a device

Together, these three help computers know:

• which device to talk to
• Which hardware card to send through
• which application/service should receive the data

A Quick Introduction to IPv6 📢

IPv4 (Internet Protocol version 4) was developed in 1973, long before the modern Internet even existed. Despite being over 50 years old, it still remains the most widely used addressing system today. But as the world changed and billions of devices went online, IPv4 began showing its age. Two major issues forced the world to look for a new version:

• We ran out of IPv4 addresses
• IPv4 configuration can be difficult and limiting

Let’s break this down in a way that finally makes sense—even for someone completely new to networking.

Why Did We Run Out of IPv4 Addresses ❗ ? IPv4 uses a 32-bit address, which means the maximum number of addresses is: 2³² = 4,294,967,296 (about 4.3 billion)

At first, this seems like an impossibly large number. How could the world ever use 4.3 billion addresses? But here’s the catch:

Not all 4.3 billion IPv4 addresses can be used. 🛑

A large portion of the IPv4 address space is reserved, meaning it cannot be assigned to devices on the public internet. Think of it like a house with 10 rooms:

• 3 rooms are permanently locked
• 2 rooms are for storage only
• 1 must remain empty
• 1 is only for guests

Suddenly, you have only three usable rooms. IPv4 works the same way.

IPv4 Blocks That Cannot Be Used Publicly 🌍

Large portions of IPv4 are reserved for internal, special, or experimental use.

Private network ranges (used in homes and offices) 🔐

These addresses NEVER go onto the internet:

• 10.0.0.0 – 10.255.255.255
• 172.16.0.0 – 172.31.255.255
• 192.168.0.0 – 192.168.255.255

Every home in the world uses 192.168.x.x behind their router. These DO NOT count toward the public pool.

Loopback & testing ꩜

• 127.0.0.0 – 127.255.255.255

This block is used for internal testing (like pinging 127.0.0.1).

Multicast 👥👥

• 224.0.0.0 – 239.255.255.255

Used for group traffic—not public hosts.

Experimental ranges 🧪

• 240.0.0.0 – 255.255.255.254

Reserved for future use, not assigned to devices.

Large allocations from the early days 📑

In the 1980s and 1990s, big organizations received enormous IPv4 blocks:

• universities
• government agencies.
• tech giants in the early internet years
• telecom companies

Some received millions of addresses each. These blocks are still in use and cannot simply be reclaimed.

So, How Many IPv4 Addresses Were Actually Usable? 🔢

Even though 4.3 billion addresses exist, after removing all the reserved blocks, only ~250 million IPv4 addresses were available for worldwide public use.

250 million may sound like a lot, until you realize how many devices exist today.

The World Exploded With Devices 💥

These 250 million usable addresses had to be shared among:

• computers
• smartphones
• tablets
• smart TVs
• printers
• routers
• cars
• security cameras
• smart bulbs
• Alexa and Google Home devices
• gaming consoles
• data centers
• cloud servers
• entire companies
• entire countries

Today, the world has 25+ billion connected devices—and billions more coming every year. IPv4 could not keep up.

Why IPv4 Didn’t Expect This Growth 🚀📈

When IPv4 was created:

• There was no World Wide Web
• no mobile phones
• no smart devices
• no home Wi-Fi
• No cloud computing
• Only universities and government labs were online

No one imagined a world where:

• Every person owns 3–10 internet-connected devices
• Every home has a Wi-Fi router
• Every car, camera, TV, watch, speaker, appliance, and even doorbell needs an IP address

IPv4 was never designed for the modern world.

How Did the Internet Survive So Long Then?

Two major “hacks” saved IPv4: 🛠️

• NAT (Network Address Translation)

Your home likely has one public IP, but inside you have:

• phones
• laptops
• smart TVs
• tablets
• IoT devices

NAT allows all of them to share one public address.

• Private IP ranges. Private ranges like 192.168.x.x let billions of devices coexist internally.

Without NAT and private IPs, IPv4 would have collapsed before 2005

Enter IPv6 — The Long-Term Solution 🌟🚪

To fix IPv4’s limitations, the industry created IPv6, a new version of TCP/IP. Unlike IPv4’s 32-bit addresses, IPv6 uses 128-bit addresses.

So how many addresses is that? 3.4 × 10³⁸ addresses. That’s 340 undecillion.

To put this in perspective:

• enough to give billions of IP addresses to every human
• enough to give hundreds of IPs to every grain of sand on Earth
• enough to support future technology for centuries

IPv6 will never run out, even if every device and object becomes internet-connected.

IPv6 Comes With Other Benefits ✨ 🎁

IPv6 also includes many features that were optional in IPv4:

• automatic configuration (plug-and-play)
• more efficient routing
• better performance for modern networks
• cleaner address hierarchy
• security improvements

Even though IPv6 addresses look long and intimidating, the way they work under the hood is actually simpler and often easier to manage than IPv4.

IPv6 Works Together With IPv4 🔗

One of the biggest concerns about introducing a new protocol was compatibility. ➡️ IPv6 is backward compatible.

It can run:

• on the same computer
• on the same network
• at the same time as IPv4

This means:

• You don’t need to remove IPv4
• You don’t need to rebuild your network
• You don’t need to change all devices at once
• Both protocols coexist until full migration is complete.

Quick Summary ⭐📄

• IPv4 was created in 1973 and uses 32-bit addresses
• Although it has 4.3 billion possible addresses, most are reserved
• Only ~250 million public addresses were usable
• The modern world has billions of devices → IPv4 ran out
• IPv6 uses 128 bits, offering 3.4 × 10³⁸ addresses
• IPv6 includes built-in improvements and easier configuration
• IPv4 and IPv6 can run together during migration

DHCP & DNS — Two Critical TCP/IP Services You Must Know ‼️

Two of the most important services in TCP/IP networking are:

• DHCP — Dynamic Host Configuration Protocol
• DNS — Domain Name System

Both services usually run on a server, though DHCP is also commonly built into home routers. Both provide essential functionality that makes modern networking easy and user-friendly.

Let’s break them down with simple examples.

DHCP — Dynamic Host Configuration Protocol 🚀

DHCP’s job is simple but powerful: It automatically gives network configuration to devices.

Whenever a computer or phone joins a network, it needs important information:

• IP address
• Subnet mask
• Default gateway
• DNS server address

Instead of entering all these settings manually, DHCP gives them automatically.

Real-World Example: Moving Into a New Apartment 🏠

Imagine moving into a fully furnished apartment where:

• The furniture is already arranged
• The water and electricity are already connected
• The Wi-Fi password is already provided
• Everything is ready the moment you enter

This is DHCP. The moment your device joins the network:

• It automatically receives an IP address
• It knows where the router is
• It knows which DNS server to contact
• It’s instantly able to communicate

No manual setup. No typing. No hassle.

Without DHCP: Static IP Addressing 📌

If DHCP didn’t exist, an administrator would have to configure manually:

• the IP address
• subnet mask
• default gateway
• DNS server

for every single device. Imagine manually setting IP settings for:

• 200 office PCs
• 75 printers
• 80 phones
• laptops that employees bring in
• guest devices
• IoT devices

That would be painful and prone to mistakes. DHCP solves this by making IP addressing automatic and dynamic.

DNS — Domain Name System 💱

DNS has one significant job: DNS converts hostnames (like google.com) into IP addresses.

Computers understand IP addresses, but humans prefer names.

Real-World Example: Your Phone’s Contact List ☎️📒

You don’t memorize people’s phone numbers anymore. Instead, you tap “Mom”, “John”, or “Doctor ABC.” Your phone looks up the saved number and calls it.

DNS works the same way.

• You type google.com
• Your computer asks DNS: “What is the IP address of google.com?”
• DNS replies with something like 142.250.191.14
• Your computer then uses that IP to connect to Google’s servers

Without DNS, you would have to memorize IP addresses for:

• Google
• YouTube
• Facebook
• Amazon
• Netflix
• ChatGPT
• Every website you ever visit

Imagine typing: 142.250.191.14, instead of google.com. No one would browse the internet!

DNS Behind the Scenes 🎬 🌐

When you type a website name in your browser:

• You enter https://google.com
• Your computer asks your DNS server: “Who is google.com?”
• DNS replies with an IP address (for example, 142.250.191.14)
• Your computer uses that IP to reach Google
• The webpage loads

This entire process happens in milliseconds.

DNS on Internal Networks (Intranet) 🏢

DNS is not just for the internet. Inside a company network (an intranet), DNS might help you find:

• liz-printer01.company.local
• Joe-fileserver
• hr-portal.company.local

The process is identical: You type a name → DNS gives the IP → Your computer connects.

From the Client Perspective 🧑‍💻

All your device needs is one thing: The address of a valid DNS server.

Once DNS is configured (and DHCP usually provides that automatically), your device can resolve:

• websites
• internal servers
• printers
• apps
• cloud services

DNS quietly powers almost every action on your network.

Summary — DHCP vs DNS – Basics ⭐

Service	Full Form	What It Does	Real-World Analogy
DHCP	Dynamic Host Configuration Protocol	Automatically gives devices IP settings	Moving into a fully set-up apartment
DNS	Domain Name System	Converts names (google.com) into IP addresses	Contact list converting names into phone numbers

Together, DHCP and DNS make networking:

• automatic
• simple
• user-friendly
• scalable

Without them, every device would need manual configuration, and the internet would be impossible for humans to use.

A Real-World Scenario: How Data Travels From Point A to Point B on a Network 🚀

Let’s imagine something extremely common: A laptop user connected to the internet just clicked Send on an email to a friend.

Simple action for us. But under the hood? A lot happens.

Let’s walk through the journey — step by step — in a way a beginner can truly understand.

Step 1: Email Client Knows Where to Send the Message

Based on the software you use (Outlook, Apple Mail, Thunderbird, Gmail app), your laptop already knows the name of the email server it needs to send your outgoing mail to. For Gmail, the outgoing mail server is: smtp.gmail.com

But your computer cannot work with names. It needs an IP address

Step 2: Laptop Contacts DNS to Get the IP Address

Your laptop looks at its TCP/IP settings (usually provided automatically by DHCP) to find the DNS server address.

• It then asks the DNS server: “What is the IP address of smtp.gmail.com?”
• The DNS server replies with something like: 142.250.153.109
• Now, your laptop knows precisely where to send your email.

Step 3: Is the Destination on the Same Network?

Before sending the packet, your laptop must decide whether the email server is:

• on the same network, OR
• on a different network somewhere on the internet

To do this, your laptop:

• Looks at its own IP address
• Looks at its subnet mask
• Calculates its network address
• Then calculates the server’s network address using the same mask

• If both network addresses match → The destination is local. Send directly.
• If they do NOT match → Send the packet to the default gateway (your router). This is the door from your home or office to the rest of the internet.

For Gmail, the server is definitely NOT on your local network. So the laptop sends the packet to your router.

Step 4: The Email Message Is Broken Into Packets

Your message does not travel as one big piece. Instead, TCP/IP breaks it into small, manageable chunks called packets.

Each packet contains:

• Packet Header
• Source IP address
• Destination IP address
• Protocol used (TCP/UDP)
• Other control information

Packet Data

• A portion of the message you’re sending

Each packet is numbered so the receiving server can put them back in order.

Step 5: Packet Travels Router to Router Across the Internet

Your router receives the packet, checks the destination IP address, and forwards it to the next router. From there, the packet:

• hops from router to router
• across ISPs
• across backbone networks
• across data centers
• until it reaches Google’s mail servers

This is called routing, and each router in this chain is a hop.

Your packet may pass through:

• local ISP routers
• regional routers
• country-level internet exchange points
• Google’s own infrastructure

It’s incredible how much coordination happens behind the scenes in a matter of milliseconds.

Step 6: Mail Server Receives and Reassembles Packets

Once all the packets arrive at the mail server:

• It verifies the packet numbers
• Reassembles them into the original email
• Stores the message
• Sends it to your friend’s mailbox

This entire process happens faster than a blink.

Bonus Level: Packets Are Broken Down Even Further

Technically:

• Packets are broken into frames
• Frames are broken into bits
• Bits travel electrically (copper), through light pulses (fiber), or radio waves (Wi-Fi)

At the destination:

• Bits → reassembled into frames
• Frames → reassembled into packets
• Packets → reassembled into your email message

It’s honestly amazing that the internet works as smoothly as it does — every second of every day.

Want to See This in Action? Try Traceroute 👀

Every operating system has a command to show how many routers (hops) your packet passes through on its way to a destination.

• The command in Windows: tracert google.com
• The command in macOS / Linux: traceroute google.com

This will show you every hop from your device → your router → ISP → backbone → Google.

Wrapping Up 🧭

In this section, we explored how devices communicate on a network — from IP addresses and subnet masks to ports, IPv6, DHCP, DNS, and the real journey a packet takes across the internet.

What feels like a simple click or “Send” button actually triggers a complex series of steps involving name resolution, addressing, routing, and packet transmission. Yet it all happens so quickly and smoothly that we barely notice it.

The key takeaway? Modern networking works because many technologies operate together behind the scenes, each handling one small but essential part of the communication process.

This article is part of the Networking Concepts & Technologies series, where we break down how devices connect, communicate, and share information. For the complete overview of wired vs. wireless connections, essential networking devices, and how data travels across networks, 👉 Networking Concepts