https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14700
--- Comment #14 from Peter Wu <pe...@lekensteyn.nl> ---
This problem is also present when capturing from multiple interfaces on an
Ethernet bridge with TCP/IP packets. In that case, packets are wrongly
identified as TCP Out-of-Order/Retransmission/Dup ACK/..., but data is
reassembled correctly due to availability of a sequence number.
To fix reassembly here, I guess it could incorporate the Mesh Destination
address in the 32-bit reassembly ID (e.g. "(mesh_dest_id << 16) |
datagram_tag"). Could that work?
--
You are receiving this mail because:
You are watching all bug changes.
___________________________________________________________________________
Sent via: Wireshark-bugs mailing list <wireshark-bugs@wireshark.org>
Archives: https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe
