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.
Claude names the failure: a lost UE
From capture to answer in four steps.
-
01 Capture
Record PCAPs on every CI/CD run, then turn VisualEther loose on them.
-
02 Diagram
Read each run as sequence diagrams — whole-capture overview down to a single session.
-
03 Triage
VisualEther classifies every session by outcome, so the failures surface first.
-
04 Diagnose
Point Claude Code at the failed sessions and ask why — it debugs them in plain English.
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.
Analyze moto_edge_30_pro.pcap across layers — why did the session drop?
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.