An open-source, vendor-agnostic network simulator — a modern alternative to Cisco Packet Tracer.
PacketForge lets you drag-and-drop routers, switches, hosts, firewalls, access points and point-to-point radios onto a canvas, cable them together, configure them from a CLI, and watch real packets (ARP, IPv4, ICMP) flow through the topology — hop by hop — in your browser. It is not tied to any one vendor: a Cisco, Juniper, Arista, MikroTik, Huawei or Ubiquiti box is just a JSON file, and they all run the same simulation engine and the same command set.
- Zero runtime dependencies.
node server/index.jsand you're done. Nonpm install, no database. - Real simulation, not canned animation. The engine does MAC learning, flooding, ARP resolution, longest-prefix routing, default gateways, TTL decrement and ICMP echo/reply — with a replayable event stream.
- Modern web UI. Dark theme, pan/zoom canvas, drag-to-move, click-a-port-to-cable, right-click-a-cable-to-pull-it, per-device console, live packet animation, WebSocket multi-client sync.
- Physically accurate. 90 media types across ten families (Ethernet, Fibre Channel, GPON, DOCSIS, DSL, powerline, DAC, serial, console, wireless) and 28 connector cages; per-port speed capabilities and PoE budgets. Impossible cables are refused, not drawn — an SC/APC patch lead will not go into an SC/UPC socket. See docs/PHYSICAL_LAYER.md and docs/CONNECTORS.md.
- Any hardware. Add a new model in ~10 lines of JSON. See docs/DEVICE_REGISTRY.md.
git clone https://git.jayw.uk/jaylouisw/packetforge.git
cd packetforge
node server/index.jsOpen http://localhost:8000.
The server listens on 127.0.0.1 only, so nothing else on the network can reach it. To use it from
another machine, start it with PF_HOST=0.0.0.0 npm start ($env:PF_HOST='0.0.0.0'; npm start in
PowerShell) — there is no authentication, so only on a network you trust.
docker run --rm -p 8000:8000 ghcr.io/jaylouisw/packetforge:latestThen open http://localhost:8000. The image sets PF_HOST=0.0.0.0 so the published port reaches
the container; a bare npm start stays on loopback.
-
Click a device in the left palette (e.g. Router), then click the canvas to place it.
-
Place two PCs and a Switch.
-
Cable them, either way:
- Device first (recommended): click 🔗 Create link (or press
C), click the switch, then the PC. The panel lists the link types the two boxes can actually share — 1000BASE-T, 10GBASE-LR — with the port pairs underneath, andEsccancels. If nothing fits it says why (E_CONNECTOR_MISMATCH,E_NO_FREE_PORTS, …) instead of failing one guess at a time. - Port first: click a port on one device, then a port on another.
- Device first (recommended): click 🔗 Create link (or press
-
Select a PC → Console tab → type:
configure terminal interface eth0 ip address 192.168.1.10 255.255.255.0 -
Select the other PC, give it
192.168.1.20/24. -
Select the first PC → Simulate tab → ping
192.168.1.20.
You'll see ARP requests flood the switch, the reply come back, and the ICMP echo/reply travel across the link with a live animation and event log.
| Area | What's implemented |
|---|---|
| Devices | router, L2 switch, L3 switch, PC, server, firewall, access point, PTP radio, cloud |
| Vendors | 2,352 models across 258 vendors, in 25 categories (router, switch, L3 switch, firewall, AP, wireless, PTP radio, OLT, ONT, modem, powerline, NAS, server, desktop, laptop, tablet, phone, printer, camera, NVR, IoT, tap, splitter, cloud, host) + generic models. Adding one is a single JSON file (registry) |
| L2 | MAC address table, learning, unknown-unicast/broadcast flooding |
| L3 | IPv4 addressing, connected + static routes, default gateway, longest-prefix match |
| Protocols | ARP, IPv4, ICMP echo + errors, traceroute, DHCP client + server (pools, ranges, exclusions, reservations — in the data path), DNS (NXDOMAIN/NODATA/SERVFAIL), NAT (static + PAT), extended ACLs, OSPF, BGP, SCION, VRRP (election, virtual MAC, gratuitous ARP on takeover), IPv6 with SLAAC/RA, LLDP, 802.1D STP, 802.1Q VLANs, LACP |
| Physical layer | 90 media types, 28 connector cages, per-port speed caps + PoE, live feasibility validation, Fibre Channel as its own protocol (docs) |
| L2 features | 802.1Q VLANs (access/trunk/native), LACP aggregation, 802.1D spanning tree |
| CLI | Cisco-like vendor-agnostic console: show, interface, ip address, ip dhcp pool, ip route, ping [count] [at <ms>], traceroute, converge |
| UI | drag-drop canvas, pan/zoom, port cabling, per-device console, packet animation, event log |
| Convergence | Control planes take time: STP Listening/Learning, OSPF hello + SPF hold, DHCP exchange, VRRP master-down. Ask any question at an instant with setRunTime(ms) / ping ... at 5000; an unfinished process reports converging, not "timed out" (docs) |
| Link failure | Pull a cable without deleting it: frames die at the link, STP heals around it, MAC tables flush, and every timer re-runs from the instant of the change. link down l5 at 10000 then ask at 11000 — nothing gets through, and the reply says so (docs) |
| Latency | Per-link propagation from the medium's velocity, serialisation from frame size and line rate, store-and-forward per hop — so a 40 km span is not the same as a 1 m patch lead |
| Persistence | save/load topologies as JSON (import/export buttons) |
| Sync | WebSocket broadcasts topology edits to every connected client in real time |
Stated plainly, because a simulator that overstates itself teaches wrong things:
- DHCP relay. A DISCOVER does not cross a router, so a central server cannot serve a remote subnet. Snooping, Option 82 and DHCPv6 are absent too; leases are computed at run start and do not age.
- HSRP and GLBP. VRRP is wired (election, virtual MAC, failover); the Cisco and Avaya equivalents are not modelled, and neither is BFD or graceful restart.
- Timed interleaving. Control planes now have a duration (CONVERGENCE.md), but a question is answered as of an instant — no hello loss, no dead-interval expiry, no re-convergence after a topology change.
- TCP and application protocols. Flows are tracked; TCP state, HTTP, TLS and friends are not simulated.
Each of these is a tracked issue rather than a surprise.
packetforge/
├── engine/ # pure-JS simulation engine (zero deps)
│ ├── net.js # IPv4 / MAC / subnet helpers
│ ├── device.js # Device + Interface model
│ ├── link.js # Link model
│ ├── topology.js # Topology container + (de)serialization
│ ├── simulator.js # event-driven L2/L3/ARP/ICMP engine
│ ├── cli.js # vendor-agnostic management console
│ └── index.js # public API
├── devices/ # hardware catalog — JSON only
│ ├── registry.js # loads + groups device specs
│ └── <vendor>/*.json
├── server/ # HTTP + hand-rolled WebSocket server (zero deps)
├── web/ # frontend (vanilla JS + SVG, no build step)
├── examples/ # ready-to-import lab topologies
├── test/ # engine + CLI tests
├── scripts/ # syntax checker + merge tools
├── .github/ # CI/CD workflows, issue/PR templates (read by Forgejo too)
├── .forgejo/ # Forgejo Actions workflows
└── docs/ # architecture, registry, CLI, CI, roadmap, link state
See docs/ARCHITECTURE.md for the full design.
npm test # engine + CLI tests
node examples/build-examples.js # regenerates + self-verifies the example labs
npm run syntax # syntax-check every JS file- Packet Tracer is Windows/macOS-only, closed-source, Cisco-centric, and its "simulation" is partly scripted rather than a real protocol engine.
- GNS3 / EVE-NG run real firmware images — powerful but heavy (need images, licenses, virtualization), and overkill for learning fundamentals.
- PacketForge is browser-native, instant, open source, and models behavior generically so the same engine works for every manufacturer. It's designed to be forked and extended.
Contributions are welcome — especially new hardware models. See CONTRIBUTING.md for the full guide and docs/DEVICE_REGISTRY.md for the device schema.
Development, CI and releases run on Forgejo; GitHub is a read-only mirror. Where the two differ, Forgejo is right. docs/MIRRORING.md explains what stays in sync, what cannot, and how a contribution made on GitHub reaches review here.
Every device is one JSON file, so a good request is mostly a good datasheet link. Anything internet-connected is in scope: routers, switches, firewalls, APs and point-to-point radios, OLTs and ONTs, cable and DSL modems, powerline and MoCA adapters, servers, NAS, laptops, phones, printers, IP cameras, NVRs and IoT gear.
Requests are triaged with node scripts/request-queue.js, which checks each one
against the catalog and for a usable datasheet before any time is spent on it.
The full process — what we need, what happens, and what we will not do (invent
port counts) — is in docs/REQUESTING-HARDWARE.md.
Please report security issues privately — see SECURITY.md.
MIT — see LICENSE. Roadmap in docs/ROADMAP.md.