https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=3495
--- Comment #13 from Tobias Witek <witek@xxxxxx> 2009-08-26 02:23:33 PDT ---
Hi Vincent,
what kind of trace format are you using (PCAP/Catapult DCT2000/Tektronix
K12/K15)?
In general, you need two things:
* Somewhere to start dissecting and branch off into the correct dissector (in
my case, this is the ATM dissector, which calls the FP dissector from its AAL2
code)
* Additional information required by FP, MAC, RLC and RRC that is stored on a
per-packet basis using p_add_proto_data() - this includes information such as
the number of TBs, TF channel sizes, etc. (this information cannot easily be
derived from the raw trace data)
You need to fill these fields for MAC, RLC, RRC and also FP. The FP data such
as TF channel size and number of TBs is required by the MAC dissector to
correctly extract the payload data. Maybe this should be changed, though. I am
not sure how the FP information translates to your situation.
If you have traces that contain only the RRC data (i.e. no RLC/MAC below), you
would only need to fill the per-packet information (rrc_info) for RRC with the
correct message type (i.e. UL CCCH, DL DCCH, ...).
Hopefully, this has answered some of your questions. If there's any further
information you require, I'll gladly provide it.
Best regards,
Tobias
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.