How can I avoid out-of-order TCP packets in Wireshark -
i have following situation - when recorded tcp traffic wireshark packets out-of-order. need save data pdml (wireshark detail xml) , process each main tag 1 one. problem i'm expecting data saved in correct order, out-of-order packets not true. packets looks following:
- id time ... ack seq
- 1 12:10:01 ... 1 1
- 2 12:10:02 ... 206 1461
- 3 12:10:03 ... 206 1 (out-of-order)
- 4 12:10:04 ... 2143 206
- 5 12:10:05 ... 2143 218
- 6 12:10:06 ... 283 2143
so 3rd packet actual start of response server , 2nd 1 continuation.
this situation occurs , can manually switch packets in produced pdml. automatically if possible, prevent problem sure.
so question - there default possibility configure sorting in wireshark avoid such issue? or option write own parser produced pdml described situation must handled.
what need output 2nd , 3rd packets switched.
how can avoid out-of-order tcp packets in wireshark
assuming packets weren't delivered machine out of order, can avoid them doing capturing on operating system doesn't deliver packets out of order capture mechanism libpcap/winpcap uses. @ least versions of linux would, on multiprocessor/multicore machines, sometimes, because 2 packets processed different cores, , 1 arrived later on machine made pf_packet socket first.
the packets in example in order time stamp, significant time difference between them; happens in captures? if so, packets are arriving on capturing host out of order.
there no mechanism in wireshark sort packets tcp sequence number , write them out in order.
Comments
Post a Comment