Repository navigation
Weblab v0.9.0
Weblab v0.9.0
Inspect traffic directly on a lab link, decode network protocols, and export
PCAP files. The Export dialog also gains a guarded workspace reset.
Link traffic monitor
Click a link and choose Monitor traffic. An independent floating window
shows packet time, direction, addresses, protocol, size, summary and relay outcome.
Filter by protocol or direction, follow incoming packets, and resize the divider
between the packet list and details with the mouse, touch or keyboard.
Decoded uses TShark, included in the core image. Its installed protocol
library supports switching and routing protocols such as LLDP, CDP, DTP, VTP,
STP/PVST+, LACP, ARP, OSPF and BGP, alongside IP, transport and application
protocols. Filters expand with detected protocols. Hex / ASCII shows the
captured bytes; Download PCAP includes every captured frame regardless of
those display filters.
Captures observe frames entering the link relay. Forwarded means sent to the
peer socket, not confirmed delivery to the guest. Blocked and undelivered frames
are also recorded. No guest commands or host-interface sniffing are used.
- Each capture stops after 60 seconds, 2,000 frames or 8 MiB. At most four capture
buffers exist server-wide; they expire 15 minutes after creation. - Captures are temporary: closing their window, logging out or restarting the
server discards them. Download the PCAP before closing if it should be kept. - With authentication enabled, admin and writer can capture. Each capture belongs
to its exact login session; readers and other logins cannot access it. - Decoding runs outside the forwarding path with resource/time limits. Summary
batches and selected-packet details do not reconstruct conversations across
batches or reassemble TCP/IP messages. Use Wireshark on the PCAP for that work. - Native installations need
tsharkandutil-linuxfor full decoding. Basic
summaries, raw bytes and PCAP remain available if decoding is unavailable.
See traffic monitoring.
Export and reset
In Export, select Reset lab after export, save the JSON or ZIP download,
then confirm the reset. A separate Reset without export… button offers the
same confirmation without creating a backup. All nodes must be stopped; with
authentication enabled, reset requires admin access. A competing workspace change
invalidates the reset request instead of clearing a changed lab.
Reset clears topology and device storage, including retained storage from removed
nodes. Installed images, authentication settings, activity records, Agent history
and published instructions remain. JSON is not a complete device-state backup;
choose Saved lab ZIP for the current lab's saved state. Storage retained from
previously removed nodes is not included in current-topology exports.
See backup and reset behavior.
Installation and upgrade
Use matching 0.9.0 core, Agent and EXOS image tags. Back up the lab and preserve
its volumes when recreating existing containers; no configuration migration is
required. Building from source requires a rebuild to install TShark.
The release includes weblab-install.sh and SHA256SUMS for fresh installations.
It retains the optional Agent, authentication, running example and core-only
--dns override. It is not an upgrade tool. Follow the
installation guide.
LL2S stays at 0.2.0 and Weblab FRR at 10.7.1-wl1. Their existing image and
source/binary distribution are unchanged.