![]() Cause of not capturing a packet before are perhaps two of either following. ![]() The most typical reason is packet loss and/or late start of capture, which is the reason why the wording in question is used. I'm debugging the code implemented internally, hoping to find out why. TCP Previous segment not captured This is displayed when the 'As far as we see the Seq (sequence number) of the packet, a packet should be observed before this packet but not seen in Wireshark'. If packet N is marked with previous segment not captured, it means that in the capture there is no packet from the same TCP session whose seq + length would match the seq of packet N. I'm willing to provide a PR but it may take some time. The more reasonable results are as follows: | cipher = TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256
0 Comments
Leave a Reply. |