http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=2509
--- Comment #5 from João Fonseca <j.pedro.fonseca@xxxxxxxxxxxxxxx> 2008-04-30 03:30:57 GMT ---
(In reply to comment #3)
> Hmmm, I'm not sure I agree that your patch makes sense.
>
> The assoc data is supposed to span multiple messages (I guess it's named
> "assoc" so that multiple messages are "assoc"iated together?). I think its
> primary purpose is for Class-2 where the data messages don't have the SSN on
> them: this structure lets us know what the SSN for the _connection_ is.
>
I must admit I'm not at all familiar with the SCCP protocol. But, from what I
understand from your words, the assoc variable keeps connection state between
several packets.
If so, isn't this the source of the problem? If the capture contains multiple
connections, a single assoc variable isn't enough. It should be a lookup table,
containing the state for each connection, indexed by some kind of connection
ID.
Does this make sense?
--
Configure bugmail: http://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
