Project

General

Profile

Bug #2951

OsmoSGSN Accepts two MO L3 Messages with N(U) set to zero

Added by laforge over 1 year ago. Updated 1 day ago.

Status:
In Progress
Priority:
Normal
Assignee:
Category:
-
Target version:
-
Start date:
02/16/2018
Due date:
% Done:

0%

Spec Reference:

Description

when
  • the MS sends its first GMM message "ATTACH REQUEST" in LLC with N(U) set to 0 (expected)
  • the SGSN then inquires abou the IMEI using GMM "IDENTITY REQUEST"
  • the MS subsequently sends its GMM "IDENTITY RESPONSE" in LLC with N(U) set to 0 again (broken behavior!)

Then OsmoSGSN still accepts that IDENTITY RESPONSE. This is odd. Later on, OsmoSGSN detects duplicate N(U) sequence numbers. But at the initial stage (or maybe when it's 0?) it doesn't detect the duplicate sequence number [which should be dropped].

History

#1 Updated by laforge about 1 year ago

  • Assignee changed from sysmocom to lynxis

#2 Updated by laforge 7 months ago

  • Assignee changed from lynxis to osmith

#3 Updated by osmith 1 day ago

  • Status changed from New to In Progress

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)