osmocom-commitlog February 2016

osmocom-commitlog@lists.osmocom.org

1 participants
159 discussions

libosmo-abis.git branch master updated. 0.3.2-2-g0db1d43

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 0db1d43c0d6bdf4c2e67a07ebf77923e9e191aff (commit) from 86fc3c8787a9c29f566a44969d528a604ee7e11f (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 ----------------------------------------------------------------- ----------------------------------------------------------------------- Summary of changes: include/internal.h | 3 +++ include/osmocom/abis/e1_input.h | 1 + src/e1_input_vty.c | 19 +++++++++++++++++++ src/input/ipaccess.c | 23 +++++++++++++++++++++-- 4 files changed, 44 insertions(+), 2 deletions(-) hooks/post-receive -- Osmocom A-bis protcol interface library

9 years, 5 months

libosmo-abis.git branch neels/bind updated. 0.3.2-2-g0db1d43

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, neels/bind has been updated discards 518cca04b7feeda3995cf4c15066aafa918d341d (commit) via 0db1d43c0d6bdf4c2e67a07ebf77923e9e191aff (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 (518cca04b7feeda3995cf4c15066aafa918d341d) \ N -- N -- N (0db1d43c0d6bdf4c2e67a07ebf77923e9e191aff) 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/libosmo-abis/commit/?id=0db1d43c0d6bdf4c2e67a07ebf7… commit 0db1d43c0d6bdf4c2e67a07ebf77923e9e191aff Author: Neels Hofmeyr <nhofmeyr(a)sysmocom.de> Date: Mon Feb 22 13:29:09 2016 +0100 ipa driver: make bind address vty configurable Add VTY function to set the ipa bind address: e1_input ipa bind A.B.C.D Add a priv pointer to struct e1inp_driver in order to communicate the bind address parameter to ipaccess_line_update(). Add two "internal.h" functions to get/set it in the ipa driver struct. Add static ip_bind_addr() to use the IP address set from the VTY or, if NULL, use "0.0.0.0". Apply in ipaccess_line_update(). ----------------------------------------------------------------------- Summary of changes: include/internal.h | 4 ++-- include/osmocom/abis/e1_input.h | 2 +- src/e1_input_vty.c | 18 +++++------------- src/input/ipaccess.c | 31 +++++++++++++------------------ 4 files changed, 21 insertions(+), 34 deletions(-) hooks/post-receive -- Osmocom A-bis protcol interface library

9 years, 5 months

osmo-pcu.git branch max/pacch updated. 0.2-752-g86581a5

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, max/pacch has been updated via 86581a56341fc41838eaa1cb7e07adaf8236215d (commit) from 0ba0d186a558a9bcf75fabdb4649970439a58c29 (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-pcu/commit/?id=86581a56341fc41838eaa1cb7e07ada… commit 86581a56341fc41838eaa1cb7e07adaf8236215d Author: Max <msuraev(a)sysmocom.de> Date: Thu Feb 25 11:40:06 2016 +0100 further expand rlcmac diag ----------------------------------------------------------------------- Summary of changes: src/bts.cpp | 2 +- src/tbf.cpp | 13 ++++++++++--- 2 files changed, 11 insertions(+), 4 deletions(-) hooks/post-receive -- UNNAMED PROJECT

9 years, 5 months

libosmocore.git branch master updated. 0.9.0-80-gf81eb32

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 f81eb328b61f65a09b7233aaa70b2f655c0300bc (commit) via 4934309dab3dcd785e75f3ba227e51b19fe714fb (commit) via 96172f01002a64359bbe643c4a0d3cfa9a929b56 (commit) from cc00bf8779f48fd1e592fc7d0a60fc00b04826cd (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 ----------------------------------------------------------------- ----------------------------------------------------------------------- Summary of changes: include/Makefile.am | 3 +- include/osmocom/ctrl/control_if.h | 4 ++ include/osmocom/ctrl/control_vty.h | 9 ++++ include/osmocom/vty/command.h | 2 +- include/osmocom/vty/vty.h | 3 ++ src/ctrl/Makefile.am | 4 ++ src/ctrl/control_if.c | 10 ++++- src/ctrl/control_vty.c | 88 ++++++++++++++++++++++++++++++++++++++ src/vty/vty.c | 28 ++++++++++++ 9 files changed, 148 insertions(+), 3 deletions(-) create mode 100644 include/osmocom/ctrl/control_vty.h create mode 100644 src/ctrl/control_vty.c hooks/post-receive -- An utility library for Open Source Mobile Communications

9 years, 5 months

libosmocore.git branch neels/bind updated. 0.9.0-80-gf81eb32

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, neels/bind has been updated discards 32655ae179533b1c925481e88e16c19755793903 (commit) discards f16588988123af283cbb3fc851f4163b46ea76e0 (commit) discards 00fe6d3b89f34bc1b5274bf71579af0cf7633ed3 (commit) via f81eb328b61f65a09b7233aaa70b2f655c0300bc (commit) via 4934309dab3dcd785e75f3ba227e51b19fe714fb (commit) via 96172f01002a64359bbe643c4a0d3cfa9a929b56 (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 (32655ae179533b1c925481e88e16c19755793903) \ N -- N -- N (f81eb328b61f65a09b7233aaa70b2f655c0300bc) 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/libosmocore/commit/?id=f81eb328b61f65a09b7233aaa70b… commit f81eb328b61f65a09b7233aaa70b2f655c0300bc Author: Neels Hofmeyr <nhofmeyr(a)sysmocom.de> Date: Wed Feb 24 00:10:41 2016 +0100 vty: add ctrl section for Control interface bind address This may seem like overkill for a mere const char * config item, but it makes the Control interface VTY commands reusable in any main() scope (inspired by libosmo-abis' VTY config). Add API functions ctrl_vty_init() and ctrl_vty_get_bind_addr(), in new files src/ctrl/control_vty.c and include/osmocom/ctrl/control_vty.h, compiled and/or installed dependent on ENABLE_VTY. Using these functions allows configuring a static const char* with the VTY commands ctrl bind A.B.C.D which callers shall subsequently use to bind the Control interface to a specific local interface address, by passing the return value of ctrl_vty_get_bind_addr() to control_interface_setup(). Add CTRL_NODE to enum node_type, "eating" RESERVED4_NODE to heed that comment on avoiding ABI changes. http://cgit.osmocom.org/libosmocore/commit/?id=4934309dab3dcd785e75f3ba227e… commit 4934309dab3dcd785e75f3ba227e51b19fe714fb Author: Neels Hofmeyr <nhofmeyr(a)sysmocom.de> Date: Wed Feb 24 00:09:40 2016 +0100 add ctrl_interface_setup_dynip() for bind address Make the ctrl interface bind address configurable, so that it may be made available on other addresses than 127.0.0.1. The specific aim is to allow running multiple osmo-nitbs alongside each other (commits in openbsc follow). http://cgit.osmocom.org/libosmocore/commit/?id=96172f01002a64359bbe643c4a0d… commit 96172f01002a64359bbe643c4a0d3cfa9a929b56 Author: Neels Hofmeyr <nhofmeyr(a)sysmocom.de> Date: Tue Feb 23 14:01:41 2016 +0100 vty: add bind command for telnet vty line Add VTY command line vty bind A.B.C.D The command merely stores the configured IP-address, which can then be used by the calling main program to set the telnet port of the VTY line. (Commits in openbsc and osmo-iuh will follow up on this.) Add function vty_get_bind_addr() to publish the address in the vty.h API. Add static vty_bind_addr to store. For allocation/freeing reasons, a NULL address defaults to 127.0.0.1. BTW, I decided against allowing keywords 'any' and 'localhost' in place of an actual IP address to make sure a written config is always identical to the parsed config. ----------------------------------------------------------------------- Summary of changes: src/ctrl/control_vty.c | 10 ++++------ src/vty/vty.c | 2 +- 2 files changed, 5 insertions(+), 7 deletions(-) hooks/post-receive -- An utility library for Open Source Mobile Communications

9 years, 5 months

osmo-iuh.git branch neels/wip updated. 9e2a714e961c57d25973ec9404d4f201961332bf

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 code for Iuh interface". The branch, neels/wip has been updated discards d67f3709709c4932152767e8dea61201f75fa7bf (commit) discards 9ab9d756246966ab56f051aeb162cfbcc6531204 (commit) discards d5b80a185c84233fc17466204641b43b5eeb8804 (commit) discards 465d29560fc1232ceea1567a8861502052d47d63 (commit) discards 5b5dcf6306283367221fb7ef38374b8088747f01 (commit) discards 7a299f3dea615058f075797597f9aefdff6286ec (commit) via 9e2a714e961c57d25973ec9404d4f201961332bf (commit) via daa5e698dd08a5f6b82bdf32617daa0e1e026219 (commit) via cad87ce10d97ac428cfa7bb2bbd17987e590b749 (commit) via ffe109207642e49f4f15635ee050f90093e4e982 (commit) via cddc33889f05730b26031ae6cc21941199014170 (commit) via 0968a588362efdebb24183c0e5f164346d3fed34 (commit) via a0d21479a775583cd3dc2bb55295b089284a1b07 (commit) via 19dea8b49b538a1918bd25d814c212fe397b3cad (commit) via ce5b9965f94839c79128c6ff72034995022db1de (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 (d67f3709709c4932152767e8dea61201f75fa7bf) \ N -- N -- N (9e2a714e961c57d25973ec9404d4f201961332bf) 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-iuh/commit/?id=9e2a714e961c57d25973ec9404d4f20… commit 9e2a714e961c57d25973ec9404d4f201961332bf Author: Neels Hofmeyr <nhofmeyr(a)sysmocom.de> Date: Thu Feb 18 23:03:15 2016 +0100 hnb-test: attempt to reply to an MM Identity Request http://cgit.osmocom.org/osmo-iuh/commit/?id=daa5e698dd08a5f6b82bdf32617daa0… commit daa5e698dd08a5f6b82bdf32617daa0e1e026219 Author: Neels Hofmeyr <nhofmeyr(a)sysmocom.de> Date: Thu Feb 18 01:18:20 2016 +0100 hnb-test: decode NAS pdu when receiving RUA from CN http://cgit.osmocom.org/osmo-iuh/commit/?id=cad87ce10d97ac428cfa7bb2bbd1798… commit cad87ce10d97ac428cfa7bb2bbd17987e590b749 Author: Neels Hofmeyr <nhofmeyr(a)sysmocom.de> Date: Thu Jan 14 13:06:47 2016 +0100 hnb-test: tweak comment http://cgit.osmocom.org/osmo-iuh/commit/?id=ffe109207642e49f4f15635ee050f90… commit ffe109207642e49f4f15635ee050f90093e4e982 Author: Neels Hofmeyr <nhofmeyr(a)sysmocom.de> Date: Thu Jan 14 13:05:24 2016 +0100 hnb-test: comment on gen_initue_lu() IMSI http://cgit.osmocom.org/osmo-iuh/commit/?id=cddc33889f05730b26031ae6cc21941… commit cddc33889f05730b26031ae6cc21941199014170 Author: Neels Hofmeyr <nhofmeyr(a)sysmocom.de> Date: Thu Jan 14 12:52:53 2016 +0100 move dummy_cn to 127.0.0.2 (Iu-PS) because I'm testing Osmo-CSCN on 127.0.0.1 (Iu-CS) http://cgit.osmocom.org/osmo-iuh/commit/?id=0968a588362efdebb24183c0e5f1643… commit 0968a588362efdebb24183c0e5f164346d3fed34 Author: Neels Hofmeyr <nhofmeyr(a)sysmocom.de> Date: Mon Jan 11 15:19:38 2016 +0100 hnb-test: some rua rx printfs http://cgit.osmocom.org/osmo-iuh/commit/?id=a0d21479a775583cd3dc2bb55295b08… commit a0d21479a775583cd3dc2bb55295b089284a1b07 Author: Neels Hofmeyr <nhofmeyr(a)sysmocom.de> Date: Wed Feb 24 20:50:31 2016 +0100 osmo-hnbgw, hnb-test: allow configuring VTY address ----------------------------------------------------------------------- Summary of changes: asn1/utils/asn1tostruct.py | 12 + include/osmocom/ranap/ranap_ies_defs.h | 317 ++++++++++++++++++++++- specs/by_chapter/25.931.pdf | 1 + specs/by_name/examples_signalling_procedures.pdf | 1 + specs/files/tr_125931v130000p.pdf | Bin 0 -> 918422 bytes src/hnbgw.c | 6 +- src/tests/hnb-test.c | 3 +- 7 files changed, 337 insertions(+), 3 deletions(-) create mode 120000 specs/by_chapter/25.931.pdf create mode 120000 specs/by_name/examples_signalling_procedures.pdf create mode 100644 specs/files/tr_125931v130000p.pdf hooks/post-receive -- Osmocom code for Iuh interface

9 years, 5 months

openbsc.git branch neels/bind updated. 0.15.0-179-g7597337

by gitosis＠osmocom.org

9 years, 5 months

openbsc.git branch neels/bind updated. 0.15.0-179-gb95a611

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, neels/bind has been updated discards 5e490419f2be30df330ca19cd219090ba8aa7eae (commit) discards 3b017c73e40769f15ee76dfbb55e63b31c143958 (commit) discards 5cf85a69e55e6eae3a26c7b72f1d0deb81afdcda (commit) discards dfe28a47032700d4cbeaf051a40c0f1f1f8bd94a (commit) discards c9ba14034b4f5a811aa6bba8657f08a84b4d4346 (commit) discards 62320a2c970bdda0458ed12a2ea9bfa3cd496c2b (commit) via b95a6113acc0d4372d000c29a37592d9b80b8f1c (commit) via ee6844b26642a6bc2a3893bc46351a17b1f40df8 (commit) via 4d919de0b22485f211a4398ef174691739d863c4 (commit) via c655f6bf311d4533c13309660eb5f9b2cb6c6631 (commit) via a180f6472cfaa7d89824a7777173cd0bf5af7aa2 (commit) via 271db46716db46adc5c65b018d11258bb7a23a03 (commit) via 18394fdbed069f03c2c7ad910632bfba84acdc04 (commit) via 75b580869498966c1359b7ab6588f7ac80422337 (commit) via d5dee43a03b6f8c34460d6f7e74f5bea16d72439 (commit) via f25f8cebb58ad1f5241a33d9bac76654cd2a68a2 (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 (5e490419f2be30df330ca19cd219090ba8aa7eae) \ N -- N -- N (b95a6113acc0d4372d000c29a37592d9b80b8f1c) 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=b95a6113acc0d4372d000c29a37592d9… commit b95a6113acc0d4372d000c29a37592d9b80b8f1c Author: Neels Hofmeyr <nhofmeyr(a)sysmocom.de> Date: Wed Feb 24 19:15:39 2016 +0100 smpp: refactor initialization, add bind address Make the SMPP bind address configurable (used to be harcoded as "0.0.0.0"). However, to be useful, this patch has to go somewhat further: refactor the initialization procedure, because it was impossible to run the VTY commands without an already established connection. The SMPP initialization procedure was weird. It would first open a connection on the default port, and a subsequent VTY port reconfiguration while reading the config file would try to re-establish a connection on a different port. If that failed, smpp would switch back to the default port instead of failing the program launch as the user would expect. If anything else ran on port 2775, SMPP would thus refuse to launch despite the config file having a different port: the first bind would always happen on 0.0.0.0:2775. Change that. In the VTY commands, merely store address and port if no fd is established yet. Introduce several SMPP initialization stages: * allocate struct and initialize pointers, * then read config file without immediately starting to listen, * and once the main program is ready, start listening. After that, the VTY command behaves as before: try to re-establish the old connection if the newly supplied address and port don't work out. I'm not actually sure why this switch-back behavior is needed, but fair enough. In detail, replace the function smpp_smsc_init() with the various steps smpp_smsc_alloc_init() -- prepare struct for VTY commands smpp_smsc_conf() -- set addr an port only, for reading the config file smpp_smsc_start() -- establish a first connection, for main() smpp_smsc_restart() -- switch running connection, for telnet VTY smpp_smsc_stop() -- tear down connection, used by _start() twice And replace smpp_openbsc_init() smpp_openbsc_set_net() with smpp_openbsc_alloc_init() smpp_openbsc_start() I'd have picked function names like "_bind"/"_unbind", but in the SMPP protocol there is also a bind/unbind process, so instead I chose the names "_start", "_restart" and "_stop". The smsc struct used to be talloc'd outside of smpp_smsc_init(). Since the smsc code internally uses talloc anyway and employs the smsc struct as talloc context, I decided to enforce talloc allocation within smpp_smsc_alloc_init(). Be stricter about osmo_signal_register_handler() return codes. http://cgit.osmocom.org/openbsc/commit/?id=ee6844b26642a6bc2a3893bc46351a17… commit ee6844b26642a6bc2a3893bc46351a17b1f40df8 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=4d919de0b22485f211a4398ef1746917… commit 4d919de0b22485f211a4398ef174691739d863c4 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=c655f6bf311d4533c13309660eb5f9b2… commit c655f6bf311d4533c13309660eb5f9b2cb6c6631 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=a180f6472cfaa7d89824a7777173cd0b… commit a180f6472cfaa7d89824a7777173cd0bf5af7aa2 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=271db46716db46adc5c65b018d11258b… commit 271db46716db46adc5c65b018d11258bb7a23a03 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. http://cgit.osmocom.org/openbsc/commit/?id=18394fdbed069f03c2c7ad910632bfba… commit 18394fdbed069f03c2c7ad910632bfba84acdc04 Author: Neels Hofmeyr <nhofmeyr(a)sysmocom.de> Date: Wed Feb 24 19:30:52 2016 +0100 gsm340_rx_tpdu: comment-out two unused vars Kills two compiler warnings. http://cgit.osmocom.org/openbsc/commit/?id=75b580869498966c1359b7ab6588f7ac… commit 75b580869498966c1359b7ab6588f7ac80422337 Author: Neels Hofmeyr <nhofmeyr(a)sysmocom.de> Date: Wed Feb 24 19:29:59 2016 +0100 ipaccess_rcvmsg: fix returncode, add partial write warning Kills a compiler warning. http://cgit.osmocom.org/openbsc/commit/?id=d5dee43a03b6f8c34460d6f7e74f5bea… commit d5dee43a03b6f8c34460d6f7e74f5bea16d72439 Author: Neels Hofmeyr <nhofmeyr(a)sysmocom.de> Date: Wed Feb 24 03:12:44 2016 +0100 bsc_nat: fail if VTY telnet port cannot be bound, clarify comment http://cgit.osmocom.org/openbsc/commit/?id=f25f8cebb58ad1f5241a33d9bac76654… commit f25f8cebb58ad1f5241a33d9bac76654cd2a68a2 Author: Neels Hofmeyr <nhofmeyr(a)sysmocom.de> Date: Wed Feb 24 19:31:33 2016 +0100 remove warning on 64bit, add warning on i386? ----------------------------------------------------------------------- Summary of changes: openbsc/include/openbsc/smpp.h | 4 +- openbsc/src/gprs/sgsn_ctrl.c | 2 +- openbsc/src/ipaccess/ipaccess-proxy.c | 8 +++- openbsc/src/libbsc/bsc_ctrl_lookup.c | 4 +- openbsc/src/libmsc/gsm_04_11.c | 7 ++- openbsc/src/libmsc/smpp_openbsc.c | 43 ++++++++++------- openbsc/src/libmsc/smpp_smsc.c | 90 +++++++++++++++++++++++++---------- openbsc/src/libmsc/smpp_smsc.h | 7 ++- openbsc/src/libmsc/smpp_vty.c | 75 ++++++++++++++++++++++++----- openbsc/src/osmo-bsc/osmo_bsc_vty.c | 4 +- openbsc/src/osmo-nitb/bsc_hack.c | 4 +- 11 files changed, 183 insertions(+), 65 deletions(-) hooks/post-receive -- The OpenBSC GSM Base Station Controller (+MSC/HLR/SGSN)

9 years, 5 months

openbsc.git branch sysmocom/iu updated. 0.15.0-284-g772f348

by gitosis＠osmocom.org

9 years, 5 months

libosmocore.git branch neels/bind updated. 0.9.0-80-g32655ae

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, neels/bind has been updated discards 469390d8e461e178a48d1790d084ce559f9e9ca3 (commit) discards b2f7b00356d2a32f8c3bf53636ea082a6cf0f6b2 (commit) via 32655ae179533b1c925481e88e16c19755793903 (commit) via f16588988123af283cbb3fc851f4163b46ea76e0 (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 (469390d8e461e178a48d1790d084ce559f9e9ca3) \ N -- N -- N (32655ae179533b1c925481e88e16c19755793903) 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/libosmocore/commit/?id=32655ae179533b1c925481e88e16… commit 32655ae179533b1c925481e88e16c19755793903 Author: Neels Hofmeyr <nhofmeyr(a)sysmocom.de> Date: Wed Feb 24 00:10:41 2016 +0100 vty: add ctrl section for Control interface bind address This may seem like overkill for a mere const char * config item, but it makes the Control interface VTY commands reusable in any main() scope (inspired by libosmo-abis' VTY config). Add API functions ctrl_vty_init() and ctrl_vty_get_bind_addr(), in new files src/ctrl/control_vty.c and include/osmocom/ctrl/control_vty.h, compiled and/or installed dependent on ENABLE_VTY. Using these functions allows configuring a static const char* with the VTY commands ctrl bind A.B.C.D which callers shall subsequently use to bind the Control interface to a specific local interface address, by passing the return value of ctrl_vty_get_bind_addr() to control_interface_setup(). Add CTRL_NODE to enum node_type, "eating" RESERVED4_NODE to heed that comment on avoiding ABI changes. http://cgit.osmocom.org/libosmocore/commit/?id=f16588988123af283cbb3fc851f4… commit f16588988123af283cbb3fc851f4163b46ea76e0 Author: Neels Hofmeyr <nhofmeyr(a)sysmocom.de> Date: Wed Feb 24 00:09:40 2016 +0100 add ctrl_interface_setup_dynip() for bind address Make the ctrl interface bind address configurable, so that it may be made available on other addresses than 127.0.0.1. The specific aim is to allow running multiple osmo-nitbs alongside each other (commits in openbsc follow). ----------------------------------------------------------------------- Summary of changes: include/osmocom/vty/command.h | 3 +-- src/ctrl/control_vty.c | 6 +++--- 2 files changed, 4 insertions(+), 5 deletions(-) hooks/post-receive -- An utility library for Open Source Mobile Communications

9 years, 5 months

← Newer
1
2
3
4
5
6
7
8
...
16
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

osmocom-commitlog February 2016