Actions
Bug #2755
closedBSSMAP Cipher Mode Reject lacks the Cause IE
Start date:
12/14/2017
Due date:
% Done:
100%
Spec Reference:
Description
wireshark says:
No. Time Length Source Source Port Destination Destination Port Protocol Media Port Context-ID CN-DomainIndicator Info 337 25.967697395 122 187 185 BSSAP SACK DT1 (BSSMAP) Cipher Mode Reject Frame 337: 122 bytes on wire (976 bits), 122 bytes captured (976 bits) on interface 1 Ethernet II, Src: 00:00:00_00:00:00 (00:00:00:00:00:00), Dst: 00:00:00_00:00:00 (00:00:00:00:00:00) Internet Protocol Version 4, Src: 127.0.0.1, Dst: 127.0.0.1 Stream Control Transmission Protocol, Src Port: 2905 (2905), Dst Port: 43964 (43964) MTP 3 User Adaptation Layer Signalling Connection Control Part BSSAP GSM A-I/F BSSMAP - Cipher Mode Reject Message Type Cipher Mode Reject Missing Mandatory element (0x04) Cause, rest of dissection is suspect [Expert Info (Warning/Protocol): Missing Mandatory element (0x04) Cause, rest of dissection is suspect] [Missing Mandatory element (0x04) Cause, rest of dissection is suspect] [Severity level: Warning] [Group: Protocol] Extraneous Data, dissector bug or later version spec(report to wireshark.org) [Expert Info (Note/Protocol): Extraneous Data, dissector bug or later version spec(report to wireshark.org)] [Extraneous Data, dissector bug or later version spec(report to wireshark.org)] [Severity level: Note] [Group: Protocol]
Attached is a pcap showing the packets leading up to a cipher mode reject. Ignore the errors causing the cipher mode reject (comes from #2745), the point is that the reject message itself is apparently malformed.
Files
Updated by neels over 6 years ago
- Assignee changed from dexter to neels
I think I've already fixed this "for free" ... will comment later
Updated by laforge over 6 years ago
- Status changed from New to Closed
- % Done changed from 0 to 100
I can confirm that the message now contains a valid cause value.
Actions