OpenBSC

openbsc@lists.osmocom.org

4173 discussions

by Daniel Willmann

Hello, I've noticed that recent versions of bs11_config don't show all the infos they used to. commit eb429b7b44f1c39548a1995cb93484b9cbe2996e Author: Sylvain Munaut <tnt(a)246tNt.com> Date: Mon Oct 26 20:19:59 2009 +0100 [TLV] Split the parser into 'parse loop' and 'parse single value' seems to be the problem. If I revert it bs11_config query shows more information again. I've looked at the patch, but so far couldn't find out what it does differently. I'll keep looking, but maybe someone else has an idea. Regards, Daniel Willmann

15 years, 7 months

Branches update & things to consider for merging

by Sylvain Munaut

Hi, I've just tested code I started at 26c3 but didn't get a chance to test and I updated my various branches. Here's a little status : sylvain/rrlp : This contains only changes to rrlp-ephemeris. Mostly fixes and more support to provide assistance data. Also asn1c patches to fix bugs and a script for people to generate their own test data.ubx from their receiver (to get up-to-date / local data). sylvain/pending: Various things / fixes I made that I consider ready to be reviewed / merged. I tested it all on both my nanoBTS 139. sylvain/encryption: The current state of my encryption support work. I rebased it and used the db structure you pushed for encryption. Everything but the last 3 patches are pre-work / preparation / fixes and are imho OK. The last 3 patches are the real implementation and I also think they're in pretty good shape. Tested and working here :) Limitations includes : No Kc re-use & No MT encryption yet. sylvain/encryption_testing: More encryption work, based on sylvain/encryption but not done/ready. Only pushed so that people can have a peek ... Cheers, Sylvain

15 years, 7 months

Stack corruption from set_system_infos

by Holger Freyther

Hi Harald, I have a stack corruption due the above method and here is my analysis of the problem... set_system_infos is having a u_int8_t array with 23 bytes on the stack and is asking to generate system infos into this array... Now what happens is: 1.) some system information types structs are already bigger than the 23 bytes... 2.) this does not take the rest octets into account.. I would like to fix it like this: 1.) Turn bitvec_spare_padding to return void 2.) In the rest_octets_siX method return the bit_vec.data_len 3.) Change the generate_siX to return the sizeof the struct + return value of the rest_octets_siX instead of the fixed MACBLOCK_LEN (23) 4.) always use this rc value instead of the size of the buffer... (due to 1. of the above we set truncated values as well) do you have a better idea? would you just increase the buffer size? z.

15 years, 7 months

[PATCH 0/5] Change PLL set/work value

by Daniel Willmann

Hello, this list of patches includes support to change the PLL set and work value with bs11_config. Many thanks go to Dieter Spaar who figured out how to change the work value. Harald, if these patches are okay for you I'll go ahead and commit them. Regards, Daniel Willmann (5): [abis_nm] Add generic abis_nm_bs11_logon function [abis_nm] Add abis_nm_bs11_infield_logon to logon as user field [abis_nm] Add abis_nm_bs11_set_pll function to change the set/work value [bs11_config] Whitespace changes so the help text looks nice [bs11_config] Add pll-setvalue and pll-workvalue commands openbsc/include/openbsc/abis_nm.h | 3 ++ openbsc/src/abis_nm.c | 39 +++++++++++++++++++++++++--- openbsc/src/bs11_config.c | 50 +++++++++++++++++++++++++----------- 3 files changed, 72 insertions(+), 20 deletions(-)

15 years, 7 months

OpenBSC code questions

by Dimitris Karampatsis

Hello, I ‘ve tried to use the latest OpenBSC code with a nanoBTS at 850 MHz. I have been able to compile the code in Debian Linux and run it successfully. Mobiles were able to register successfully to the network. In addition the IMSI and TMSI numbers were collected successfully. However, I have encountered a few issues that are summarised below: - Segmentation faults (software crashes) occur in situations where I try to send an SMS message through the telnet interface or when I try to make a phone call from one mobile to another - When sending SMSs from one mobile to another, the SMS are collected successfully to the database but are not sent to the other mobile. In the telnet interface I use the command “SMS SEND PENDING” but nothing happens. The SMSs are sent to the terminating mobile when either restarting the OpenBSC software or when the terminating mobile re-registers to the OpenBSC network - IMEI numbers are sometimes not collected (especially on Nokia phones) or the wrong IMEI number is displayed Have anyone else noticed these issues? I am trying to install a debugger to check why the segmentation faults occurs. The only debugger that works is from Netbeans that uses the GDB debugger. However the debugger hangs when trying to initialise the database (it stucks in command dbi_initialize(NULL) on db.c file) Can anyone help why the debugger hangs or recommend a debugger that will work with this code? Many thanks Regards, Dimitris

15 years, 7 months

Question about the "Move db usage out of the libbsc (fork dumping of subscr)" commit

by Sylvain Munaut

Hi, I don't see how this commits helps ? The function code is exactly the same in both files and the db.c dependency in vty_interface.c hasn't been removed. Am I missing something here ? [ See commit 424c4f0e2927d5a7538b31c69113c6e4f861d2c9 on the git for context ] Sylvain

15 years, 7 months

Re: OpenBSC / GSM network at camp site

by ich＠henrik-hansen.de

On Fri, 01 Jan 2010 04:05:06 +0100, Miguel Elias <nobody_su(a)chaostreff.ch> wrote: > hi hi, nicht witzig ich arbeite momentan dran :) > 2m sind normalerweise für amateure verwendet, die bos sind normalerweise > auf 4m, aber dass heist nicht das auch auf den kommerziellen frequenzen > auch bos dienste möglich sind. Stimmt schon nur sagt die PDV/DV 800 (hab sie momentan nicht hier, daher kann ich nicht zitieren) das der 2m W/U Funk auf den Betriebskanälen nur für Übungs und einsatzzwecke zu verwenden ist. > ich sehe das nicht so eng und ich denke auch die bnetza nicht, da ihr > auf dem camp nicht den funkdienst mitsbraucht sondern auch da übungen > für eure feuerwehrarbeit. Die Interessiert das herzlich wenig, habe schon 4 auf 2m Relais gesehen um der knappheit an 4m Handfunkgeräten zu entgehen. Rechtlich gesehen absolutes no-go aber kratzt keinen. > es wird wird wohl einfacher sein, mehr dieser 2m funkgeräte zubesorgen > und zusätlich ein sog. relais zu besorgen, welches du dann an einem > hohen standort installieren müsstes... damit würdest jenach gegenheiten > bis zu 30km und mehr abdecken. Da kommen wir schonwieder zu diversen Problemen, BOS 2m Geräte sind eher unerschwinglich (minimum 300eu). Akkus sind relativ teuer. Und sie werden meißtens (99%) dafür angeschafft um auf Fahrzeugen verlastet zu sein. Um im Ernstfalle (Einsatzfall) halt Griffbereit zu sein. Das wir derzeit fürs Zeltlager diese Menge an 2m aus dem Tagesgeschäft rausziehen ist vielen aktiven Kammeraden ein riesiges Dorn im Auge. Und ehrlich gesagt will ich das auch nicht mehr, weil Funk nur dann funktioniert wenn alle richtig Mitspielen. Darüberhinaus habe ich selbst schon oft die erfahrung gemacht das man oft im Feld bei den Kids, es nicht mitbekommt wenn man selber gerufen wird. Und was passiert? 30sek. später klingelt das Handy. 30km hört sich zwar verdammt lecker an, ist aber nicht das was ich will. Fläche von ca 90.000 qm = quadrat von 300m :) (im idealfall) > eine BTS für ein soches netz aufzubauen ist zu einem gewissen grad ein > overkill... Finde ich nicht. Derzeit habe ich zwar noch nicht wirklich Informationen darüber welches Einzugsgebiet ich mit ner nanoBTS abdecken kann, aber wenns was werden sollte denke ich das wir minimum 2 eher 3 BTS'n aufbauen werden. Derzeit habe ich noch keine offiziellen Preise gefunden, aber bereits den Hinweis bekommen das die Kisten für rund 2.5keu über den Ladentisch gehen. Endgeräte finden sich in den meißten Haushalten. Ob man jetzt beigeht und sein primär Handy verwendet, oder das vor-24Monats Modell welches in der Schublade oxidiert, ist jetzt erstmal egal. Aber defakto ist doch das Endgeräte vorhanden sind. Weiterhin ist für mich entscheidend das niemand von mir eine Einweisung in ein Handy braucht. Im regelfall weiß jeder wie sein Handy funktioniert und wenn nicht... ich hab 2000 potentielle 1-Level-Supporter rumlaufen :D Letztlich denke ich das in vielen Köpfren vorhanden ist, das GSM bzw. Mobile Kommunikation immer was mit teurer Technik verbunden ist. Was defakto durch die Arbeit des openBTS Projekts einfach nicht mehr der fall ist. (An dieser Stelle nochmal vielen Dank für die tolle Arbeit) Ausserdem warum nicht? Was spricht dagegen GSM zu verwenden (und Geld ist für mich kein Grund)? Gruß Henrik

15 years, 8 months

Hello my name is ...

by ich＠henrik-hansen.de

Hi first i wan't to intoduce myself, i m henrik and am from germany. my english isn't good as is should be but i hope everyone can understand me. :) I'm searching for a Siemens BS-11 GSM1800. Why? Im the technical operator of the biggest summer-camp in lower saxony / germany of youth-fire-fighters. I know hard to understand. :D My plan is it, to operate a GSM zell on our camp next year. some background informations: -2000 youth member at the camp-ground. -up to 200 tecnical supporters. -300 youth supporters. more informations about the event 2009: http://www.zeltlager-2009.de/ The Mainorganisators of the camp know about this idea, and are willing to get a short-time licence for the event. The first contact to the "Bundesnetzagentur" is already done. What can i give the openBSC community? A place to test / benchmark OpenBSC. Also i'm a c / php developer and maybe i can help develope some external features for openBSC. Greetings from cold old Germany Henrik

15 years, 8 months

REQUEST: Letter of Support for OpenBSC

by Harald Welte

Dear List, some entities in the GSM Industry seem to have started to discredit our efforts for an Open Source implementation of GSM protocols. In order to prove them wrong and demonstrate the usefulness of OpenBSC, I would like to ask everyone who uses OpenBSC in a commercial or educational context (companies, universities, schools) to show their support by writing a letter of support. This is a way how you can contribute back to the OpenBSC project, even without writing any code. Simply put a couple of sentences on your letterhead where you explain that you use OpenBSC, and if or how you think it is a useful tool for your research and/or development. I will collect those letters and forward them to those who try to discredit us, and if that is not sufficient, put the letters on the project homepage and take that dispute somewhat more public. I'm looking forward to your letter. Thanks for your support! -- - 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)

15 years, 8 months

Work on ipaccess-config and software load

by Holger Freyther

Hi All, in the last couple of days I have implemented Software Loading for the nanoBTS. Use this at your own risk but it is working here(tm). Software Load is implemented as of the GSM 12.21 with some quirks and extra messages compared to the BS11. - BS11 got the length of the "length" wrong and it should have been a short. ipaccess got this right so I needed to change that part - For the nanoBTS in the SW Load Init and Load End message one needs to add the SW_DESCR IE but without a length. 12.21 would probably require the length but this is omitted. The other part is that the file id must be set to "id\0" and the version to "version\ 0" or at least was set like this in the example trace I had. - Strings must be written with the '\0' in it. - After the Software Load End ACK one needs to send a special SET NVATTR to set the software as default. The message must contain the ID and Version of two firmware parts. I'm not sure which funtional part they relate to but they have the "more more magic" ids of 0x1000 and 0x2001. I have changed ipaccess-config to exit after the software load, or setting the primary OML IP by handling the ACK and carrying a state. One can also chain "-r" and the above two so the primary action will be executed first and then the reset will be issue and with a reset ack/nack the app will exit. With doing the above it becomes aware that we should change ipaccess-config a lot, all the options you could enable should generate an operation and we should put these into a queue and then execute them one after another and exit once all of them are done but this will be a bigger project as we need some more cooperation with abis_nm.c. Is anyone volunteering to fix the structure of this small application helper? regards holger

15 years, 8 months

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

OpenBSC