OpenBSC May 2011

openbsc@lists.osmocom.org

20 participants
42 discussions

Problems suspected to be related to _output() rework

by Harald Welte

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)

13 years, 10 months

comment on ipaccess-find: Work without providing an interface name

by Pablo Neira Ayuso

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.

13 years, 10 months

Re: Reseting Unit-ID on nanoBTS

by Holger Hans Peter Freyther

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

13 years, 10 months

Wanted: dpkg/deb/rpm package maintainer

by Harald Welte

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

13 years, 10 months

Osmocom project vs. sysmocom GmbH

by Harald Welte

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

13 years, 10 months

Sim programmer Software for Linux

by Steve Mortimer

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

13 years, 10 months

FrOSCon 2011 - DevRoom anyone?

by Peter Hasse

Hi I'm happy to invite you to the up comming FrOSCon. Like last year we can offer a developer room for the weekend and a official Licences to use one RFCN. We would futher be me more than happy to find some opensource GSM talks in our CFP. The FrOSCon 2011 takes palce in Sank Ausgustin near Bonn in Germany from the 20. to 21. August (one week after the CCC Camp). Below you find the offical CFP invite email. Looking forward to see some of you at FrOSCon 2011 mfg Peter Meanwhile, preparations for the sixth FrOSCon are well underway. This year's FrOSCon takes place on August 20th/21st 2011. We thought you might be interested to hear that the Call for Projects has started. If you as a project want to participate again, please visit https://callforprojects.froscon.org/ and sign up for a room or booth, depending on your needs. Since the demand for developer rooms and booths exceeds the number of rooms and booth we can offer, we need a short summary (1-2 paragraphs) of what you plan to do. On the basis of this text we will choose the projects that appear most promising to us. The deadline for submission of projects is 23rd May 2011. Additionally our Call for Papers has started, so we are looking forward to your submissions of talks. Please visit http://www.froscon.de/en/program/call- for-papers.html for further information. The Call for Papers will end on 23rd May 2011 If you have questions concerning the developer rooms feel free to contact projects(a)froscon.org <https://mng.derpeter.net/horde/imp/message.php?mailbox=FrOSCon.Orga&index=5…>. For questions concerning a booth contact exhibitors(a)froscon.org <https://mng.derpeter.net/horde/imp/message.php?mailbox=FrOSCon.Orga&index=5…> We would love to see all of you again in August. Also, please spread the word and help make this year's FrOSCon's special. Kind regards, Patrick Hallen The FrOSCon Team -- Address: FrOSCon e.V. c/o FH Bonn-Rhein-Sieg Grantham-Allee 20 53757 Sankt Augustin E-Mail: projects(a)froscon.org <https://mng.derpeter.net/horde/imp/message.php?mailbox=FrOSCon.Orga&index=5…> Homepage: http://www.froscon.org

13 years, 10 months

Planning for Radio Village at 2011 CCC Camp

by Harald Welte

Hi all! [This message is cross-posted to many lists, please be careful when replying to it! Think twice if your respones really matters to all those projects...] In order to do some better planning for our Camp activities this summer, I would like to request all people who intend to participate in the radio village to add themselves to the wiki: https://events.ccc.de/camp/2011/wiki/index.php/RadioVillage The list of citizens is auto-generated if you use Person template like I have done in my user page at https://events.ccc.de/camp/2011/wiki/index.php/User:LaForge The large main tent is not really intended as a place to sleep, but more like a place where we set up our gear and work on the various projects, similar to what happened at HAR. Thanks in advance! -- - 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)

13 years, 10 months

Questions

by Christopher HENARD

Hello everyone, 1) Is it possible to act as a nano BTS and send packets to open BSC ? But how to do that since openBSC uses config files (openbsc.cfg.nanobts, ...) ? 2)I can't get last source code with git, the command always results in a timeout: git clone git://git.osmocom.org/openbsc.git Cloning into openbsc... git.osmocom.org[0: 213.95.46.201]: errno=Connection timed out git.osmocom.org[0: 2001:780:45:f046::201]: errno=Network is unreachable fatal: unable to connect a socket (Network is unreachable) Would that be possible to update the tarballs on the wiki? It seems the current tarball of openBSC (http://openbsc.osmocom.org/trac/wiki) doesn't contains config files in the osmo-nitb directory. There's only source and makefile. The wiki mention 'OpenBSC has a configuration file. The default config file name is *openbsc.cfg* in the current working directory of the osmo-nitb process.' Thank you, Chris

13 years, 10 months

[ANN] libosmocore stable API/ABI

by Harald Welte

Hi all! I think now that the namespace issues in libosmocore have been resolved, we seriously have to think of maintaining a stable API and ABI. This allows us to have truly independent library and application releases, and the dynamic linker library versioning support should ensure compatibility. So please think twice about any modifying libosmocore. It is safe to add new functions, but we cannot change the prototypes (number of arguments) for existing functions. As soon as new functions are introduced, we should increment the library interface number. For more information, see http://www.gnu.org/software/libtool/manual/libtool.html#Versioning especially the rules in Chapter 7.3: # If the library source code has changed at all since the last update, then increment revision (‘c:r:a’ becomes ‘c:r+1:a’). # If any interfaces have been added, removed, or changed since the last update, increment current, and set revision to 0. # If any interfaces have been added since the last public release, then increment age. # If any interfaces have been removed or changed since the last public release, then set age to 0. 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)

13 years, 10 months

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

OpenBSC May 2011