Wireshark-users: Re: [Wireshark-users] [Bug 3360]Wiresharkgivesdecodingerrorduring rnsap messaged
From: Tapas Chatterjee <tapas.chatterjee@xxxxxxxxxxx>
Date: Thu, 2 Apr 2009 12:02:24 +0530
Hi, I am attaching the correct decoding of the packet no 9.Also current decoding of the packet shown as "UNKNOWN PER: 10.9.3.8.1" after use the SVN 27853 Please help me how to fix the issue? With regards, Tapas -----Original Message----- From: wireshark-users-bounces@xxxxxxxxxxxxx [mailto:wireshark-users-bounces@xxxxxxxxxxxxx] On Behalf Of Tapas Chatterjee Sent: Friday, March 27, 2009 6:13 PM To: Community support list for Wireshark Subject: Re: [Wireshark-users] [Bug 3360]Wiresharkgivesdecodingerrorduring rnsap messagedissection Hi, It won't work in my local build. What ever I do mention below: 1) Copy files packet-per.c & packet-per.h (use SVN 27853) 2) Copy files asn2wrs.py in /tools/ directory 3) Run make copy_files in rnsap, rrc, ranap, nbap, h225 etc. folder 4) Compile the code But when I tried to open the capture file it shows "UNKNOWN PER: 10.9.3.8.1" Could you please help me out? With regards, Tapas -----Original Message----- From: wireshark-users-bounces@xxxxxxxxxxxxx [mailto:wireshark-users-bounces@xxxxxxxxxxxxx] On Behalf Of Anders Broman Sent: Friday, March 27, 2009 12:08 PM To: 'Community support list for Wireshark' Subject: Re: [Wireshark-users] [Bug 3360] Wiresharkgivesdecodingerrorduring rnsap messagedissection Hi, Have you tried buildbot build SVN27853 or later? Regards Anders -----Ursprungligt meddelande----- Från: wireshark-users-bounces@xxxxxxxxxxxxx [mailto:wireshark-users-bounces@xxxxxxxxxxxxx] För Tapas Chatterjee Skickat: den 27 mars 2009 06:00 Till: Community support list for Wireshark Ämne: Re: [Wireshark-users] [Bug 3360] Wiresharkgivesdecodingerrorduring rnsap messagedissection Hi, I got your point. Could you please tell me any way to fix this problem? And for next problem I have removed duplicate messages but still it gives same decoding error. With regards, Tapas -----Original Message----- From: wireshark-users-bounces@xxxxxxxxxxxxx [mailto:wireshark-users-bounces@xxxxxxxxxxxxx] On Behalf Of Anders Broman Sent: Thursday, March 26, 2009 9:34 PM To: Community support list for Wireshark Subject: Re: [Wireshark-users] [Bug 3360] Wireshark givesdecodingerrorduring rnsap messagedissection Hi, Wireshark didn't take >Neighbouring-FDD-CellInformation ::= SEQUENCE ( SIZE >(1..maxNrOfFDDNeighboursPerRNC,...)) OF >Neighbouring-FDD-CellInformationItem >E.g the SEQUENCE OF constraint has extension which is not catered for in Wireshark Into account which lead to it beeing one bit off in the decoding. The next problem is with reasembly I beleve, in the trace the same message are sent 2 or 3 times Which I think messes up reassembly... Regards Anders -----Original Message----- From: wireshark-users-bounces@xxxxxxxxxxxxx [mailto:wireshark-users-bounces@xxxxxxxxxxxxx] On Behalf Of Tapas Chatterjee Sent: den 26 mars 2009 10:30 To: Community support list for Wireshark Subject: Re: [Wireshark-users] [Bug 3360] Wireshark gives decodingerrorduring rnsap messagedissection Hi, Yea the rnsap_packet.txt file dissection result and my internal tools dissection result are same. Could you please tell me what way you fix it? Also the packet number 10 gives dissection error. With regards, Tapas -----Original Message----- From: wireshark-users-bounces@xxxxxxxxxxxxx [mailto:wireshark-users-bounces@xxxxxxxxxxxxx] On Behalf Of Anders Broman Sent: Thursday, March 26, 2009 2:37 PM To: Community support list for Wireshark Subject: Re: [Wireshark-users] [Bug 3360] Wireshark gives decodingerrorduring rnsap messagedissection Hi, Does this decoding look right to you? Fore some reeason dissecting the actual trace with my fix does not work(reassembly???) but I extracted the rnsap data And used text2pcap to crate a new packet. ( Edit->preferenses_>protocols->DLT_USER 150 -> rnsap). Regards Anders -----Original Message----- From: wireshark-users-bounces@xxxxxxxxxxxxx [mailto:wireshark-users-bounces@xxxxxxxxxxxxx] On Behalf Of Tapas Chatterjee Sent: den 26 mars 2009 05:41 To: Community support list for Wireshark Subject: Re: [Wireshark-users] [Bug 3360] Wireshark gives decoding errorduring rnsap messagedissection Hi, I am decoding the message some of our internal tools (based on ASN) which gives the correct decoding result. So I think there is no error in the message. Regards Tapas -----Original Message----- From: wireshark-users-bounces@xxxxxxxxxxxxx [mailto:wireshark-users-bounces@xxxxxxxxxxxxx] On Behalf Of Anders Broman Sent: Wednesday, March 25, 2009 10:38 PM To: Community support list for Wireshark Subject: Re: [Wireshark-users] [Bug 3360] Wireshark gives decoding errorduring rnsap messagedissection Hi, Do you have a "Correct" decoding by some other tool? I think the problem may be due to: Neighbouring-FDD-CellInformation ::= SEQUENCE ( SIZE (1..maxNrOfFDDNeighboursPerRNC,...)) OF Neighbouring-FDD-CellInformationItem E.g the SEQUENCE OF constraint has extension which is not catered for in Wireshark but when I try to fix it I get strange results :-( Regards Anders -----Original Message----- From: wireshark-users-bounces@xxxxxxxxxxxxx [mailto:wireshark-users-bounces@xxxxxxxxxxxxx] On Behalf Of Tapas Chatterjee Sent: den 25 mars 2009 13:11 To: wireshark-users@xxxxxxxxxxxxx Subject: [Wireshark-users] [Bug 3360] Wireshark gives decoding error during rnsap messagedissection Hi, It is going right up to rNC ID: 109 after its start dissection "neighbouring-FDD-CellInformation" Where C-ID the value decode now "8448" Hex "20 01" instead "331" Hex "01 4b" So offset movement start's going wrong here. Hope this info may help you. Any clarity further let me know. With regards Tapas -----Original Message----- From: bugzilla-daemon@xxxxxxxxxxxxx [mailto:bugzilla-daemon@xxxxxxxxxxxxx] Sent: Wednesday, March 25, 2009 5:13 PM To: Tapas Chatterjee Subject: [Bug 3360] Wireshark gives decoding error during rnsap messagedissection https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=3360 Anders Broman <anders.broman@xxxxxxxxxxxx> changed: What |Removed |Added ------------------------------------------------------------------------ ---- CC| |anders.broman@xxxxxxxxxxxx --- Comment #1 from Anders Broman <anders.broman@xxxxxxxxxxxx> 2009-03-25 04:43:07 PDT --- Hi, Looking at packet 9 txDiversityIndicator: true (0) 0e0 2a 0a 00 -- The next is the iE-Extensions ProtocolExtensionContainer { { Neighbouring-FDD-CellInformationItem-ExtIEs} } OPTIONAL, .Sequence-Of Length: 46338 00e0 2a 0a 00 b5 01 ----- So here's where it start's to go wrong is the decoding up to here looking ok? or is WS missing some mandatorry element? Should it have been on octet further eg '01' insted can you pinpoint more exactly waht's wrong up to here? Regards Anders -- Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You reported the bug. "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." ________________________________________________________________________ ___ Sent via: Wireshark-users mailing list <wireshark-users@xxxxxxxxxxxxx> Archives: http://www.wireshark.org/lists/wireshark-users Unsubscribe: https://wireshark.org/mailman/options/wireshark-users mailto:wireshark-users-request@xxxxxxxxxxxxx?subject=unsubscribe ________________________________________________________________________ ___ Sent via: Wireshark-users mailing list <wireshark-users@xxxxxxxxxxxxx> Archives: http://www.wireshark.org/lists/wireshark-users Unsubscribe: https://wireshark.org/mailman/options/wireshark-users mailto:wireshark-users-request@xxxxxxxxxxxxx?subject=unsubscribe "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." ________________________________________________________________________ ___ Sent via: Wireshark-users mailing list <wireshark-users@xxxxxxxxxxxxx> Archives: http://www.wireshark.org/lists/wireshark-users Unsubscribe: https://wireshark.org/mailman/options/wireshark-users mailto:wireshark-users-request@xxxxxxxxxxxxx?subject=unsubscribe "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." ________________________________________________________________________ ___ Sent via: Wireshark-users mailing list <wireshark-users@xxxxxxxxxxxxx> Archives: http://www.wireshark.org/lists/wireshark-users Unsubscribe: https://wireshark.org/mailman/options/wireshark-users mailto:wireshark-users-request@xxxxxxxxxxxxx?subject=unsubscribe ___________________________________________________________________________ Sent via: Wireshark-users mailing list <wireshark-users@xxxxxxxxxxxxx> Archives: http://www.wireshark.org/lists/wireshark-users Unsubscribe: https://wireshark.org/mailman/options/wireshark-users mailto:wireshark-users-request@xxxxxxxxxxxxx?subject=unsubscribe "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." ___________________________________________________________________________ Sent via: Wireshark-users mailing list <wireshark-users@xxxxxxxxxxxxx> Archives: http://www.wireshark.org/lists/wireshark-users Unsubscribe: https://wireshark.org/mailman/options/wireshark-users mailto:wireshark-users-request@xxxxxxxxxxxxx?subject=unsubscribe ___________________________________________________________________________ Sent via: Wireshark-users mailing list <wireshark-users@xxxxxxxxxxxxx> Archives: http://www.wireshark.org/lists/wireshark-users Unsubscribe: https://wireshark.org/mailman/options/wireshark-users mailto:wireshark-users-request@xxxxxxxxxxxxx?subject=unsubscribe "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." ___________________________________________________________________________ Sent via: Wireshark-users mailing list <wireshark-users@xxxxxxxxxxxxx> Archives: http://www.wireshark.org/lists/wireshark-users Unsubscribe: https://wireshark.org/mailman/options/wireshark-users mailto:wireshark-users-request@xxxxxxxxxxxxx?subject=unsubscribe "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."
RNSAP-PDU (CHOICE, header)
{
successfulOutcome (SEQUENCE, choice)
{
procedureID (SEQUENCE, mandatory)
{
procedureCode (INTEGER) = 19
ddMode (INTEGER) = fdd
}
criticality (INTEGER) = reject
transactionID (CHOICE, mandatory)
{
longTransActionId (INTEGER) = 0
}
value (ANY, mandatory)
{
RLSetupRespFDD (SEQUENCE, header)
{
protocolIEs (SEQUENCE OF, mandatory)
{
elem_0 (SEQUENCE, multiple)
{
id (INTEGER) = 21
criticality (INTEGER) = ignore
value (ANY, mandatory)
{
D-RNTI (INTEGER) = 24705
}
}
elem_1 (SEQUENCE, multiple)
{
id (INTEGER) = 10
criticality (INTEGER) = ignore
value (ANY, mandatory)
{
CN-PS-DomainIdentifier (SEQUENCE, header)
{
pLMN-Identity (OCTET STRING) =
62F211
lAC (OCTET STRING) =
05E7
rAC (OCTET STRING) =
01
}
}
}
elem_2 (SEQUENCE, multiple)
{
id (INTEGER) = 9
criticality (INTEGER) = ignore
value (ANY, mandatory)
{
CN-CS-DomainIdentifier (SEQUENCE, header)
{
pLMN-Identity (OCTET STRING) =
62F211
lAC (OCTET STRING) =
05E7
}
}
}
elem_3 (SEQUENCE, multiple)
{
id (INTEGER) = 137
criticality (INTEGER) = ignore
value (ANY, mandatory)
{
RL-InfoRespList-RL-SetupRspFDD (SEQUENCE OF, header)
{
elem_0 (SEQUENCE, multiple)
{
id (INTEGER) = 133
criticality (INTEGER) = ignore
value (ANY, mandatory)
{
RL-InfoRespItem-RL-SetupRspFDD (SEQUENCE, header)
{
rL-ID (INTEGER) = 2
rL-Set-ID (INTEGER) = 2
sAI (SEQUENCE, mandatory)
{
pLMN-Identity (OCTET STRING) =
62F211
lAC (OCTET STRING) =
05E7
sAC (OCTET STRING) =
000B
}
received-total-wide-band-power (INTEGER) = 245
dl-CodeInfo (SEQUENCE OF, mandatory)
{
elem_0 (SEQUENCE, multiple)
{
dl-ScramblingCode (INTEGER) = 0
fDD-DL-ChCodeNumber (INTEGER) = 2
}
}
diversityInd (CHOICE, mandatory)
{
nonCombiningOrFirstRL (SEQUENCE, choice)
{
dCH-InfoResp (SEQUENCE OF, mandatory)
{
elem_0 (SEQUENCE, multiple)
{
dCH-ID (INTEGER) = 24
bindingID (CHOICE, optional)
{
normally (OCTET STRING) =
18A60000
}
transportLayerAddress (CHOICE, optional)
{
normally (BIT STRING) =
00110101000000000000000100001010000110010111110101011001
00000000000000000000000000000000000000000000000000000000
0000000000000000
}
}
elem_1 (SEQUENCE, multiple)
{
dCH-ID (INTEGER) = 1
bindingID (CHOICE, optional)
{
normally (OCTET STRING) =
18A80000
}
transportLayerAddress (CHOICE, optional)
{
normally (BIT STRING) =
00110101000000000000000100001010000110010111110101011001
00000000000000000000000000000000000000000000000000000000
0000000000000000
}
}
}
}
}
sSDT-SupportInd (INTEGER) = sSDT-not-supported
maxUL-SIR (INTEGER) = 135
minUL-SIR (INTEGER) = 15
maximumAllowedULTxPower (INTEGER) = 24
maximumDLTxPower (INTEGER) = 35
minimumDLTxPower (INTEGER) = -114
primaryScramblingCode (INTEGER) = 11
primaryCPICH-Power (INTEGER) = 330
neighbouring-UMTS-CellInfo (SEQUENCE OF, optional)
{
elem_0 (SEQUENCE, multiple)
{
id (INTEGER) = 95
criticality (INTEGER) = ignore
value (ANY, mandatory)
{
Neighbouring-UMTS-CellInfoItem (SEQUENCE, header)
{
rNC-ID (INTEGER) = 109
neighbouring-FDD-CellInfo (CHOICE, optional)
{
normally (SEQUENCE OF, choice)
{
elem_0 (SEQUENCE, multiple)
{
c-ID (INTEGER) = 331 //raj =8449
uARFCNforNu (CHOICE, mandatory)
{
normally (INTEGER) = 9812 //raj 38
}
uARFCNforNd (CHOICE, mandatory)
{
normally (INTEGER) = 10762 //raj 42
}
primaryScramblingCode (INTEGER) = 331 //2561
primaryCPICH-Power (INTEGER) = 330 //raj
txDiversityInd (INTEGER) = false //true
//raj
iE-Extensions (SEQUENCE OF, optional)
{
elem_0 (SEQUENCE, multiple)
{
id (INTEGER) = 19
criticality (INTEGER) = ignore
extensionValue (ANY, mandatory)
{
DPC-Mode-Change-SupportInd (INTEGER) = dPC-ModeChangeSupp
}
}
}
}
}
}
}
}
}
elem_1 (SEQUENCE, multiple)
{
id (INTEGER) = 95
criticality (INTEGER) = ignore
value (ANY, mandatory)
{
Neighbouring-UMTS-CellInfoItem (SEQUENCE, header)
{
rNC-ID (INTEGER) = 111
cN-PS-DomainIdentifier (SEQUENCE, optional)
{
pLMN-Identity (OCTET STRING) =
62F211
lAC (OCTET STRING) =
05E6
rAC (OCTET STRING) =
01
}
cN-CS-DomainIdentifier (SEQUENCE, optional)
{
pLMN-Identity (OCTET STRING) =
62F211
lAC (OCTET STRING) =
05E6
}
neighbouring-FDD-CellInfo (CHOICE, optional)
{
normally (SEQUENCE OF, choice)
{
elem_0 (SEQUENCE, multiple)
{
c-ID (INTEGER) = 371 //8193
uARFCNforNu (CHOICE, mandatory)
{
normally (INTEGER) = 9812 //38
}
uARFCNforNd (CHOICE, mandatory)
{
normally (INTEGER) = 10762 //42
}
primaryScramblingCode (INTEGER) = 371 //2561
primaryCPICH-Power (INTEGER) = 330 //raj
txDiversityInd (INTEGER) = false /true
}
}
}
}
}
}
elem_2 (SEQUENCE, multiple)
{
id (INTEGER) = 95
criticality (INTEGER) = ignore
value (ANY, mandatory)
{
Neighbouring-UMTS-CellInfoItem (SEQUENCE, header)
{
rNC-ID (INTEGER) = 110
cN-PS-DomainIdentifier (SEQUENCE, optional)
{
pLMN-Identity (OCTET STRING) =
62F211
lAC (OCTET STRING) =
05E9
rAC (OCTET STRING) =
01
}
cN-CS-DomainIdentifier (SEQUENCE, optional)
{
pLMN-Identity (OCTET STRING) =
62F211
lAC (OCTET STRING) =
05E9
}
neighbouring-FDD-CellInfo (CHOICE, optional)
{
normally (SEQUENCE OF, choice)
{
elem_0 (SEQUENCE, multiple)
{
c-ID (INTEGER) = 181 //raj 8192
uARFCNforNu (CHOICE, mandatory)
{
normally (INTEGER) = 9812 //raj 0
}
uARFCNforNd (CHOICE, mandatory)
{
normally (INTEGER) = 10762 //raj 21504
}
primaryScramblingCode (INTEGER) = 181 //raj 10762
primaryCPICH-Power (INTEGER) = 330 //raj
txDiversityInd (INTEGER) = false //true
}
elem_1 (SEQUENCE, multiple)
{
c-ID (INTEGER) = 351
uARFCNforNu (CHOICE, mandatory)
{
normally (INTEGER) = 9812
}
uARFCNforNd (CHOICE, mandatory)
{
normally (INTEGER) = 10762
}
primaryScramblingCode (INTEGER) = 351
primaryCPICH-Power (INTEGER) = 330
txDiversityInd (INTEGER) = false
//raj----------------------------------------------------------------
}
}
}
}
}
}
elem_3 (SEQUENCE, multiple)
{
id (INTEGER) = 95
criticality (INTEGER) = ignore
value (ANY, mandatory)
{
Neighbouring-UMTS-CellInfoItem (SEQUENCE, header)
{
rNC-ID (INTEGER) = 108
cN-PS-DomainIdentifier (SEQUENCE, optional)
{
pLMN-Identity (OCTET STRING) =
62F211
lAC (OCTET STRING) =
05E6
rAC (OCTET STRING) =
01
}
cN-CS-DomainIdentifier (SEQUENCE, optional)
{
pLMN-Identity (OCTET STRING) =
62F211
lAC (OCTET STRING) =
05E6
}
neighbouring-FDD-CellInfo (CHOICE, optional)
{
normally (SEQUENCE OF, choice)
{
elem_0 (SEQUENCE, multiple)
{
c-ID (INTEGER) = 61
uARFCNforNu (CHOICE, mandatory)
{
normally (INTEGER) = 9812
}
uARFCNforNd (CHOICE, mandatory)
{
normally (INTEGER) = 10762
}
primaryScramblingCode (INTEGER) = 61
primaryCPICH-Power (INTEGER) = 330
txDiversityInd (INTEGER) = false
}
elem_1 (SEQUENCE, multiple)
{
c-ID (INTEGER) = 191
uARFCNforNu (CHOICE, mandatory)
{
normally (INTEGER) = 9812
}
uARFCNforNd (CHOICE, mandatory)
{
normally (INTEGER) = 10762
}
primaryScramblingCode (INTEGER) = 191
primaryCPICH-Power (INTEGER) = 330
txDiversityInd (INTEGER) = false
}
elem_2 (SEQUENCE, multiple)
{
c-ID (INTEGER) = 311
uARFCNforNu (CHOICE, mandatory)
{
normally (INTEGER) = 9812
}
uARFCNforNd (CHOICE, mandatory)
{
normally (INTEGER) = 10762
}
primaryScramblingCode (INTEGER) = 311
primaryCPICH-Power (INTEGER) = 330
txDiversityInd (INTEGER) = false
}
}
}
}
}
}
}
pC-Preamble (CHOICE, mandatory)
{
normally (INTEGER) = 0
}
sRB-Delay (CHOICE, mandatory)
{
normally (INTEGER) = 0
}
}
}
}
}
}
}
elem_4 (SEQUENCE, multiple)
{
id (INTEGER) = 184
criticality (INTEGER) = ignore
value (ANY, mandatory)
{
UL-SIR (INTEGER) = 135
}
}
}
}
}
}
}
- Prev by Date: Re: [Wireshark-users] filtering on Ethernet MAC OUI
- Next by Date: Re: [Wireshark-users] [Wireshark-announce] Question about the private key of a homerouter for SSL decryption
- Previous by thread: Re: [Wireshark-users] Wireshark-users Digest, Vol 35, Issue 1
- Next by thread: Re: [Wireshark-users] [Wireshark-announce] Question about the private key of a homerouter for SSL decryption
- Index(es):