--- Comment #11 from Pascal Quantin <pascal.quan...@gmail.com> ---
that's also my understanding, but that does not allow to differentiate the case
where the END is sent by the same host as the one that sent the BEGIN, from a
END sent by the peer host, when both are using the same transaction id (which
is the case in this log).
In your capture the tid aaaaaad0 is used twice by the same machine (MTP3 PC
11330): once as otid for the BEGIN (packet 6) and once as otid for the first
CONTINUE after a BEGIN (packet 8). Given that the MTP3 PC and SCCP GT can
change during the transaction, it cannot be used as an identifier to perform
the matching. So for now I have no clue on how to handle this the best.
You are receiving this mail because:
You are watching all bug changes.
Sent via: Wireshark-bugs mailing list <firstname.lastname@example.org>