https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=6692
--- Comment #9 from Vladimir <boronin@xxxxxxxx> 2012-01-08 05:08:49 PST ---
(In reply to comment #8)
> > Also I can not understand why Wireshark tries to dissect X2AP values as item
> > from RRC protocol?
>
> 3GPP TS 36.423 version 8.5.0 Release 8
> 9.1.1.2 HANDOVER REQUEST ACKNOWLEDGE
>
> Target eNB To Source eNB Transparent Container M OCTET STRING
> Includes the RRC EUTRA Handover Command message as defined in subclause 10.2.2
> in [9]. YES ignore
>
> So infact even if it is an OCTET STRING(opaque structure) in X2AP the content
> is
> an RRC message which contents is specified in [9] 3GPP TS 36.331: "Evolved
> Universal Terrestrial Radio Access (E-UTRAN); Radio Resource
> Control (RRC) Protocol Specification". So wireshark calls the RRC dissector
> to display the actual content of the Target eNB To Source eNB Transparent
> Container which might be useful if the content is correct.
>
> Best regards
> Anders
Hi Anders,
Thank you for clear explanations so, as I understand wireshark tries to dissect
"TargeteNBToSource-eNBTransparentContainer" for HandoverRequestAcknowledge and
"RRC Context" for HandoverRequest as RRC protocol item and due to invalid value
it shows the packed as malformed. Right?
I use eNodeB simulator to encode X2Ap messages and I don't have RRC encoder -
that is why RRC related values are probably incorrect
Just few questions:
1) In wireshark v7 (in comparance with v1.6.4 ) I see that it didn't stopped
(if it is incorrect) in HandoverRequest on dissection of RRC context and
dissected also "UE-HistoryInformation" which present after RRC Context so, I
understand there were additional fixed for this purpose?
2) May be do you have any correct example for RRC related item which I could
fill to check that everything is OK
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
