Wireshark
Host: Windows, Linux, macOS · Cost: Unknown
Record how the capture was obtained and whether it is a HAR, SAZ or packet file. Start with endpoints and protocol framing, then inspect one bounded request or packet sequence relevant to your question.
Suggested level: Intermediate. Captured traffic may contain credentials or personal data. A single session does not describe every protocol state.
Documented target: Recorded packets. Selected fields, repeated values, filters and decode-as rules
Requirements: Linux: TShark 4.x + prlimit; [capture guide](docs/packet-captures.md)
Documented on main branch; not locally tested. Confirm the installed package and connected tool list before using this path.
Source: REA documentation