osmocom-commitlog September 2016

osmocom-commitlog@lists.osmocom.org

1 participants
225 discussions

osmo-bts.git branch master updated. 0.4.0-268-g3cc9174

by gitosis＠osmocom.org

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 "Osmocom BTS-side code (Abis, scheduling, ...)". The branch, master has been updated via 3cc91746a3d93824e248c67dda3b69e2eec81281 (commit) via c9a1f284acf518cb4e62c3898e20398ed53807c3 (commit) via ed6b48e4a5fba07c3ecccf689991799ae13a2aaa (commit) from 8431bbb80ffcab865e57b46af0e3a28eaee60108 (commit) 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/osmo-bts/commit/?id=3cc91746a3d93824e248c67dda3b69e… commit 3cc91746a3d93824e248c67dda3b69e2eec81281 Author: Neels Hofmeyr <nhofmeyr(a)sysmocom.de> Date: Tue Sep 6 15:15:07 2016 +0200 octphy: fix build with OCTSDR-OPENBSC-02.07.00-B708: name changed There was an apparent change of name from cOCTVC1_HW_CLOCK_SYNC_MGR_STATE_ENUM_IDLE to cOCTVC1_HW_CLOCK_SYNC_MGR_STATE_ENUM_UNUSED in: git://git.osmocom.org/octphy-2g-headers commit 953a258aadf18c05e8128a339f15b1c5bb377cfd "Import headers from OCTSDR-OPENBSC-02.07.00-B708.tgz" In order to build octphy with these headers, apply the same rename in osmo-bts-octphy/*. Change-Id: Ic07055860035a7c1b83ab923817423eeb39f33d3 http://cgit.osmocom.org/osmo-bts/commit/?id=c9a1f284acf518cb4e62c3898e20398… commit c9a1f284acf518cb4e62c3898e20398ed53807c3 Author: Neels Hofmeyr <nhofmeyr(a)sysmocom.de> Date: Tue Sep 6 15:08:34 2016 +0200 octphy: fix build: Revert "octphy: add support for multiple trx ids" This reverts commit c4fc00d8515ddc9990dfaf700c501cb8fe490cab, except: we keep the part that sets the trx_id in bts_model_phy_instance_set_defaults(). Theoretically, this patch makes a lot of sense, but in order to be able to build osmo-bts-octphy until the headers version is clarified, revert use of usCentreArfcn: Above commit uses an usCentreArfcn member that is never defined in the history of our octphy-2g-headers.git. This usCentreArfcn does exist in a code snapshot OCTSDR-2G-02.05.00-B780-DEBUG, which is not (yet?) publicly available. Also, the current headers version is apparently 02.07, though the octasic version numbers have been known to cause confusion among osmocom folks. This along with one other revert fixes this build problem: make[3]: Entering directory '/n/s/octphy/git/osmo-bts/src/osmo-bts-octphy' CC l1_oml.o l1_oml.c: In function ‘l1if_trx_open’: l1_oml.c:1350:13: error: ‘tOCTVC1_GSM_TRX_CONFIG’ has no member named ‘usCentreArfcn’ oc->Config.usCentreArfcn = plink->u.octphy.center_arfcn; ^ l1_oml.c:1352:13: error: ‘tOCTVC1_GSM_TRX_CONFIG’ has no member named ‘usCentreArfcn’ oc->Config.usCentreArfcn = trx->arfcn; ^ In file included from ../../include/osmo-bts/logging.h:5:0, from l1_oml.c:33: l1_oml.c:1365:13: error: ‘tOCTVC1_GSM_TRX_CONFIG’ has no member named ‘usCentreArfcn’ oc->Config.usCentreArfcn, oc->Config.usTsc, oc->RfConfig.ulRxGainDb, ^ Change-Id: Ic643709e8fb3df2d66337190ed1f07fd230d7dca http://cgit.osmocom.org/osmo-bts/commit/?id=ed6b48e4a5fba07c3ecccf689991799… commit ed6b48e4a5fba07c3ecccf689991799ae13a2aaa Author: Neels Hofmeyr <nhofmeyr(a)sysmocom.de> Date: Tue Sep 6 15:08:07 2016 +0200 octphy: fix build: Revert "octphy: fix for multiple trx with more than 1 dsp" This reverts commit 06968beab90806cba94c8b331276e4dc209c152b. Theoretically, this patch makes a lot of sense, but in order to be able to build osmo-bts-octphy until the headers version is clarified, revert use of usCentreArfcn: Above commit uses an usCentreArfcn member that is never defined in the history of our octphy-2g-headers.git. This usCentreArfcn does exist in a code snapshot OCTSDR-2G-02.05.00-B780-DEBUG, which is not (yet?) publicly available. Also, the current headers version is apparently 02.07, though the octasic version numbers have been known to cause confusion among osmocom folks. This along with one other revert fixes this build problem: make[3]: Entering directory '/n/s/octphy/git/osmo-bts/src/osmo-bts-octphy' CC l1_oml.o l1_oml.c: In function ‘l1if_trx_open’: l1_oml.c:1350:13: error: ‘tOCTVC1_GSM_TRX_CONFIG’ has no member named ‘usCentreArfcn’ oc->Config.usCentreArfcn = plink->u.octphy.center_arfcn; ^ l1_oml.c:1352:13: error: ‘tOCTVC1_GSM_TRX_CONFIG’ has no member named ‘usCentreArfcn’ oc->Config.usCentreArfcn = trx->arfcn; ^ In file included from ../../include/osmo-bts/logging.h:5:0, from l1_oml.c:33: l1_oml.c:1365:13: error: ‘tOCTVC1_GSM_TRX_CONFIG’ has no member named ‘usCentreArfcn’ oc->Config.usCentreArfcn, oc->Config.usTsc, oc->RfConfig.ulRxGainDb, ^ Change-Id: I222766f6961f5f35aa3651e2907e3e908fe9a66e ----------------------------------------------------------------------- Summary of changes: include/osmo-bts/phy_link.h | 3 +-- src/osmo-bts-octphy/l1_oml.c | 12 ++---------- src/osmo-bts-octphy/l1_utils.c | 2 +- src/osmo-bts-octphy/octphy_hw_api.c | 2 +- 4 files changed, 5 insertions(+), 14 deletions(-) hooks/post-receive -- Osmocom BTS-side code (Abis, scheduling, ...)

8 years, 9 months

osmo-pcu.git branch nrw/litecell15-merge-and-rebase created. 0.2-829-g16ddc90

by gitosis＠osmocom.org

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 "UNNAMED PROJECT". The branch, nrw/litecell15-merge-and-rebase has been created at 16ddc90eabad423d247753f7d89639659e049d35 (commit) - Log ----------------------------------------------------------------- http://cgit.osmocom.org/osmo-pcu/commit/?id=16ddc90eabad423d247753f7d896396… commit 16ddc90eabad423d247753f7d89639659e049d35 Author: Minh-Quang Nguyen <minh-quang.nguyen(a)nutaq.com> Date: Tue Sep 6 10:27:11 2016 -0400 LC15: Change TRX numbering for the latest Litecell15 hardware Change-Id: If3c4aff0366587dd3e5baa3d15b9e91d8ebe7753 ----------------------------------------------------------------------- hooks/post-receive -- UNNAMED PROJECT

8 years, 9 months

osmo-bts.git branch master updated. 0.4.0-265-g8431bbb

by gitosis＠osmocom.org

8 years, 9 months

osmo-bts.git branch neels/dyn_no_pcu updated. 0.4.0-265-g3e4ea87

by gitosis＠osmocom.org

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 "Osmocom BTS-side code (Abis, scheduling, ...)". The branch, neels/dyn_no_pcu has been updated discards 7ea38df5378309a5eb831125dbebbec34aab107e (commit) via 3e4ea873b75890765dfa241652be808d943d0aa5 (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 (7ea38df5378309a5eb831125dbebbec34aab107e) \ N -- N -- N (3e4ea873b75890765dfa241652be808d943d0aa5) 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/osmo-bts/commit/?id=3e4ea873b75890765dfa241652be808… commit 3e4ea873b75890765dfa241652be808d943d0aa5 Author: Neels Hofmeyr <nhofmeyr(a)sysmocom.de> Date: Mon Aug 22 23:07:09 2016 +0200 dyn TS: if PCU is not connected, allow operation as TCH Before this patch, Osmocom style TCH/F_TCH/H_PDCH dyn TS were paralyzed if no PCU was running. The state of the dyn TS would lock up in the PDCH activation phase since the PCU never completed the process. Make more robust, i.e. don't concern the BSC with PDCH activation failures. This matches the way plain PDCH TS work: besides declaring the TS as PDCH, the BSC is not involved and is not told about errors. During PDCH deactivation, still wait for the PCU to tear down the PDTCH SAPIs, but in case no PCU is connected, send a rel ack right away. Thus, the BSC will happily switch Osmocom style dynamic timeslots to and from PDCH mode, using the dyn TS as voice channels as needed, and not caring about possible PDCH failures. GPRS starts working right away as soon as a PCU connects, regardless of dyn TS having been used for voice any number of times, and without another switchover needed. In detail: In rsl_rx_chan_activ(), upon receiving a PDCH activation, send an RSL chan act ack right away, unconditionally (with an explaining comment). Do not concern the Abis link with PDCH activation failures. Since we're acking right away now, drop the chan act ack that would follow after the PCU activation: as before dyn TS, only send acks and nacks for rel_act_kind == LCHAN_REL_ACT_RSL (PDCH runs as LCHAN_REL_ACT_PCU). In dyn_ts_pdch_release, indicate that the PCU is not connected by means of returning 1. In rsl_rx_rf_chan_rel(), use this indicator to send a rel ack right away if the PCU is not connected. Change-Id: I2a0b9730197786b99ff3bc1f08c75f7d279cb1f7 ----------------------------------------------------------------------- Summary of changes: src/common/rsl.c | 21 +++++++++++++-------- 1 file changed, 13 insertions(+), 8 deletions(-) hooks/post-receive -- Osmocom BTS-side code (Abis, scheduling, ...)

8 years, 9 months

libosmo-abis.git branch master updated. 0.3.2-19-gc77c2a6

by gitosis＠osmocom.org

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 "Osmocom A-bis protcol interface library". The branch, master has been updated via c77c2a6aa13accbc558888ab788d1148eb9aeb1a (commit) from 085ab0bb9ce99693e8b06acf721cf415abc08cf0 (commit) 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/libosmo-abis/commit/?id=c77c2a6aa13accbc558888ab788… commit c77c2a6aa13accbc558888ab788d1148eb9aeb1a Author: Neels Hofmeyr <nhofmeyr(a)sysmocom.de> Date: Mon Sep 5 14:09:56 2016 +0200 osmo_ortp.c: fix order of set_connected_mode and set_remote_addr In libortp, rtp_session_set_connected_mode() sets a flag that is used in rtp_session_set_remote_addr(). The name rtp_session_set_remote_addr() is misleading: this function actually does take a lot of action, including an attempt to connect to the remote server. Thus the "connected mode" flag needs to be set before this. Suggested-by: NuRan Wireless <nuranwireless.com> Change-Id: I92308ddffc376af8d4d65e6b9cbeee222b7bff5e ----------------------------------------------------------------------- Summary of changes: src/trau/osmo_ortp.c | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) hooks/post-receive -- Osmocom A-bis protcol interface library

8 years, 9 months

libosmocore.git branch master updated. 0.9.0-223-ge65315f

by gitosis＠osmocom.org

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 "An utility library for Open Source Mobile Communications". The branch, master has been updated via e65315fb373602082b9289020ccc17f0c4b79935 (commit) from 0318f6b6cae7a3f2d786a1caee519241d81d6745 (commit) 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/libosmocore/commit/?id=e65315fb373602082b9289020ccc… commit e65315fb373602082b9289020ccc17f0c4b79935 Author: Alexander Couzens <lynxis(a)fe80.eu> Date: Mon Aug 22 21:42:57 2016 +0200 core/counter: add osmo_counter_dec() Change-Id: I030140a45afa295c3ebc4d3ccaffd437b984f515 ----------------------------------------------------------------------- Summary of changes: include/osmocom/core/statistics.h | 6 ++++++ 1 file changed, 6 insertions(+) hooks/post-receive -- An utility library for Open Source Mobile Communications

8 years, 9 months

openbsc.git branch master updated. 0.15.0-427-g58f446c

by gitosis＠osmocom.org

8 years, 9 months

osmo-pcu.git branch sysmocom/revert_WAIT_ASSIGN updated. 0.2-829-g303be72

by gitosis＠osmocom.org

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 "UNNAMED PROJECT". The branch, sysmocom/revert_WAIT_ASSIGN has been updated discards 2d0da6371dba88860d843998faabd98518d50179 (commit) via 303be72c9fe3266214e3bf70852270ad45d3eb95 (commit) via 7c7a86c080edd9c92778c941bbe484f59a81f93c (commit) via a35c911a91ea7b6d8b017fd103c0d86f79bb271e (commit) via 3c2eaebd214fd39ebaf0bf86d2120bd226c62309 (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 (2d0da6371dba88860d843998faabd98518d50179) \ N -- N -- N (303be72c9fe3266214e3bf70852270ad45d3eb95) 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/osmo-pcu/commit/?id=303be72c9fe3266214e3bf70852270a… commit 303be72c9fe3266214e3bf70852270ad45d3eb95 Author: Neels Hofmeyr <neels(a)hofmeyr.de> Date: Wed Jun 8 15:27:40 2016 +0200 Revert "tbf: Add state WAIT_ASSIGN" This reverts commit f1a7b8fc6651f92a8b7f3f27b7ca05d07f4e44e0. Conflicts: tests/tbf/TbfTest.err The commit broke GPRS service at least for osmo-bts-sysmo on a SysmoBTS 1002 with current master of osmo-bts (ef30f50d5d6d5f863fc147d05ccdceb89284934e). The error observed is the following log output (was viewing both osmo-bts-sysmo and osmo-pcu logs interleaved): <0002> tbf.cpp:874 TBF(TFI=0 TLLI=0x00000000 DIR=UL STATE=WAIT ASSIGN) T3169 timeout during transsmission <0002> tbf.cpp:893 - Assignment was on CCCH <0002> tbf.cpp:899 - No uplink data received yet <0007> l1sap.c:904 RACH for packet access <0001> pcu_l1_if.cpp:311 RACH request received: sapi=1 qta=0, ra=121, fn=13653 [repeat] When removing this single commit from current osmo-pcu master, GPRS service works well on SysmoBTS, with current osmo-bts master. The TbfTest.err expected output needed adjustment after the revert. Disclaimer: I am not aware of adverse effects this commit may have. I have no idea what the WAIT_ASSIGN state is used for -- further review is required. Change-Id: I1532f8e93194368cdc1e3846f82afa6d68cd5fbd ----------------------------------------------------------------------- Summary of changes: src/rlc.cpp | 2 +- tests/tbf/TbfTest.cpp | 60 +++++++++++++++++++++++++++++++++++++++++++++++ tests/tbf/TbfTest.err | 49 ++++++++++++++++++++++++++++++++++++++ tests/tbf/TbfTest.ok | 2 ++ tests/types/TypesTest.cpp | 17 ++++++++++++++ 5 files changed, 129 insertions(+), 1 deletion(-) hooks/post-receive -- UNNAMED PROJECT

8 years, 9 months

osmo-bts.git branch neels/dyn_no_pcu updated. 0.4.0-265-g7ea38df

by gitosis＠osmocom.org

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 "Osmocom BTS-side code (Abis, scheduling, ...)". The branch, neels/dyn_no_pcu has been updated discards 42edba5fe67ac96d4dde6ebb5f5d84fea9124f4f (commit) discards 370a91c4eac99948376c2175ef9e352c70be2b53 (commit) via 7ea38df5378309a5eb831125dbebbec34aab107e (commit) via bf6bae2b2363a182bb1b95574c2922bf4257c4d9 (commit) via 8a148613b4c93f5a25dd2a2d9929de75882adbc5 (commit) via 4dfc3da96bbad9e6a8641233c87a05a46af7d906 (commit) via 9faaf4ecf01322189808901398e06d7e4f14560d (commit) via 3b2e5de3aea8652969e7bbd1e3c04206dce51330 (commit) via 988f634c97d070840f4ffc952f6bac32d967859b (commit) via e77bcaecb6e45b55b8e31fea7cf10c2652431c1c (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 (42edba5fe67ac96d4dde6ebb5f5d84fea9124f4f) \ N -- N -- N (7ea38df5378309a5eb831125dbebbec34aab107e) 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/osmo-bts/commit/?id=7ea38df5378309a5eb831125dbebbec… commit 7ea38df5378309a5eb831125dbebbec34aab107e Author: Neels Hofmeyr <nhofmeyr(a)sysmocom.de> Date: Mon Aug 22 23:07:09 2016 +0200 dyn TS: if PCU is not connected, allow operation as TCH Before this patch, Osmocom style TCH/F_TCH/H_PDCH dyn TS were paralyzed if no PCU was running. The state of the dyn TS would lock up in the PDCH activation phase since the PCU never completed the process. Make more robust, i.e. don't concern the BSC with PDCH activation failures. This matches the way plain PDCH TS work: besides declaring the TS as PDCH, the BSC is not involved and is not told about errors. During PDCH deactivation, still wait for the PCU to tear down the PDTCH SAPIs, but in case no PCU is connected, send a rel ack right away. Thus, the BSC will happily switch Osmocom style dynamic timeslots to and from PDCH mode, using the dyn TS as voice channels as needed, and not caring about possible PDCH failures. GPRS starts working right away as soon as a PCU connects, regardless of dyn TS having been used for voice any number of times, and without another switchover needed. In detail: In rsl_rx_chan_activ(), upon receiving a PDCH activation, send an RSL chan act ack right away, unconditionally (with an explaining comment). Do not concern the Abis link with PDCH activation failures. Since we're acking right away now, drop the chan act ack that would follow after the PCU activation: as before dyn TS, only send acks and nacks for rel_act_kind == LCHAN_REL_ACT_RSL (PDCH runs as LCHAN_REL_ACT_PCU). In dyn_ts_pdch_release, indicate that the PCU is not connected by means of returning 1. In rsl_rx_rf_chan_rel(), use this indicator to send a rel ack right away if the PCU is not connected. Change-Id: I2a0b9730197786b99ff3bc1f08c75f7d279cb1f7 ----------------------------------------------------------------------- Summary of changes: include/osmo-bts/gsm_data.h | 1 + include/osmo-bts/pcu_if.h | 3 ++- include/osmo-bts/pcuif_proto.h | 6 ++++-- src/common/l1sap.c | 30 +++++++++++------------------- src/common/lchan.c | 16 ++++++++++++++++ src/common/measurement.c | 16 +--------------- src/common/pcu_sock.c | 5 ++++- src/osmo-bts-litecell15/l1_if.c | 2 +- src/osmo-bts-litecell15/oml.c | 27 +++++++++++++++++++-------- src/osmo-bts-sysmo/l1_if.c | 8 +++++++- src/osmo-bts-sysmo/oml.c | 27 +++++++++++++++++++-------- 11 files changed, 85 insertions(+), 56 deletions(-) hooks/post-receive -- Osmocom BTS-side code (Abis, scheduling, ...)

8 years, 9 months

openbsc.git branch master updated. 0.15.0-425-g21b269f

by gitosis＠osmocom.org

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, master has been updated via 21b269f81454919a379d22b9c2be74bb680be500 (commit) via c17cdb40b545a5006e9b97e76559d7a4b46e030d (commit) via fac9758820d6b792a15da0aea002e1c29cb96916 (commit) via 5b2363ebb281f0e3428ed1949d7ab1ee533d7e19 (commit) via af241727a9f03f9259529e1e374329adf4ca0626 (commit) via 1dee2b6e96dfce363a31097da97ef4ac14470245 (commit) via 3ecfbbba6f9df1fa57032fcdcba0a83d702be6f5 (commit) via 770f3e32e00f70c668e9981e1b17c1f6c4d4ac06 (commit) from 7bc6986f6babdaf5f2436dae2f603ae5823aa7b4 (commit) 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=21b269f81454919a379d22b9c2be74bb… commit 21b269f81454919a379d22b9c2be74bb680be500 Author: Daniel Willmann <dwillmann(a)sysmocom.de> Date: Wed May 11 12:43:47 2016 +0200 IuPS: Change GTP-U endpoint to SGSN in PMM_IDLE and page UE when data arrives Change-Id: I47b73a40cbdda6b7c31fb2767f74f9f93d84056b http://cgit.osmocom.org/openbsc/commit/?id=c17cdb40b545a5006e9b97e76559d7a4… commit c17cdb40b545a5006e9b97e76559d7a4b46e030d Author: Daniel Willmann <dwillmann(a)sysmocom.de> Date: Wed May 11 12:42:54 2016 +0200 IuPS: Introduce function to change PMM state This is where IuPS will redirect GTP-U endpoints in a subsequent commit. Also add comprehensive logging of pmm_state transitions. Change-Id: I7c2cd1abc1805659b01dffffff31c49fe5161086 http://cgit.osmocom.org/openbsc/commit/?id=fac9758820d6b792a15da0aea002e1c2… commit fac9758820d6b792a15da0aea002e1c29cb96916 Author: Daniel Willmann <dwillmann(a)sysmocom.de> Date: Sat May 21 00:21:15 2016 +0200 IuPS: GMM Attach: reset MM ctx pending_req Change-Id: I0df0f3d88085939eb617405e2013ad164eed477b http://cgit.osmocom.org/openbsc/commit/?id=5b2363ebb281f0e3428ed1949d7ab1ee… commit 5b2363ebb281f0e3428ed1949d7ab1ee533d7e19 Author: Daniel Willmann <dwillmann(a)sysmocom.de> Date: Sat May 21 00:01:21 2016 +0200 IuPS: sgsn_mm_ctx: add enum gprs_pmm_state field, track PMM state Iu needs to page to transfer data in PMM-IDLE state. Change-Id: Id37778cb9a0328a21c8e8246998ecdb43dd687d8 http://cgit.osmocom.org/openbsc/commit/?id=af241727a9f03f9259529e1e374329ad… commit af241727a9f03f9259529e1e374329adf4ca0626 Author: Daniel Willmann <dwillmann(a)sysmocom.de> Date: Sat May 21 00:35:41 2016 +0200 IuPS: RA UPD: make sure to authorize, for Iu Integrity Protection Change-Id: I2ea2089895f8a8e125ef39d9bef70dafb2b1ce69 http://cgit.osmocom.org/openbsc/commit/?id=1dee2b6e96dfce363a31097da97ef4ac… commit 1dee2b6e96dfce363a31097da97ef4ac14470245 Author: Daniel Willmann <dwillmann(a)sysmocom.de> Date: Sat May 21 00:15:29 2016 +0200 IuPS: add GMM Service Request rx and tx Change-Id: Ib935de22d23a15f449927840d4d59497ce22abbd http://cgit.osmocom.org/openbsc/commit/?id=3ecfbbba6f9df1fa57032fcdcba0a83d… commit 3ecfbbba6f9df1fa57032fcdcba0a83d702be6f5 Author: Daniel Willmann <dwillmann(a)sysmocom.de> Date: Sat May 21 00:16:55 2016 +0200 IuPS: send Security Mode Command, track the new_key flag. Change-Id: I0b2593c2df13b79eb36975b0d302e31cfdf8bb09 http://cgit.osmocom.org/openbsc/commit/?id=770f3e32e00f70c668e9981e1b17c1f6… commit 770f3e32e00f70c668e9981e1b17c1f6c4d4ac06 Author: Daniel Willmann <dwillmann(a)sysmocom.de> Date: Sat May 21 00:31:12 2016 +0200 IuPS: dev hack: init hardcoded Ki on ATT REQ DEVELOPMENT HACK: Our current HLR does not support 3G authentication tokens. A new HLR/VLR implementation is being developed. Until it is ready and actual milenage authentication is properly supported, we are hardcoding a fixed Ki and use 2G auth. Change-Id: Ieca45960fa941a3a706c6e479b04b9f2ef89d860 ----------------------------------------------------------------------- Summary of changes: openbsc/include/openbsc/gprs_sgsn.h | 11 ++ openbsc/include/openbsc/sgsn.h | 1 + openbsc/src/gprs/gprs_gmm.c | 289 +++++++++++++++++++++++++++++++++++- openbsc/src/gprs/gprs_sgsn.c | 2 + openbsc/src/gprs/sgsn_libgtp.c | 19 +++ 5 files changed, 320 insertions(+), 2 deletions(-) hooks/post-receive -- The OpenBSC GSM Base Station Controller (+MSC/HLR/SGSN)

8 years, 9 months

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

osmocom-commitlog September 2016