openbsc.git branch neels/bind updated. 0.15.0-174-g3b017c7

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, neels/bind has been updated discards f99e2722c1203456fdc5e798098ee433e876b403 (commit) discards b9a35ba970c31cafdc2d5954d47317570aab5ce9 (commit) discards 9566a666b187bca3ef3e3a4101692cc9d89f872c (commit) discards 89638275e2ec12e9f9fbdc0797ba75b0b456e02b (commit) discards d06c2082663241b9f0fab52c7448756f44fb307f (commit) via 3b017c73e40769f15ee76dfbb55e63b31c143958 (commit) via 5cf85a69e55e6eae3a26c7b72f1d0deb81afdcda (commit) via dfe28a47032700d4cbeaf051a40c0f1f1f8bd94a (commit) via c9ba14034b4f5a811aa6bba8657f08a84b4d4346 (commit) via 62320a2c970bdda0458ed12a2ea9bfa3cd496c2b (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 (f99e2722c1203456fdc5e798098ee433e876b403) \ N -- N -- N (3b017c73e40769f15ee76dfbb55e63b31c143958) 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=3b017c73e40769f15ee76dfbb55e63b3… commit 3b017c73e40769f15ee76dfbb55e63b31c143958 Author: Neels Hofmeyr <nhofmeyr(a)sysmocom.de> Date: Tue Feb 23 15:10:33 2016 +0100 enable ctrl bind config for various programs Add ctrl_vty_init() calls and feed the ctrl_vty_get_bind_addr() return value to ctrl_interface_setup() in the following programs: osmo-bsc osmo-bsc_nat osmo-nitb osmo-sgsn For osmo-sgsn, move the control interface setup invocation below the config parsing, so that the ctrl_vty_get_bind_addr() can return the configured address. http://cgit.osmocom.org/openbsc/commit/?id=5cf85a69e55e6eae3a26c7b72f1d0deb… commit 5cf85a69e55e6eae3a26c7b72f1d0deb81afdcda Author: Neels Hofmeyr <nhofmeyr(a)sysmocom.de> Date: Tue Feb 23 14:59:43 2016 +0100 osmo-nitb: be strict about cmdline args Abort upon unknown options and missing option arguments. This came to my attention while rewiring the -m and -M options: passing -M without argument would launch nitb with wrong configuration. So, rather exit immediately. If there are legacy options that should be ignored, they deserve an own 'case:' in the option switch. There are none that I'm aware of though. http://cgit.osmocom.org/openbsc/commit/?id=dfe28a47032700d4cbeaf051a40c0f1f… commit dfe28a47032700d4cbeaf051a40c0f1f1f8bd94a Author: Neels Hofmeyr <nhofmeyr(a)sysmocom.de> Date: Tue Feb 23 14:57:22 2016 +0100 osmo-nitb: cosmetic: rename to rf_ctrl_path, following mncc_sock_path Strictly speaking, the unix domain socket location is not a name but a path. The MNCC socket is called path, so it is confusing to call the ctrl socket a 'name'. http://cgit.osmocom.org/openbsc/commit/?id=c9ba14034b4f5a811aa6bba8657f08a8… commit c9ba14034b4f5a811aa6bba8657f08a84b4d4346 Author: Neels Hofmeyr <nhofmeyr(a)sysmocom.de> Date: Tue Feb 23 14:55:17 2016 +0100 osmo-nitb: add -M to pass specific MNCC socket path The old -m option without argument is still available and marked deprecated, to not make users' lives more difficult than necessary. http://cgit.osmocom.org/openbsc/commit/?id=62320a2c970bdda0458ed12a2ea9bfa3… commit 62320a2c970bdda0458ed12a2ea9bfa3cd496c2b Author: Neels Hofmeyr <nhofmeyr(a)sysmocom.de> Date: Tue Feb 23 14:09:38 2016 +0100 enable telnet VTY bind address config for various programs Following the 'line vty'/'bind A.B.C.D' command added in libosmocore, use the configured address to set the telnet bind for the VTY line. It is now possible to publish the VTY on a specific local interface (including 0.0.0.0 aka "any"). Implement in all of: osmo-gbproxy osmo-gtphub osmo-sgsn osmo-bsc osmo-bsc_nat osmo-bsc_mgcp osmo-nitb In some of these main programs, move the telnet initialization below the configuration parsing. Historically, this was not a good idea for programs using bsc_init.c (aka bsc_bootstrap_network()), since they expected a gsm_network struct pointer in ((struct telnet_connection*)vty->priv)->priv, so that telnet had to be either initialized or replaced by a dummy struct. In the meantime, the gsm_network struct is not actually looked up in a priv pointer but in the static bsc_vty.c scope (bsc_gsmnet), so this limitation is mere legacy (even though said legacy is still there in an "#if 0" chunk). In the other binaries I have briefly looked at the init sequence dependencies and found no reason to initialize telnet above the config file parsing. In any case, I have tested every single one of abovementioned binaries to verify that they still parse the example config successfully and launch, allowing VTY connections on the configured address(es). I hope this suffices. In all of the above, log VTY address and port. LOGL_INFO is disabled by default in some of the logging scopes, and since it is a single log message right at program launch, I decided for the slightly more aggressive LOGL_NOTICE. ----------------------------------------------------------------------- Summary of changes: hooks/post-receive -- The OpenBSC GSM Base Station Controller (+MSC/HLR/SGSN)