Lines Matching +full:capture +full:- +full:only

7 - qlog
8 - Packet capture
13 - In general, qlog is aimed at storing only information relevant to the
18 - By comparison, packet capture stores all packets in their entirety.
23   packet capture cannot directly tell you when an implementation deems a packet
31 - qlog:
32   - Pro: Smaller files
33   - Con: May leave out data assumed to be irrelevant
34   - Pro: Information on internal states and decisions made by a QUIC
36   - Pro: No need to obtain a keylog
37 - PCAP:
38   - Pro: Complete capture
39   - Con: No direct information on internal states of a QUIC implementation
40   - Con: Need to obtain a keylog
43 ----------
47 - build using the `enable-unstable-qlog` build-time configuration option;
49 - set the environment variable `QLOGDIR` to a directory where qlog log files
52 - set the environment variable `OSSL_QFILTER` to a filter specifying the events
56 qlog files in the JSON-SEQ format to the specified directory. The files have the
73 Note that since qlog emphasises logging only data which is relevant to a QUIC
81 ----------
83 To use PCAP you can use any standard packet capture tool, such as Wireshark or
84 tcpdump (e.g. `tcpdump -U -i "$IFACE" -w "$FILE" 'udp port 1234'`).
86 **Using Wireshark.** Once you have obtained a packet capture as a standard
119 - **Manual configuration.** Select Edit →
121   under “(Pre)-Master-Secret log filename". You can have key information being
125 - **Embedding.** Alternatively, you can embed a keylog file into a `.pcapng`
127   the packet capture file is opened. This avoids the need to have a centralised
128   key log file and ensures that the key log for a specific packet capture is
130   to distribute a packet capture file publicly, for example for educational
134   after taking a packet capture (note that `tls` should be specified below
138   $ editcap --inject-secrets tls,$PATH_TO_KEYLOG_FILE \