Actions
Bug #6295
openTMSI realloc complete leads to SecurityModeReject
Start date:
12/07/2023
Due date:
% Done:
0%
Spec Reference:
Description
With osmo-sgsn 1.11.1 and nano3g, I'm observing the following sccp traffic (pcap in SYS#6582):
- SecurityModeCommand
- SecurityModeComplete
- TMSI realloc complete
- SecurityModeCommand
- SecurityModeReject with error code conflict-with-already-existing-integrity-protection-and-or-ciphering-information (13)
I guess we should tell the hnb to forget the ciphering information when doing a tmsi realloc? or there might be a way to not have SecurityModeCommand after TMSI realloc?
Creating the issue for future reference, currently looking into another problem.
No data to display
Actions
