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
I use your method to get the data data of tcpsession as shown in the figure
When encountering [TCP Previous segment not captured] and [TCP Out-Of-Order] in wireshark, there is a problem. In order to obtain data with a length of 67 bytes, "TCP Previous segment not captured" should be obtained first, but I obtained The data does not get this data, but gets the data of the "[TCP Out-Of-Order]" TCP payload (1460 bytes) on both sides, in wireshark "TCP Out-Of-Order" shows that there is no "data" "of.
The screenshot of "TCP Previous segment not captured" is as follows
Screenshot of "TCP Out-Of-Order", as follows
A screenshot of the data I printed, as shown below, the TCP Out-Of-Order on both sides is printed
this is the packet gmzta.zip
The text was updated successfully, but these errors were encountered:
@qq1176914912
Thank you.
Marked this as "Help Wanted" issue since I'm not sure when I will get to it.
Feel free to send a Pull Request if you want to fix it.
I use your method to get the data data of tcpsession as shown in the figure
When encountering [TCP Previous segment not captured] and [TCP Out-Of-Order] in wireshark, there is a problem. In order to obtain data with a length of 67 bytes, "TCP Previous segment not captured" should be obtained first, but I obtained The data does not get this data, but gets the data of the "[TCP Out-Of-Order]" TCP payload (1460 bytes) on both sides, in wireshark "TCP Out-Of-Order" shows that there is no "data" "of.
The screenshot of "TCP Previous segment not captured" is as follows
Screenshot of "TCP Out-Of-Order", as follows
A screenshot of the data I printed, as shown below, the TCP Out-Of-Order on both sides is printed
this is the packet
gmzta.zip
The text was updated successfully, but these errors were encountered: