Wireshark mailing list archives
Re: bssmap malformed packet
From: Anders Broman <anders.broman () ericsson com>
Date: Mon, 13 Sep 2010 17:06:11 +0200
Hi, I'm not sure what you mean but .... ..1. Optional Field Bit: True (v3a0NonCriticalExtensions is present) ..1. .... Optional Field Bit: True (laterNonCriticalExtensions is present) .... .1.. Optional Field Bit: True (v3g0NonCriticalExtensions is present) .... ...1 Optional Field Bit: True (v4b0NonCriticalExtensions is present) It might be that some optional field bit present/not present indicator is missing? Forinstance v4d0NonCriticalExtensions. Regards Anders ________________________________ From: wireshark-users-bounces () wireshark org [mailto:wireshark-users-bounces () wireshark org] On Behalf Of damker Sent: den 13 september 2010 15:59 To: 'Community support list for Wireshark' Subject: Re: [Wireshark-users] bssmap malformed packet If it do not contain "additional R99 extensions" cause it's optional ? and the last 5 octet "38 03 f5 02 eb" is for other bssmap element ? Hi, Looks to me likeInterRATHandoverInfo has been cut short, does the decoding look right up to accessStratumReleaseIndicator: rel-5 (1) ? If so I think somethingh is missing in the message. Regards Anders InterRATHandoverInfo ::= SEQUENCE { -- This structure is defined for historical reasons, backward compatibility with 44.018 predefinedConfigStatusList CHOICE { absent NULL, present PredefinedConfigStatusList }, uE-SecurityInformation CHOICE { absent NULL, present UE-SecurityInformation }, ue-CapabilityContainer CHOICE { absent NULL, -- present is an octet aligned string containing IE UE-RadioAccessCapabilityInfo present OCTET STRING (SIZE (0..63)) }, -- Non critical extensions v390NonCriticalExtensions CHOICE { absent NULL, present SEQUENCE { interRATHandoverInfo-v390ext InterRATHandoverInfo-v390ext-IEs, v3a0NonCriticalExtensions SEQUENCE { interRATHandoverInfo-v3a0ext InterRATHandoverInfo-v3a0ext-IEs, laterNonCriticalExtensions SEQUENCE { interRATHandoverInfo-v3d0ext InterRATHandoverInfo-v3d0ext-IEs, -- Container for additional R99 extensions interRATHandoverInfo-r3-add-ext BIT STRING (CONTAINING InterRATHandoverInfo-r3-add-ext-IEs) OPTIONAL, v3g0NonCriticalExtensions SEQUENCE { interRATHandoverInfo-v3g0ext InterRATHandoverInfo-v3g0ext-IEs, v4b0NonCriticalExtensions SEQUENCE { interRATHandoverInfo-v4b0ext InterRATHandoverInfo-v4b0ext-IEs, v4d0NonCriticalExtensions SEQUENCE { interRATHandoverInfo-v4d0ext InterRATHandoverInfo-v4d0ext-IEs, -- Reserved for future non critical extension v590NonCriticalExtensions SEQUENCE { interRATHandoverInfo-v590ext InterRATHandoverInfo-v590ext-IEs, v690NonCriticalExtensions SEQUENCE { interRATHandoverInfo-v690ext InterRATHandoverInfo-v690ext-IEs, v6b0NonCriticalExtensions InterRATHandoverInfo-NonCriticalExtension-v6b0-IEs OPTIONAL } OPTIONAL } OPTIONAL } OPTIONAL } OPTIONAL } OPTIONAL } OPTIONAL } OPTIONAL } } } ________________________________ From: wireshark-users-bounces () wireshark org [mailto:wireshark-users-bounces () wireshark org] On Behalf Of damker Sent: den 13 september 2010 12:31 To: 'Community support list for Wireshark' Subject: [Wireshark-users] bssmap malformed packet Hi all Attachment file is bssmap malformed packet , might be because of element coding not updated.
___________________________________________________________________________ Sent via: Wireshark-users mailing list <wireshark-users () wireshark org> Archives: http://www.wireshark.org/lists/wireshark-users Unsubscribe: https://wireshark.org/mailman/options/wireshark-users mailto:wireshark-users-request () wireshark org?subject=unsubscribe
Current thread:
- How to use wireshark for capture Soap Messages Victor Hugo Jabur Passavaz (Sep 10)
- Re: How to use wireshark for capture Soap Messages Martin Visser (Sep 11)
- Re: How to use wireshark for capture Soap Messages Victor Hugo Jabur Passavaz (Sep 12)
- bssmap malformed packet damker (Sep 13)
- Re: bssmap malformed packet Anders Broman (Sep 13)
- Re: bssmap malformed packet damker (Sep 13)
- Re: bssmap malformed packet Anders Broman (Sep 13)
- Bug 1029 - Tshark -R doesn't support "frame.time >= Jul 20, 2006 17:51:38.368" Steve Evans (Sep 13)
- Re: Bug 1029 - Tshark -R doesn't support "frame.time >= Jul 20, 2006 17:51:38.368" Jeff Morriss (Sep 14)
- Re: Bug 1029 - Tshark -R doesn't support "frame.time >= Jul 20, 2006 17:51:38.368" Steve Evans (Sep 14)
- Re: Bug 1029 - Tshark -R doesn't support "frame.time >= Jul 20, 2006 17:51:38.368" Jeff Morriss (Sep 14)
- Re: Bug 1029 - Tshark -R doesn't support " frame.time > = Jul 20, 2006 17:51:38.368" Christopher Maynard (Sep 14)
- Re: Bug 1029 - Tshark -R doesn't support " frame.time > = Jul 20, 2006 17:51:38.368" Steve Evans (Sep 14)
- Re: Bug 1029 - Tshark -R doesn't support "frame.time >= Jul 20, 2006 17:51:38.368" Steve Evans (Sep 14)
- Re: Bug 1029 - Tshark -R doesn't support "frame.time >= Jul 20, 2006 17:51:38.368" Jeff Morriss (Sep 14)
- Re: How to use wireshark for capture Soap Messages Martin Visser (Sep 11)