SSL/TLS packet capture prompts ignored unknown record
There are two cases of this prompt. First, packet capture is late, part of the SSL/TLS negotiation data is not obtained, and Wireshark cannot recognize and parse it. Second, the packet uses a special protocol type, Wireshark can not correct, waiting for later Wireshark improvement.
Similar Posts:
- #TCP you can learn “TCP spurious retransmission” in Wireshark
- About Wireshark “the NPF driver isn’t running “Solutions
- TCP segment of a reassembled PDU
- Code a packet sniffer in python with pcapy exte…
- [original] TCP previous segment not captured
- Wireshark window size value and calculated window size
- Solutions to database connection problems: “connections could not be acquired from the underlying database!”
- [Solved] ORA-03137 – ORA-12592 TNS:BAD PACKET OR ORA-3137
- Oracle error:ORA-01704: string literal too long
- Run Wireshark or tshark as a Non-Root User