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.
netverdict docs
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.
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 works
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.
| Subsystem | Status | Notes | Open lab |
|---|---|---|---|
| IPv4 forwardingRFC 791 / RFC 1812 | supported | Routing-table lookup, TTL handling, traceroute-style drops, and ICMP errors for common lab scenarios. | Open |
| OSPFv2RFC 2328 | supported | Neighbors, DR / BDR election, multi-area routing, summaries, ranges, virtual links, and stub-area variants. | Open |
| BGP-4 + MP-BGPRFC 4271 / 4760 / 4364 | supported | Common policy labs work: attributes, route maps, communities, local-pref, MED, AS-path, and VPNv4. | Open |
| MPLS / LDPRFC 3032 / RFC 5036 | supported | Label distribution, push / swap / pop, PHP, TTL handling, and L3VPN-style VRF forwarding. | Open |
| ACLs + time rangesCisco semantics / RFC 1812 | supported | First-match rules, implicit deny, object groups, port ranges, and active time windows. | Open |
| NAT / PATRFC 2663 | partial | Static NAT and UDP PAT work. TCP / ICMP PAT and deeper ASA NAT cases are not complete yet. | Open |
| RIPRFC 2453 | stub | You can parse some RIP config, but there is no full RIP routing process yet. | - |
Config support
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.
| Profile | Can paste config? | Good for | Current limit |
|---|---|---|---|
| IOS-stylecisco-ios / ios-xe / nx-os / ios-xr | Yes, for common running-config shapes | IOS-style routing, switching, ACL, NAT, services, and policy labs | Not every platform-specific command exists. |
| ASA-stylecisco-asa | Yes, through an ASA-specific parser | Firewall rules, security levels, ACLs, and ASA-shaped NAT labs | Full ASA NAT parity is still limited. |
| Junos-stylejuniper-junos | Yes, set-style and XML import paths | Candidate config, commit, rollback, and Junos-style practice | Junos-style surface, not Junos OS. |
| VyOS / EdgeOSvyos / edgeos | Yes, parser-direct | Vyatta-family config import and routing labs | Firewall, VRRP, WireGuard, QoS, and IPv6 depth varies. |
| OpenWrt / UniFiopenwrt / unifi | Yes, UCI and controller JSON | Home / branch router and controller-export scenarios | UniFi uses controller export data, not a device CLI. |
| Gaia / EXOScheckpoint-gaia / extreme-exos | Yes, parser-direct | Stateful firewall and VLAN-centric switch scenarios | Config import is deeper than interactive CLI depth. |
Why trust it?
Run the same lab twice with the same commands and netverdict should produce the same routes, packet path, and assessment verdict.
Because results repeat, a bug report or failed lab can be replayed instead of reconstructed from memory.
Packet capture export writes libpcap files that open in Wireshark for supported frame types.
Different CLI styles feed the same simulator model underneath, so reachability checks do not depend on which vendor syntax you used.
Try it
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