25 Feb
2016
25 Feb
'16
11:02 a.m.
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