OpenBSC

openbsc@lists.osmocom.org

4315 discussions

Bounce action notification
by mailman＠lists.osmocom.org 22 Jul '11

22 Jul '11

This is a Mailman mailing list bounce action notice: List: OpenBSC Member: christoph_schueler(a)web.de Action: Subscription disabled. Reason: Excessive or fatal bounces. The triggering bounce notice is attached below. Questions? Contact the Mailman site administrator at mailman(a)lists.osmocom.org.

1 0

Telecommunication and Wireless Hacking at CCC CAMP 2011
by Fabio Pietrosanti (naif) 22 Jul '11

22 Jul '11

Hi all, i just wanted to send a summary of all most cool talk that will be at CCC CAMP 2011 related to Telecommunications and Wireless Technologies hacking: Open-source 4G radio - It's time to start WiMAX and LTE hacking http://events.ccc.de/camp/2011/Fahrplan/events/4446.en.html Applied Research on security of TETRA radio - Digital radio technology beyond GSM http://events.ccc.de/camp/2011/Fahrplan/events/4496.en.html GPRS Intercept - Wardriving phone networks http://events.ccc.de/camp/2011/Fahrplan/events/4504.en.html Introduction to Satellite Communications - Installation and Operation of Satellite Systems http://events.ccc.de/camp/2011/Fahrplan/events/4442.en.html Transition Telecom - Telecommunications and networking during energy descent http://events.ccc.de/camp/2011/Fahrplan/events/4459.en.html Anyone missing to the list? -naif

1 1

[PATCH 0/4] logrotate related patches
by Daniel Willmann 19 Jul '11

19 Jul '11

Hi, this series of patches makes sure that the logs generated by osmo_pcap_server are cleaned up. I wasn't able to use logrotate since we wanted to keep the timestamped filenames and logrotate would treat every log as independent. The script now sorts the pcap logs per-client and deletes all but the newest N files. The oldest M remaining files will be compressed with gzip. Some small fixes for problems I encountered are included. I hope the requirement for libosmocore 0.3.2 is okay. Regards, Daniel Willmann (4): server: Fix memory leak and error handling in restart_pcap server: Register signal handler to reopen logfiles on SIGHUP Catch up with API change in osmo_sock_init contrib: Add a script to clean up in regular intervals Makefile.am | 2 +- configure.ac | 3 +- contrib/Makefile.am | 1 + contrib/clean_old | 46 ++++++++++++++++++++++++++++++++++ include/osmo-pcap/osmo_pcap_server.h | 2 + src/osmo_client_network.c | 2 +- src/osmo_server_main.c | 4 +++ src/osmo_server_network.c | 31 +++++++++++++++++++++- 8 files changed, 86 insertions(+), 5 deletions(-) create mode 100644 contrib/Makefile.am create mode 100755 contrib/clean_old -- 1.7.5.3

2 5

[PATCH 0/1] Updated script to handle whitespace
by Daniel Willmann 19 Jul '11

19 Jul '11

Hello, here an updated version of the script that handles whitespace in filennames properly. Thanks Holger for pointing out that such things do exist. :-) Regards, Daniel Willmann (1): contrib: Add a script to clean up in regular intervals Makefile.am | 2 +- configure.ac | 1 + contrib/Makefile.am | 1 + contrib/osmo_pcap_clean_old | 47 +++++++++++++++++++++++++++++++++++++++++++ 4 files changed, 50 insertions(+), 1 deletions(-) create mode 100644 contrib/Makefile.am create mode 100755 contrib/osmo_pcap_clean_old -- 1.7.5.3

1 1

Making NITB Database code async
by Holger Hans Peter Freyther 18 Jul '11

18 Jul '11

Hi all, I wonder what is the easiest way to make our database code async. Looking at our tables and code we do not seem to have a very complicated use. Problem: libdbi makes queries to SQLite that kills performance (e.g. every SELECT sends out pragma queries for every column to be queried). We have a hacked up libdbi from the last congress. We have some issues inserting new data into the database (e.g. the db being locked). In one way or another we have some issues there (either nitb will block, or the external process will...) When moving to postgres and a database on a different system we will have to deal with latencies and round trip time, but our code is sync. Goal: Most of our setting is 'set and forget'. We don't have complicate transactions (e.g. we don't have two nitb's setting the LAC of a subscriber, or wouldn't really care). When updating the in-memory representation, we don't mind how long it will take until it hits the disk on the remote system. Proposal: Also setting/storing will can remain like they are, the return value does only mean that a request has been sent. Only loading the subscriber, SMS, need to be asynchronous. M1: Change the gsm_subscriber code to load a subscriber asynchronously, this will mostly touch the gsm48 code and the VTY area. On load one can specify a callback. M2: Change the SMS code to load a SMS asynchronously, this will mostly change the SMS queue, some parts of the SMS submit (e.g. to check if there are still SMS to be sent) and the submit in the VTY M3: Probably create our own DB abstraction and provide a SQLite3 and Postgres backend using the native API of both of them (and getting rid of the libdbi and gdb issue) biggest problem: What do we do with the DB queries done from VTY that are asynchronous, e.g to confirm a SMS has been stored? Do we care about it? Do we turn this to a 'notification'? comments holger

2 1

Compile Error with latest Version
by Axel Walsleben 18 Jul '11

18 Jul '11

Hi List, i just tried to build openbsc latest checkout. libosmocore compiles fine (checkout is also from today) i got this error: make[3]: Betrete Verzeichnis '/home/demo/openbsc/openbsc/src/libcommon' CC common_vty.o In file included from common_vty.c:26: ../../include/openbsc/vty.h:32: error: redeclaration of enumerator ‘E1INP_NODE’ /usr/local/include/osmocom/vty/command.h:77: note: previous definition of ‘E1INP_NODE’ was here In file included from common_vty.c:28: ../../include/openbsc/debug.h:16: error: expected identifier before ‘-’ token In file included from ../../include/openbsc/bsc_nat.h:24, from common_vty.c:30: ../../include/openbsc/mgcp.h: In function ‘mgcp_timeslot_to_endpoint’: ../../include/openbsc/mgcp.h:180: error: ‘DMGCP’ undeclared (first use in this function) ../../include/openbsc/mgcp.h:180: error: (Each undeclared identifier is reported only once ../../include/openbsc/mgcp.h:180: error: for each function it appears in.) make[3]: *** [common_vty.o] Fehler 1 make[3]: Verlasse Verzeichnis '/home/demo/openbsc/openbsc/src/libcommon' make[2]: *** [all-recursive] Fehler 1 make[2]: Verlasse Verzeichnis '/home/demo/openbsc/openbsc/src' make[1]: *** [all-recursive] Fehler 1 make[1]: Verlasse Verzeichnis '/home/demo/openbsc/openbsc' so libcommon failes. is there a fix available or it is a unknown problem thanks. Regards axel

1 0

OML issue?
by Holger Hans Peter Freyther 18 Jul '11

18 Jul '11

Hi all, I have seen a strange OML NACK loop in OpenBSC with the ipaccess BTS. When I restart the osmo-nitb it is working again, so I suspect somehow our state of the BTS is corrupted. any ideas holger

3 8

[PATCH] bts-init: Initialize the BTS like it will look after a reset
by Holger Hans Peter Freyther 18 Jul '11

18 Jul '11

Reset the BTS MO State on BTS bootstrap. This way we will always test the BTS disconnect/reconnect case of the BTS. Do not reset the administrative state of objects. The BSC might have set these and wants to maintain them across disconnect/ reconnect. Right now this is true for the TRX state. --- openbsc/src/libbsc/bsc_init.c | 3 +++ openbsc/src/libcommon/gsm_data_shared.c | 1 - 2 files changed, 3 insertions(+), 1 deletions(-) diff --git a/openbsc/src/libbsc/bsc_init.c b/openbsc/src/libbsc/bsc_init.c index 1be8cb7..02a3adf 100644 --- a/openbsc/src/libbsc/bsc_init.c +++ b/openbsc/src/libbsc/bsc_init.c @@ -406,6 +406,9 @@ static int bootstrap_bts(struct gsm_bts *bts) bts->si_common.ncc_permitted = 0xff; + /* Initialize the BTS state */ + gsm_bts_mo_reset(bts); + return 0; } diff --git a/openbsc/src/libcommon/gsm_data_shared.c b/openbsc/src/libcommon/gsm_data_shared.c index 58e3bed..b52d58a 100644 --- a/openbsc/src/libcommon/gsm_data_shared.c +++ b/openbsc/src/libcommon/gsm_data_shared.c @@ -36,7 +36,6 @@ void gsm_abis_mo_reset(struct gsm_abis_mo *mo) { - mo->nm_state.administrative = NM_STATE_NULL; mo->nm_state.operational = NM_OPSTATE_NULL; mo->nm_state.availability = NM_AVSTATE_POWER_OFF; } -- 1.7.4.1 --------------050709080504010702000704--

1 0

Different protocols
by Seungju Kim 17 Jul '11

17 Jul '11

I see that pretty much every vendor in GSM industry uses their own dialect in their core network products, I wonder why. What do they achieve from it while killing compatibility with other products from other companies?

4 6

[PATCH] gsm 04.80: fix typo 265->256
by Alexander Huemer 16 Jul '11

16 Jul '11

Commit 79599ba0eb7a9aeaeb9dfbbf4881f0633724a471 contained a double typo. --- include/osmocom/gsm/tlv.h | 4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-) diff --git a/include/osmocom/gsm/tlv.h b/include/osmocom/gsm/tlv.h index 1e59cca..f659411 100644 --- a/include/osmocom/gsm/tlv.h +++ b/include/osmocom/gsm/tlv.h @@ -236,11 +236,11 @@ struct tlv_def { }; struct tlv_definition { - struct tlv_def def[265]; + struct tlv_def def[256]; }; struct tlv_parsed { - struct tlv_p_entry lv[265]; + struct tlv_p_entry lv[256]; }; extern struct tlv_definition tvlv_att_def; -- 1.7.6

2 1

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

OpenBSC