316e7002c1
uBridge's window mode gained the semantics the B.2 spec asked for — `tc window_drop <if> <start> <outage> <pct> [<period> [<jitter>]]`: a single outage that traffic passes before *and* after, recurring flaps with period >= outage, and a per-cycle jitter — so the kernel-only `window_drop` filter type is now exposed: - validation mirrors the tc grammar (3-5 params, ranges, period >= outage, jitter cap) and adds window_drop to KERNEL_ONLY_FILTERS; filter_inactive_filters keeps start=0 — unlike every other filter a zero first parameter means "the outage starts now", not "disabled". - `_ubridge_apply_ebpf_drops` sends `tc window_drop` (positional pass-through) and turns the mode off explicitly when absent, under the same ebpf=1 gate. - FILTERS entry (Start/Outage/Chance/Period/Jitter) + available_filters. The schedule is relative to the apply: reconcile re-sets the classifier on every apply, so any filter change, node restart or link reset restarts the window. Verified on a two-container kernel link, 15/15: a single outage [1000, 1500, 100] arrives per-seq as [0..4, 13..19] (passing before the window, dropped inside, passing after); recurring 1000/2000 ms = 52 % round trip (duty cycle); period == outage = permanent outage; period < outage = 409 before uBridge; jittered flap keeps the ~50 % duty cycle; 30 % chance on a permanent window = 53 % round trip against the per-direction theory 1-0.7^2 = 51 %; coexist with netem; node restart restores; available_filters kernel vs relay (409 + hidden); teardown clean. P6b re-run as a regression on the same uBridge build: 13/13. Worth recording for the next rebuild: the first delivered window program loaded as root but reported ebpf=0 through gns3-server — the verifier's non-root path loses the loop counter's bound, treats the catch-up loop as unbounded and rejects the *whole* program (E2BIG, 8193 pending states), which also took frequency_drop and quota down, with ebpf=0 as the only symptom. Smaller trip caps did not help; the loop had to go (uBridge 572ca0c), on top of a Makefile header-dependency fix (53e34bb) that had been shipping a stale program object.
GNS3 server repository
The GNS3 server manages emulators and other virtualization software such as Dynamips, Qemu/KVM, Docker, VPCS, VirtualBox and VMware Workstation. Clients like the GNS3 GUI and the GNS3 Web UI control the server using a HTTP REST API.
Installation
These instructions are for using GNS3, please see below for development.
Windows & macOS
Please use our Windows installer or DMG package to install the stable build along with the GNS3 VM. Note that as of GNS3 version above 3.0, you must run the server using the GNS3 VM or on a Linux system (remote, cloud or virtual machine).
Linux
Ubuntu based distributions
We build and test packages for actively supported Ubuntu versions. Other distros based on Ubuntu, like Mint, should also be supported.
Packages can be installed from our Personal Package Archives (PPA) repository:
sudo apt update
sudo apt install software-properties-common
sudo add-apt-repository ppa:gns3/ppa
sudo apt update
sudo apt install gns3-gui gns3-server
Other Linux distributions
GNS3 is often packaged for other distributions by third-parties:
PyPi
You may use PyPi in case no package is provided, or you would like to do a manual installation:
python3 -m pip install gns3-gui
python3 -m pip install gns3-server
Optional Features
GNS3 server supports optional features that can be installed as needed:
AI Features (Optional — includes AI Copilot and MCP):
python3 -m pip install gns3-server[ai-features]
AI-powered assistant for network topology design, automation, and MCP protocol support for AI agent integration.
Development (For contributors):
python3 -m pip install gns3-server[dev]
Web Wireshark (Optional):
pip install gns3-server && gns3server-web-wireshark-setup
Browser-based packet capture analysis using Wireshark in a Docker container.
Combination Installation: You can install multiple optional features together:
python3 -m pip install gns3-server[ai-features,dev]
Why optional?
- Reduces installation size for users who don't need specific features
- Supports restricted environments (government, education, corporate) where certain libraries may not be allowed
- Faster installation for basic GNS3 usage
- Allows users to choose only the features they need
Note: If you install without optional extras, the server will work normally but optional features will be disabled. You can add features later by running the appropriate install command.
Uninstalling AI Features:
To remove AI Features dependencies (AI Copilot + MCP):
gns3server-uninstall-ai-features
This will remove all AI Copilot and MCP dependencies while keeping the core functionality intact. The server will continue to work, but AI features will be disabled.
Please see our documentation for more details.
Software dependencies
In addition to Python dependencies, other software may be required, recommended or optional.
- uBridge is required, it interconnects the nodes.
- Dynamips is required for running IOS routers (using real IOS images) as well as the internal switches and hubs.
- VPCS is recommended, it is a builtin node simulating a very simple computer to perform connectivity tests using ping, traceroute etc.
- Qemu is strongly recommended as most node types are based on Qemu, for example Cisco IOSv and Arista vEOS.
- libvirt is recommended as it's needed for the NAT cloud.
- Docker is optional, some nodes are based on Docker.
- mtools is recommended to support data transfer to/from QEMU VMs using virtual disks.
- i386-libraries of libc and libcrypto are optional, they are only needed to run IOU based nodes.
Note that Docker needs the script program (bsdutils or util-linux package), when running a Docker VM and a static busybox during installation (python3 setup.py install / pip3 install / package creation).
Development
Setting up
These commands will install the server with core Python dependencies:
git clone https://github.com/GNS3/gns3-server
cd gns3-server
git checkout 3.1
python3 -m venv venv-gns3server
source venv-gns3server/bin/activate
python3 -m pip install .
python3 -m gns3server
For AI Copilot development, install with additional dependencies:
python3 -m pip install .[ai-features,dev]
For development (tests and linting):
python3 -m pip install .[dev]
You will have to manually install other software dependencies (see above), for Dynamips, VPCS and uBridge the easiest is to install from our PPA.
Docker container
Alternatively, you can run the GNS3 server in a container
bash scripts/docker_dev_server.sh
use Docker Compose
docker compose up -d
Running tests
First, install the development dependencies:
python3 -m pip install -r dev-requirements.txt
Then run the tests using pytest:
python3 -m pytest -vv tests/
API documentation
The API documentation can be accessed when running the server locally:
- On
http://IP:PORT/docsto see with Swagger UI (i.e.http://localhost:3080/docs) - On
http://IP:PORT/redocto see with ReDoc (i.e.http://localhost:3080/redoc)
The documentation can also be viewed online however it may not be the most up-to-date version since it needs manually synchronization with the current code. Also, you cannot use this to interact with a GNS3 server.
Branches
master
master is the next stable release, you can test it in your day-to -day activities. Bug fixes or small improvements pull requests go here.
3.x development brand for the next major release.
Never use this branch for production. Pull requests for major new features go here.