OpenBSC

openbsc@lists.osmocom.org

2 participants
4155 discussions

by Josip Stjepanović

Hello, Unfortunately I have come up to the problem that I can't google myself and my friends can't help with either. Maybe it has something to do with readme saying that libsomocore in the git I pulled isn't for system wide installation but when I make the osmocombb src then it spits out this: configure: error: Package requirements (libosmovty >= 0.10.0) were not met: Requested 'libosmovty >= 0.10.0' but version of Osmocom VTY Interface Library is UNKNOWN Consider adjusting the PKG_CONFIG_PATH environment variable if you installed software in a non-standard prefix. Alternatively, you may set the environment variables LIBOSMOVTY_CFLAGS and LIBOSMOVTY_LIBS to avoid the need to call pkg-config. See the pkg-config man page for more details. Makefile:94: recipe for target 'host/layer23/Makefile' failed make: *** [host/layer23/Makefile] Error 1 If I need to get a different libosmocore could you provide it to me? Thank you

5 years, 8 months

optional steps in ttcn3 interleave

by Neels Hofmeyr

Hi, I've got the problem that optional steps seem to not be possible in 'interleave' statements. What I want: accept either BSSMAP Assignment Request or Iu Rab Assignment: interleave { [g_pars.ran_is_geran] BSSAP.receive(tr_BSSMAP_AssignmentReq) { ... }; [not g_pars.ran_is_geran] BSSAP.receive(tr_RANAP_RabAssReq(rab_sml)) { ... }; [] other {...}; [] complex {...}; [] steps {...}; } But that's illegal syntax; works for altsteps, but not for interleave. Even in the language spec, there is no token between the interleave braces. How unfortunate. Options I am considering: 1) moving the optionals into a separate altstep var default assignment; if (g_pars.ran_is_geran) { assignment := activate(as_BSSMAP_assignment()); } else { assignment := activate(as_RANAP_assignment()); } interleave { [] other {...}; [] complex {...}; [] steps {...}; } deactivate(assignment); or 2) blatant code dup if (g_pars.ran_is_geran) { interleave { [] BSSAP.receive(tr_BSSMAP_AssignmentReq) { ... }; [] other {...}; [] complex {...}; [] steps {...}; } } else { interleave { [] BSSAP.receive(tr_RANAP_RabAssReq) { ... }; [] other {...}; [] complex {...}; [] steps {...}; } } 3) boolean dance and break var boolean done1 := false; var boolean done2 := false; var boolean done3 := false; var boolean done4 := false; interleave { [] BSSAP.receive(tr_BSSMAP_AssignmentReq) { if (not g_pars.ran_is_geran) { setverdict(fail); } done1 := true; if (done1 and done2 and done3 and done4) { break; } }; [] BSSAP.receive(tr_RANAP_RabAssReq(rab_sml)) { if (g_pars.ran_is_geran) { setverdict(fail); } done1 := true; if (done1 and done2 and done3 and done4) { break; } }; [] other { done2 := true; if (done1 and done2 and done3 and done4) { break; } }; [] complex { done3 := true; if (done1 and done2 and done3 and done4) { break; } }; [] steps { done4 := true; if (done1 and done2 and done3 and done4) { break; } }; } 1) is bad because the interleave may exit without having seen an actual assignment at all. Also interacting with local variables isn't allowed in this kind of altstep. Also if there are more optional parts, the side-altsteps become hard to understand. Also the altstep needs to "repeat;" so that it doesn't break the outer interlave, which makes us accept more than one of the optional message. 2) is bad because it is code dup. 3) is bad because of code clutter that is likely to cause weird failure when the interleave is modified. I am already using this method somewhere... but. Are there other options?? Why is this coming up? I am preparing for a change in osmo-msc during call setup, and I am making the ttcn3 call testing more flexible and cleaning things up. As a result, some more tests are moved to using f_mo_call_establish() instead of copy-pasting it. That makes some Iu tests go from passed to FAIL, because the f_mo_call_establish() is unable to do the above distinguishing between BSSMAP and IU. We can also choose to ignore those Iu tests that start to fail. But I am curious whether there is a way for optional interleave steps in ttcn3. Thanks, ~N

5 years, 8 months

gerrit update / reply by e-mail

by Harald Welte

Dear Osmocom community, I just upgraded gerrit to 2.16.12, the latest version of the 2.16 branch, still featuring the option to use the old UI. While reading through change logs, I just discovered that one can actually send responses to gerrit e-mail notifications, and those changes will end up creating new comments int he gerrit database/UO: http://gerrit-documentation.storage.googleapis.com/Documentation/2.14/intro… Maybe that's useful for some of you here... Regards, Harald -- - Harald Welte <laforge(a)osmocom.org> http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6)

5 years, 8 months

DW-TV report on Rhizomatica, TIC and Osmocom/sysmocom

by Harald Welte

Hi all, DW-TV has just released a video report on the community owned and operated cellular networks within TIC, the Mexican partner of Rhizomatica. You can find the (Spanish only) video at https://www.dw.com/es/telefon%C3%ADa-ind%C3%ADgena-en-defensa-del-derecho-a… I recommend to watch the full video to catch some glimpses into the life of people in one of the communities operating their own Osmocom based cellular network. If you don't have the time to follow the full video, some pointers below: * from 4:35 you can see how the taxi service (the only form of public transport!) can pick up people anywhere in the region after they make a mobile phone call * from 12:50 onwards, the BTS is introduced, and its role (and that of the BSC) are explained in a nice animation. * from 18:49 you can see the part covering the role Osmocom and sysmocom are playing in the development of the underlying technology. You can also catch a glimpse of the sysmocom office Especially for somebody who's never been there in person, it is very enlightening to see more about how people use it. And the technology geek in me of course enjoys the work related to power supply, including the home-made inverter for solar charging (from 16:12) Let me conclude with the statement that I'm extremely happy about (and proud of) the amazing work that Rhizomatica, TIC and friends are doing. It's great to see Osmocom code being put to use in such a meaningful way, and for what it was crated: To enable people (literally anyone) to operate their own cellular networks in whatever way, independent of large multi-national corporations. There are just very few places where people have actually managed to do this, given all the legal, political, economic constraints, including spectrum licensing. Thanks to Peter, Keith and his colleagues for dedicating many years to this cause. Thanks to DW-TV and Eva Usi (the reporter behind this piece). Further links (in case you weren't aware of those projects/entities): https://www.rhizomatica.org/ https://www.tic-ac.org/ 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)

5 years, 9 months

Fwd: Build failure of network:osmocom:nightly/libosmo-netif in Debian_8.0/x86_64

by Harald Welte

In case this wasn't noticed yet, libosmo-netif doesn't build (pass "make check") on debian 8 anymore. This clearly looks like a regression. It happens both on x86_64 and on armv7l. Thanks in advance for anyone finding time to investigate. Cheers (from holidays), Harald -------- Original Message -------- From: OBS Notification <admin(a)opensuse.org> Sent: September 19, 2019 3:44:40 AM GMT+02:00 To: Alexander Couzens <lynxis(a)fe80.eu>, Harald Welte <laforge(a)gnumonks.org>, OpenBSC gerrit-log Mailing List <gerrit-log(a)lists.osmocom.org> Subject: Build failure of network:osmocom:nightly/libosmo-netif in Debian_8.0/x86_64 Visit https://build.opensuse.org/package/live_build_log/network:osmocom:nightly/l… Package network:osmocom:nightly/libosmo-netif failed to build in Debian_8.0/x86_64 Check out the package for editing: osc checkout network:osmocom:nightly libosmo-netif Last lines of build log: [ 124s] autoreconnecting test step 3 [client OK, server OK], FD reg 1 [ 124s] [ 124s] autoreconnecting test step 2 [client OK, server OK], FD reg 0 [ 124s] + [ 124s] +autoreconnecting test step 1 [client OK, server OK], FD reg 0 [ 124s] connection closed with srv [ 124s] [ 124s] -autoreconnecting test step 1 [client OK, server NA], FD reg 0 [ 124s] +autoreconnecting test step 0 [client OK, server NA], FD reg 0 [ 124s] [ 124s] non-reconnecting test step 7 [client NA, server OK], FD reg 1 [ 124s] [ 124s] 1. testsuite.at:4: 1. stream_test (testsuite.at:4): FAILED (testsuite.at:8) [ 124s] debian/rules:27: recipe for target 'override_dh_auto_test' failed [ 124s] make[1]: *** [override_dh_auto_test] Error 1 [ 124s] make[1]: Leaving directory '/usr/src/packages/BUILD' [ 124s] debian/rules:13: recipe for target 'build' failed [ 124s] make: *** [build] Error 2 [ 124s] dpkg-buildpackage: error: debian/rules build gave error exit status 2 [ 124s] [ 124s] build30 failed "build libosmo-netif_0.6.0.2.a1e9.dsc" at Thu Sep 19 01:44:36 UTC 2019. [ 124s] [ 124s] ### VM INTERACTION START ### [ 125s] Powering off. [ 125s] [ 106.236806] reboot: Power down [ 125s] ### VM INTERACTION END ### [ 125s] [ 125s] build30 failed "build libosmo-netif_0.6.0.2.a1e9.dsc" at Thu Sep 19 01:44:38 UTC 2019. [ 125s] -- Configure notifications at https://build.opensuse.org/user/notifications openSUSE Build Service (https://build.opensuse.org/) -- Sent from a mobile device. Please excuse my brevity.

5 years, 9 months

C/C++ dialect defaults

by Oliver Smith

Hello Osmocom community, how about we set the C and C++ dialect defaults in for each Osmocom program? Then we would not run into the kind of errors, where code compiled without errors in the gerrit verification jenkins job, but failed to compile elsewhere because a different GCC uses different default dialects. We ran into this already with differences in gerrit verification and master builds [1], and it can easily happen when building the binary packages for the various Debian versions and derivatives in OBS. In [2] is an example patch for OsmoPCU, hardcoding the following dialects (gnu89 is the same as the linux kernel uses [3]). CXXFLAGS="$CXXFLAGS -std=gnu++03" CFLAGS="$CFLAGS -std=gnu89" (Note that we can't use the non-gnu dialects, libosmocore won't build with those.) Is anybody against doing this, or has other recommendations for dialects we should use? Regards, Oliver [1] https://osmocom.org/issues/3598 [2] https://gerrit.osmocom.org/c/osmo-pcu/+/15565 [3] https://github.com/torvalds/linux/commit/51b97e354ba9fce1890cf38ecc754aa496… -- - Oliver Smith <osmith(a)sysmocom.de> https://www.sysmocom.de/ ======================================================================= * sysmocom - systems for mobile communications GmbH * Alt-Moabit 93 * 10559 Berlin, Germany * Sitz / Registered office: Berlin, HRB 134158 B * Geschaeftsfuehrer / Managing Director: Harald Welte

5 years, 9 months

Looking for variables names that can be read via osmo-msc CONTROL interface

by Igor Lateliev

Dear osmocom-cni contributors, I would like to retrieve (i.e. read or get) some data from a running osmo-msc from the CONTROL interface... but sorry, currently I cannot find either from the manuals or the source code the name of variables I can query. Is there a mean to list all the variables that can be “GET” from the osmo-msc CONTROL interface? And… the list that can be “SET” through the osmo-msc CONTROL interface? I am also interested in other osmo-cni nodes. Thanks a lot in advance. BR, Igor.

5 years, 10 months

2019-09-10: Talk about commercial cellular base station technology

by Harald Welte

Dear Osmocom community and friends, Next week on September 10, I will be presenting a talk about cellular base station technology as part of the "Datengarten" series of talks at Chaos Computer Club Berlin (CCCB). The talk will focus on actual base station hardware as it evolved during the last 20 years or so. It will not assume much in terms of protocol stacks or cellular architecture, but more focus on the hardware building blocks. More information can be found at https://berlin.ccc.de/datengarten/102/ The event is public, so feel free to invite anyone along whom you think might be interested. Regards, Harald --- Abstract In today’s hyper-connected society, everyone constantly uses their smartphone, which in turn uses the commercial cellular networks (from 2G/GSM to 4G/LTE) in order to achieve connectivity. However, contrary to WiFi technology, even most technology-minded people don’t have much of an idea how the infrastructure behind those cellular networks looks like. This talk does not cover the architecture and protocols of underlying cellular systems, but focuses on the physical side of things: * what are the typical components of cellular base stations? * what are their key functionalities? * how did cellular base station technology evolve during the past 20 years? * how do we expect cellular base stations to change in the [near] future? We will not cover DIY or hobbyist projects here, but the actual technology deployed in the field by real-world commercial operators. --- -- - 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)

5 years, 10 months

ABIS Over SCTP Port 14597

by Borjan Jovanovski

Hi everyone! I have a BTS that is trying to connect to openbsc via SCTP, but as i see it is not supported. I have attached a capture file between the core network equipment and BTS 10.0.0.7 is the IP Address of the ABIS link and port is 14597 the rest is for UMTS and LTE so please ignore it. I would be really gratefull if someone could look into this Kind thanks to everyone!

5 years, 10 months

all cccamp2019 branches now on git.osmocom.com

by Alexander Couzens

Hi, i've pushed all modificatons from the chaos communication camp 2019 to the osmocom repositories as cccamp2019. Except for libosmo-abis which I directly pushed to gerrit. I would like to go next over the 35c3 branches, take a short overlook and remove them if them aren't useful. best, lynxis -- Alexander Couzens mail: lynxis(a)fe80.eu jabber: lynxis(a)fe80.eu gpg: 390D CF78 8BF9 AA50 4F8F F1E2 C29E 9DA6 A0DF 8604

5 years, 10 months

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

OpenBSC