Bug #3187

rx cipher mode reject from BSS broken

Added by neels 8 months ago. Updated 20 days ago.

In Progress
A interface (general)
Target version:
Start date:
Due date:
% Done:




bssmap_rx_ciph_rej() looks for a cause IE using the BSS_MAP_MSG_CIPHER_MODE_REJECT message discriminator. This is clearly wrong and invariably leads to

<000a> a_iface_bssap.c:629 Rx MSC DT1 BSSMAP CIPHER MODE REJECT
<000a> a_iface_bssap.c:453 BSC sends cipher mode reject (conn_id=65)
<000a> a_iface_bssap.c:457 Cause code is missing -- discarding message!

We need a test verifying that the MSC properly receives a Cipher Mode Reject.
Since in ttcn3, we don't verify log output, this might actually be good to incorporate in the msc_vlr tests instead?
Is there a message response we could trigger on in ttcn3?

Related issues

Related to Cellular Network Infrastructure - Bug #3043: A5/3 encryption failsResolved2018-03-08


#1 Updated by neels 8 months ago

  • Related to Bug #3043: A5/3 encryption fails added

#2 Updated by laforge 6 months ago

  • Assignee set to neels

#3 Updated by laforge 2 months ago

  • Priority changed from Normal to High

#4 Updated by laforge about 2 months ago

  • Category set to A interface (general)
  • Assignee changed from neels to msuraev

#5 Updated by msuraev about 1 month ago

  • Status changed from New to In Progress
  • % Done changed from 0 to 60

Fix is available in not sure how to test it yet though.

#6 Updated by msuraev about 1 month ago

One way to test this in ttcn would be to introduce counter for cipher mode reject and check its value via CTRL interface.

#7 Updated by msuraev about 1 month ago

Related patches available in gerrit 11601, 11577 and 11655.

#8 Updated by msuraev 20 days ago

Patches for libosmocore and osmo-msc were merged. Remaining bits:
  • add TTCN3 tests checking related counters

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)