OpenBSC

openbsc@lists.osmocom.org

4317 discussions

[PATCH 0/4] openbsc: various improvements and fixes
by Alexander Huemer 24 May '11

24 May '11

These are improvements for the autoconf input of openbsc, an update to .gitignore, and a fix for a segfault. Please integrate them, if they seem useful. Alexander Huemer (4): openbsc: add missing AC_LANG_SOURCE for current autoconf openbsc: rename configure.in -> configure.ac openbsc: update .gitignore libabis: fix segfault on malformed ipaccess RSL link openbsc/.gitignore | 3 +++ openbsc/{configure.in => configure.ac} | 2 +- openbsc/src/libabis/input/ipaccess.c | 5 ++++- 3 files changed, 8 insertions(+), 2 deletions(-)

1 4

[PATCH 0/3] new VTY commands to enable IPA proxy
by pablo＠gnumonks.org 23 May '11

23 May '11

From: Pablo Neira Ayuso <pablo(a)gnumonks.org> Hi! This patchset adds new VTY commands that allows to route IPA flows. Patch 3/3 includes one feature that changes the current default behaviour of OpenBSC since you explicity have to make a "ipa setup" to enable OML and RSL links. If you like it, I can make a similar patch for HSL femto, so the only initial open socket is the one at port 4242 for telnet configuration. BTW, the original command syntax was proposed by Harald. Successfully tested bootstrapping the nanoBTS. See the patches for more details. Comments welcome! Pablo Neira Ayuso (3): libcommon: add make_sock_stream_connect() libabis: add VTY commands to route IPA flows libabis: add IPA VTY command to setup ip.access nanoBTS OML and RSL links openbsc/include/openbsc/ipaccess.h | 3 + openbsc/include/openbsc/socket.h | 2 + openbsc/include/openbsc/vty.h | 1 + openbsc/src/ipaccess/Makefile.am | 4 +- openbsc/src/libabis/Makefile.am | 2 +- openbsc/src/libabis/e1_input.c | 2 + openbsc/src/libabis/input/ipaccess.c | 962 +++++++++++++++++++++++++++++- openbsc/src/libbsc/bsc_vty.c | 1 + openbsc/src/libcommon/socket.c | 54 ++ openbsc/src/openbsc.cfg.ipa-proxy | 18 + openbsc/src/openbsc.cfg.nanobts | 3 + openbsc/src/openbsc.cfg.nanobts.multitrx | 3 + openbsc/tests/db/Makefile.am | 5 +- 13 files changed, 1043 insertions(+), 17 deletions(-) create mode 100644 openbsc/src/openbsc.cfg.ipa-proxy -- 1.7.2.3

3 5

[PATCH 0/4] openBSC: minor fixes and updates
by pablo＠gnumonks.org 22 May '11

22 May '11

From: Pablo Neira Ayuso <pablo(a)gnumonks.org> This patchset contains minor fixes and updates. You can find them in pablo/updates branch. Merge it if you consider that they're OK. Thanks. Pablo Neira Ayuso (4): abis: skip e1_input nesting if empty libbsc: fix bail out in case of problems bootstrapping BTS or E1 input libabis: add init function for emulated ipaccess/HSL emulated E1 input bsc: on-demand setup of nanoBTS and HSL femto sockets openbsc/include/openbsc/Makefile.am | 3 ++- openbsc/include/openbsc/bss.h | 17 +++++++++++++++++ openbsc/include/openbsc/e1_input.h | 1 + openbsc/include/openbsc/gsm_data.h | 3 +++ openbsc/src/libabis/e1_input.c | 4 ++++ openbsc/src/libabis/e1_input_vty.c | 3 +++ openbsc/src/libabis/input/hsl.c | 11 +++++------ openbsc/src/libabis/input/ipaccess.c | 11 +++++------ openbsc/src/libbsc/Makefile.am | 2 +- openbsc/src/libbsc/bsc_init.c | 23 ++++++++++++++--------- openbsc/src/libbsc/bts_ericsson_rbs2000.c | 10 +++++++++- openbsc/src/libbsc/bts_hsl_femtocell.c | 11 ++++++++++- openbsc/src/libbsc/bts_init.c | 29 +++++++++++++++++++++++++++++ openbsc/src/libbsc/bts_ipaccess_nanobts.c | 12 +++++++++++- openbsc/src/libbsc/bts_siemens_bs11.c | 10 +++++++++- openbsc/src/libcommon/gsm_data.c | 8 ++++++++ openbsc/src/osmo-bsc/osmo_bsc_main.c | 11 ++--------- openbsc/src/osmo-nitb/bsc_hack.c | 17 ++--------------- 18 files changed, 135 insertions(+), 51 deletions(-) create mode 100644 openbsc/include/openbsc/bss.h create mode 100644 openbsc/src/libbsc/bts_init.c -- 1.7.2.3

2 5

fix missing all logging command option
by Pablo Neira Ayuso 18 May '11

18 May '11

Hi Holger, Thanks for fixing this, I missed it: http://cgit.osmocom.org/cgit/libosmocore/commit/?id=952a18ed19f531b82e26108… However, this fix is incomplete: /* This generates the logging command string for VTY. */ const char *log_vty_command_string(const struct log_info *info) { int len = 0, offset = 0, ret, i, rem; int size = strlen("logging level () ()") + 1; ^^ We also have to add `(all|' there.

2 2

Problems suspected to be related to _output() rework
by Harald Welte 18 May '11

18 May '11

Hi Pablo! I am sometimes getting osmo-nitb segfaults, and sometimes random bytes as output of log messages. I've quickly started it in valgrind, and even during connection of the BTS I get the following issues: <000d> input/ipaccess.c:693 accept()ed new OML link from 192.168.200.117 ==21897== Conditional jump or move depends on uninitialised value(s) ==21897== at 0x60D4BD4: vfprintf (vfprintf.c:1620) ==21897== by 0x60F8F01: vsnprintf (vsnprintf.c:120) ==21897== by 0x4E33670: _output (logging.c:177) ==21897== by 0x4E33878: _logp (logging.c:227) ==21897== by 0x4E33BCB: logp2 (logging.c:246) ==21897== by 0x435E5C: listen_fd_cb (ipaccess.c:692) ==21897== by 0x4E32419: osmo_select_main (select.c:132) ==21897== by 0x40555B: main (bsc_hack.c:306) ==21897== ==21897== Use of uninitialised value of size 8 ==21897== at 0x60D5008: vfprintf (vfprintf.c:1620) ==21897== by 0x60F8F01: vsnprintf (vsnprintf.c:120) ==21897== by 0x4E33670: _output (logging.c:177) ==21897== by 0x4E33878: _logp (logging.c:227) ==21897== by 0x4E33BCB: logp2 (logging.c:246) ==21897== by 0x435E5C: listen_fd_cb (ipaccess.c:692) ==21897== by 0x4E32419: osmo_select_main (select.c:132) ==21897== by 0x40555B: main (bsc_hack.c:306) ==21897== ==21897== Use of uninitialised value of size 8 ==21897== at 0x6101CE0: _IO_default_xsputn (genops.c:480) ==21897== by 0x60D4ED3: vfprintf (vfprintf.c:1620) ==21897== by 0x60F8F01: vsnprintf (vsnprintf.c:120) ==21897== by 0x4E33670: _output (logging.c:177) ==21897== by 0x4E33878: _logp (logging.c:227) ==21897== by 0x4E33BCB: logp2 (logging.c:246) ==21897== by 0x435E5C: listen_fd_cb (ipaccess.c:692) ==21897== by 0x4E32419: osmo_select_main (select.c:132) ==21897== by 0x40555B: main (bsc_hack.c:306) ==21897== ==21897== Conditional jump or move depends on uninitialised value(s) ==21897== at 0x6101CF2: _IO_default_xsputn (genops.c:479) ==21897== by 0x60D4ED3: vfprintf (vfprintf.c:1620) ==21897== by 0x60F8F01: vsnprintf (vsnprintf.c:120) ==21897== by 0x4E33670: _output (logging.c:177) ==21897== by 0x4E33878: _logp (logging.c:227) ==21897== by 0x4E33BCB: logp2 (logging.c:246) ==21897== by 0x435E5C: listen_fd_cb (ipaccess.c:692) ==21897== by 0x4E32419: osmo_select_main (select.c:132) ==21897== by 0x40555B: main (bsc_hack.c:306) ==21897== <000d> input/ipaccess.c:755 accept()ed new RSL link from 192.168.200.117 <0004> bsc_init.c:251 bootstrapping RSL for BTS/TRX (0/0) on ARFCN 871 using MCC=602 MNC=42 LAC=1 CID=0 BSIC=63 TSC=7 ==21897== Use of uninitialised value of size 8 ==21897== at 0x60D2EDB: _itoa_word (_itoa.c:195) ==21897== by 0x60D5386: vfprintf (vfprintf.c:1619) ==21897== by 0x60F8F01: vsnprintf (vsnprintf.c:120) ==21897== by 0x4E33670: _output (logging.c:177) ==21897== by 0x4E33878: _logp (logging.c:227) ==21897== by 0x4E33BCB: logp2 (logging.c:246) ==21897== by 0x410141: inp_sig_cb (bsc_init.c:247) Can you please investigate? I suspect it to be related to your recent _output() related changes in libosmocore. Regards, Harald -- - Harald Welte <laforge(a)gnumonks.org> http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6)

4 10

comment on ipaccess-find: Work without providing an interface name
by Pablo Neira Ayuso 17 May '11

17 May '11

Hi Holger, I think this patch is wrong: http://cgit.osmocom.org/cgit/openbsc/commit/?id=d3080be1317cfa0269b1c12c8f2… ifname should be set if argc == 2, but it seems to be set if argc < 2, in that case argv[1] is always NULL.

2 1

Re: Reseting Unit-ID on nanoBTS
by Holger Hans Peter Freyther 15 May '11

15 May '11

On 05/15/2011 06:05 PM, henry han wrote: > 你好! Ni Hao! do you think you could try to write in English?

1 0

Wanted: dpkg/deb/rpm package maintainer
by Harald Welte 14 May '11

14 May '11

Hi all, for quite some time we've been having debian dpkg packaging information as part of our libosmocore, libosmo-sccp, openggsn and openbsc repositories. As the library ABI sis now considered stable, it starts to make sense not only to release source tarballs, but also to offer .deb packages for ubunto and debian, probably both i386 and amd64 and lenny, squeeze and natty as well as ubuntu 10.04. The resulting packages could initially be hosted on an osmoxom.org apt feed that people can wimply put in their sources.list We're looking for somebody with dpkg packaging experience, who would volunteer to take care of building the deb files and maintaining that apt feed. If somebody wants to take care about RPM packaging, that would of course be also welcome. Thanks in advance, Harald -- Sent from a mobile device, excuse my short response

1 0

Osmocom project vs. sysmocom GmbH
by Harald Welte 13 May '11

13 May '11

Hi all! As some of you already know, Holger and I have recently started a new company called "sysmocom - systems for mobile communications GmbH". The process of establishing the new company has now formally concluded. Before some rumours start to spread, we would like to clarify some points and make sure there is mutual understanding between the Osmocom community and the sysmocom company. sysmocom is intended to provide commercial offerings related to the Osmocom projects. This is not entirely new. Especially on the network side, people like Holger and I have been doing quite a lot of paid development to bring those projects forward. We would not have many of the features we have today, if it wasn't for customers who actually pay us for development of OpenBSC, OsmoBSC, OsmoSGSN and the various side projects more targetted at a real network operator like cellmgr-ng, bsc-nat, gb_proxy - just to name a few. However, this has always only been freelancing development of Software. With sysmocom, we want to go one step further and work on hardware products related to the various Free Software projects. Right now I don't want to talk too much about unfinished products, but we are working towards an inexpensive BTS product, we are funding the prototypes for Osmocom SIMtrace, and we will likely also see stuff like OpenBSC appliances. Given our past involvement and exposure into other projects that share a split Free Software / business set-up, we think we understand very well where potential issues of conflict between the two sides may be. Let me make some more clarification what this is not about: * sysmocom is not about creating proprietary derivates of Osmocom software. We work on Free Software which is publicly available under OSI approved and FSF endorsed licenses. We may offer proprietary hardware and sometimes software - but those are independent projects from existing Osmocom software. * we specifically will not have a public and a non-public version of the same program with differences in features. * sysmocom is not a VC-funded startup. It's a very small company run out of personal funds with no intention to take external funding or grow rapidly. Nobody but Holger and I determine where it goes and what it does. * sysmocom does not hold any copyright on the Free Software projects. The copyrights stay distributed with the major authors such as Holger, Onwaves, Sylvain, Dieter, Andreas and myself. None of the others have any affiliation with sysmocom. I have (personally, unrelated to sysmocom) asked some of the smaller contributors for a copyright transfer to make sure we could do the AGPLv3 transition, or future re-licensing decisions without having to ask dozens and dozens of people. sysmocom does not seek to control the Free Software projects. * we will maintain a strict separation between the community side of things and the business side. Unlike some other popular projects, we will not end up in a situation where the osmocom.org websites will be full of advertisements and hidden links that lure you on the company website. * we will keep a strict separation of naming. Osmocom is for the FOSS projects, sysmocom for the business. The company will use the term "Osmocom" only in descriptive context, not as a product name, brand or for advertisement. If you do have any concerns, please feel free to share them. However, I'd like to avoid cross-posting them throguh different mailing lists. Please follow-up-to openbsc(a)lists.osmocom.org Regards, Harald -- - Harald Welte <hwelte(a)sysmocom.de> http://www.sysmocom.de/ ======================================================================= * sysmocom - systems for mobile communications GmbH * Schivelbeiner Str. 5 * 10439 Berlin, Germany * Sitz / Registered office: Berlin, HRB 134158 B * Geschaeftsfuehrer / Managing Directors: Holger Freyther, Harald Welte

1 0

Sim programmer Software for Linux
by Steve Mortimer 13 May '11

13 May '11

Hi, I am after recommendations for software that will allow me to program Super SIM's, etc. I have seen the recent thread on programmer's and understand that a CCID compliant reader is recommended. Many thanks, Steve

2 4

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

OpenBSC