[Wireshark-bugs] [Bug 13926] TCAP SRT Analysis incorrectly matched TCAP begins and ends

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13926 --- Comment #33 from conall.prenderg...@anam.com --- Verified this latest build on this issue as well as the issues described at 13739, and also with a single continue. Good work here Pascal, enjoy your vacation :) -- You are receiving

[Wireshark-bugs] [Bug 13926] TCAP SRT Analysis incorrectly matched TCAP begins and ends

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13926 --- Comment #32 from Gerrit Code Review --- Change 23090 merged by Pascal Quantin: TCAP: fix infinite loop introduced in g35f9349396 https://code.wireshark.org/review/23090 -- You are receiving this

[Wireshark-bugs] [Bug 13926] TCAP SRT Analysis incorrectly matched TCAP begins and ends

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13926 --- Comment #31 from Gerrit Code Review --- Change 23089 merged by Pascal Quantin: TCAP: more fixes for SRT analysis https://code.wireshark.org/review/23089 -- You are receiving this mail because: You

[Wireshark-bugs] [Bug 13926] TCAP SRT Analysis incorrectly matched TCAP begins and ends

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13926 Pascal Quantin changed: What|Removed |Added Status|IN_PROGRESS

[Wireshark-bugs] [Bug 13926] TCAP SRT Analysis incorrectly matched TCAP begins and ends

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13926 --- Comment #30 from Gerrit Code Review --- Change 23090 had a related patch set uploaded by Pascal Quantin: TCAP: fix infinite loop introduced in g35f9349396 https://code.wireshark.org/review/23090 --

[Wireshark-bugs] [Bug 13926] TCAP SRT Analysis incorrectly matched TCAP begins and ends

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13926 --- Comment #29 from Gerrit Code Review --- Change 23089 had a related patch set uploaded by Pascal Quantin: TCAP: more fixes for SRT analysis https://code.wireshark.org/review/23089 -- You are

[Wireshark-bugs] [Bug 13926] TCAP SRT Analysis incorrectly matched TCAP begins and ends

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13926 --- Comment #28 from Gerrit Code Review --- Change 23088 merged by Pascal Quantin: TCAP: fix infinite loop introduced in g35f9349396 https://code.wireshark.org/review/23088 -- You are receiving this

[Wireshark-bugs] [Bug 13926] TCAP SRT Analysis incorrectly matched TCAP begins and ends

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13926 --- Comment #27 from Gerrit Code Review --- Change 23088 had a related patch set uploaded by Pascal Quantin: TCAP: fix infinite loop introduced in g35f9349396 https://code.wireshark.org/review/23088 --

[Wireshark-bugs] [Bug 13926] TCAP SRT Analysis incorrectly matched TCAP begins and ends

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13926 --- Comment #26 from Gerrit Code Review --- Change 23087 merged by Pascal Quantin: TCAP: fix infinite loop introduced in g35f9349396 https://code.wireshark.org/review/23087 -- You are receiving this

[Wireshark-bugs] [Bug 13926] TCAP SRT Analysis incorrectly matched TCAP begins and ends

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13926 --- Comment #25 from Gerrit Code Review --- Change 23087 had a related patch set uploaded by Pascal Quantin: TCAP: fix infinite loop introduced in g35f9349396 https://code.wireshark.org/review/23087 --

[Wireshark-bugs] [Bug 13926] TCAP SRT Analysis incorrectly matched TCAP begins and ends

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13926 Pascal Quantin changed: What|Removed |Added Status|INCOMPLETE

[Wireshark-bugs] [Bug 13926] TCAP SRT Analysis incorrectly matched TCAP begins and ends

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13926 --- Comment #23 from conall.prenderg...@anam.com --- Created attachment 15777 --> https://bugs.wireshark.org/bugzilla/attachment.cgi?id=15777=edit Single continue causing tshark to hang -- You are receiving this mail because: You are

[Wireshark-bugs] [Bug 13926] TCAP SRT Analysis incorrectly matched TCAP begins and ends

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13926 conall.prenderg...@anam.com changed: What|Removed |Added Resolution|FIXED |---

[Wireshark-bugs] [Bug 13926] TCAP SRT Analysis incorrectly matched TCAP begins and ends

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13926 --- Comment #21 from Gerrit Code Review --- Change 23081 merged by Michael Mann: TCAP: more fixes for SRT analysis https://code.wireshark.org/review/23081 -- You are receiving this mail because: You

[Wireshark-bugs] [Bug 13926] TCAP SRT Analysis incorrectly matched TCAP begins and ends

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13926 --- Comment #20 from Gerrit Code Review --- Change 23081 had a related patch set uploaded by Michael Mann: TCAP: more fixes for SRT analysis https://code.wireshark.org/review/23081 -- You are

[Wireshark-bugs] [Bug 13926] TCAP SRT Analysis incorrectly matched TCAP begins and ends

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13926 Michael Mann changed: What|Removed |Added Status|CONFIRMED |RESOLVED

[Wireshark-bugs] [Bug 13926] TCAP SRT Analysis incorrectly matched TCAP begins and ends

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13926 --- Comment #19 from Gerrit Code Review --- Change 23048 merged by Michael Mann: TCAP: more fixes for SRT analysis https://code.wireshark.org/review/23048 -- You are receiving this mail because: You

[Wireshark-bugs] [Bug 13926] TCAP SRT Analysis incorrectly matched TCAP begins and ends

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13926 --- Comment #18 from Gerrit Code Review --- Change 23048 had a related patch set uploaded by Pascal Quantin: TCAP: more fixes for SRT analysis https://code.wireshark.org/review/23048 -- You are

[Wireshark-bugs] [Bug 13926] TCAP SRT Analysis incorrectly matched TCAP begins and ends

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13926 Pascal Quantin changed: What|Removed |Added Status|INCOMPLETE

[Wireshark-bugs] [Bug 13926] TCAP SRT Analysis incorrectly matched TCAP begins and ends

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13926 --- Comment #17 from Pascal Quantin --- Which is basically what the code used to do until bug 10841 development, because this was not sufficient either to cover all cases. -- You are receiving this mail

[Wireshark-bugs] [Bug 13926] TCAP SRT Analysis incorrectly matched TCAP begins and ends

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13926 --- Comment #16 from conall.prenderg...@anam.com --- Yes, so we can link a continue to the begin if the BEGIN's (otid+calling address) == CONTINUE's (otid+calling) or (dtid+called).. However, we also have to record the calling address of

[Wireshark-bugs] [Bug 13926] TCAP SRT Analysis incorrectly matched TCAP begins and ends

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13926 --- Comment #15 from Pascal Quantin --- (In reply to conall.prendergast from comment #14) > I think it would be possible to use the calling address, as this will never > change. The only thing that could change

[Wireshark-bugs] [Bug 13926] TCAP SRT Analysis incorrectly matched TCAP begins and ends

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13926 --- Comment #14 from conall.prenderg...@anam.com --- I think it would be possible to use the calling address, as this will never change. The only thing that could change is the called address through the GT translation. -- You are

[Wireshark-bugs] [Bug 13926] TCAP SRT Analysis incorrectly matched TCAP begins and ends

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13926 --- Comment #13 from Pascal Quantin --- (In reply to conall.prendergast from comment #12) > Do we not know it is coming from the same host that sent the BEGIN because > the END and the BEGIN have the same SCCP

[Wireshark-bugs] [Bug 13926] TCAP SRT Analysis incorrectly matched TCAP begins and ends

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13926 --- Comment #12 from conall.prenderg...@anam.com --- Do we not know it is coming from the same host that sent the BEGIN because the END and the BEGIN have the same SCCP calling address? -- You are receiving this mail because: You are

[Wireshark-bugs] [Bug 13926] TCAP SRT Analysis incorrectly matched TCAP begins and ends

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13926 --- Comment #11 from Pascal Quantin --- Hi Conall, 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

[Wireshark-bugs] [Bug 13926] TCAP SRT Analysis incorrectly matched TCAP begins and ends

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13926 --- Comment #10 from conall.prenderg...@anam.com --- Hi Pascal, >From my understanding, the following rules will always apply to a tcap transaction. Given that entity A sends a BEGIN to entity B. For TCAP CONTINUEs to A: The dtid and

[Wireshark-bugs] [Bug 13926] TCAP SRT Analysis incorrectly matched TCAP begins and ends

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13926 --- Comment #9 from Pascal Quantin --- (In reply to conall.prendergast from comment #8) > Could we use the SCCP calling GT? > Taking into account a possible change in the first replay, as mentioned by > Vasil

[Wireshark-bugs] [Bug 13926] TCAP SRT Analysis incorrectly matched TCAP begins and ends

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13926 --- Comment #8 from conall.prenderg...@anam.com --- Could we use the SCCP calling GT? Taking into account a possible change in the first replay, as mentioned by Vasil here. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13739#c6 --

[Wireshark-bugs] [Bug 13926] TCAP SRT Analysis incorrectly matched TCAP begins and ends

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13926 --- Comment #7 from Pascal Quantin --- So this capture is the opposite of bug 13739. We have a match both for the source tid / source address, and destination tid / destination address. Either we test first with

[Wireshark-bugs] [Bug 13926] TCAP SRT Analysis incorrectly matched TCAP begins and ends

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13926 --- Comment #6 from Pascal Quantin --- Given than code points can also change and cannot be used as part of the key to find matches, I do not see how to solve this for now. How can we differentiate that the end

[Wireshark-bugs] [Bug 13926] TCAP SRT Analysis incorrectly matched TCAP begins and ends

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13926 --- Comment #5 from conall.prenderg...@anam.com --- 4c585f would be the otid in this case. That TCAP END is being sent by OPC=11334. -- You are receiving this mail because: You are watching all bug

[Wireshark-bugs] [Bug 13926] TCAP SRT Analysis incorrectly matched TCAP begins and ends

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13926 --- Comment #4 from Pascal Quantin --- I saw that they use one common tid. But packet 5 is using source tid 4c585f and packet 17 is using destination tid aad0. Based on the previous logs in bug 13739, I would

[Wireshark-bugs] [Bug 13926] TCAP SRT Analysis incorrectly matched TCAP begins and ends

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13926 --- Comment #3 from conall.prenderg...@anam.com --- Hi Pascal, Apologies for the confusion. In the trace above, there are two distinct TCAP transactions, but they happen to use a common transaction ID (ad0). You are correct in saying

[Wireshark-bugs] [Bug 13926] TCAP SRT Analysis incorrectly matched TCAP begins and ends

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13926 Pascal Quantin changed: What|Removed |Added CC|

[Wireshark-bugs] [Bug 13926] TCAP SRT Analysis incorrectly matched TCAP begins and ends

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13926 --- Comment #1 from conall.prenderg...@anam.com --- Correction. v2.2.7 does not address the issue in bug 13737 -- You are receiving this mail because: You are watching all bug