VisualEther · Wireshark PCAP analysis for humans and AI

Wireshark shows the packets.
VisualEther shows the answer.

Turn a Wireshark capture into a sequence diagram you can read at a glance — then point Claude Code at it and ask “why did it fail?” in plain English. Built for 5G developers, test engineers, and network professionals.

VisualEther renders a 5G NR sequence diagram from a Wireshark capture while Claude Code traces an RLC poll-retransmission storm to a lost UE. Claude names the failure: a lost UE
VisualEther diagram (left) + Claude Code cross-layer analysis (right) of moto_edge_30_pro.pcap.
How it works

From capture to answer in four steps.

  1. A Wireshark packet list of a 5G NR capture, filtered to the RRC signaling messages.

    01 Capture

    Record PCAPs on every CI/CD run, then turn VisualEther loose on them.

  2. A 5G NR RRC sequence diagram rendered by VisualEther — UE and gNB as columns with RRC Setup Request and RRC Setup message arrows, each annotated with a key-parameter table.

    02 Diagram

    Read each run as sequence diagrams — whole-capture overview down to a single session.

  3. VisualEther session-outcome charts per session type — IP-FLOW, MAC-UE, NAS-5GS, RRC-CONNECTION, SDAP-BEARER and SIP — each pie split between Timeout and Incomplete.

    03 Triage

    VisualEther classifies every session by outcome, so the failures surface first.

  4. A Claude Code case-study turn: asked to walk through the complete flow, Claude summarizes one UE across three connection episodes — a full attach with IMS registration plus two short re-accesses.

    04 Diagnose

    Point Claude Code at the failed sessions and ask why — it debugs them in plain English.

See the full workflow
What the case studies show

Claude Code drives VisualEther — author, debug, verify.

Each case study is a real user–Claude Code session — you watch this loop play out, prompt by prompt, on an actual capture.

01 User Debug request

Analyze moto_edge_30_pro.pcap across layers — why did the session drop?

02 Claude Cross-layer analysis

The capture ends in an RLC poll-retransmission storm on RRC Release. The gNB polls repeatedly and never gets an ACK — the UE had already detached. Not a bug: the textbook signature of a lost UE.