Before touching any network device, you need to master basic computer operation and the binary number system, then prepare the PNETLab server, Cisco Images (vIOS and IOL/IOU), a console terminal client, and Wireshark. In this episode you make sure every prerequisite is in place and verify the lab for the first time.

Welcome to the Learn Computer Networking PNETLab series! This series will take you through mastering computer networking — from Layer 2 foundations all the way to complex Layer 3 routing — practiced directly on PNETLab. Inside PNETLab you will assemble topologies, place devices such as Cisco vIOS Routers and IOL Switches, and connect everything with virtual cables just like a real lab.
Before moving on to the following episodes, there are a few foundational skills and tools you must prepare first. Why are these prerequisites important? Because the entire series is built on comfortable computer operation and an understanding of the binary number system. Without both, the subnetting calculations in episode 3 will feel very heavy.
Episode 0 is your roadmap: we make sure the foundational skills are in place, prepare the PNETLab server, load the Cisco Images, configure the terminal client, and run the first verification. Once this episode is done, you can follow the whole series without any obstacles.
You should be comfortable operating Windows, Linux, or macOS. The minimum skills: opening a terminal or command prompt, navigating directories, running installers, changing virtual adapter settings, and managing files. PNETLab is accessed through a web interface, but many installation steps still require terminal skills, for example running the following verification command:
uname -a
grep -cE 'vmx|svm' /proc/cpuinfoThe command grep -cE 'vmx|svm' /proc/cpuinfo displays the number of
CPU cores that support hardware virtualization. A result greater than zero
means the hypervisor can use full acceleration for PNETLab.
Computer networking is built on the binary number system. Every IPv4 address
consists of 32 bits, and each decimal number in it is a conversion of 8 binary
bits. You do not need to memorize, but you must understand basic conversions
such as 255 becoming 11111111 and 192 becoming 11000000. Episode 3 will
review this material in more depth.
Quick exercise: calculate the decimal value of the binary 11000000. Those
eight bits represent 128 + 64 = 192. Building this calculation habit will help
you a lot when you do manual subnetting later.
PNETLab is not an ordinary desktop application; it is an appliance that runs on top of a hypervisor such as VMware Workstation, Proxmox VE, or VirtualBox. The recommended minimum specifications for an experimental lab: CPU 4 cores, RAM 8 GB, and 100 GB of storage. Add more RAM as the number of nodes you run simultaneously grows.
Download the latest PNETLab v5 (the .ova or .iso file) from the official
site pnetlab.com, then import it into your hypervisor. On VMware Workstation
use the File menu then Import, while on Proxmox VE use the qm importovf
command. After the VM first boots, PNETLab will display its IP address on the
console.
qm create 9000 --name pnetlab --memory 8192 --cores 4
qm importovf 9000 PNETLab.ova local-lvm
qm start 9000Access the web interface through a browser at http://<pnetlab-ip> with the
default credentials admin:pnet. Change the password immediately after your
first login.
Cisco Images are the fuel of your lab. vIOS is a router and switch image that runs IOS in full, while IOL/IOU (IOS on Linux/UNIX) is lighter and faster for Layer 2 switches. For this series prepare the vIOS-L3 Router and IOL-L2 Switch as the minimum.
Go to the Manage Images menu, then choose Add. PNETLab accepts image definitions in JSON format. An example for an IOL L3 Router:
{
"image": "iOL-L3_8.4.0.qcow2",
"category": "L3Router",
"name": "IOL-L3-8.4"
}Once the image is registered, the image node appears under Devices and can be dragged onto the canvas. Also add the VPCS (Virtual PC Simulator) image as a simple host and the Docker Linux Host for the lightweight server used in episode 18 later.
Node consoles in PNETLab can be opened directly in the browser, but for comfort you can integrate SecureCRT, PuTTY, or MobaXterm. A console connection is essentially SSH or Telnet to a specific port on the PNETLab server; the integration is configured in the System Settings menu.
Also prepare Wireshark as your frame analysis tool. From the PNETLab canvas you can right-click a link and choose Capture, and the traffic passing through will open directly in Wireshark. Your ability to read capture output will be used from episode 4 all the way to episode 20.
Before moving on to episode 1, make sure everything runs normally. Log in to the PNETLab server over SSH and check the version and service status:
ssh admin@<pnetlab-ip>
pnet version
docker psThe last two commands, pnet version and docker ps, ensure
the appliance and PNETLab containers are running without errors. If both come
up without issues, your environment is ready for the entire series.
Here is what you prepared in episode 0: basic computer operation, binary and decimal concepts, a running PNETLab server, registered Cisco vIOS and IOL images, an integrated terminal client, and Wireshark ready to use. If anything is still missing, stop here and complete it before moving on to the next material.
Key takeaways:
pnet version and docker ps before starting your first lab.In the next episode, episode 1, we will discuss networking fundamentals and the OSI vs TCP/IP reference models — why computers need networks, the components of end devices and network media, the seven OSI layers, the four TCP/IP layers, and the data encapsulation and decapsulation process. Make sure your lab is ready, because the Learn Computer Networking PNETLab journey has just begun!