osmocom-commitlog

osmocom-commitlog@lists.osmocom.org

7948 discussions

osmo-hlr.git branch master updated. 0.0.1-109-g16140f7

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, master has been updated via 16140f70c5d8138311397388cc938e10f0d992db (commit) from 36bec87104576f6e7f192698c1efa6a40ce15409 (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-hlr/commit/?id=16140f70c5d8138311397388cc938e1… commit 16140f70c5d8138311397388cc938e10f0d992db Author: Neels Hofmeyr <neels(a)hofmeyr.de> Date: Wed Oct 25 19:17:18 2017 +0200 db api: fix/add API docs Change-Id: I854fafd8e56bd0b8394f8ed79d023c11c2fdbdca ----------------------------------------------------------------------- Summary of changes: src/db_hlr.c | 89 +++++++++++++++++++++++++++++++++++++++++++++++++++--------- 1 file changed, 76 insertions(+), 13 deletions(-) hooks/post-receive -- UNNAMED PROJECT

7 years, 8 months

osmo-gsm-manuals.git branch master updated. c481a988e33e4046c53f1f38d52522db67401820

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 "Manuals for Osmocom GSM components". The branch, master has been updated via c481a988e33e4046c53f1f38d52522db67401820 (commit) from 1b1b176e68730f5e42bf71e444c0ba1f3d9acea4 (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-gsm-manuals/commit/?id=c481a988e33e4046c53f1f3… commit c481a988e33e4046c53f1f38d52522db67401820 Author: Neels Hofmeyr <neels(a)hofmeyr.de> Date: Thu Oct 19 05:11:57 2017 +0200 refactor Makefile build rules, don't use the FORCE The initial goal was to make sure we don't have overall FORCE rules causing unnecessary rebuilds -- annoying while writing documentation. As I looked through possible dependencies, I finally understood what's going on here. Remove code dup and nicely sort which belongs where in build/Makefile.*.inc. In each, describe in a top comment how to use it, and also unify how they are used: - Rename Makefile.inc to Makefile.docbook.inc and refactor - Add Makefile.vty-reference.inc - Add Makefile.common.inc Make sure that we accurately pick up all dependencies. Drop use of the macro called 'command', that silenced the actual command lines invoked and replaced them with short strings: it obscures what is actually going on and makes the Makefiles hard to read and understand. Each manual's makefile is greatly reduced to few definitions and a Makefile include, e.g. one for asciidoc, one for VTY reference. Move common/bsc_vty_additions.xml to OsmoBSC/vty/libbsc_vty_additions.xml, link from OsmoNITB. It applies only to OsmoBSC and OsmoNITB. Add a script that combines a VTY reference file with *all* additions files found in a manual's vty/ dir. Call this from Makefile.vty-reference.inc. Change-Id: I9758e04162a480e28c7dc83475b514cf7fd25ec0 ----------------------------------------------------------------------- Summary of changes: OsmoBSC/Makefile | 55 +++------------------- .../vty/libbsc_vty_additions.xml | 0 OsmoBTS/Makefile | 52 +++----------------- OsmoGGSN/Makefile | 41 +++------------- OsmoGSMTester/Makefile | 13 ++--- OsmoHLR/Makefile | 44 +++-------------- OsmoMGCP/Makefile | 33 ++----------- OsmoMSC/Makefile | 44 +++-------------- OsmoNAT/Makefile | 33 ++----------- OsmoNITB/Makefile | 46 +++--------------- OsmoNITB/vty/bsc_vty_additions.xml | 1 + OsmoPCU/Makefile | 44 ++--------------- OsmoSGSN/Makefile | 45 +++--------------- build/Makefile.asciidoc.inc | 35 +++++++++++--- build/Makefile.common.inc | 14 ++++++ build/Makefile.docbook.inc | 35 ++++++++++++++ build/Makefile.inc | 47 ------------------ build/Makefile.vty-reference.inc | 42 +++++++++++++++++ build/vty_reference_combine.sh | 25 ++++++++++ 19 files changed, 206 insertions(+), 443 deletions(-) rename common/bsc_vty_additions.xml => OsmoBSC/vty/libbsc_vty_additions.xml (100%) create mode 120000 OsmoNITB/vty/bsc_vty_additions.xml create mode 100644 build/Makefile.common.inc create mode 100644 build/Makefile.docbook.inc delete mode 100644 build/Makefile.inc create mode 100644 build/Makefile.vty-reference.inc create mode 100755 build/vty_reference_combine.sh hooks/post-receive -- Manuals for Osmocom GSM components

7 years, 8 months

osmo-hlr.git branch neels/db_tool updated. 0.0.1-112-g9d99d99

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, neels/db_tool has been updated discards c0d4c63863d47684986f5f2283acca2e23ddfbde (commit) via 9d99d99137e127a3045071ebf0ca2a9520789e59 (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 (c0d4c63863d47684986f5f2283acca2e23ddfbde) \ N -- N -- N (9d99d99137e127a3045071ebf0ca2a9520789e59) 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-hlr/commit/?id=9d99d99137e127a3045071ebf0ca2a9… commit 9d99d99137e127a3045071ebf0ca2a9520789e59 Author: Neels Hofmeyr <neels(a)hofmeyr.de> Date: Tue Oct 24 23:26:53 2017 +0200 add osmo-hlr-db-tool Change-Id: I0dfa6ec033dd93161c1adc2ce1637195fe5b7a63 ----------------------------------------------------------------------- Summary of changes: src/Makefile.am | 1 + src/db_hlr.c | 4 +- src/hlr_db_tool.c | 248 ++++++++++++++++++++++++++++++++++++++++++++++++++---- src/logging.c | 6 +- 4 files changed, 237 insertions(+), 22 deletions(-) hooks/post-receive -- UNNAMED PROJECT

7 years, 8 months

osmo-hlr.git branch neels/db_tool created. 0.0.1-112-gc0d4c63

by gitosis＠osmocom.org

7 years, 8 months

osmo-bts.git branch master updated. 0.6.0-21-g9982b95

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 9982b95069c58a3cb9b97bb6bc75932db81886ad (commit) from bf9298eb0f087b3b16fd08e04310d8d2e156dc8d (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=9982b95069c58a3cb9b97bb6bc75932… commit 9982b95069c58a3cb9b97bb6bc75932db81886ad Author: Harald Welte <laforge(a)gnumonks.org> Date: Tue Oct 24 18:42:30 2017 +0200 Fix Downlink AMR FSM name to avoid illegal space character Since libosmocore Change-Id I9ef59432f43a3cdb94e4cbb0c44ac3f9b2aac0f2 we enforce that FSM names do not contain illegal characteers such as spaces. Let's change the DL TX FSM for AMR to comply to this. Also, actually do check the result of the FSM registration. Change-Id: Ieccd1dc32c0faf5e544d17daca4a417d1d168c21 ----------------------------------------------------------------------- Summary of changes: src/common/bts.c | 4 +++- src/common/dtx_dl_amr_fsm.c | 2 +- 2 files changed, 4 insertions(+), 2 deletions(-) hooks/post-receive -- Osmocom BTS-side code (Abis, scheduling, ...)

7 years, 8 months

libosmocore.git branch master updated. 0.9.6-464-gb48e82ca

by gitosis＠osmocom.org

7 years, 8 months

libosmocore.git branch master updated. 0.9.6-463-gcbf5cdfe

by gitosis＠osmocom.org

7 years, 8 months

libosmocore.git branch master updated. 0.9.6-461-g04c88120

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 04c881207f903f48bd5863bc851b8384a06578de (commit) via a7a5065385be71239d49bb60a690402d3153eb34 (commit) via ae510dc4a743e981b40fc5e1fdb4c109f2425e27 (commit) via 8c4f5457aa185bc9d74b6962aaafdd263ea6af56 (commit) via febe83c4243520ccc64544026d5f496ef945a9aa (commit) from c8ef736370483df6feb761b49fccaa6790b6f8c2 (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=04c881207f903f48bd5863bc851b… commit 04c881207f903f48bd5863bc851b8384a06578de Author: Harald Welte <laforge(a)gnumonks.org> Date: Tue Oct 3 18:34:48 2017 +0800 stats_test: Extend check to include test for counter group name mangling In Change-Id Ifc6ac824f5dae9a848bb4a5d067c64a69eb40b56 we introduce name mangling to replace any '.' in counter (group) names to be converted to ':'. Let's test for this functionality explicitly as part of the stats_test. Change-Id: Ie35682aa79526e2ffeab6995cd640b7847d855bf http://cgit.osmocom.org/libosmocore/commit/?id=a7a5065385be71239d49bb60a690… commit a7a5065385be71239d49bb60a690402d3153eb34 Author: Harald Welte <laforge(a)gnumonks.org> Date: Tue Oct 3 17:49:21 2017 +0800 Convert lib-internal rate_ctr from '.' separator to ':' separator The rate_ctr.c code would do this mangling automatically, but let's avoid using this from new versions of our code for simplicity/explicitness. Change-Id: I24a556f447cfac25efb6e83cac2d0c2972d98fe3 http://cgit.osmocom.org/libosmocore/commit/?id=ae510dc4a743e981b40fc5e1fdb4… commit ae510dc4a743e981b40fc5e1fdb4c109f2425e27 Author: Harald Welte <laforge(a)gnumonks.org> Date: Tue Oct 3 17:46:14 2017 +0800 rate_ctr: Enforce counter (and ctr_group) names are valid identifiers As rate counters are automatically exposed on the CTRL interface, we need to make sure they don't contain special characters such as '.' which are not permitted/supported by CTRL. In order to be able to run old versions of osmocom programs with libosmocore versions after this commit, we introduce some special name mangling: Any '.' in the names are replaced with ':' during counter group registration, if valid identifiers can be obtained this way. Change-Id: Ifc6ac824f5dae9a848bb4a5d067c64a69eb40b56 http://cgit.osmocom.org/libosmocore/commit/?id=8c4f5457aa185bc9d74b6962aaaf… commit 8c4f5457aa185bc9d74b6962aaafdd263ea6af56 Author: Harald Welte <laforge(a)gnumonks.org> Date: Tue Oct 3 17:44:03 2017 +0800 fsm: Enforce FSM and FSM instance names are valid osmocom identifiers Let's enforce that the names of FSMs and their instances are valid osmocom identifiers. This is important as the FSMs are automatically exported via those names on the CTRL inteface, and we have to make sure CTRL syntax actually permits them. Change-Id: I9ef59432f43a3cdb94e4cbb0c44ac3f9b2aac0f2 http://cgit.osmocom.org/libosmocore/commit/?id=febe83c4243520ccc64544026d5f… commit febe83c4243520ccc64544026d5f496ef945a9aa Author: Harald Welte <laforge(a)gnumonks.org> Date: Tue Oct 3 17:41:59 2017 +0800 Introduce osmo_identifier_valid() function to check validity of identifier We define the notion of an 'osmocom identifier' which is basically a 7-bit US-ASCII without any special characters beyond "-_:@". We introduce a function to verify if an identifier consists only of the permitted characters. Change-Id: I96a8d345c5a69238a12d040f39b70c485a5c421c ----------------------------------------------------------------------- Summary of changes: include/osmocom/core/rate_ctr.h | 2 +- include/osmocom/core/utils.h | 3 + src/fsm.c | 13 ++++- src/gb/gprs_bssgp.c | 10 ++-- src/gb/gprs_ns.c | 14 ++--- src/rate_ctr.c | 118 +++++++++++++++++++++++++++++++++++++++- src/utils.c | 28 ++++++++++ tests/gb/gprs_ns_test.c | 2 +- tests/stats/stats_test.c | 43 ++++++++++----- tests/stats/stats_test.ok | 108 ++++++++++++++++++++++-------------- 10 files changed, 270 insertions(+), 71 deletions(-) hooks/post-receive -- An utility library for Open Source Mobile Communications

7 years, 8 months

osmo-hlr.git branch neels/subscr_ctrl created. 0.0.1-111-ga64fbcc

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, neels/subscr_ctrl has been created at a64fbccd0570cab900d2e729d929b61627927278 (commit) - Log ----------------------------------------------------------------- http://cgit.osmocom.org/osmo-hlr/commit/?id=a64fbccd0570cab900d2e729d929b61… commit a64fbccd0570cab900d2e729d929b61627927278 Author: Neels Hofmeyr <neels(a)hofmeyr.de> Date: Tue Oct 17 22:26:00 2017 +0200 test_subscriber.ctrl: test against octal/hex interpretation of id Add a large enough subscriber id and add a test that ensures a leading zero is not interpreted as octal, and that a leading 0x is invalid and not interpreted as hexadecimal. Change-Id: Ib468b7cb595cf52331ebb41e6de0e8f57f69e173 http://cgit.osmocom.org/osmo-hlr/commit/?id=f2a15dd9d3295a12c445b66598e0987… commit f2a15dd9d3295a12c445b66598e09872f90c8f83 Author: Neels Hofmeyr <neels(a)hofmeyr.de> Date: Tue Oct 17 01:58:24 2017 +0200 ctrl: completely replace all CTRL commands The previous commands are not conforming to how the CTRL interface is intended to work: SET enable-ps <IMSI> SET disable-ps <IMSI> SET status-ps <IMSI> 'status-ps' is a write-only command even though it returns the status. 'enable-ps' / 'disable-ps' indicate the value instead of a variable name of an entity. The entity <IMSI> takes the place of the variable value. See also https://lists.osmocom.org/pipermail/openbsc/2017-September/011236.html Instead, replace with SET subscriber.by-imsi-123456.ps-enabled {0,1} GET subscriber.by-imsi-123456.ps-enabled and also provide further CTRL functions while at it: {SET,GET} subscriber.by-{imsi,msisdn,id}-123456.{cs,ps}-enabled {0,1} GET subscriber.by-{imsi,msisdn,id}-123456.{info,info-aud,info-all} Provide CTRL tests in the form of transcripts. Adjust tests/test_subscriber.sql to feature nonzero SQN, to see some values for SQN in the CTRL transcript tests. (This does not affect the VTY tests, because that creates its own subscribers, and there's no VTY command to set the SQN.) This is the first time an application uses CTRL_NODE ids that are defined outside of libosmocore, see 'Depends' below. Implementation choice: the first idea was to have a '.' between the 'by-xxx' and the value, like: subscriber.by-xxx.123456.function but the difficulty with subscribers is that they are not in RAM, and I can't just point node_data at a struct instance that is always there (like, say, a global bts[0] struct in osmo-bsc). Instead, I want to store the selector and later decide whether to read from the DB or whatever. With a '.' separating things, the only way in a ctrl function to obtain both 'by-xxx' and '123456' for picking a subscriber record would be to parse the entire variable path string elements, including 'subscriber' and 'function', which would then also clumsily fix at which node level we hook these commands; there could have been separate CTRL_NODE_SUBSCR_BY_{IMSI,MSISDN,ID} parent nodes, but we cannot introspect the current parent node dynamically within a ctrl function handler (plus I'm not sure whether it's possible and a good idea to have the same command under multiple parent nodes). Rather than that, I store the 'by-foo-123' token in the node_data pointer to have both bits of information pointed at by a single pointer; I use the incoming command parsing to get this token pre-separated from surrounding node names, and no need to re-allocate it, since the vector of tokens lives until after command execution is complete. Each leaf command obtains this token from cmd->node (aka node_data), and feeds this token to a common static function to parse selector and value from it and to retrieve a subscriber record as needed. (BTW, I have mentioned on the mailing list that this way might be necessary to avoid numeric-only CTRL node names, but we don't need to, and that is not at all related to this choice of structure.) Depends: libosmocore I1bd62ae0d4eefde7e1517db15a2155640a1bab58 libosmocore Ic9dba0e4a1eb5a7dc3cee2f181b9024ed4fc7005 Change-Id: I98ee6a06b3aa6a67adb868e0b63b0e04eb42eb50 http://cgit.osmocom.org/osmo-hlr/commit/?id=1eed54f449413a6168f2f74c74cf39f… commit 1eed54f449413a6168f2f74c74cf39f5cb1475d8 Author: Neels Hofmeyr <neels(a)hofmeyr.de> Date: Tue Oct 24 17:23:04 2017 +0200 cosmetic: tweak params of hlr_controlif_setup() Cosmetically prepare for adding new CTRL commands in hlr_controlif_setup(): - drop unused 'gs' param. - use ctrl_interface_setup_dynip2(), so far with default CTRL nodes; custom nodes will be added soon. Prepares: I98ee6a06b3aa6a67adb868e0b63b0e04eb42eb50 Change-Id: I63004a7953b04988449697dbc5d55d7ed0c6d82d ----------------------------------------------------------------------- hooks/post-receive -- UNNAMED PROJECT

7 years, 8 months

osmo-gsm-manuals.git branch neels/osmo-hlr updated. 8a08220bbb0086220922b91e8dbd59e6164aeaf7

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 "Manuals for Osmocom GSM components". The branch, neels/osmo-hlr has been updated via 8a08220bbb0086220922b91e8dbd59e6164aeaf7 (commit) via 38b7cff16cee2fb787ca26e2e892dc93e6c9e06c (commit) from 68a9801c88b20f717cee3ccab29d57ec07be91d5 (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-gsm-manuals/commit/?id=8a08220bbb0086220922b91… commit 8a08220bbb0086220922b91e8dbd59e6164aeaf7 Author: Neels Hofmeyr <neels(a)hofmeyr.de> Date: Tue Oct 24 15:47:12 2017 +0200 OsmoHLR: update ctrl description and examples The patch to refactor ctrl commands to osmo-hlr, change I98ee6a06b3aa6a67adb868e0b63b0e04eb42eb50, was tweaked. Adjust accordingly. Change-Id: Ie4da6115bb2eb005a9f95bf4de1bfe36468fd607 http://cgit.osmocom.org/osmo-gsm-manuals/commit/?id=38b7cff16cee2fb787ca26e… commit 38b7cff16cee2fb787ca26e2e892dc93e6c9e06c Author: Neels Hofmeyr <neels(a)hofmeyr.de> Date: Tue Oct 24 14:31:13 2017 +0200 OsmoHLR: add make target to update the example ctrl and vty files Change-Id: I88027396ec15101697a79aa5e964387d47abdae2 ----------------------------------------------------------------------- Summary of changes: OsmoHLR/Makefile | 41 +++++++++++++++++++++++++++ OsmoHLR/chapters/control.adoc | 13 ++++++--- OsmoHLR/example_subscriber_cs_ps_enabled.ctrl | 25 ++++++++++++++++ OsmoHLR/example_subscriber_info.ctrl | 18 ++++++++++-- 4 files changed, 91 insertions(+), 6 deletions(-) hooks/post-receive -- Manuals for Osmocom GSM components

7 years, 8 months

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

osmocom-commitlog