Wireshark · Wireshark-users: Re: [Wireshark-users] [Bug 3360] Wiresharkgivesdecodingerrorduring rnsap messagedissection

["Anders Broman" <a.broman@xxxxxxxxx>]

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