| 2021-02-15 07:18:46 +0000 | commented answer | Previous segment not captured and tcp out-of-order Thank you! |
| 2021-02-15 07:18:19 +0000 | marked best answer | Previous segment not captured and tcp out-of-order Hi! 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! |
| 2021-02-15 07:18:19 +0000 | received badge | ● Scholar (source) |
| 2021-02-11 12:30:11 +0000 | edited question | Previous segment not captured and tcp out-of-order Previous segment not captured and tcp out-of-order Hi! I have warnings "TCP Previous segment no captured" and "TCP Out- |
| 2021-02-11 12:19:12 +0000 | received badge | ● Editor (source) |
| 2021-02-11 12:19:12 +0000 | edited question | Previous segment not captured and tcp out-of-order Previous segment not captured and tcp out-of-order Hi! I have warnings "TCP Previous segment no captured" and "TCP Out- |
| 2021-02-11 12:17:43 +0000 | asked a question | Previous segment not captured and tcp out-of-order Previous segment not captured and tcp out-of-order Hi! I have warnings "TCP Previous segment no captured" and "TCP Out- |
Copyright Wireshark Foundation, 2017-2023 Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.