OpenBSC October 2011

openbsc@lists.osmocom.org

23 participants
37 discussions

Re: [RFT] Couple of changes to nanoBTS and nokia insites bootup sequences to be tested
by Dieter Spaar 17 Oct '11

17 Oct '11

Hello Sylvain, On Mon, 17 Oct 2011 14:11:58 +0200, "Sylvain Munaut" <246tnt(a)gmail.com> wrote: > And also a fix for the Nokia InSite startup sequence where the reset > command was not sent due to missing initialization of .do_reset. The Reset command was enabled in my initial version. As far as I know it was intentionally disabled during the CCC camp to get faster turnaround times while setting up the camp network. Its possible to skip the reset if nothing has changed in the configuration, however if for example the ARFCN is changed, the reset is required (it might be possible to do a TRX-only reset but I never tested it). Best regards, Dieter -- Dieter Spaar, Germany spaar(a)mirider.augusta.de

1 0

Re: [RFT] Couple of changes to nanoBTS and nokia bootup sequences to be tested
by Sylvain Munaut 17 Oct '11

17 Oct '11

Hi, > The Reset command was enabled in my initial version. As far as I know > it was intentionally disabled during the CCC camp to get faster > turnaround times while setting up the camp network. > > Its possible to skip the reset if nothing has changed in the configuration, > however if for example the ARFCN is changed, the reset is required (it > might be possible to do a TRX-only reset but I never tested it). Mmm, I'll retry tonight but at least with the new LAPD code I had trouble when the reset wasn't there. Actually to get it to start I have to: - After powering it, wait for like 10 min. (If I try to start openbsc any sooner, it will never bootstrap) - Then start openbsc with the 'reset' part in it. But I could add this 'reset' process as an nokia specific option to the vty (i.e. reset_on_start or something ). Cheers, Sylvain

1 0

libosmocore ABI change (libosmocore-3.0.0.so)
by Harald Welte 17 Oct '11

17 Oct '11

Hi all, this is just a heads-up: The ABI of the osmo_timer has just changed (due to merging pablo's rb_tree based timer implementation instead of our linked list one). The API has not changed, so simply recompiling the programs against the new library header files will work. As a result, I have bumped the major library version, resulting in libosmocore-3.0.0.so. There is also a new version tag to mark this change: 0.4.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)

1 0

[ANNOUNCE] First OsmocomGMR code release
by Harald Welte 16 Oct '11

16 Oct '11

First Osmocom GMR code release As some of the readers may already know, a couple of Osmocom developers have been working on a new sub-project: OsmocomGMR. The primary goal of this project is to provide a reusable and clean implementation of the various layers of GMR-1. What is GMR-1 ? Well, it stands for "GEO Mobile Radio" and it's a set of specifications describing a satellite based mobile phone network heavily inspired from GSM. One of the major commercial operators of GMR-1 technology is "Thuraya", providing coverage over Europe/Africa/Asia/Australia. So far the implementation focused on the lowest layers: * Physical layer with FCCH sync and demodulation support for * pi4-CBPSK and pi4-CQPSK bursts. * Channel coding layer (scrambling/puncturing/convolutional coding/crc/interleaving/...) And some ancillary tools to exploit those: * A good capture tool to listen to particular ARFCN(s) and channelize them properly * Wireshark support (BCCH only so far) The first 'demo application' using all of the above provides functionalities similar to what airprobe is for GSM: An air interface protocol analyzer that goes all the way from capturing data off-the-air to sending packets to wireshark for analysis. Limited to BCCH only currently but this will evolve with time. Development was mainly done by Sylvain Munaut, with help from Dimitri Stolnikov (early signal captures and his great capture tool), Harald Welte (initiating the project) and Steve Margraf (testing different setup and antenna ideas). If you'd like to know more, you are encourated to read the wiki (http://gmr.osmocom.org/) and join the mailing list (http://lists.osmocom.org/mailman/listinfo/gmr) -- - 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)

1 0

GPRS not coming up on NanoBTS 140
by Gus Bourg 15 Oct '11

15 Oct '11

Hello all, Looking for ideas. I have a NanoBTS Model 140 which doesn't seem to work with GPRS. It never connects to the SGSN. The openbsc/sgsn environment is ok - I can swap in another nano and it works fine. I've taken some log captures:

4 3

RFC: sgsn should command/response set to 1 in gsm48_tx_gmm_ra_upd_rej?
by Holger Hans Peter Freyther 15 Oct '11

15 Oct '11

Hi, I think the REJECT should be sent with the C/R bit set to 1? holger

1 2

"Mandatory info element out of sequence"
by anish achenkunju 14 Oct '11

14 Oct '11

Hi All, I'm getting the following error "Received packet without a valid source address!!!" on sgsnemu 0.84 [root@n003-000-000-000 openggsn-0.84]# sgsnemu --listen 7.7.7.7 --remote 7.7.7.1 --timelimit 10 --contexts 1 --apn internet --imsi 2400112 34567890 --msisdn 46702123456 -u root -p nsil --createif --defaultroute Using default DNS server Local IP address is: 7.7.7.7 (7.7.7.7) Remote IP address is: 7.7.7.1 (7.7.7.1) IMSI is: 240011234567890 (0xf098765432110042) Using NSAPI: 0 Using GTP version: 1 Using APN: internet Using selection mode: 1 Using MSISDN: 46702123456 Initialising GTP library openggsn[4597]: GTP: gtp_newgsn() started Setting up interface Done initialising GTP library Sending off echo request Setting up PDP context #0 Waiting for response from ggsn........ Received echo response Received create PDP context response. IP address: 218.59.100.38 Disconnecting PDP context #0 Received packet without a valid source address!!! [root@n003-000-000-000 openggsn-0.84]# The error I get on GGSN (Cisco 7200) on debugging is "Mandatory info element out of sequence" *Oct 13 17:01:42.444: GTP IE:4200113254769800:rcvd 0 out of order previous IE 0 *Oct 13 17:01:42.448: %GTP-2-PDPACTIVATIONFAIL: GTP PDP activation/update failed, GSN: 0.0.0.0, TID: 00, Reason: Mandatory info element out of sequence I'm sticking with 0.84 as 0.91 has a bug while sending echo " Mandatory IE invalid" . Any help on this is greatly appreciated. Thank you, Anish

2 1

libosmocore licensing
by Alexander Chemeris 13 Oct '11

13 Oct '11

Hi all, but especially Harald, We're looking for a good library with complex arithmetic, bit functions and other RF processing stuff to be used as a base for porting of our WiMAX stuff to C/C++. I'm looking at libosmocore as a perfect candidate for that, but we're going to release our work under LGPL and thus we want an LGPL base library. I wonder, is it possible to re-license libosmocore under LGPL instead of GPL? I know that Sylvain has no strong objections about that. Harald, Holger and other contributors - what would you say? In general, I believe that LGPL is much better suited for libraries then GPL and many widely used libraries, like ffmpeg, use it with great success. And I wish libosmocore to be as successful as those LGPL libraries. PS Our WiMAX effort is to create an open-source receiver for Mobile WiMAX: http://code.google.com/p/wimax-scanner/ We have written somewhat working Matlab code and we're going to port it to something more real-time now. -- Regards, Alexander Chemeris.

1 0

libosmocore lapd_rx_u and unitialized rc
by Holger Hans Peter Freyther 12 Oct '11

12 Oct '11

Hi all, in the above method there are paths were rc will never be initialized. I think initializing rc = 0 or -EINVAL would be cheating, instead we should consider splitting it into manageable pieces. holger

1 0

[PATCH 0/1] [v2] openbsc (master): libctrl: bugfix to prevent a SIGABRT
by Alexander Huemer 12 Oct '11

12 Oct '11

In case the control interface on TCP port 4249 is used in an unintended way, a SIGABRT can be caused because of a missing initialization of a msgb*. The upcoming patch fixes this bug. If the patch seems useful, please feel free to merge it. Kind regards, -Alexander Huemer Alexander Huemer(1): libctrl: only free() msgb if it was alloc()ed openbsc/src/libctrl/control_if.c | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-)

1 1

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

OpenBSC October 2011