Courseiva
FC0-U71Chapter 11 of 18Objective 4.3

IP Addressing and Network Protocols

IP addressing and network protocols are the rules and identifiers that let computers, phones, and servers talk to each other across the internet or a local office network. Without them, devices would send data into a void with no way to reach the right destination or to make sense of the message. Understanding these concepts is essential for passing FC0-U71 because nearly every question about networking relies on knowing how devices find each other and how they agree on the format of the data they exchange.

12 min read
Intermediate
Updated Jul 23, 2026
Editorial oversight: Johnson Ajibi· Security Systems Architect · MSc IT Security · IEEE Senior Member

A simple way to picture IP Addressing and Network Protocols

The Apartment Building Mailbox Room Analogy

Your friend’s apartment building has 200 units, each with a unique number—like 4B or 12B. You want to mail them a birthday card. You address the envelope with their name, the building’s street address, and the specific flat number. This works because every flat has a unique address within the building, and the building itself has a unique address on the street.

Now, inside the building’s ground-floor mailbox room, there is a central noticeboard that lists which postal carrier services are allowed to deliver mail. Some parcels need to be signed for, which requires a specific service like Royal Mail’s “signed-for” option. When a parcel arrives without the right service label, the building manager might hold it or send it back. This is exactly how IP addressing and network protocols work together. The IP address is like the flat number—it uniquely identifies each device on a network so data can be sent to the right place. The network protocol is like the mail service rule—it defines how data is packaged, addressed, and checked for errors so the information actually arrives correctly. Without the addressing, data would have no destination; without the protocol, data would be unreadable or lost. Every device in a network needs both—just like every flat needs a number and every parcel needs a service rule.

How It Actually Works

At its simplest, IP addressing is like giving every device a unique postal address so that data knows where to go. Network protocols are the common languages those devices agree to speak so the data is understandable once it arrives.

Let us start with IP addresses. IP stands for Internet Protocol. An IP address is a numeric label assigned to each device connected to a computer network that uses the Internet Protocol for communication. There are two main versions you need to know for FC0-U71: IPv4 and IPv6.

IPv4 is the older, more widely used version. It is a 32-bit number, which means it can support about 4.3 billion unique addresses. You usually see it written as four decimal numbers separated by dots, like 192.168.1.10. Each of those four numbers ranges from 0 to 255. Because the world ran out of unique IPv4 addresses, IPv6 was created. IPv6 uses 128 bits, which gives a staggering number of addresses—roughly 340 undecillion. IPv6 addresses are written as eight groups of four hexadecimal digits, like 2001:0db8:85a3:0000:0000:8a2e:0370:7334.

A key concept for the exam is the subnet mask. A subnet mask is a 32-bit number that tells you which part of an IP address is the network portion (like a city) and which part is the host portion (like a street address within that city). For example, the subnet mask 255.255.255.0 means the first three numbers of the IP address identify the network, and the last number identifies a specific device. This is also written in CIDR (Classless Inter-Domain Routing) notation as something like /24—the number after the slash tells you how many bits are used for the network part.

The default gateway is the device—usually a router—that connects your local network to other networks, like the internet. When your computer wants to send data to a device that is not on your local subnet, it sends the data to the default gateway, which then forwards it.

Now let us talk about network protocols. A protocol is simply a set of rules that defines how data is formatted and transmitted over a network. The most fundamental protocol suite is TCP/IP (Transmission Control Protocol/Internet Protocol). This is actually a collection of protocols that work together to move data across networks.

TCP is a connection-oriented protocol. It ensures that data is delivered accurately and in the correct order. Think of TCP as a telephone call—you establish a connection, talk, and then hang up. If a message is lost, TCP retransmits it. UDP (User Datagram Protocol) is different. UDP is connectionless and does not guarantee delivery. It is like sending a postcard through the mail—you send it, but you do not know if it arrives. UDP is used for real-time applications like streaming video or online gaming, where speed matters more than perfect accuracy.

Beyond TCP and UDP, FC0-U71 tests several application-layer protocols: HTTPS (HTTP Secure) is the protocol used for secure web browsing. It encrypts the data between your browser and the web server so no one can read it in transit. FTP (File Transfer Protocol) is used to transfer files between computers on a network, often for uploading files to a web server. DNS (Domain Name System) is like the phonebook of the internet—it translates human-readable domain names like www.courseiva.com into IP addresses that computers use. DHCP (Dynamic Host Configuration Protocol) automatically assigns IP addresses to devices on a network. Without DHCP, you would have to manually configure every device. SMTP (Simple Mail Transfer Protocol) is used for sending outgoing email, while POP3 and IMAP are used for receiving email.

A port is a virtual point where network connections start and end. Each protocol uses a specific port number. For example, HTTPS uses port 443, HTTP uses port 80, DNS uses port 53, and DHCP uses ports 67 and 68. Knowing these port numbers is important for the exam because you may be asked to identify which protocol works with which port.

Finally, network protocols also handle error checking and flow control. For instance, ICMP (Internet Control Message Protocol) is used by devices to send error messages, like when a destination is unreachable—you have seen this when you “ping” a device. ARP (Address Resolution Protocol) maps IP addresses to physical MAC addresses (Media Access Control addresses) so data can travel over the local network hardware.

In summary, IP addressing gives each device a unique location, subnet masks divide networks, default gateways connect networks, and protocols provide the rules for reliable or fast communication. Every part works together to make the internet function.

This flowchart shows how a laptop obtains an IP address from a DHCP server, sends data through the default gateway to the internet, and uses DNS and HTTPS to reach a web server.

Walk-Through

1

Device connects to the network

When a laptop joins an office network, it sends a DHCP Discover message over the local broadcast. This is the first step because the device needs an IP address before it can communicate with anything else.

2

DHCP server responds with an IP address offer

The DHCP server picks an unused address from its pool (e.g., 192.168.1.12) and sends a DHCP Offer to the laptop. The offer includes the IP address, subnet mask, default gateway, and DNS server address. The device then requests the address and the server acknowledges it.

3

Device uses the subnet mask to determine the network boundary

The laptop looks at the subnet mask (e.g., 255.255.255.0) and decides which IP addresses are on its local subnet. If it wants to talk to 192.168.1.20, it knows that is on the same network and sends the data directly. If it wants to talk to 8.8.8.8, it knows that is on a different network.

4

Data is sent to the default gateway for off-subnet traffic

For any destination outside the local subnet, the laptop sends the data to the default gateway (the router). The router then uses its routing table to forward the data hop by hop across the internet until it reaches the target network.

5

The protocol stack encapsulates the data

The application creates data (like a web request). TCP or UDP adds a header with source and destination port numbers. IP adds a header with source and destination IP addresses. The network interface adds a header with source and destination MAC addresses. This layered encapsulation is how data is prepared for transmission.

6

Destination device receives and de-encapsulates the data

The receiving server strips each layer of header in reverse order. It checks the port number to know which application should receive the data (e.g., web server on port 443). The data is then passed up the protocol stack to the application. If TCP is used, the receiver sends an acknowledgement back to the sender.

What This Looks Like on the Job

An IT professional working for a mid-sized company called GreenLeaf Consulting is setting up a new office network for 50 employees. The office has computers, printers, a server room, and Wi-Fi for guests. The IT professional needs to design a network that makes everything communicate correctly while keeping sensitive data secure.

First, the IT professional designs the IP addressing scheme. The company’s internet service provider gives them a single public IP address for connecting to the internet. Inside the office, the IT professional uses private IP addresses—these are reserved ranges that cannot be routed on the internet, such as 192.168.1.0/24. They set up a DHCP server on the office router to automatically assign IP addresses from this private range to every employee’s laptop and phone. The DHCP server ensures no two devices get the same IP address.

Next, the IT professional configures the default gateway. They set the router’s internal IP address to 192.168.1.1. Every device that receives an IP address from DHCP also receives this default gateway address. When an employee wants to access a website, their computer sends the data to the router, which acts as the gateway and routes it to the internet using NAT (Network Address Translation). NAT converts the private IP address of the employee’s device into the single public IP address that the internet sees. This keeps the internal network invisible to the outside world.

Then, the IT professional sets up network protocols for specific services. They enable HTTPS on the company’s web server (port 443) so employees can securely access internal tools from home. They configure DNS to resolve internal server names like “fileserver.greenleaf.local” to the correct private IP address. They also set up SMTP for outgoing emails and IMAP for incoming emails on the email server.

For security, the IT professional uses a firewall that inspects traffic based on port numbers. They block inbound traffic on port 22 (SSH) from the internet to prevent unauthorised remote access. They allow traffic on port 443 for web access. They also use port forwarding to direct external requests on a specific port to a particular internal server.

When a help desk ticket comes in that an employee cannot connect to the internet, the IT professional follows a troubleshooting process:

Check if the device has an IP address by running “ipconfig” on Windows or “ifconfig” on Linux.

Pings the default gateway (192.168.1.1) to see if the local network is working.

if the ping fails, they check the DHCP server to ensure it has available addresses.

They check the DNS server by pinging a domain name like www.google.com—if that fails but pinging 8.8.8.8 (Google’s DNS) succeeds, then the DNS configuration is the problem.

They check the firewall logs to see if traffic was blocked.

The IT professional also monitors network usage to plan for growth. They notice that the office is running out of available IP addresses because more devices are connecting. They decide to change the subnet mask from 255.255.255.0 (/24) to 255.255.254.0 (/23) which doubles the number of available addresses. This requires reconfiguring the DHCP server and some static IP addresses on servers.

This real-world scenario shows that IP addressing and protocols are not just theory—they are the very tools an IT person uses every day to keep a business running.

How FC0-U71 Actually Tests This

The FC0-U71 exam tests your understanding of IP addressing and network protocols in a very specific way. You do not need to remember every detail—just the bell.

First, expect multiple-choice questions that ask you to match a protocol with its port number. For example, “Which port does HTTPS use?” The answer is 443. Similarly, FTP uses ports 20 and 21, DNS uses 53, DHCP uses 67 and 68, and SMTP uses 25. You need to know these by heart.

Second, the exam loves to ask about the difference between TCP and UDP. A classic question is: “Which protocol is connection-oriented and guarantees delivery?” The answer is TCP. A trap question might ask: “Which protocol is used for streaming video?” The answer is UDP because even though it loses some data, video can still play without waiting for resends.

Third, you will be tested on the IP address assignment methods: static and dynamic. Static IP addresses are manually configured and never change—used for servers. Dynamic IP addresses are assigned by DHCP and can change—used for client devices. A trap might suggest that static addresses are always better because they are more reliable. The truth is that static addresses are harder to manage and should only be used when necessary.

Fourth, you must understand private vs public IP addresses. The exam will ask which ranges are private. Memorise these three ranges: 10.0.0.0–10.255.255.255, 172.16.0.0–172.31.255.255, and 192.168.0.0–192.168.255.255. If a question shows an IP address in one of these ranges, it cannot be routed on the internet.

Fifth, you need to compare IPv4 and IPv6. The exam might ask about the length of IPv6 addresses (128 bits) or the format (hexadecimal with colons). A common trap is to give an IPv4 address in dotted-decimal and ask you to identify it as IPv6—it is not.

Sixth, understand the role of a subnet mask. You may see a question like “What subnet mask would give you a /24 network?” The answer is 255.255.255.0. You will not need to perform binary subnetting, but you must know that the subnet mask defines the boundary between the network and host parts of an IP address.

Key definitions to memorise for the exam:

IP address: a unique identifier for a device on a network.

Subnet mask: separates the network ID from the host ID.

Default gateway: the device that routes traffic from the local network to other networks.

DNS: translates domain names to IP addresses.

DHCP: automatically assigns IP addresses.

NAT: translates private IP addresses to a public IP address for internet access.

TCP: connection-oriented, reliable.

UDP: connectionless, fast.

Port: a virtual communication endpoint associated with a protocol.

The exam also likes to test loopback addresses. The IPv4 loopback address is 127.0.0.1, and it always refers to your own computer. The IPv6 loopback is ::1.

Finally, be aware of APIPA (Automatic Private IP Addressing). If a Windows computer tries to get an IP via DHCP but fails, it assigns itself an address in the 169.254.x.x range with a subnet mask of 255.255.0.0. This is a sign that the DHCP server is unreachable. The exam may present a scenario where a device has a 169.254.x.x address and ask you what is likely wrong.

In summary, practise matching protocols to ports, understanding the TCP vs UDP trade-off, and knowing the private IP ranges. These are the areas where most beginners lose marks.

Key Takeaways

An IP address uniquely identifies a device on a network, just like a postal address identifies a house.

IPv4 uses 32-bit addresses (e.g., 192.168.1.1) while IPv6 uses 128-bit addresses (e.g., 2001:db8::1).

TCP guarantees delivery of data in the correct order, whereas UDP trades reliability for speed and is used for streaming and gaming.

DHCP automatically assigns IP addresses to devices so you do not have to configure each one manually.

DNS translates human-readable domain names (like www.courseiva.com) into IP addresses that computers use to find each other.

Private IP addresses (10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16) are not routable on the internet and are used inside local networks.

Each network protocol uses a specific port number—HTTPS uses port 443, HTTP uses port 80, DNS uses port 53.

The default gateway is the device that sends traffic from your local network to other networks, typically a router.

Easy to Mix Up

These come up on the exam all the time. Here's how to tell them apart.

TCP

Connection-oriented: establishes a session before sending data

Guarantees delivery and orders packets correctly

Used for web browsing, email, file transfers

UDP

Connectionless: sends data without establishing a session

Does not guarantee delivery; packets may arrive out of order or be lost

Used for streaming video, online gaming, VoIP

IPv4

32-bit address space, about 4.3 billion addresses

Written in dotted-decimal format (e.g., 192.168.1.1)

Requires NAT to extend address usage

IPv6

128-bit address space, 340 undecillion addresses

Written in hexadecimal with colons (e.g., 2001:db8::1)

Built-in security (IPsec) and no need for NAT

Static IP Address

Manually configured and never changes

Requires manual entry on each device

Used for servers and devices that must always have the same address

Dynamic IP Address (DHCP)

Automatically assigned by a DHCP server

Can change over time (lease expires)

Used for client devices like laptops and phones

Private IP Address

Used within a local network only

Cannot be routed on the internet

Falls into reserved ranges: 10.x.x.x, 172.16.x.x–172.31.x.x, 192.168.x.x

Public IP Address

Unique on the internet

Assignable by an ISP

Used for servers that need to be accessed from outside the network

Watch Out for These

Mistake

An IP address is the same thing as a MAC address—they both identify a device on a network.

Correct

An IP address is a logical address that can change depending on the network you join; a MAC address is a physical, fixed address burned into the network interface card. They perform different functions: IP for routing across networks, MAC for local delivery.

Both are unique identifiers, but beginners often conflate them because they both 'identify' a device. The fact that the IP address can change while the MAC stays the same is a subtle distinction that gets overlooked.

Mistake

If a device has a 169.254.x.x address, it means the internet is down.

Correct

A 169.254.x.x address (APIPA) means the device could not reach a DHCP server to get a valid IP. The local network might still be operational internally, but the device cannot communicate beyond the local subnet until it gets a proper IP address.

People see 'no internet' and assume the internet connection itself is broken, not the IP configuration. They forget that the device can still talk to other devices on the same subnet.

Mistake

Using the same port number for two different protocols causes a collision and breaks the network.

Correct

Port numbers are only meaningful within a specific transport protocol. TCP port 80 and UDP port 80 are completely separate and can both be used simultaneously without conflict. It is the combination of transport protocol + port that is unique.

We talk about 'port 80' as if it is a singular thing, which makes it sound like a shared resource. The reality is that each transport protocol has its own set of ports, so TCP and UDP do not interfere.

Mistake

IPv6 is just IPv4 with more addresses and the same structure.

Correct

IPv6 is fundamentally different from IPv4. It uses 128-bit addresses in hexadecimal, does not require NAT because there are enough addresses, and eliminates broadcast traffic in favour of multicast. It also has built-in IPsec security, which was optional in IPv4.

The similar name 'IP' makes it seem like an upgrade rather than a complete redesign. Many beginners assume they can just learn IPv4 and add a few extra digits.

Mistake

A default gateway is always a router.

Correct

While a router is the most common default gateway in home and small office networks, any device that can forward packets between networks can act as a default gateway—including a computer with two network interfaces (a multihomed host) or a firewall appliance.

Routers are so associated with internet access that we forget the definition is just 'the next hop to another network.' That role can be fulfilled by any device with the appropriate configuration.

Do You Actually Know This?

Reveal each answer, then mark whether you got it right. Score 60%+ to unlock the next chapter.

Frequently Asked Questions

What is the difference between a public IP address and a private IP address?

A public IP address is unique on the internet and assigned by your ISP. A private IP address is used inside your home or office network and cannot be used directly on the internet. Private IPs fall into reserved ranges like 192.168.x.x.

Why do I need to know port numbers for the CompTIA Tech+ exam?

The exam asks matching questions that require you to know which protocol uses which port, such as HTTPS using port 443 or DNS using port 53. remembering these numbers is essential for passing the networking section.

What does it mean when my computer has an IP address starting with 169.254?

That is an Automatic Private IP Addressing (APIPA) address. It means your computer tried to get an IP from a DHCP server but failed, so it assigned itself a random address in the 169.254.x.x range. Usually, this points to a problem with the DHCP server or the network cable.

Is TCP always better than UDP?

No. TCP is reliable but slower, which makes it good for web pages and emails. UDP is faster but can lose data, which makes it better for video streaming, online gaming, and VoIP where a slight delay is worse than a lost packet.

What is a subnet mask and why do I care?

A subnet mask is a number that tells your device which part of the IP address is the network ID and which part is the host ID. It helps your computer decide whether to send data directly to another device on the same network or to the router first.

Can two devices have the same IP address on the same network?

No. Every device on the same network must have a unique IP address. If two devices share the same IP, you get an IP conflict, which causes connectivity issues and network errors for both devices.

Terms Worth Knowing

Keep going

You've finished IP Addressing and Network Protocols. Continue through the FC0-U71 study guide to build a complete picture of the exam.

Done with this chapter?