Wireshark-bugs: [Wireshark-bugs] [Bug 3758] M3UA version 5 packet dissecting issue
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Tue, 21 Jul 2009 02:40:25 -0700 (PDT)
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=3758





--- Comment #12 from Jack Liu <congliulyc@xxxxxxxxx>  2009-07-21 02:40:24 PDT ---
Hi, Michael,
I still have difficulty in understanding the code, and very painful in
developing the M2UA V2 dissector. 

I found the the explanation of the parameter length definition of V2: the value
of length is only for the value. The parameter hdeader(tag and the length) are
*NOT* included. That is why in V2, the length is 4, not 8. 

You stated that "Length=8 is coded nowhere".

Here are my concerns:
1. How does Wireshark know the expected value is 8? How does the "Malformed
pakcet" string come up?
2. I want to decode tvb in V2 way, any way to control the offset? In
packet-m3ua.c #1298~#1323, I do not see any offset control. How does Wireshark
which parameter block it is dissecting? 

Maybe my questions are stupid, thanks very much. Michael.


-- 
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.