IPv4 address structure in Computer Networks - Mini Project: Build & Apply

IPv4 Address Structure

📖 Scenario: You are learning about how devices on a network are identified using IPv4 addresses. Each IPv4 address is made up of four numbers separated by dots, and each number can range from 0 to 255.Understanding the structure of IPv4 addresses helps in configuring networks and troubleshooting connectivity issues.

🎯 Goal: Build a simple representation of an IPv4 address by creating its four parts, setting a subnet mask, combining them into a full address, and then adding a description to complete the understanding of the IPv4 address structure.

📋 What You'll Learn

Create four variables representing each part of the IPv4 address with exact values

Add a variable for the subnet mask

Combine the four parts into a single string representing the full IPv4 address

Add a description string explaining the IPv4 address

💡 Why This Matters

🌍 Real World

IPv4 addresses are used to identify devices on home and business networks, allowing them to communicate with each other and the internet.

💼 Career

Understanding IPv4 address structure is essential for network administrators, IT support, and cybersecurity professionals to configure and troubleshoot networks.

1

Create the four parts of the IPv4 address

Create four variables called part1, part2, part3, and part4 with the exact integer values 192, 168, 1, and 10 respectively.

Computer Networks

# Your code here

Hint

Each part of an IPv4 address is a number between 0 and 255. Use simple assignment statements.

2

Add the subnet mask variable

Add a variable called subnet_mask and set it to the string "255.255.255.0".

Computer Networks

part1 = 192
part2 = 168
part3 = 1
part4 = 10
# Your code here

Hint

The subnet mask is a string that shows which part of the IP address is the network part.

3

Combine the parts into a full IPv4 address string

Create a variable called full_ip that combines part1, part2, part3, and part4 into a single string separated by dots. Use an f-string for this.

Computer Networks

part1 = 192
part2 = 168
part3 = 1
part4 = 10
subnet_mask = "255.255.255.0"
# Your code here

Hint

Use an f-string to join the four parts with dots between them.

4

Add a description of the IPv4 address

Create a variable called description and set it to the string "This is a typical private IPv4 address with subnet mask 255.255.255.0.".

Computer Networks

part1 = 192
part2 = 168
part3 = 1
part4 = 10
subnet_mask = "255.255.255.0"
full_ip = f"{part1}.{part2}.{part3}.{part4}"
# Your code here

Hint

The description explains what the IP address and subnet mask represent.

Practice

1. What is the correct structure of an IPv4 address?

easy

A. Three numbers separated by dots, each from 0 to 255

B. Six numbers separated by colons, each from 0 to 65535

C. Four numbers separated by dots, each from 0 to 255

D. Four numbers separated by commas, each from 0 to 255

Solution

1. Step 1: Understand IPv4 format

   An IPv4 address consists of four parts called octets, separated by dots.

2. Step 2: Check the range of each octet

   Each octet ranges from 0 to 255, which fits in 8 bits.

3. Final Answer:

   Four numbers separated by dots, each from 0 to 255 -> Option C

4. Quick Check:

   IPv4 = 4 octets (0-255) [OK]

Hint: IPv4 always has 4 dot-separated numbers 0-255 [OK]

Common Mistakes:

• Confusing IPv4 with IPv6 format
• Using commas instead of dots
• Incorrect number of parts

2. Which of the following is a valid IPv4 address?

easy

A. 10.0.0.1

B. 192.168.1.256

C. 172.16.300.5

D. 255.255.255

Solution

1. Step 1: Check each octet's value

   Valid IPv4 octets must be between 0 and 255 inclusive.

2. Step 2: Validate each option

   A has all octets 0-255 and 4 parts (valid). B: 192.168.1.256 has 256 (invalid), C has 300 (invalid), D has only 3 parts (invalid). Only A is valid.

3. Final Answer:

   10.0.0.1 -> Option A

4. Quick Check:

   All octets 0-255 and 4 parts = valid IPv4 [OK]

Hint: Check each number is 0-255 and count 4 parts [OK]

Common Mistakes:

• Allowing numbers above 255
• Ignoring missing octets
• Confusing IPv4 with IPv6

3. What is the decimal value of the first octet in the IPv4 address 11000000.10101000.00000001.00000001?

medium

A. 255

B. 168

C. 1

D. 192

Solution

1. Step 1: Convert first octet from binary to decimal

   Binary 11000000 equals 128+64=192.

2. Step 2: Confirm decimal value

   The first octet decimal value is 192.

3. Final Answer:

   192 -> Option D

4. Quick Check:

   11000000 binary = 192 decimal [OK]

Hint: Convert binary octet to decimal by adding powers of 2 [OK]

Common Mistakes:

• Misreading binary digits
• Adding wrong powers of two
• Confusing octet positions

4. Identify the error in this IPv4 address: 256.100.50.25

medium

A. Too many octets

B. The first octet is out of range

C. Octets must be separated by commas

D. The last octet is missing

Solution

1. Step 1: Check each octet's value range

   IPv4 octets must be between 0 and 255 inclusive.

2. Step 2: Identify invalid octet

   The first octet is 256, which is outside the valid range.

3. Final Answer:

   The first octet is out of range -> Option B

4. Quick Check:

   Octet > 255 means invalid IPv4 [OK]

Hint: Octets must be 0-255; 256 is invalid [OK]

Common Mistakes:

• Thinking 256 is valid
• Confusing separators
• Ignoring octet count

5. You need to assign IP addresses to 300 devices in a network. Which of these IPv4 address ranges can you use without running out of addresses?

hard

A. 172.16.0.0 to 172.16.1.255

B. 10.0.0.0 to 10.0.0.127

C. 192.168.1.0 to 192.168.1.255

D. 192.168.0.0 to 192.168.0.100

Solution

1. Step 1: Calculate number of addresses in each range

   Range A: 256 addresses (0-255), B: 128 addresses, C: 512 addresses (two full /24 blocks), D: 101 addresses.

2. Step 2: Compare with required 300 devices

   Only range C has enough addresses (512) to cover 300 devices.

3. Final Answer:

   172.16.0.0 to 172.16.1.255 -> Option A

4. Quick Check:

   More than 300 addresses needed, only C fits [OK]

Hint: Count addresses: 256 per block; need ≥300 [OK]

Common Mistakes:

• Assuming 256 addresses cover 300 devices
• Ignoring address range size
• Confusing IP blocks