https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=5511
Martin Mathieson <martin.r.mathieson@xxxxxxxxxxxxxx> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |martin.r.mathieson@googlema
| |il.com
--- Comment #1 from Martin Mathieson <martin.r.mathieson@xxxxxxxxxxxxxx> 2010-12-21 10:07:06 PST ---
(In reply to comment #0)
> Created an attachment (id=5650)
--> (https://bugs.wireshark.org/bugzilla/attachment.cgi?id=5650) [details]
> This is a text file of the captured data. We can open with Wireshark for output
>
> Build Information:
> Paste the COMPLETE build information from "Help->About Wireshark", "wireshark
> -v", or "tshark -v".
> --
> All RRC message will go on either SRB0 or SRB1 or SRB2.But i am getting fixed
> value in decimal 170 which corresponding hex value is 0xaa.
> I have attached my data capture text file which can be open in wireshark.
>
> In function static void dissect_rrc_lte(tvbuff_t *tvb, gint offset,
> packet_info *pinfo, proto_tree *tree)
> of file wireshark-1.4.2/epan/dissectors/packet-catapult-dct2000.c
>
> at line number 664 there is code
>
> col_append_fstr(pinfo->cinfo, COL_INFO, " SRB:%u",
> tvb_get_guint8(tvb, offset));
>
> It is printing SRB and for %u it is always 170(0xaa).
> Which should be SRB id as 0, 1 or 2.
0xaa (as you'll see from the source) is the tag that precedes that actual RRC
payload. The SRB id should be 1 or 2 - it can't be 0.
I can tell from your file that you're not actually using the DCT2000 (now
IxCatapult) to generate these files. Your file doesn't decode properly using
the IxCatapult decoders or the trunk version of Wireshark. I don't remember
the format ever changing, but it could.
This change may help you
http://anonsvn.wireshark.org/viewvc?view=rev&revision=35050. If it does it can
be queued for 1.4.
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
