Wireshark-users: [Wireshark-users] [Bug 3360] Wireshark gives decoding error during rnsap message
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."
