Wireshark-dev: Re: [Wireshark-dev] RRC Messages does not decode correctely
From: "Anders Broman" <a.broman@xxxxxxxxx>
Date: Thu, 30 Aug 2007 21:42:28 +0200
Hi, The problem is how to handle bitstrings of 17-65k bits length I don't really fancy doing for(i=0;i<min_len;i++){ offset=dissect_per_boolean(tvb, offset, actx, tree, -1, &bit); bytes[0]=(bytes[0]<<1)|bit; } Etc for 65k long ones... I don't know how usual really long bitstrings are perhaps we could only display the value for the ones up to 32 bits? Would a display like ...0 0000 (etc) 00.. Be better? Regards Anders -----Ursprungligt meddelande----- Från: wireshark-dev-bounces@xxxxxxxxxxxxx [mailto:wireshark-dev-bounces@xxxxxxxxxxxxx] För Martin Andersson Skickat: den 30 augusti 2007 19:48 Till: Developer support list for Wireshark Ämne: Re: [Wireshark-dev] RRC Messages does not decode correctely Anders Broman (AL/EAB) wrote: > Hi, > A quick fix to packet-per.c the displayed value will be wrong though. Hej Anders As referense how the value should be decoded (the bitstring are in hex in wireshark). rg/Martin value UL-DCCH-Message ::= { message rrcConnectionSetupComplete : { rrc-TransactionIdentifier 0, startList { { cn-DomainIdentity cs-domain, start-Value '00000000 10101011 1100'B }, { cn-DomainIdentity ps-domain, start-Value '00000000 11001011 1010'B } }, ue-RadioAccessCapability { pdcp-Capability { losslessSRNS-RelocationSupport FALSE, supportForRfc2507 supported : dummy }, rlc-Capability { totalRLC-AM-BufferSize kb1000, maximumRLC-WindowSize mws2047, maximumAM-EntityNumber am30 }, transportChannelCapability { dl-TransChCapability { maxNoBitsReceived b163840, maxConvCodeBitsReceived b163840, turboDecodingSupport supported : b163840, maxSimultaneousTransChs e32, maxSimultaneousCCTrCH-Count 8, maxReceivedTransportBlocks tb512, maxNumberOfTFC tfc1024, maxNumberOfTF tf1024 }, ul-TransChCapability { maxNoBitsTransmitted b163840, maxConvCodeBitsTransmitted b163840, turboEncodingSupport supported : b163840, maxSimultaneousTransChs e32, modeSpecificInfo fdd : NULL, maxTransmittedBlocks tb512, maxNumberOfTFC tfc1024, maxNumberOfTF tf1024 } }, rf-Capability { fddRF-Capability { ue-PowerClass 1, txRxFrequencySeparation default-TxRx-separation } }, physicalChannelCapability { fddPhysChCapability { downlinkPhysChCapability { maxNoDPCH-PDSCH-Codes 1, maxNoPhysChBitsReceived b48000, supportForSF-512 TRUE, dummy TRUE, dummy2 supported : { maxNoSCCPCH-RL rl1, simultaneousSCCPCH-DPCH-DPDCH-Reception TRUE } }, uplinkPhysChCapability { maxNoDPDCH-BitsTransmitted b9600, dummy TRUE } } }, ue-MultiModeRAT-Capability { multiRAT-CapabilityList { supportOfGSM TRUE, supportOfMulticarrier TRUE }, multiModeCapability fdd }, securityCapability { cipheringAlgorithmCap { spare15, spare14, spare13, spare12, spare11, spare10, spare9, spare8, spare7, spare6, spare5, spare4, spare3, spare2, uea1, uea0 }, integrityProtectionAlgorithmCap { spare15, spare14, spare13, spare12, spare11, spare10, spare9, spare8, spare7, spare6, spare5, spare4, spare3, spare2, uia1, spare0 } }, ue-positioning-Capability { standaloneLocMethodsSupported TRUE, ue-BasedOTDOA-Supported TRUE, networkAssistedGPS-Supported networkBased, supportForUE-GPS-TimingOfCellFrames TRUE, supportForIPDL TRUE }, measurementCapability { downlinkCompressedMode { fdd-Measurements TRUE, tdd-Measurements FALSE, gsm-Measurements { gsm900 TRUE, dcs1800 TRUE, gsm1900 TRUE }, multiCarrierMeasurements TRUE }, uplinkCompressedMode { fdd-Measurements TRUE, tdd-Measurements FALSE, gsm-Measurements { gsm900 TRUE, dcs1800 TRUE, gsm1900 TRUE }, multiCarrierMeasurements TRUE } } }, v370NonCriticalExtensions { rrcConnectionSetupComplete-v370ext { }, v380NonCriticalExtensions { rrcConnectionSetupComplete-v380ext { dl-PhysChCapabilityFDD-v380ext { } }, v3a0NonCriticalExtensions { rrcConnectionSetupComplete-v3a0ext { }, laterNonCriticalExtensions { v3g0NonCriticalExtensions { rrcConnectionSetupComplete-v3g0ext { }, v4b0NonCriticalExtensions { rrcConnectionSetupComplete-v4b0ext { }, v590NonCriticalExtensions { rrcConnectionSetupComplete-v590ext { ue-RadioAccessCapability-v590ext { dl-CapabilityWithSimultaneousHS-DSCHConfig kbps384, pdcp-Capability-r5-ext { supportForRfc3095ContextRelocation TRUE, maxHcContextSpace by131072 }, rlc-Capability-r5-ext { totalRLC-AM-BufferSize kb750 }, physicalChannelCapability { fdd-hspdsch supported : { hsdsch-physical-layer-category 12, dummy TRUE, dummy2 FALSE }, tdd384-hspdsch unsupported : NULL, tdd128-hspdsch unsupported : NULL }, multiModeRAT-Capability-v590ext { supportOfUTRAN-ToGERAN-NACC FALSE } }, ue-RATSpecificCapability-v590ext { geranIu-RadioAccessCapability '001'B } } } } } } } } } } } _______________________________________________ Wireshark-dev mailing list Wireshark-dev@xxxxxxxxxxxxx http://www.wireshark.org/mailman/listinfo/wireshark-dev
- Follow-Ups:
- Re: [Wireshark-dev] RRC Messages does not decode correctely
- From: Martin Andersson
- Re: [Wireshark-dev] RRC Messages does not decode correctely
- References:
- Re: [Wireshark-dev] RRC Messages does not decode correctely
- From: Martin Andersson
- Re: [Wireshark-dev] RRC Messages does not decode correctely
- Prev by Date: Re: [Wireshark-dev] Broken windows build
- Next by Date: Re: [Wireshark-dev] RRC Messages does not decode correctely
- Previous by thread: Re: [Wireshark-dev] RRC Messages does not decode correctely
- Next by thread: Re: [Wireshark-dev] RRC Messages does not decode correctely
- Index(es):