This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "The OpenBSC GSM Base Station Controller (+MSC/HLR/SGSN)". The branch, sysmocom/ipa_nano3G has been updated discards bfaa4d6e64bdc42baa684ec2586861a93466c4c8 (commit) via 14d527a0243e9e268d7505a03e1b6d970b4d4f15 (commit) via 20e97facea65eb9b25662a1f43de256940176134 (commit) via c358b5ec1b686efd2702180e52566f873d9e95c1 (commit) This update added new revisions after undoing existing revisions. That is to say, the old revision is not a strict subset of the new revision. This situation occurs when you --force push a change and generate a repository containing something like this: * -- * -- B -- O -- O -- O (bfaa4d6e64bdc42baa684ec2586861a93466c4c8) \ N -- N -- N (14d527a0243e9e268d7505a03e1b6d970b4d4f15) When this happens we assume that you've already had alert emails for all of the O revisions, and so we here report only the revisions in the N branch from the common base, B. Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log ----------------------------------------------------------------- http://cgit.osmocom.org/openbsc/commit/?id=14d527a0243e9e268d7505a03e1b6d970... commit 14d527a0243e9e268d7505a03e1b6d970b4d4f15 Author: Neels Hofmeyr <nhofmeyr@sysmocom.de> Date: Mon Apr 25 15:40:54 2016 +0200 RAB Assignment: IuPS + IuCS: use shorter 32 bit IP address format This is needed for the ip.access nano3G femto cell. Change-Id: I80fe96505c24cf8730e48f24a34004a51e95ee32 http://cgit.osmocom.org/openbsc/commit/?id=20e97facea65eb9b25662a1f43de25694... commit 20e97facea65eb9b25662a1f43de256940176134 Author: Neels Hofmeyr <nhofmeyr@sysmocom.de> Date: Tue Oct 11 00:50:05 2016 +0200 IuCS: fix: no paging when conn is already open The 2G paradigm is to close a subscriber connection as soon as nothing else is pending. Hence the code frequently calls msc_release_connection() to see whether a conn can be discarded. In 3G however, we so far don't actively release IuCS connections from the MSC side, but wait until the IuCS is released from the UE side. So the IuCS often stays open and valid even though msc_release_connection() has already discarded the gsm_subscriber_connection for it. Thus, when further events occured, we would try to page the subscriber even though the UE expects to already be connected, with auth and ciphering established. To fix, never discard gsm_subscriber_connections when msc_release_connection() is called. An alternative fix would be to actively send an Iu Release when msc_release_connection() is invoked, so that auth and ciphering is re-established for the next pending event (which might be better, even). Change-Id: I012378cfa432d791146db387554ec1909de05297 http://cgit.osmocom.org/openbsc/commit/?id=c358b5ec1b686efd2702180e52566f873... commit c358b5ec1b686efd2702180e52566f873d9e95c1 Author: Neels Hofmeyr <nhofmeyr@sysmocom.de> Date: Tue Oct 11 01:05:22 2016 +0200 IuCS: detect whether a conn is already secure If a CM Service Request is received on an already secure IuCS connection, we so far didn't notice and started to authenticate again. The UE would readily renew its authentication, but then our state got stuck since ciphering was already established. Instead, don't authenticate again when integrity protection is already established. Change-Id: I3c01fe58276ba0ad918f2cd30cc3dca7c6663e68 ----------------------------------------------------------------------- Summary of changes: openbsc/src/libmsc/gsm_04_08.c | 4 ++++ openbsc/src/libmsc/osmo_msc.c | 4 ++++ 2 files changed, 8 insertions(+) hooks/post-receive -- The OpenBSC GSM Base Station Controller (+MSC/HLR/SGSN)