OpenBSC March 2022

openbsc@lists.osmocom.org

8 participants
18 discussions

by Justin

Hi Osmocom, Do we have feature/functionality in OSMO-BSC similar to authorized-regex of OSMO-NITB where a IMSI prefix or regex is used to determine if the subscriber is permitted to register to the network or not. I've tried to looked at the osmo-bsc manual but I haven't seen any configurations related to the said feature/functionality. I've tried also the access-list configuration but I think it's no longer supported in latest version. Regards, Justin

3 years, 3 months

Re: OsmoHNBGW, libosmocore make error , CentOS Linux release 7.9.2009

by Pau Espin Pedrol

Hi, please reply to the ML, not only to me. according to [1] osmo-hnbw is available in CentOS_8, but I think you are using CentOS_7. Maybe try using the package from CentOS_8. [1] https://build.opensuse.org/project/monitor/network:osmocom:nightly On 3/18/22 08:46, Sjur Thomas Lien wrote: > Hi, > > Thanks for quick feedback. > First of all, I can't find OsmoHNBGW executable, so that at least needs to be compiled. And I totally agree, I'll use prebuilt packages if I can find them. I did find prebuilt libosmocore, but did not find prebuilt osmo-mgw. > So when running 'make ' on osmo-mgw, I see that file osmocom/netif/osmux.h is missing. Netif was not available, so I did a git clone of netif, and tried a ./configure. > > That's when I got this fault: > > checking for osmo_sock_init2_multiaddr in -losmocore... no > configure: error: libosmocore built without libsctp support > [root@tmaeurcellmngr libosmo-netif]# > > So my conclusion was that the prebuilt libosmocore could not be used in my case. That's why I tried to compile libosmocore from scratch. > > But thanks for advice, I'll give it another go. > > BR, > /Sjur > -- - Pau Espin Pedrol <pespin(a)sysmocom.de> http://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

3 years, 3 months

OsmoHNBGW, libosmocore make error , CentOS Linux release 7.9.2009

by Sjur Thomas Lien

Hi, Did a git clone of libosmocore. ./configure gives a few faults when checking the log, but seems to finish OK. From config.log: . . . configure:12134: $? = 0 configure:12134: gcc -c -std=gnu11 conftest.c >&5 conftest.c: In function 'main': conftest.c:71:21: error: expected expression before ')' token if (sizeof ((size_t))) ^ configure:12134: $? = 1 configure: failed program was: | /* confdefs.h */ | #define PACKAGE_NAME "libosmocore" | #define PACKAGE_TARNAME "libosmocore" | #define PACKAGE_VERSION "1.6.0.77-381dc" . . . configure:12379: result: -ldl configure:12388: checking for library containing dlsym configure:12419: gcc -o conftest -std=gnu11 conftest.c >&5 /tmp/ccp0wxaN.o: In function `main': conftest.c:(.text+0xa): undefined reference to `dlsym' collect2: error: ld returned 1 exit status configure:12419: $? = 1 configure: failed program was: | /* confdefs.h */ | #define PACKAGE_NAME "libosmocore" | #define PACKAGE_TARNAME "libosmocore" | . . . There are more "conftest.c" errors, but not sure if these are very serious. Anyway, ./configure finishes off without errors when done executing. So next thing is "make". And here I encounter a problem that stops the process: [root@tmaeurcellmngr libosmocore]# make make all-recursive make[1]: Entering directory `/root/hnbgw/osmo-hnbgw/libosmocore' Making all in include make[2]: Entering directory `/root/hnbgw/osmo-hnbgw/libosmocore/include' make all-am make[3]: Entering directory `/root/hnbgw/osmo-hnbgw/libosmocore/include' make[3]: Nothing to be done for `all-am'. make[3]: Leaving directory `/root/hnbgw/osmo-hnbgw/libosmocore/include' make[2]: Leaving directory `/root/hnbgw/osmo-hnbgw/libosmocore/include' Making all in src make[2]: Entering directory `/root/hnbgw/osmo-hnbgw/libosmocore/src' make all-am make[3]: Entering directory `/root/hnbgw/osmo-hnbgw/libosmocore/src' CC context.lo gcc: error: /usr/local/lib:/lib:/usr/lib64: No such file or directory make[3]: *** [context.lo] Error 1 make[3]: Leaving directory `/root/hnbgw/osmo-hnbgw/libosmocore/src' make[2]: *** [all] Error 2 make[2]: Leaving directory `/root/hnbgw/osmo-hnbgw/libosmocore/src' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/root/hnbgw/osmo-hnbgw/libosmocore' make: *** [all] Error 2 [root@tmaeurcellmngr libosmocore]# So this my "real" problem. I did find a compiled version of libosmocore and thought this would help me to compile osmoHNBGW. But , as OsmoHNBGW need a MGW client I ran into another problem. During "make" of osm-mgw: . . CC mgcp_protocol.o In file included from mgcp_protocol.c:39:0: ../../include/osmocom/mgcp/osmux.h:5:33: fatal error: osmocom/netif/osmux.h: No such file or directory #include <osmocom/netif/osmux.h> . . And I saw that "netif" was not there at all. Did a git clone of netif. Then I did a "netif" ./configure. But then I see a new problem, probably caused by the use of the already-compiled libmocore: . . checking netinet/sctp.h usability... yes checking netinet/sctp.h presence... yes checking for netinet/sctp.h... yes checking for osmo_sock_init2_multiaddr in -losmocore... no configure: error: libosmocore built without libsctp support [root@tmaeurcellmngr libosmo-netif]# So , I've hit the wall here. Best Regards, Sjur Internal

3 years, 3 months

UCAAT 2022 -- Call for Submissions

by Simon, Matthias (Nokia - DE/Ulm)

Hi, maybe you remember me: I am a TTCN-3 tool developer and fan of your TTCN-3 test suite. :) Therefore I'd like to shamelessly promote a test oriented conference by ETSI, which I think some of you could be interested in. The User Conference on Advanced Automated Testing is calling for submissions, deadline is 2 May 2022. Topics of interest include: * Open-source projects, testing solutions and automated test frameworks. * Lessons learnt from advanced test automation techniques (CI, AI, Cloud, ...) * Good practices for automated testing (TDD, BDD, MBT, ...) * Advances in test specification languages and methodologies * ... See you in Munich maybe? Cheers, Matthias PS: Forgive me, if this mail was inappropriate for this channel.

3 years, 3 months

osmo-dev changes for OsmoBSCNAT

by Oliver Smith

Hey Neels, and potentially other users of osmo-dev.git reading the ML, since I'm using osmo-dev's net scripts to test OsmoBSCNAT while developing it, I submitted patches with significant changes that make testing easier/possible: * config_mine is now a diff to config_2g3g * optionally build mobile + virtphy from osmocom-bb.git * optionally start BSC2, virtual BTS, virtual MS * all cmds can be overwritten in config_mine now, without modifying run.sh (e.g. to use valgrind, CMD_BSCNAT="valgrind osmo-bsc-nat") Patches were submitted for review here: https://gerrit.osmocom.org/c/osmo-dev/+/27432/1 Related osmo-bsc-nat patches: https://gerrit.osmocom.org/c/osmo-bsc-nat/+/27461 Best, Oliver -- - 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

3 years, 3 months

OsmoDevCall on Mar 11, 2022: USB-C: The connector and USB-PD

by Harald Welte

Dear Osmocom community, It's my pleasure to announce the next OsmoDevCall on March 11, 2022 at 20:00 CET at https://meeting5.franken.de/b/har-xbc-bsx-wvs (URL has changed!) In this edition, Kevin "tsaitgaist" Redon will present on "USB-C - the connector and USB-PD (Power Delivery)". This meeting will have the following schedule: 20:00 meet + greet 20:10 presentation as outlined above 21:00 unstructured supplementary social event [*] Attendance is free of charge and open to anyone with an interest in Osmocom or open source cellular technologies. More information about OsmoDevCall, including the schedule for further upcoming events can be found at https://osmocom.org/projects/osmo-dev-con/wiki/OsmoDevCall Looking forward to meeting you on Friday. Best regards, Harald [*] this is how we started to call the "unstructured" part of osmocom developer conferences in the past, basically where anyone can talk about anything, no formal schedule or structure. -- - 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)

3 years, 3 months

OsmoDevCon 2022 ?

by Harald Welte

Dear fellow Osmocom developers, as you all know, we've sadly had to skip OsmoDevCon 2020 and 2021, trying to compensate it at least to some extent with our OsmoDevCall every two weeks. The COVID-19 pandemic is far from over, and we don't know what the upcoming winter season will bring. Nevertheless, I think it would be a good idea to start a discussion of whether we should plan for an OsmoDevCon in 2022. I personally would say let's plan for the usual late April 2022 time frame, and if the pandemic situation deteriorates, we can still cancel it with something like one month lead time. I would also personally suggest to limit attendance to people who are fully vaccinated, and in addition do a self-test for all participants every morning. In terms of venue, we might also consider to move to a venue that allows better ventilation. Irrespective of the above we can also bring the air filters from the sysmocom office. So with that as an input statement, I would like to hear your opinion on the above proposals. Who would want to attend? Any complaints against the "vaccinated only plus daily self-tests in the morning" approach? 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)

3 years, 3 months

ttcn3-bsc-test-latest failures / tag a release?

by Neels Hofmeyr

Just now I looked at the failures in ttcn3-bsc-test-latest. https://jenkins.osmocom.org/jenkins/job/ttcn3-bsc-test-latest/ TL;DR: we should roll a release. Two real failures happen that are actual bugs in the latest release, and the rest of the failures are due to the lingering subscriber leak. BSC_Tests.TC_ho_into_this_bsc fails because osmo-bsc-latest omits the 'Codec List (BSS Supported)' in the Handover Request Acknowledge message, which is mandatory on AoIP. This error is fixed on osmo-bsc master. It makes no sense to me to punch a hole in the tests for latest -- this failure shows a real failure of the current osmo-bsc release. BSC_Tests.TC_cm_service_during_lcs_loc_req shows a subscriber leak, where a bsc_subscr is not cleaned up. This bsc_subscr lingers all the way to the end of the BSC_Tests run, and all other current failures of ttcn3-bsc-test-latest are due to that. (The only one not failing is TC_refuse_chan_act_to_vamos(), because it is the only one not verifying that no bsc_subscr stay behind.) So this also shows a real error in the current osmo-bsc release. There is nothing I would do at this point to make bsc-test-latest appear to be passing, because the errors shown are errors. The conclusion is that it might be time to roll another release one of these days. Related: important fixes I recently submitted are all merged to master, so from my side it would be a good time. ~N -- - Neels Hofmeyr <nhofmeyr(a)sysmocom.de> http://www.sysmocom.de/ ======================================================================= * sysmocom - systems for mobile communications GmbH * Alt-Moabit 93 * 10559 Berlin, Germany * Sitz / Registered office: Berlin, HRB 134158 B * Geschäftsführer / Managing Directors: Harald Welte

3 years, 3 months

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

OpenBSC March 2022