Hi, A quick fix to packet-per.c the displayed value will be wrong though. Regards Anders
________________________________ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Anders Broman (AL/EAB) Sent: den 30 augusti 2007 15:16 To: Developer support list for Wireshark Subject: Re: [Wireshark-dev] RRC Messages does not decode correctely Hi, RRC is using unaligned PER I think. This is not so well tested so there might be a problem in packet-per.c. If you go to edit->preferences->per and tick the box about detailed per decoding it might be possible to se if "byte aligning" is taking place where it should not. Regards Anders ________________________________ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: den 30 augusti 2007 13:09 To: Developer support list for Wireshark; Community support list for Wireshark Subject: [Wireshark-dev] RRC Messages does not decode correctely Hi, 0000 4a 88 02 af 20 19 75 46 6c ce 7e 62 e6 72 2a ac 0010 10 bf 4e ff ff ff ff e7 ef f7 d2 69 ff e2 ec 04 0020 40 I am sending this hex dump to RRC this is a rrc connection setup complete message. RRC dissector decode thsi message correctely , this is rrc connection setup complete but does not decode whole message correctely. For eg in this message in Item 0 and Item 1 both are showing CS domain, (But if same hex dump decode by another tool it decode correctely one Item is CS domain another is PS domain). RRC ASN is correct. this type of some errors comes duringrrc decoding. please tell what is the problem? Radio Resource Control (RRC) protocol UL-DCCH-Message message: rrcConnectionSetupComplete (18) rrcConnectionSetupComplete rrc-TransactionIdentifier: 0 startList: 2 items Item 0 Item cn-DomainIdentity: cs-domain (0) start-Value: 02AF20 Item 1 Item cn-DomainIdentity: cs-domain (0) start-Value: 197546 ue-RadioAccessCapability pdcp-Capability .... .1.. losslessSRNS-RelocationSupport: True supportForRfc2507: supported (1) supported: by1024 (1) rlc-Capability totalRLC-AM-BufferSize: kb500 (5) maximumRLC-WindowSize: mws4095 (1) maximumAM-EntityNumber: am4 (1) transportChannelCapability dl-TransChCapability maxNoBitsReceived: b20480 (9) maxConvCodeBitsReceived: b163840 (12) turboDecodingSupport: supported (1) supported: Unknown (15) maxSimultaneousTransChs: e16 (2) maxSimultaneousCCTrCH-Count: 4 maxReceivedTransportBlocks: tb8 (1) maxNumberOfTFC: tfc512 (7) maxNumberOfTF: tf64 (1) ul-TransChCapability maxNoBitsTransmitted: b20480 (9) maxConvCodeBitsTransmitted: b163840 (12) turboEncodingSupport: supported (1) supported: b1280 (1) maxSimultaneousTransChs: e8 (2) modeSpecificInfo: tdd (1) tdd maxSimultaneousCCTrCH-Count: 3 maxTransmittedBlocks: Unknown (11) maxNumberOfTFC: dummy1 (0) maxNumberOfTF: tf128 (2) rf-Capability physicalChannelCapability tddPhysChCapability downlinkPhysChCapability maxTS-PerFrame: 8 maxPhysChPerFrame: 234 minimumSF: sf16 (1) .... ..1. supportOfPDSCH: True maxPhysChPerTS: 8 uplinkPhysChCapability maxTS-PerFrame: 16 maxPhysChPerTimeslot: ts2 (1) minimumSF: Unknown (7) ...1 .... supportOfPUSCH: True ue-MultiModeRAT-Capability multiRAT-CapabilityList .... 1... supportOfGSM: True .... .1.. supportOfMulticarrier: True multiModeCapability: Unknown (3) securityCapability cipheringAlgorithmCap: FFFF integrityProtectionAlgorithmCap: E7EF ue-positioning-Capability 1... .... standaloneLocMethodsSupported: True .1.. .... ue-BasedOTDOA-Supported: True networkAssistedGPS-Supported: noNetworkAssistedGPS (3) .... 0... supportForUE-GPS-TimingOfCellFrames: False .... .1.. supportForIPDL: True v370NonCriticalExtensions rrcConnectionSetupComplete-v370ext ue-RadioAccessCapability-v370ext ue-RadioAccessCapabBandFDDList: 7 items Item 0 Item radioFrequencyBandFDD: fdd1900 (1) fddRF-Capability ue-PowerClass: class2 (1) txRxFrequencySeparation: spare1 (2) measurementCapability compressedModeMeasCapabFDDList: 8 items Item 0 Item radioFrequencyBandFDD: extension-indicator (7) .... ..1. dl-MeasurementsFDD: True .... ...1 ul-MeasurementsFDD: True Item 1 Item radioFrequencyBandFDD: bandVII (6) .... 0... dl-MeasurementsFDD: False .... .0.. ul-MeasurementsFDD: False Item 2 Item radioFrequencyBandFDD: bandVI (3) ..1. .... dl-MeasurementsFDD: True ...0 .... ul-MeasurementsFDD: False Item 3 Item radioFrequencyBandFDD: bandIV (4) 0... .... dl-MeasurementsFDD: False .0.. .... ul-MeasurementsFDD: False Item 4 Item ...0 .... dl-MeasurementsFDD: False .... 0... ul-MeasurementsFDD: False Item 5 Item radioFrequencyBandFDD: fdd2100 (0) .1.. .... dl-MeasurementsFDD: True ..0. .... ul-MeasurementsFDD: False Item 6 Item .... 0... dl-MeasurementsFDD: False .... .0.. ul-MeasurementsFDD: False Item 7 Item .... ...0 dl-MeasurementsFDD: False [Malformed Packet: RRC] 0000 4a 88 02 af 20 19 75 46 6c ce 7e 62 e6 72 2a ac J... .uF l.~b.r*. 0010 10 bf 4e ff ff ff ff e7 ef f7 d2 69 ff e2 ec 04 ..N..... ...i.... 0020 40 Thanks & Regards, Vaibhav *********************** Aricent-Unclassified *********************** "DISCLAIMER: This message is proprietary to Aricent and is intended solely for the use of the individual to whom it is addressed. It may contain privileged or confidential information and should not be circulated or used for any purpose other than for what it is intended. If you have received this message in error, please notify the originator immediately. If you are not the intended recipient, you are notified that you are strictly prohibited from using, copying, altering, or disclosing the contents of this message. Aricent accepts no responsibility for loss or damage arising from the use of the information transmitted by this email including damage from virus."
per.diff
Description: per.diff
_______________________________________________ Wireshark-dev mailing list [email protected] http://www.wireshark.org/mailman/listinfo/wireshark-dev
