LABNETWORK WORKSPACE

OPEN SOURCE. SELF-HOSTED. YOUR LAB.

Your network lab.
All in one view.

Build a topology. Open your consoles. Follow the exercise.
Keep your focus in one browser workspace.

Build your first lab Explore the source

Runs on your Linux host. Works from your desktop or tablet.

THE WORKSPACETOPOLOGY + CONSOLES + INSTRUCTIONS
A running ten-device Weblab topology with Cisco, Extreme and Arista devices, an EXOS console and the node inspector. View full size ↗
A mixed-vendor lab, connected and running. Your map and CLI stay together.

BRING YOUR OWN IMAGES

See supported profiles and requirements

LESS WINDOW SWITCHING. MORE NETWORKING.

A workspace that
works the way you do.

From your first VLAN to a multi-vendor troubleshooting lab, keep the tools you need within reach.

01 / WORKSPACE

Make room for the whole lab.

Float, resize and arrange the topology, consoles and instructions. Keep consoles in tabs or open them side by side. Go fullscreen when it’s time to focus.

Explore the workspace ↗
02 / CONSOLES

Pick up where you left off.

View the same device console from multiple workstations. Input locks and confirmed takeover keep typing coordinated. On a tablet, Ctrl+C, Tab and arrow keys are within reach.

Meet the console tools ↗
03 / PRACTICE

Keep the exercise beside the CLI.

Open Markdown or text instructions in a floating window. Copy commands into a console and work through the lab without leaving the page.

Read about instructions ↗
YOUR LAYOUT, YOUR FOCUSFLOAT · RESIZE · ARRANGE
Six arranged windows show a topology, four device consoles and Markdown instructions together in Weblab. View full size ↗
The map, four consoles and instructions, arranged side by side in one browser tab.

BREAK IT. UNDERSTAND IT. FIX IT.

See how your
network reacts.

Block traffic in one direction or both while a lab is running. Model a silent link failure, watch a protocol converge, and restore traffic when you’re ready.

For supported IOSv and IOL profiles, cable controls also request a link-down state at the selected endpoint.

Explore link failure controls

Frame loss and carrier state are separate controls, so you can practice different kinds of failure.

Link actions with separate controls for directional frame loss and unplugging each endpoint.
Change link behavior without rebuilding your topology.

YOUR IMAGES. YOUR TOPOLOGIES.

Build once.
Practice, save, share.

Upload supported device images, connect the interfaces and start your lab. Mix device families in the same topology to explore how they work together.

Share a topology as JSON, seed fresh Cisco devices with initial configurations, or export a stopped lab’s saved device storage as a ZIP.

Find the right export for your lab

Device images and required licenses are supplied by you. Save device configurations before stopping; Alpine PC filesystems are temporary.

Weblab image upload dialog with a file picker for supported device images.
Add your images directly from the device library.

FROM SOURCE TO YOUR FIRST LAB

Start small. Connect more.

Use an x86-64 Linux host or VM with rootful Docker and Compose. Enable KVM for QEMU devices.

  1. 01

    Set up Weblab

    Follow the installation guide for Docker, host permissions and remote access.

    Installation guide ↗
  2. 02

    Add your devices

    Supply your images, then build a topology or import the starter example.

    Try the starter lab ↗
  3. 03

    Make it your own

    Practice routing, switching and failure scenarios. Save your work and share an exercise.

    Explore an OSPF exercise ↗
GET THE SOURCEgit clone https://github.com/weblab-network/weblab.git

Designed for your own host or a trusted group. Weblab currently has no authentication or per-user isolation; keep the lab service on a trusted network or behind an SSH tunnel.

BUILT TO BE SHARED

Your next lab
starts here.

Free, open-source tools for hands-on networking.
Try a lab, report an issue, or help improve the project.

Find Weblab on GitHub