Previous segment not captured and tcp out-of-order

asked 2021-02-11 12:17:43 +0000

itbn
3 ●2

updated 2021-02-11 12:30:11 +0000

Hi!
I have warnings "TCP Previous segment no captured" and "TCP Out-Of-Order".

I guess it's because the second part of the segment comes first. For example, first comes segment Seq=12586 Ack=3056 Len:187. And then comes segment Seq=11138 Ack=3056 Len:1448. But Seq=11138 must be first.

And i have a lot of those segments. What could be the reason? Help me, please. Is this a network problem?

Thank you!

answered 2021-02-11 20:54:52 +0000

JasMan

81 ●1 ●21 ●11

You're right with your guess. There are different reasons why the packets didn't arrived in order. The most likely reason is that your capture device or driver was not able to keep the original order of the packets because of the total amount of received packets. The size of the packets might be a reason too, because according to your screenshot only full-size packets with a size of 1514 bytes are having this problem.

Another reason could be the router between the two communication partners. Larger packets may be "overtaken" by the smaller ones due to performance reason.

This is not a problem for the network, the clients or the application. The time difference between the messed up packets is very small or not existing, and TCP is responsible to reassemlbe the stream at the destination.

edit flag offensive delete link

Comments

Thank you!

itbn ( 2021-02-15 07:18:46 +0000 )edit

add a comment

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Previous segment not captured and tcp out-of-order

1 Answer

Comments

Your Answer

Question Tools

Stats

Previous segment not captured and tcp out-of-order edit

1 Answer

Comments

Your Answer

Question Tools

Stats

Previous segment not captured and tcp out-of-order