tree 83f9978da074777642b2ab972b80dc9b04c2df4a
parent 38f1fa525942b95617f7bd48e09ddd1a4f6be747
author Jacob Erlbeck <jerlbeck@sysmocom.de> 1409835210 +0200
committer Jacob Erlbeck <jerlbeck@sysmocom.de> 1410249956 +0200

gbproxy: Fix P-TMSI reassignment

Currently, a new P-TMSI within an Attach Accept or within an RA
Update Request is applied to the TLLI mapping (gbproxy_reassign_tlli)
_before_ patching is done. This can lead to inconsistent behaviour
when the TLLI validation has not been completed, which is the case
when subsequent RA UDP REQ are received. The new TLLI must not be
applied to the message itself yet, it should only be considered for
following messages.

This patch moves the TLLI reassignment to
gbproxy_update_tlli_state_after() to fix that.

It also separates the implementation of the feature that a new
tlli_info can be created when such a message is received from the
SGSN. This makes sense, when P-TMSI patching is not active and the
tlli_info entry has expired.

Sponsored-by: On-Waves ehf