You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Feature request: Add an optional “Hide CONTROL packets” checkbox to the packet monitor #96
Add a clearly visible Hide CONTROL packets checkbox to the packet monitor so users can reduce visual noise when they are not investigating control traffic.
This is an opt-in display preference: CONTROL packets must remain visible by default. The checkbox must be unchecked for users without a saved preference.
Motivation
CONTROL packets can make the packet monitor harder to scan during normal use. They still provide useful information for discovery and signal diagnostics, so users should be able to hide them temporarily without losing access to the data.
Requested behavior
Add a checkbox labelled Hide CONTROL packets.
Leave it unchecked by default, retaining the current behavior.
When checked, hide CONTROL packets from both the historical list and incoming live traffic.
When unchecked, show CONTROL packets again, subject to the other active filters.
Persist both checked and unchecked choices across reloads, and respect existing packet-type filter selections.
Keep direct links to individual CONTROL packets accessible, even when the display filter is enabled.
Scope
This is a packet-monitor display feature only. Do not change packet ingestion, database retention, statistics, or anomaly detection.
Acceptance criteria
A user without a saved preference sees CONTROL packets and an unchecked checkbox.
Toggling the checkbox updates the current list without requiring a page reload and applies consistently to subsequent live updates.
The selected preference survives a reload, including an explicit unchecked choice.
Other packet types and existing filters continue to behave as expected.
Historical loading and pagination remain usable when CONTROL packets are hidden; filtering must not strand the user on an empty page when matching packets are available.
Direct packet links remain usable, and no collected data is discarded.
Implemented by #211 (merged as 9989b97f): an opt-in Hide CONTROL packets checkbox on the packets page.
It is off by default and hides payload type 11 only.
Live packets follow the checkbox without a reload.
The choice is saved, and deep-linked as hideControl=.
Known limit: the list filters the fetched window on the client (1,000 packets on mobile, 50,000 on desktop), the same as the type filter. Server-side type exclusion is tracked in #242.
Activity
test(packets): tolerate packets added by earlier CI E2E steps (#96)
test(packets): pin the #211 review nits for Hide CONTROL (#96)
fix(packets): address the #211 review nits for Hide CONTROL (#96)
Merge pull request #211 from dborup/codex/issue-96-hide-control-packets
dborup commentedon Oct 5, 2026
Implemented by #211 (merged as
9989b97f): an opt-in Hide CONTROL packets checkbox on the packets page.hideControl=.Known limit: the list filters the fetched window on the client (1,000 packets on mobile, 50,000 on desktop), the same as the type filter. Server-side type exclusion is tracked in #242.