Project

General

Profile

Bug #2954

No GMM ATTACH REJECT on GSUP SendAuthInfo Error

Added by laforge 7 months ago. Updated 4 days ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
GSUP interface
Target version:
-
Start date:
02/17/2018
Due date:
% Done:

100%

Estimated time:
Spec Reference:

Description

When the HLR responds with a SendAuthInfo Error during AttachRequest processing, OsmoSGSN doesn't send the expected GMM ATTACH REJECT to the MS:

Sat Feb 17 09:22:04 2018 DMM <0002> gprs_gmm.c:1271 MM(---/ffffffff) -> GMM ATTACH REQUEST MI(262420000000003) type="GPRS attach" 
Sat Feb 17 09:22:04 2018 DMM <0002> gprs_sgsn.c:237 MM(/00000000) Allocated with GEA0 cipher.
Sat Feb 17 09:22:04 2018 DLGLOBAL <001d> rate_ctr.c:218 counter group 'sgsn:mmctx' already exists for index 0, instead using index 1. This is a software bug that needs fixing.
Sat Feb 17 09:22:04 2018 DMM <0002> gprs_gmm.c:556 MM(262420000000003/c2b7f00d) <- GPRS IDENTITY REQUEST: mi_type=IMEI
Sat Feb 17 09:22:04 2018 DLLC <0012> gprs_llc_parse.c:81 LLC SAPI=1 C   U GEA0 IOV-UI=0x000000 FCS=0x612fca CMD=UI DATA 
Sat Feb 17 09:22:04 2018 DMM <0002> gprs_gmm.c:1194 MM(262420000000003/c2b7f00d) -> GMM IDENTITY RESPONSE: MI(IMEI)=499990000000003
Sat Feb 17 09:22:04 2018 DMM <0002> sgsn_auth.c:160 MM(262420000000003/c2b7f00d) Requesting authorization
Sat Feb 17 09:22:04 2018 DMM <0002> sgsn_auth.c:185 MM(262420000000003/c2b7f00d) Requesting authentication tuples
Sat Feb 17 09:22:04 2018 DMM <0002> gprs_subscriber.c:894 MM(262420000000003/c2b7f00d) Requesting subscriber authentication info
Sat Feb 17 09:22:04 2018 DGPRS <000f> gprs_subscriber.c:504 SUBSCR(262420000000003) GSUP protocol remote error, GMM cause = 'GSM authentication unacceptable' (23)

I've created SGSN_Tests.TC_attach_auth_sai_reject for this

20180216-sgsn-sai-reject.pcap 20180216-sgsn-sai-reject.pcap 3.31 KB laforge, 02/17/2018 08:24 AM

Related issues

Related to OsmoSGSN - Bug #3302: implement a FSM for GMM Attach RequestClosed2018-05-29

History

#1 Updated by laforge 4 months ago

  • Assignee changed from sysmocom to lynxis

#2 Updated by lynxis 4 months ago

  • Status changed from New to Stalled
  • % Done changed from 0 to 60
  • Parent task set to #3302

TC passing when using the new FSM implementation.

#3 Updated by lynxis 4 months ago

  • Parent task deleted (#3302)

#4 Updated by lynxis 4 months ago

  • Related to Bug #3302: implement a FSM for GMM Attach Request added

#5 Updated by lynxis 4 days ago

  • Status changed from Stalled to Closed
  • % Done changed from 60 to 100

The test is passing now.

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)