Packet Tracer is great for CCNA basics, but sooner or later you will want to run real network operating systems: real IOS commands, real rou...
Packet Tracer is great for CCNA basics, but sooner or later you will want to run real network operating systems: real IOS commands, real routing protocol behavior, and real packet captures in Wireshark. GNS3 lets you do that on your own Windows PC. In this guide I will walk you through installing the GNS3 all-in-one package, setting up the GNS3 VM, adding a Cisco IOSv image that you are licensed to use, and building a first two-router topology.
What GNS3 is (and how it differs from Packet Tracer)
Packet Tracer is a simulator: it imitates IOS behavior, so some commands are missing or behave differently. GNS3 is an emulator front end: it boots actual router, switch and firewall images inside virtual machines or containers, and connects them with virtual cables. The trade-off is that GNS3 needs more RAM and CPU, and you must provide the images yourself.
| Feature | Packet Tracer | GNS3 |
|---|---|---|
| Runs real IOS | No (simulation) | Yes (emulation) |
| Images included | Yes | No, you supply licensed images |
| Multi-vendor | Cisco only | Cisco, Juniper, Arista, MikroTik, Linux and more |
| Wireshark capture | No (Simulation mode shows PDUs instead) | Real captures on any link |
| Hardware needed | Light | 16 GB RAM recommended, CPU with VT-x/AMD-V |
Before you start
- Windows 10 or 11, 64-bit.
- RAM: 8 GB works for very small labs; 16 GB or more is much more comfortable. Each IOSv router uses about 512 MB.
- Hardware virtualization enabled in BIOS/UEFI. Look for Intel VT-x (sometimes "Intel Virtualization Technology") or AMD-V/SVM. In Task Manager > Performance > CPU, "Virtualization: Enabled" confirms it.
- Disk space: at least 20 GB free for GNS3, the VM and images.
- A free account on gns3.com to download the installer and the GNS3 VM.
Which version?
At the time of writing, GNS3 has two active release lines: the newer 3.x and the long-running 2.2.x. Either is fine for learning. The rule that matters is this: the GNS3 desktop application and the GNS3 VM must be exactly the same version, down to the last digit (if the application is 2.2.x, the VM must be that same 2.2.x release). A mismatch is the most common reason the GNS3 VM refuses to connect.
Step 1: Install the GNS3 all-in-one package
- Log in at gns3.com, go to the download page and download the Windows all-in-one installer (a file named like
GNS3-x.y.z-all-in-one.exe). - Run it as administrator and accept the license.
- On the Choose Components page, the defaults are fine for most people. Make sure these remain selected: GNS3, Npcap, Wireshark, Dynamips, QEMU and VPCS. You can untick Solar-PuTTY if you prefer standard PuTTY or the Windows Terminal.
- Accept the prompts that install Npcap and Wireshark as part of the setup; they are needed for packet captures.
- Finish the installer and launch GNS3.
Step 2: Install a hypervisor and the GNS3 VM
You can run some devices directly on Windows, but Cisco IOSv and most modern images need QEMU with KVM acceleration, which only works on Linux. The GNS3 VM is a small Linux virtual machine built for exactly this. GNS3 on Windows becomes the "remote control", and the GNS3 VM does the heavy lifting.
Choose a hypervisor
I recommend VMware Workstation Pro, which Broadcom now offers free of charge (a Broadcom account is needed to download it). VMware passes hardware virtualization into the GNS3 VM (nested virtualization), which KVM needs. GNS3 also publishes a Hyper-V build of the VM for Windows Pro/Enterprise users, and a VirtualBox build exists, but VirtualBox nested virtualization is less reliable for this use.
Import the GNS3 VM
- From the GNS3 download page, download the GNS3 VM for VMware Workstation. Pick the same version as the GNS3 application you installed.
- Extract the zip file. Inside is an
.ovafile. - In VMware Workstation, choose File > Open, select the
.ova, and import it. Keep the nameGNS3 VM. - Before starting it, open the VM settings, select Processors and tick Virtualize Intel VT-x/EPT or AMD-V/RVI.
- Do not start the VM manually. GNS3 will start it for you.
The Hyper-V conflict
If Hyper-V, WSL2, Windows Sandbox or Virtualization-based Security (Memory Integrity / Core Isolation) is enabled, VMware runs on top of the Windows hypervisor, and nested virtualization is not available. The GNS3 VM then boots but shows a warning that KVM is not available, and IOSv will not start or will be extremely slow. Your options:
- Use the Hyper-V build of the GNS3 VM instead of the VMware one, or
- Turn off the Windows hypervisor. From an administrator Command Prompt, run
bcdedit /set hypervisorlaunchtype off, disable Memory Integrity in Windows Security, and reboot. Be aware this stops WSL2 and Docker Desktop from working until you turn it back on withbcdedit /set hypervisorlaunchtype auto.
Step 3: Run the Setup Wizard
The first time GNS3 starts, the Setup Wizard appears. If you closed it, open it again from Help > Setup Wizard.
- Choose Run appliances in a virtual machine.
- Leave the local server settings at their defaults (host 127.0.0.1) and continue.
- Select VMware (or Hyper-V) as the virtualization software, and pick GNS3 VM from the VM name list. Click Refresh if it does not appear.
- Set vCPU cores and RAM. A good starting point is 2 vCPUs and 4 GB RAM on a 16 GB laptop, more if you have it.
- Finish. GNS3 powers on the VM in VMware.
After a minute or two, look at the Servers Summary pane (View > Docks > Servers Summary if hidden). You should see your local server and the GNS3 VM, both with green indicators, and the VM showing its CPU and RAM usage.
Step 4: Add a Cisco IOSv image (legally)
This part matters, so let me be clear: GNS3 does not include any Cisco software, and you must supply your own licensed images. Do not download IOS images from random websites or file-sharing links. Apart from the legal issue, those files are a common way to spread malware and are often corrupted.
Legitimate ways to get Cisco virtual images include:
- Cisco Modeling Labs (CML), including the personal edition, which provides reference platform images such as IOSv (router) and IOSvL2 (switch) as part of the subscription.
- Your employer's Cisco account, if your organization has a service contract that entitles you to download the images and its policy allows lab use.
If you do not have Cisco images yet, you can still learn a lot with free appliances available in GNS3: VPCS, Open vSwitch, FRRouting, VyOS and MikroTik CHR. Check each vendor's license terms.
Create the IOSv template
- Copy your IOSv files to your PC. The IOSv appliance normally needs the IOSv
.qcow2disk image and a small startup-config disk image (IOSv_startup_config.img) that comes with it. - In GNS3, click File > New template.
- Choose Install an appliance from the GNS3 server, search for Cisco IOSv, and click Install.
- Choose to install it on the GNS3 VM.
- The wizard lists the image versions it knows about and marks missing files. Select your version, click Import for each required file and browse to your copy. GNS3 checks the file and uploads it to the VM.
- Finish the wizard. The template appears under Routers in the devices panel on the left.
If your version number is not listed, use the option to create a new version in the same wizard and enter your file names.
Step 5: Build your first topology
Create a new project (File > New blank project) called first-lab. Drag in two IOSv routers and two VPCS hosts, then use the cable tool to connect them.
| Device | Interface | IP address | Connected to |
|---|---|---|---|
| R1 | Gi0/0 | 10.0.12.1/30 | R2 Gi0/0 |
| R1 | Gi0/1 | 192.168.1.1/24 | PC1 |
| R2 | Gi0/0 | 10.0.12.2/30 | R1 Gi0/0 |
| R2 | Gi0/1 | 192.168.2.1/24 | PC2 |
| PC1 (VPCS) | eth0 | 192.168.1.10/24 | Gateway 192.168.1.1 |
| PC2 (VPCS) | eth0 | 192.168.2.10/24 | Gateway 192.168.2.1 |
Click the green Start button to boot everything. IOSv takes a minute or two to boot. Double-click a router to open its console.
Configure the routers
Router> enable
Router# configure terminal
Router(config)# hostname R1
R1(config)# interface gigabitEthernet0/0
R1(config-if)# ip address 10.0.12.1 255.255.255.252
R1(config-if)# no shutdown
R1(config-if)# interface gigabitEthernet0/1
R1(config-if)# ip address 192.168.1.1 255.255.255.0
R1(config-if)# no shutdown
R1(config-if)# exit
R1(config)# ip route 192.168.2.0 255.255.255.0 10.0.12.2
R1(config)# end
R1# write memory
Router> enable
Router# configure terminal
Router(config)# hostname R2
R2(config)# interface gigabitEthernet0/0
R2(config-if)# ip address 10.0.12.2 255.255.255.252
R2(config-if)# no shutdown
R2(config-if)# interface gigabitEthernet0/1
R2(config-if)# ip address 192.168.2.1 255.255.255.0
R2(config-if)# no shutdown
R2(config-if)# exit
R2(config)# ip route 192.168.1.0 255.255.255.0 10.0.12.1
R2(config)# end
R2# write memory
Each router gets a static route to the other router's LAN. These are the same commands you use in Packet Tracer, which is the point: your CCNA skills carry over directly.
Configure the VPCS hosts
PC1> ip 192.168.1.10/24 192.168.1.1
Checking for duplicate address...
PC1 : 192.168.1.10 255.255.255.0 gateway 192.168.1.1
PC1> save
Saving startup configuration to startup.vpc
. done
Do the same on PC2 with ip 192.168.2.10/24 192.168.2.1. The save command stores the setting inside the project.
Step 6: Verify
R1# show ip interface brief
Interface IP-Address OK? Method Status Protocol
GigabitEthernet0/0 10.0.12.1 YES manual up up
GigabitEthernet0/1 192.168.1.1 YES manual up up
GigabitEthernet0/2 unassigned YES unset administratively down down
GigabitEthernet0/3 unassigned YES unset administratively down down
PC1> ping 192.168.2.10
84 bytes from 192.168.2.10 icmp_seq=1 ttl=62 time=9.872 ms
84 bytes from 192.168.2.10 icmp_seq=2 ttl=62 time=6.415 ms
84 bytes from 192.168.2.10 icmp_seq=3 ttl=62 time=5.903 ms
84 bytes from 192.168.2.10 icmp_seq=4 ttl=62 time=6.128 ms
84 bytes from 192.168.2.10 icmp_seq=5 ttl=62 time=5.774 ms
The TTL of 62 tells you the packet crossed two routers (VPCS starts at 64). The first ping can time out while ARP resolves; that is normal.
Capture packets with Wireshark
Right-click the link between R1 and R2 and choose Start capture. Wireshark opens and shows live traffic on that link. Run the ping again and you will see ICMP echo requests from 192.168.1.10 to 192.168.2.10 and the replies, carried between the MAC addresses of R1 Gi0/0 and R2 Gi0/0.
In the Wireshark window you will see one line per packet. For this ping the columns look like this:
| Column | What you see for the ping |
|---|---|
| Source | 192.168.1.10 on the echo requests, 192.168.2.10 on the replies |
| Destination | 192.168.2.10 on the requests, 192.168.1.10 on the replies |
| Protocol | ICMP |
| Info | Echo (ping) request / Echo (ping) reply, with id, seq and ttl values (ttl=63 on the requests, because R1 has already decremented it once) |
Click any packet and expand the Ethernet II section in the details pane: the source and destination MAC addresses belong to R1 Gi0/0 and R2 Gi0/0, not to the PCs, because the frame is rebuilt at every router hop.
Prefer video? Watch more hands-on labs on the Technical Hakim YouTube channel.
Common mistakes
- GUI and VM versions do not match. GNS3 shows a version mismatch error and will not use the VM. Download the VM for the exact version you installed.
- KVM not available in the GNS3 VM. Either VT-x/AMD-V is disabled in BIOS, the "Virtualize Intel VT-x/EPT" option is not ticked in VMware, or the Windows hypervisor is running. See the Hyper-V section above.
- Template installed on the local server instead of the GNS3 VM. IOSv on Windows QEMU without acceleration is painfully slow. Reinstall the template on the GNS3 VM.
- Allocating too much RAM to the VM. Leave enough for Windows itself, or the whole PC starts swapping.
- Forgetting to save. Use
write memoryon routers andsaveon VPCS before closing the project, or your configuration is lost. - Using images from untrusted sources. Apart from licensing, these are a real security risk on your PC.
Summary
You installed the GNS3 all-in-one package, imported a matching GNS3 VM into VMware Workstation, connected the two with the Setup Wizard, added a Cisco IOSv image from your own licensed source, and built a working two-router lab with VPCS hosts and a Wireshark capture. From here you can rebuild any Packet Tracer lab in GNS3 and see how real IOS behaves.
Related tutorials
- Basic Cisco Router Setup: Hostname, Passwords, Banner and SSH
- Static Routes vs Default Routes: When to Use Each (with Lab)
- OSI Model vs TCP/IP Model: Layers, Protocols and a Wireshark Walkthrough
- EIGRP Configuration Lab with Verification
Sources
- GNS3 Documentation (docs.gns3.com) – GNS3 VM usage
- GNS3 Documentation – Windows install and Setup Wizard guides
- Cisco Modeling Labs – Reference Platform images documentation
- VMware Workstation Pro documentation – Nested virtualization settings
No comments