netverdict docs

Find out what netverdict can simulate today.

Use these docs to check protocol support, vendor config support, known limits, and labs you can open directly in the browser. No vendor images, no install, no guessing what "supports BGP" means.

Start here if you want a straight answer

netverdict models network behaviour directly in the browser. It does not boot vendor operating systems. That makes labs fast to open and easy to share, but it also means the docs need to be honest about what is modelled, what is partial, and what is not there yet.

What it is
A browser-based network simulator for labs and change testing
Why results repeat
The same lab and commands produce the same packet path and verdict
What to expect
Clear labels: supported, partial, stub, or not modelled yet

What works

Protocol support

This is the short version. "Supported" means you can use it in practical labs. "Partial" means useful pieces are there, but some advanced behaviour is still missing.

SubsystemStatusNotesOpen lab
IPv4 forwardingRFC 791 / RFC 1812supportedRouting-table lookup, TTL handling, traceroute-style drops, and ICMP errors for common lab scenarios.Open
OSPFv2RFC 2328supportedNeighbors, DR / BDR election, multi-area routing, summaries, ranges, virtual links, and stub-area variants.Open
BGP-4 + MP-BGPRFC 4271 / 4760 / 4364supportedCommon policy labs work: attributes, route maps, communities, local-pref, MED, AS-path, and VPNv4.Open
MPLS / LDPRFC 3032 / RFC 5036supportedLabel distribution, push / swap / pop, PHP, TTL handling, and L3VPN-style VRF forwarding.Open
ACLs + time rangesCisco semantics / RFC 1812supportedFirst-match rules, implicit deny, object groups, port ranges, and active time windows.Open
NAT / PATRFC 2663partialStatic NAT and UDP PAT work. TCP / ICMP PAT and deeper ASA NAT cases are not complete yet.Open
RIPRFC 2453stubYou can parse some RIP config, but there is no full RIP routing process yet.-

Config support

Vendor support matrix

These profiles decide which config formats you can paste and which CLI style you can use in the terminal. They are simulator surfaces, not copies of vendor operating systems.

ProfileCan paste config?Good forCurrent limit
IOS-stylecisco-ios / ios-xe / nx-os / ios-xrYes, for common running-config shapesIOS-style routing, switching, ACL, NAT, services, and policy labsNot every platform-specific command exists.
ASA-stylecisco-asaYes, through an ASA-specific parserFirewall rules, security levels, ACLs, and ASA-shaped NAT labsFull ASA NAT parity is still limited.
Junos-stylejuniper-junosYes, set-style and XML import pathsCandidate config, commit, rollback, and Junos-style practiceJunos-style surface, not Junos OS.
VyOS / EdgeOSvyos / edgeosYes, parser-directVyatta-family config import and routing labsFirewall, VRRP, WireGuard, QoS, and IPv6 depth varies.
OpenWrt / UniFiopenwrt / unifiYes, UCI and controller JSONHome / branch router and controller-export scenariosUniFi uses controller export data, not a device CLI.
Gaia / EXOScheckpoint-gaia / extreme-exosYes, parser-directStateful firewall and VLAN-centric switch scenariosConfig import is deeper than interactive CLI depth.

Why trust it?

Repeatable labs, not screenshots

Same lab, same result

Run the same lab twice with the same commands and netverdict should produce the same routes, packet path, and assessment verdict.

Good for debugging

Because results repeat, a bug report or failed lab can be replayed instead of reconstructed from memory.

Useful packet captures

Packet capture export writes libpcap files that open in Wireshark for supported frame types.

One behaviour model

Different CLI styles feed the same simulator model underneath, so reachability checks do not depend on which vendor syntax you used.

Try it

Open a lab from the docs

Docs are more useful when they connect to something runnable. These links open the simulator directly in the matching training lab, so you can read a feature, try it, break it, and inspect the result.

Known limits

What is not fully modelled yet

Works well today

  • Deterministic IPv4 / IPv6 forwarding with ARP, ND, ICMP, and TTL / hop-limit handling.
  • OSPFv2, OSPFv3, EIGRP, BGP-4, MP-BGP VPNv4, LDP, MPLS push / swap / pop.
  • ACLs with object groups, port ranges, time ranges, NAT static, UDP PAT, DHCP, CDP, pcap export.

Still limited

  • Some control planes are behaviour-correct but do not emit every real wire packet internally.
  • RIP is currently config-only; NAT PAT is UDP-focused; TCP / ICMP PAT is deferred.
  • Vendor profiles are lookalike command surfaces on the netverdict kernel, not vendor OS clones.