I decided to drop the 'any' keyword from the Abis bind address config, to
ensure that the written config is always identical to the parsed config.
Neels Hofmeyr (1):
ipa driver: make bind address vty configurable
include/internal.h | 3 +++
include/osmocom/abis/e1_input.h | 1 +
src/e1_input_vty.c | 20 ++++++++++++++++++++
src/input/ipaccess.c | 28 ++++++++++++++++++++++++++--
4 files changed, 50 insertions(+), 2 deletions(-)
--
2.1.4
I decided to drop the 'any' keyword from the Abis bind address config, to
ensure that the written config is always identical to the parsed config.
Neels Hofmeyr (1):
ipa driver: make bind address vty configurable
include/internal.h | 3 +++
include/osmocom/abis/e1_input.h | 1 +
src/e1_input_vty.c | 20 ++++++++++++++++++++
src/input/ipaccess.c | 28 ++++++++++++++++++++++++++--
4 files changed, 50 insertions(+), 2 deletions(-)
--
2.1.4
This patch allows Abis/IP bind address config for osmo-nitb as well as the
osmo-bscs, without touching openbsc.git.
This is the libosmo-abis part of making osmo-nitb's IP addresses configurable
instead of always listening on 'any'. This will allow running more than one on
the same box. Ctrl interface and vty are to follow, though not in this repo.
I did sink a bit of time until the penny dropped that all I need to do is add a
VTY command in libosmo-abis, but I did find out eventually.
Neels Hofmeyr (1):
ipa driver: make bind address vty configurable
include/internal.h | 3 +++
include/osmocom/abis/e1_input.h | 1 +
src/e1_input_vty.c | 27 +++++++++++++++++++++++++++
src/input/ipaccess.c | 28 ++++++++++++++++++++++++++--
4 files changed, 57 insertions(+), 2 deletions(-)
--
2.1.4
Hi Daniel,
the 'jerlbeck/fixes/sgsn' branch has been merged to master. sysmocom-iu
has some merge conflicts in the SGSN, so I assume it's better if you do
the rebase of sysmocom-iu onto master. Agree? It would also be nice if we
did the merge together ... maybe ping me when you do the rebase and I'll
see if I join you.
I would like to stay as close to master as possible to avoid conflict
build up. If you could do the rebase sooner rather than later, that would
be great. Thanks!
(I could have told you in person but it's good to let the list know, too)
~Neels
--
- Neels Hofmeyr <nhofmeyr(a)sysmocom.de> http://www.sysmocom.de/
=======================================================================
* sysmocom - systems for mobile communications GmbH
* Alt-Moabit 93
* 10559 Berlin, Germany
* Sitz / Registered office: Berlin, HRB 134158 B
* Geschäftsführer / Managing Directors: Holger Freyther, Harald Welte
Hi Harald,
Holger has just refreshed my memory on a conversation we've had on running
multiple NITB instances on the same box: Linux Network Namespaces vs.
making NITB configurable.
Kindly remind me of the immediate plans, should we make osmo-nitb
configurable to bind on only specific IP addresses, like, now?
IIUC that would be a VTY item for osmo-nitb and a parameter into
libosmo-abis. Concerning the VTY, the port could be configurable, or the
IP address, thinking of 127.0.0.42.
I guess relying on `ip netns` would be quicker for now, and I'd have
slightly more time for IuCS.
Is there anyone else out there that would love to configure osmo-nitb to
bind on specific IP addresses only?
Thanks,
~Neels
--
- Neels Hofmeyr <nhofmeyr(a)sysmocom.de> http://www.sysmocom.de/
=======================================================================
* sysmocom - systems for mobile communications GmbH
* Alt-Moabit 93
* 10559 Berlin, Germany
* Sitz / Registered office: Berlin, HRB 134158 B
* Geschäftsführer / Managing Directors: Holger Freyther, Harald Welte
Moin Daniel :)
(1)
About ebd4d820b3b0d7ba5db3b25a14f407d0c7276044
"libiu: Use custom setupormodifieditemies function"
It seems you forgot to commit the actual function definition of
ranap_decode_rab_setupormodifieditemies_fromlist()
I got the caller of it only and thus can't compile as-is.
(2)
About 38e2f1bca4e43414ed39a938d7c5d8bafe5e8533
"
Revert "iu.c: avoid warning by declaring ranap_free_rab_setupormodifieditemies()"
There should be no need to silence this warning, the ranap_free_*
functions are declared in libranap headers. In any case this will only
obscure any real issue. Maybe osmo-iuh was not rebuilt completely
(including generation of the c files from the python script).
This reverts commit 05ae5b1245f95bf765b42e49af7b2596e013f0a0.
"
I declared ranap_free_rab_setupormodifieditemies() like that because it is
indeed not declared in a header that is installed. Also a grep tells me
that no ranap_free_* is found in any osmo-iuh header file at all.
I also did a 'make regen' in osmo-iuh/src/ to no avail.
By 'libranap headers' I assume you mean libosmo-ranap, or is there a
libranap I'm not aware of yet?
If the ranap_free_* aren't in headers yet, I agree that they should be. I
wanted to silence the warning without being sucked down the rabbit hole of
autogenerated asn1 stuff. Any suggestions: more than welcome.
(3)
In general, I would welcome to see more of your WIP work in publicly
visible private branches, maturing as you go and merged to sysmocom/iu
once ready. For one, having a backup of your work-in-progress in the git
repos makes it harder to lose it due to hardware failure. More important
for me though is that I can see what you're up to, e.g. I could possibly
find the ranap_..._fromlist() function defintion now. It's of course
opening up your "most private" code developments to the outside world,
possibly some stupid commits will be seen by one or two hacker peers, but
I think it's a healthy premise that we all commit mostly bollocks and all
needs refinement anyway... once again: push it! :)
Ah, push it
Push it good
Ah, push it
Pu-Push it real good
-- Salt N Pepa (1987)
As always I'm open to opinions and suggestions...
~Neels
--
- Neels Hofmeyr <nhofmeyr(a)sysmocom.de> http://www.sysmocom.de/
=======================================================================
* sysmocom - systems for mobile communications GmbH
* Alt-Moabit 93
* 10559 Berlin, Germany
* Sitz / Registered office: Berlin, HRB 134158 B
* Geschäftsführer / Managing Directors: Holger Freyther, Harald Welte
From: Max <msuraev(a)sysmocom.de>
Previously the presence of header and data blocks were communicated
in-band which decreases code readability and makes it unnecessary hard
to add support for new hardware.
Note: OsmoBTS have to be modified to take advantage of extended
ph_data_param structure.
---
TODO-RELEASE | 1 +
include/osmocom/gsm/l1sap.h | 11 +++++++++++
2 files changed, 12 insertions(+)
diff --git a/TODO-RELEASE b/TODO-RELEASE
index edf1099..0939336 100644
--- a/TODO-RELEASE
+++ b/TODO-RELEASE
@@ -1,2 +1,3 @@
#library what description / commit summary line
libosmocore change major external talloc dependency / internal talloc removal
+libosmocore change major size of ph_data_param struct changed / Extend L1SAP PH-DATA with presence information
\ No newline at end of file
diff --git a/include/osmocom/gsm/l1sap.h b/include/osmocom/gsm/l1sap.h
index 9f3fe98..1af8ba8 100644
--- a/include/osmocom/gsm/l1sap.h
+++ b/include/osmocom/gsm/l1sap.h
@@ -25,6 +25,16 @@ enum osmo_mph_info_type {
PRIM_INFO_DEACT_CIPH, /*!< \brief Deactivation of ciphering */
};
+/*! \brief PH-DATA presence information */
+enum osmo_ph_pres_info_type {
+ PRES_INFO_INVALID = 0, /*!< \brief Data is invalid */
+ PRES_INFO_HEADER = 1, /*!< \brief Only header is present and valid */
+ PRES_INFO_FIRST = 3, /*!< \brief First half of data + header are valid (2nd half may be present but invalid) */
+ PRES_INFO_SECOND = 5, /*!< \brief Second half of data + header are valid (1st halfmay be present but invalid) */
+ PRES_INFO_BOTH = 7, /*!< \brief Both parts + header are present and valid */
+ PRES_INFO_UNKNOWN
+};
+
/*! \brief for PH-RANDOM_ACCESS.req */
struct ph_rach_req_param {
uint8_t ra; /*!< \brief Random Access */
@@ -48,6 +58,7 @@ struct ph_data_param {
uint8_t chan_nr; /*!< \brief Channel Number (Like RSL) */
uint32_t fn; /*!< \brief GSM Frame Number */
int8_t rssi; /*!< \brief RSSI of receivedindication */
+ enum osmo_ph_pres_info_type pdch_presence_info; /*!< \brief Info regarding presence/validity of header and data parts */
};
/*! \brief for TCH.{req,ind} | TCH-RTS.ind */
--
2.7.1
Hi all!
Moving all projects to a Redmine is a good way, I think.
In connection with the event I would like to offer my help with
post-processing some old pages (mostly OsmocomBB) and with
improving the new wiki structure.
So, my suggestions:
- Create the main page that will describe all all of the child projects
of Osmocom umbrella including recent news and plans.
- Separate the libosmocore related pages from OsmocomBB
into a new section named "Libraries", for example.
- Separate both SIMTrace and softSIM into a new sections.
It it would be nice to enable Strict-Transport-Security to avoid
some traffic interception attempts. Also what about enabling
SPF and DKIM for mailing lists?
With best regards,
Vadim Yanitskiy.
2016-02-19 4:46 GMT+06:00 <openbsc-request(a)lists.osmocom.org>:
> Send OpenBSC mailing list submissions to
> openbsc(a)lists.osmocom.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://lists.osmocom.org/mailman/listinfo/openbsc
> or, via email, send a message with subject or body 'help' to
> openbsc-request(a)lists.osmocom.org
>
> You can reach the person managing the list at
> openbsc-owner(a)lists.osmocom.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of OpenBSC digest..."
>
>
> Today's Topics:
>
> 1. Re: autoreconf v2.69 with subdir-objects: ./configure creates
> directory 'src/tests/\$(top_srcdir)' (Neels Hofmeyr)
> 2. Re: hnb_cs_lu.msc (Neels Hofmeyr)
> 3. Re: hnb_cs_lu.msc (Harald Welte)
> 4. branches: daniel/gprs-iu + sysmocom/cscn = sysmocom/iu;
> merging to master (Neels Hofmeyr)
> 5. Re: Moving from trac to a single redmine (Harald Welte)
> 6. Re: Moving from trac to a single redmine (Holger Freyther)
> 7. Re: branches: daniel/gprs-iu + sysmocom/cscn = sysmocom/iu;
> merging to master (Holger Freyther)
> 8. sysmocom/iu: your commits from today (Neels Hofmeyr)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Wed, 17 Feb 2016 15:44:35 +0100
> From: Neels Hofmeyr <nhofmeyr(a)sysmocom.de>
> To: Eric Blake <eblake(a)redhat.com>
> Cc: bug-autoconf(a)gnu.org, openbsc(a)lists.osmocom.org
> Subject: Re: autoreconf v2.69 with subdir-objects: ./configure creates
> directory 'src/tests/\$(top_srcdir)'
> Message-ID: <20160217144435.GD2106@dub6>
> Content-Type: text/plain; charset="us-ascii"
>
> Eric,
>
> you've clarified just about all of my questions.
> Many thanks for your reply!
>
> ~Neels
>
> > https://lists.gnu.org/archive/html/automake/2015-12/msg00001.html
>