Subnet a Small Office in Packet Tracer

Build a segmented office LAN with /26 subnets and VLANs in Cisco Packet Tracer.

Introduction

30 Second Summary

An office can look connected while its teams still need clear boundaries. Without those boundaries, one mistake can reach people or devices it was never meant to touch.

In this project, you will build a small-office network in Cisco Packet Tracer for six PCs across Admin, Staff, and Guest groups. The finished simulation uses IPv4 subnetting plus VLANs to control which PCs can exchange ping replies.

What You'll Build

Your finished office topology makes its boundaries visible through a ping test matrix of local successes versus cross-segment failures.

By the end of this project, you'll have:

A complete subnet plan you can use to explain how 192.168.0.0/24 becomes four non-overlapping /26 networks. It records every network address. It also records every usable host range. Each broadcast address is clearly marked.
A working office LAN where three department pairs return successful ping replies inside their assigned subnets.
A VLAN-backed test matrix that shows each department's switch ports in its own logical group. It proves local connectivity. It also proves cross-segment isolation.
Secret Mission: Use the unused fourth /26 to add an isolated IoT segment without changing the original three networks.

Are there any prerequisites?

You need a Windows computer with permission to install Cisco Packet Tracer. The project guides you through creating a free Cisco Networking Academy account.

Before We Start

Before any hands-on work begins, this is your moment to commit to the office network you are building. Defining why Admin, Staff, and Guest need separate segments gives every subnetting decision a clear purpose.

Set Up Cisco Packet Tracer

Subnet calculations are easier to trust when you can test them against a visible result. Cisco Packet Tracer gives you a safe simulator for testing addresses without buying networking hardware.

Official access matters because third-party installers can be outdated or unsafe. You will get the application through Cisco Networking Academy.

You will then install the Windows application. A blank Logical workspace confirms that your simulator is ready for the office network.

In this step, get ready to:

Create or sign in to a free Cisco Networking Academy account.
Download and install Cisco Packet Tracer from Cisco's official Resource Hub.
Sign in to Cisco Packet Tracer and reach a blank Logical workspace.

Why Use a Simulator?

A simulator lets you test each networking decision through device behavior. Mistakes become visible without risking physical equipment.

This project only needs switched connections and VLAN boundaries. Cisco Packet Tracer provides both at no cost.

Access Cisco Networking Academy

Cisco Networking Academy provides the official account and download path for Packet Tracer. Choose the account route that matches your current situation.

✔️ I already have an account

Visit the official Cisco Packet Tracer learning collection.
Sign in by following the page prompts.
Confirm that your Cisco Networking Academy account page loads.

ⓧ I need to create an account

Visit the official Cisco Packet Tracer learning collection.
Choose the account creation option on the page.
Complete the registration prompts.
Confirm that your new Cisco Networking Academy account page loads.

Return to Cisco's official Resource Hub.
Select the current Windows download.
Save the installer in your Downloads folder if your browser asks for a location.

Your browser downloads the official Windows installer from Cisco.

Stay With Cisco's Download

Use the Resource Hub as your source of truth for the current Windows installer. Avoid third-party installer mirrors.

Install Cisco Packet Tracer

The Windows installer guides you through the license and installation choices. Keeping the suggested folders makes the application easier to find later.

Press the Windows key to open the search bar.
Type File Explorer.
Press Enter.
Select Downloads in the left sidebar.
Double-click the Cisco Packet Tracer installer you downloaded.

What Choices Are Coming?

First, the installer asks you to accept the license agreement. It then asks where to install the application.

The remaining screens cover the Start Menu folder and optional shortcuts. A final review leads to installation.

Read the license agreement.
Select I accept the agreement.
Keep the suggested destination folder.
Keep the suggested Start Menu folder.
Review the optional shortcuts.
Select Install.
Keep the launch option selected when installation completes.
Select Finish to launch Cisco Packet Tracer.

The installer has done its job. You will see the Cisco Packet Tracer Login window.

Installer Does Not Open?

Confirm that you downloaded the Windows installer from Cisco's Resource Hub.
Reopen the installer from your Downloads folder.

Help me troubleshoot my Packet Tracer installation. You can also review Cisco's official installation instructions.

Sign In to Cisco Packet Tracer

Packet Tracer uses browser authentication to connect the application to your Cisco Networking Academy account. Successful authentication returns you to the simulator.

Select LOGIN in the Cisco Packet Tracer Login window.
Complete the browser authentication flow with your Cisco Networking Academy account.

Before you check the application, what workspace do you expect to see after authentication?

Return to Cisco Packet Tracer after browser authentication finishes.
Confirm that Logical is selected.
Check that the topology canvas contains no devices or links.

You will see a blank Logical topology workspace. This confirms that Cisco Packet Tracer is signed in and ready.

That setup is complete. Your simulator is ready for the small-office network.

Authentication Does Not Return?

Return to the browser window that opened during authentication.
Complete any remaining Cisco account prompts.
Switch back to Cisco Packet Tracer when the browser confirms authentication.

Help me troubleshoot Packet Tracer authentication. You can also visit Networking Academy Support and FAQs.

Cisco Packet Tracer is ready. Next up, you will build a two-PC network and prove that it can communicate.

Build Your First Working LAN

Your Cisco Packet Tracer workspace is ready. The office plan now needs a small network you can test.

You will build a two-PC LAN around one switch. A successful ping gives you a visible baseline before you deliberately introduce a subnetting mistake.

In this step, get ready to:

Build a two-PC topology around one 2960 switch.
Assign both PCs addresses in the same network.
Verify communication with a successful ping.

Place and cable the devices

A switch creates a shared Layer 2 path between connected devices. Your first topology uses this path to carry traffic between two PCs.

Select the switch category in the device selection area at the bottom-left.
Drag one 2960 switch into the Logical workspace.
Select the end-device category in the device selection area.
Drag two PC end devices into the workspace.

Packet Tracer labels the two end devices PC0 and PC1.

Select Copper Straight-Through in the connection controls at the bottom-left.
Connect PC0 FastEthernet0 to switch FastEthernet0/1.
Connect PC1 FastEthernet0 to switch FastEthernet0/2.
Wait for both switch links to turn green.

You should see one green link from each PC to the switch. The green indicators confirm that both physical connections are active.

Links not turning green?

Confirm that both links use Copper Straight-Through cables.
Reconnect PC0 FastEthernet0 to switch FastEthernet0/1.
Reconnect PC1 FastEthernet0 to switch FastEthernet0/2.

Help me diagnose links that are not turning green in my Packet Tracer topology.

Give both PCs addresses in one network

Two PCs communicate directly when their IPv4 addresses belong to the same network. The shared subnet mask tells each PC which addresses are local.

Select PC0 in the workspace.
Select the Desktop tab.
Select IP Configuration.
Enter 192.168.0.1 as the IPv4 address.
Enter 255.255.255.0 as the subnet mask.
Leave Default Gateway blank.

Why is the default gateway blank?

A default gateway sends traffic to destinations beyond a PC's local network. This topology has no router to perform that job.

Close the PC0 device window.
Select PC1 in the workspace.
Select the Desktop tab.
Select IP Configuration.
Enter 192.168.0.2 as the IPv4 address.
Enter 255.255.255.0 as the subnet mask.
Leave Default Gateway blank.

Both PCs now have unique addresses under the same subnet mask. They can test their connection without a router.

Address values not matching?

Compare the PC0 address with 192.168.0.1.
Compare the PC1 address with 192.168.0.2.
Confirm that both subnet masks show 255.255.255.0.
Clear any value from both Default Gateway fields.

Help me check the IPv4 settings on PC0 and PC1.

Prove the baseline works

A ping test sends ICMP echo requests to another address. Successful responses prove that PC0 can reach PC1 through the switch.

Close the PC1 device window.
Select PC0 in the workspace.
Select the Desktop tab.
Select Command Prompt.

Before you test the connection, do you expect PC1 to answer from the same network?

Test the connection from PC0 to PC1 by running this command:

ping 192.168.0.2

What does this command prove?

The ping command asks the destination PC to respond.
The address 192.168.0.2 identifies PC1 as the destination.
Successful responses prove that the addresses and switch links work together.

You should see successful Reply lines from 192.168.0.2. Those responses are your first proof that PC0 can reach PC1 through the switch.

Ping not fully successful?

Repeat the same command once if the first result is incomplete while address resolution finishes.
Confirm that both switch links remain green.
Recheck the two IPv4 addresses against the values above.
Confirm that both subnet masks show 255.255.255.0.

Help me diagnose a failed ping between PC0 and PC1.

Your two-PC LAN now carries traffic successfully. Next, you will change the subnet boundary and watch this working baseline fail.

Calculate the /26 Subnets

Your two-PC /24 LAN can already exchange ping replies. That working baseline proves the switch links and original addresses are correct.

Now you will narrow the IPv4 boundary in Cisco Packet Tracer to see how each PC decides which addresses are local. You will then calculate the four equal /26 networks inside 192.168.0.0/24.

In this step, get ready to:

Move PC0 and PC1 into different /26 networks.
Test the new subnet boundary with a ping.
Calculate four non-overlapping subnet ranges with a block size of 64.

Create the failure on purpose

A subnet mask tells a host which addresses belong to its local network. Changing the mask from 255.255.255.0 to 255.255.255.192 moves that boundary while the physical topology stays the same.

Return to PC0's Desktop IP Configuration window from earlier.
Replace PC0's Subnet Mask with 255.255.255.192.

PC0 should now show 192.168.0.1 with the mask 255.255.255.192.

Return to PC1's Desktop IP Configuration window from earlier.
Replace PC1's IPv4 Address with 192.168.0.65.
Replace PC1's Subnet Mask with 255.255.255.192.

PC1 should now show 192.168.0.65 with the mask 255.255.255.192. Both default gateway fields remain blank from the earlier setup.

Before you run the test, predict whether the two PCs still consider each other part of the same local network.

Return to PC0's Desktop Command Prompt from earlier.
Test PC1's new address by entering this command:

ping 192.168.0.65

Why did the ping stop?

PC0 sees 192.168.0.65 outside its local /26 network. With no router or default gateway, PC0 has no Layer 3 path to PC1.

This failed result is intentional. The links remain green, so the changed subnet boundary caused the loss of communication.

You should see no successful Reply lines in PC0's Command Prompt.

Seeing Reply lines?

Confirm that PC1 uses 192.168.0.65.
Confirm that both PCs use 255.255.255.192.
Confirm that both default gateway fields are blank.

Help me diagnose an unexpected successful ping between these two /26 networks.

Derive the /26 pattern

A CIDR prefix of /26 reserves 26 bits for the network portion of an address. Borrowing two bits from the original /24 creates four equal networks.

How the block size works

Two borrowed host bits create four possible subnet combinations.
The /26 mask ends with 192 in the final octet.
The calculation 256 - 192 = 64 gives each subnet a block size of 64 addresses.

Use a blank document or a sheet of paper for your subnet worksheet.
Write the headings Subnet, Network, Usable host range, and Broadcast.

Your worksheet should now have four empty columns ready for the subnet values.

Add four rows labelled 1 through 4.
Fill the network column by starting at 0 in the final octet and adding 64 for each row.

The network addresses should end in 0, 64, 128, and 192.

Calculate each broadcast address by subtracting one from the next network address.
Calculate each usable host range from the address after its network address to the address before its broadcast address.

Each row should now contain one network address, one usable host range, and one broadcast address.

Complete the subnet worksheet

Before you compare the rows, predict whether any usable host range should overlap with another subnet.

Check Subnet 1 against this row: network 192.168.0.0/26. Usable hosts are 192.168.0.1 to 192.168.0.62. The broadcast is 192.168.0.63.
Check Subnet 2 against this row: network 192.168.0.64/26. Usable hosts are 192.168.0.65 to 192.168.0.126. The broadcast is 192.168.0.127.
Check Subnet 3 against this row: network 192.168.0.128/26. Usable hosts are 192.168.0.129 to 192.168.0.190. The broadcast is 192.168.0.191.
Check Subnet 4 against this row: network 192.168.0.192/26. Usable hosts are 192.168.0.193 to 192.168.0.254. The broadcast is 192.168.0.255.

What does the worksheet prove?

Each network begins exactly 64 addresses after the previous one. The reserved network and broadcast addresses keep all four usable ranges separate.

PC0 belongs to the first row. PC1 belongs to the second row.

Before your final test, predict whether completing the worksheet changed the communication boundary between the PCs.

Return to PC0's Command Prompt from earlier.
Verify the boundary again by entering this command:

ping 192.168.0.65

What should the final check show?

The ping should still contain no successful Reply lines. Your worksheet explains the result because 192.168.0.1 and 192.168.0.65 belong to different /26 networks.

You have now connected the failed ping to a complete subnet plan. All four /26 ranges fit inside 192.168.0.0/24 without overlap.

Your /26 subnet plan is ready. Next, you will use it to build three working department pairs.

Build Three Department Subnets

The failed ping from the last step proved that PC0 and PC1 were separated by a /26 boundary. With no router, neither host had a path into the other subnet.

In Cisco Packet Tracer, you will turn the worksheet into three working department pairs. The final test matrix keeps the cross-subnet failure as evidence that routing is absent.

In this step, get ready to:

Expand the switch topology to six PCs.
Apply the Admin, Staff, and Guest address plan.
Verify local connectivity and cross-subnet isolation.

Expand the office topology

The existing 2960 switch has four unused ports for the remaining office hosts. Each new PC needs its own Copper Straight-Through link to the switch.

Add four PC end devices to the Logical workspace using the device palette in the lower-left corner.
Arrange the new devices near the existing switch.
Select Copper Straight-Through from the cabling palette.
Connect PC2 FastEthernet0 to switch FastEthernet0/3.
Connect PC3 FastEthernet0 to switch FastEthernet0/4.
Connect PC4 FastEthernet0 to switch FastEthernet0/5.
Connect PC5 FastEthernet0 to switch FastEthernet0/6.
Wait for all four new link indicators to turn green.

Good progress. Your one-switch topology now has all six office hosts connected through green links.

Link not turning green?

Check that each cable starts at the PC's FastEthernet0 port.
Check that the switch ends use ports FastEthernet0/3 through FastEthernet0/6 in numerical order.
Wait a little longer for the switch links to initialize.

Ask for help if a cable link remains inactive.

Apply the department address plan

Each department needs two IPv4 addresses from the same usable range. This pairing lets local traffic succeed inside each calculated subnet.

Department Address Plan

Every PC uses the mask 255.255.255.192. The Default Gateway field stays blank because the topology has no router.

Admin A uses PC0 at 192.168.0.1.
Admin B uses PC1 at 192.168.0.2.
Staff A uses PC2 at 192.168.0.65.
Staff B uses PC3 at 192.168.0.66.
Guest A uses PC4 at 192.168.0.129.
Guest B uses PC5 at 192.168.0.130.

Return to the Desktop tab on PC1.
Select IP Configuration.
Change the address to 192.168.0.2.
Confirm that the mask still shows 255.255.255.192.

PC1 now sits inside the first /26 with PC0.

Open PC2's IP Configuration page from its Desktop tab.
Enter 192.168.0.65 as the address.
Enter 255.255.255.192 as the mask.
Confirm that the gateway remains blank.

PC2 now shows the first usable Staff address from the second /26.

Open PC3's IP Configuration page from its Desktop tab.
Enter 192.168.0.66 as the address.
Enter 255.255.255.192 as the mask.
Confirm that the gateway remains blank.

PC3 now shares the Staff subnet with PC2.

Open PC4's IP Configuration page from its Desktop tab.
Enter 192.168.0.129 as the address.
Enter 255.255.255.192 as the mask.
Confirm that the gateway remains blank.

PC4 now shows the first usable Guest address from the third /26.

Open PC5's IP Configuration page from its Desktop tab.
Enter 192.168.0.130 as the address.
Enter 255.255.255.192 as the mask.
Confirm that the gateway remains blank.

PC5 now shares the Guest subnet with PC4. All three departments have non-overlapping address pairs.

Address Fields Look Wrong?

Compare the selected PC with its row in the department address plan.
Check that every mask is exactly 255.255.255.192.
Clear any value that appears in the Default Gateway field.

Ask for help checking the six address assignments.

Run the subnet test matrix

A test matrix checks each local pair before testing a destination in another subnet. This separates a working local configuration from the routing boundary you expect to remain.

Before you test, which three destinations do you expect to answer? Which destination should remain unreachable without a router?

Return to the Command Prompt on PC0 from earlier.
Use ping with 192.168.0.2 as the destination.
Open PC2's Command Prompt from its Desktop tab.
Use ping with 192.168.0.66 as the destination.
Open PC4's Command Prompt from its Desktop tab.
Use ping with 192.168.0.130 as the destination.
Return to the Command Prompt on PC0.
Use ping with 192.168.0.65 as the destination.

The first three tests return successful Reply lines. The last test from PC0 to PC2 has no successful Reply lines.

Missing a Local Reply?

Repeat a same-subnet test once if the first attempt is incomplete while address resolution finishes.
Check that the intended pair uses the two addresses shown in the department plan.
Confirm that both cable indicators for the pair are green.

Ask for help if a same-subnet ping still has no replies.

You did it: each department now has local connectivity while the boundary between different subnets remains visible.

What Does the Matrix Prove?

Each successful pair uses two addresses from the same /26. The switch can carry that local traffic directly.

PC0 and PC2 belong to different Layer 3 networks. Without a router or default gateway, neither PC can reach the other subnet.

Your three department subnets are working. Next, you will add VLANs so the switch enforces matching boundaries at Layer 2.

Configure VLAN Segmentation

Your three /26 address pairs now communicate inside their own subnets. Cross-subnet traffic already stops because the office has no router.

In Cisco Packet Tracer, every active switch port still belongs to default VLAN 1. You will create Admin, Staff, and Guest VLANs so the Layer 2 boundaries match the existing Layer 3 plan.

In this step, get ready to:

Inspect the switch's default VLAN membership.
Create three named VLANs for the office departments.
Assign six access ports to their matching VLANs.

Inspect the flat Layer 2 network

A VLAN groups switch ports into one logical network. The switch starts with every active port assigned to VLAN 1.

Select the existing 2960 switch in the Logical workspace.
Select the CLI tab.
Click inside the switch terminal area.
Inspect the current VLAN table by entering these commands:

enable
show vlan brief

What does this check show?

The enable command moves the switch into privileged EXEC mode.
The show vlan brief command displays each VLAN's name and associated ports.

You should see FastEthernet0/1 through FastEthernet0/6 listed under VLAN 1. This confirms that the current Layer 2 network is still flat.

Cannot inspect the VLAN table?

Check the switch prompt. Enter enable if the prompt ends with >.

Select the switch's CLI tab again if you entered the command in a PC window.

Ask for help with the switch CLI.

Create the VLAN boundary

The switch needs one named VLAN for each department. The names make the VLAN table easier to compare with your subnet plan.

Create the three department VLANs in the switch CLI by entering these commands:

configure terminal
vlan 10
name Admin
vlan 20
name Staff
vlan 30
name Guest
end
show vlan brief

How does this build the VLAN table?

The configure terminal command enters global configuration mode.
The three vlan commands create VLANs 10, 20, and 30.
The name commands label the VLANs as Admin, Staff, and Guest.
The final check displays the new VLAN records before any access ports are moved.

You should now see VLAN 10 named Admin, VLAN 20 named Staff, and VLAN 30 named Guest.

Assign only FastEthernet0/1 to the Admin VLAN by entering these commands:

configure terminal
interface f0/1
switchport mode access
switchport access vlan 10
end

What does this port configuration do?

The interface f0/1 command selects the port connected to PC0.
The switchport mode access command makes the port a Layer 2 access port.
The switchport access vlan 10 command assigns that port to the Admin VLAN.

Select PC0 in the Logical workspace.
Select the Desktop tab.
Select Command Prompt.

Before you run this test, do you expect PC0 to reach PC1 after only one port changes VLANs? Make your prediction now.

Test the Admin pair from PC0 by running this command:

ping 192.168.0.2

What does this result prove?

You should see no successful Reply lines. PC0 still shares an Admin subnet with PC1, but their switch ports now belong to different VLANs.

This interruption is intentional. It proves that IP addressing alone does not place ports in the same Layer 2 segment.

Complete the access port assignments

The interrupted Admin pair needs matching VLAN membership. Applying the same access-port pattern to every department restores communication inside each pair.

Return to the switch's CLI tab.
Assign the remaining five access ports by entering these commands:

configure terminal
interface f0/2
switchport mode access
switchport access vlan 10
interface f0/3
switchport mode access
switchport access vlan 20
interface f0/4
switchport mode access
switchport access vlan 20
interface f0/5
switchport mode access
switchport access vlan 30
interface f0/6
switchport mode access
switchport access vlan 30
end
show vlan brief

How are the ports grouped?

FastEthernet0/1 and FastEthernet0/2 form the Admin access-port pair in VLAN 10.
FastEthernet0/3 and FastEthernet0/4 form the Staff access-port pair in VLAN 20.
FastEthernet0/5 and FastEthernet0/6 form the Guest access-port pair in VLAN 30.
The final show vlan brief command confirms the completed mapping.

You should see FastEthernet0/1-2 under Admin, FastEthernet0/3-4 under Staff, and FastEthernet0/5-6 under Guest.

Use this reference if you want to compare the complete switch command sequence.

✔️ Awesome, I've got everything!

Your three VLANs are named correctly. All six access ports are mapped to their departments.

ⓧ I'd like to double check the full code

enable
configure terminal
vlan 10
name Admin
vlan 20
name Staff
vlan 30
name Guest
interface f0/1
switchport mode access
switchport access vlan 10
interface f0/2
switchport mode access
switchport access vlan 10
interface f0/3
switchport mode access
switchport access vlan 20
interface f0/4
switchport mode access
switchport access vlan 20
interface f0/5
switchport mode access
switchport access vlan 30
interface f0/6
switchport mode access
switchport access vlan 30
end
show vlan brief

Before the final tests, which paths do you expect to return replies? Compare your prediction with the results below.

Return to PC0's Command Prompt from earlier.
Run both PC0 tests with these commands:

ping 192.168.0.2
ping 192.168.0.65

What should PC0 see?

The ping to PC1 at 192.168.0.2 should contain successful Reply lines. Both Admin ports now belong to VLAN 10.

The ping to PC2 at 192.168.0.65 should have no successful replies. That destination sits in the Staff subnet and VLAN 20.

Select PC2 in the Logical workspace.
Select the Desktop tab.
Select Command Prompt.
Test the Staff pair by running this command:

ping 192.168.0.66

What should PC2 see?

You should see successful Reply lines from PC3. Both Staff ports belong to VLAN 20.

Select PC4 in the Logical workspace.
Select the Desktop tab.
Select Command Prompt.
Test the Guest pair by running this command:

ping 192.168.0.130

What should PC4 see?

You should see successful Reply lines from PC5. Both Guest ports belong to VLAN 30.

Ping result does not match?

Repeat a same-department ping once if the first attempt is incomplete. Packet Tracer may still be resolving the destination.

Use show vlan brief to confirm that both ports are in the expected VLAN. Check each PC against the /26 worksheet if the result is still wrong.

Help me diagnose my VLAN and ping results.

Strong result. Your switch now enforces the Admin, Staff, and Guest Layer 2 boundaries.

Your ping matrix also proves that traffic cannot cross the Layer 3 segments without a router.

Secret mission

Add an IoT Segment

Use the unused fourth `/26` network to add two IoT devices without changing the Admin, Staff, or Guest segments. Place both devices in VLAN 40. Then prove that they can communicate locally while remaining isolated from Admin.

Clean Up Your Resources

Your office network runs locally inside Cisco Packet Tracer on Windows, so there are no cloud resources or ongoing costs. Choose whether to keep the topology available, pause by saving and closing it, or delete its local .pkt file.

Resources you used:

One local Packet Tracer .pkt topology containing one 2960 switch, eight PCs, four /26 subnets, and four VLANs.

What stays available?

Your Cisco Networking Academy account and Cisco Packet Tracer installation stay available for future labs. Neither creates a cloud resource or ongoing cost for this project.

Keep everything running

No cleanup is needed. Choose this if you want to extend the office network with routing or more devices later.

Choose a descriptive filename for the segmented office topology.
Save the current topology as a .pkt file in a Windows folder you can find again.

Your eight-PC office network stays ready to reopen for another Packet Tracer lab.

Pause - I'll come back to this later

Pausing means saving the topology before closing Cisco Packet Tracer. Your local .pkt file keeps the office network available.

Save the current topology as a .pkt file in a Windows folder you can find again.
Close Cisco Packet Tracer.
Reopen the saved .pkt file when you are ready to continue.

Delete - I don't want to use this again

Deleting the local file removes your saved lab from its folder. This affects only the topology file created for this project.

Close Cisco Packet Tracer without saving if the topology exists only in the current session.
Use Windows search to find the .pkt file you saved for this project if a local copy exists.
Select the saved .pkt file.
Press the Delete key to remove the selected file.
Confirm the .pkt file no longer appears in its folder.

Your Cisco Networking Academy account and Cisco Packet Tracer installation can remain available for future networking projects.

Nice Work!

Excellent work! Your office network now has four clearly tested communication boundaries in Cisco Packet Tracer.

You've learned how to:

Divide the 192.168.0.0/24 IPv4 address space into four equal /26 subnets. You documented each network address, usable host range, and broadcast address.
Build a switched LAN with six correctly addressed PCs. You proved that each department pair could exchange successful ping replies.
Create Admin, Staff, and Guest VLANs on a 2960 switch. You mapped each access port to its intended group. Your ping matrix confirmed same-segment communication. It also confirmed cross-segment isolation without a router.
Secret Mission: Extended the design with the unused fourth /26 subnet. You added VLAN 40 named IoT. You proved that its two PCs communicate only within their segment.

Ready to quiz yourself?