| Callsign | Role | Privacy | Created | Actions |
|---|
| Time | Source | Type | Length | Stream | Callsign | Detail |
|---|
This is a real-time view of raw D-STAR UDP packets arriving at the reflector on port 20001. A raw socket sniffer captures every inbound packet and classifies it by type. The table updates every 2 seconds with the most recent packets.
Packet types: header marks the start of a voice transmission and contains the callsign routing fields (MY, UR, RPT1, RPT2). voice+data frames carry 20ms of AMBE-encoded audio plus 3 bytes of slow data. control packets are end-of-stream markers. keepalive and poll are periodic heartbeats exchanged between clients and the reflector to maintain connections.
Stream ID: Each voice transmission has a unique 2-byte stream ID. All packets belonging to the same transmission share this ID, making it easy to follow a single QSO through the log.
Loss detection: Voice frames cycle through a 0-20 sequence counter within each superframe. When a gap in the sequence is detected, the affected row is highlighted red with a LOST N badge showing exactly how many frames were dropped and where in the transmission it happened. Bursty loss at the start suggests a connection handoff; loss throughout suggests a degraded path.
Stream summaries: When a transmission ends, a bold STREAM END row appears with the total frame count, duration, packet loss percentage, and BER (bit error rate from Golay FEC checks). Loss and BER are color-coded: green (<2%), yellow (2-5%), red (>5%).
Gateway attribution: If a gateway (identified by source IP) averages 2% or more packet loss across its streams over the last hour, a GW:N% badge appears on stream summaries from that gateway. This helps distinguish between a user's poor RF link (only their streams show loss) and a degraded gateway internet path (all streams from that IP show loss). Hover the badge for full gateway stats. The window is rolling 1 hour — stale history drops off automatically.
When to use this: The packet monitor is a diagnostic tool for troubleshooting connection issues, verifying that traffic from bridges or gateways is arriving correctly, checking keepalive health, and investigating protocol-level problems. Use the filter to isolate a specific callsign, packet type, or source IP.