OpenBSC March 2022

openbsc@lists.osmocom.org

8 participants
30 discussions

OsmoDevCall on Mar 25, 2022: "Iridium reverse engineering update"
by Harald Welte 25 Mar '22

25 Mar '22

Dear Osmocom community, It's my pleasure to announce the next OsmoDevCall on March 25, 2022 at 20:00 CET at https://meeting5.franken.de/b/har-xbc-bsx-wvs In this edition, Sec and schneider will present an "Iridium reverse engineering update". 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. NOTE: There will be no recording of this talk, so if interested, please make sure you don't miss it! 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)

1 0

OSMO HnbGW gives socket error
by Sjur Thomas Lien 24 Mar '22

24 Mar '22

Hi, I've managed to install HnbGW on a Centos 8 machine. But at startup I get many errors of type socket.c:658 Unable to create socket: Protocol not supported [root@tmaeurosmohnbgw osmo_hngw_rpms]# osmo-hnbgw <0004> socket.c:658 Unable to create socket: Protocol not supported <0010> osmo_ss7.c:1629 0: asp-asp-clnt-OsmoHNBGW: Unable to open stream client for ASP asp-clnt-OsmoHNBGW, 0.0.0.0:0 ==> 10.40.2.66:2905 <0004> socket.c:658 Unable to create socket: Protocol not supported <0010> osmo_ss7.c:1629 0: asp-asp-clnt-OsmoHNBGW2: Unable to open stream client for ASP asp-clnt-OsmoHNBGW2, 0.0.0.0:0 ==> 10.40.33.6:2905 20220324104532635 DLGLOBAL NOTICE Available via telnet 127.0.0.1 4261 (telnet_interface.c:104) 20220324104532635 DLCTRL NOTICE CTRL at 127.0.0.1 4262 (control_if.c:1017) 20220324104532635 DRANAP NOTICE Remote IuCS SCCP addr: RI=SSN_PC,PC=0.27.4,SSN=RANAP (hnbgw_cn.c:488) 20220324104532636 DRANAP NOTICE Remote IuPS SCCP addr: RI=SSN_PC,PC=0.113.6,SSN=RANAP (hnbgw_cn.c:488) 20220324104532636 DRANAP NOTICE Local SCCP addr: RI=SSN_PC,PC=0.69.3,SSN=RANAP (hnbgw_cn.c:524) 20220324104532636 DLSCCP NOTICE OsmoHNBGW: Using SS7 instance 0, pc:0.69.3 (sccp_user.c:549) 20220324104532636 DLSCCP NOTICE OsmoHNBGW: Using AS instance msc-as (sccp_user.c:567) 20220324104532636 DLSCCP NOTICE OsmoHNBGW: Creating default route (sccp_user.c:572) 20220324104532636 DLSS7 INFO 0: Creating route: pc=0=0.0.0 mask=0x0 via AS 'msc-as' (osmo_ss7.c:830) 20220324104532636 DLSS7 INFO 0: asp-asp-clnt-OsmoHNBGW: Restarting ASP asp-clnt-OsmoHNBGW, r=10.40.2.66:2905<->l=0.0.0.0:0 (osmo_ss7.c:1596) 20220324104532638 DLGLOBAL ERROR Unable to create socket: Protocol not supported (socket.c:658) 20220324104532638 DLINP INFO [WAIT_RECONNECT] osmo_stream_cli_reconnect(): retrying in 5 seconds... (stream.c:286) 20220324104532638 DLSS7 ERROR 0: asp-asp-clnt-OsmoHNBGW: Unable to open stream client for ASP asp-clnt-OsmoHNBGW, 0.0.0.0:0 ==> 10.40.2.66:2905 (osmo_ss7.c:1629) 20220324104532638 DLSCCP NOTICE OsmoHNBGW: Using ASP instance asp-clnt-OsmoHNBGW (sccp_user.c:643) 20220324104532638 DLSS7 NOTICE 0: Creating SCCP instance (osmo_ss7.c:457) 20220324104532638 DLSCCP INFO Binding user 'SCCP Maangement' to SSN=1 PC=(no PC) (sccp_user.c:108) 20220324104532638 DLSCCP INFO Binding user 'OsmoHNBGW' to SSN=142 PC=0.69.3 (sccp_user.c:108) 20220324104532638 DRANAP NOTICE Remote SCCP addr: IuCS: RI=SSN_PC,PC=0.27.4,SSN=RANAP (hnbgw_cn.c:549) 20220324104532638 DRANAP NOTICE Remote SCCP addr: IuPS: RI=SSN_PC,PC=0.113.6,SSN=RANAP (hnbgw_cn.c:551) 20220324104532638 DHNBAP NOTICE Using RNC-Id 23 (hnbgw.c:660) 20220324104532638 DMAIN NOTICE Listening for Iuh at 10.30.50.69 29169 (hnbgw.c:665) 20220324104532640 DLGLOBAL ERROR Unable to create socket: Protocol not supported (socket.c:658) Cannot open server: Protocol not supported [root@tmaeurosmohnbgw osmo_hngw_rpms]# So, does anyone know why I get this socket error ? I use real MSC and SGSN, here's my config file: hnbgw iuh local-ip 10.30.50.69 local-port 29169 iucs remote-addr msc iups remote-addr sgsn cs7 instance 0 point-code 0.69.3 asp asp-clnt-OsmoHNBGW 2905 0 m3ua remote-ip 10.40.2.66 sctp-role client as msc-as m3ua asp asp-clnt-OsmoHNBGW routing-key 2 0.69.3 sccp-address msc routing-indicator PC point-code 0.27.4 asp asp-clnt-OsmoHNBGW2 2905 0 m3ua remote-ip 10.40.33.6 sctp-role client as sgsn-as m3ua asp asp-clnt-OsmoHNBGW2 routing-key 2 0.113.6 sccp-address sgsn routing-indicator PC point-code 0.113.6 log stderr logging filter all 1 logging print extended-timestamp 1 logging print category 1 logging print category-hex 0 logging print level 1 logging print file basename last logging level set-all info And since I use real MSC and SGSN, I don't need to use osmo-stp, right? As the real nodes act as SCTP servers? Internal

2 2

Whitelisting/Blocklisting
by Justin 23 Mar '22

23 Mar '22

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

2 1

Re: OsmoHNBGW, libosmocore make error , CentOS Linux release 7.9.2009
by Pau Espin Pedrol 23 Mar '22

23 Mar '22

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

2 1

OsmoHNBGW, libosmocore make error , CentOS Linux release 7.9.2009
by Sjur Thomas Lien 18 Mar '22

18 Mar '22

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 2

UCAAT 2022 -- Call for Submissions
by Simon, Matthias (Nokia - DE/Ulm) 11 Mar '22

11 Mar '22

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.

1 0

osmo-dev changes for OsmoBSCNAT
by Oliver Smith 11 Mar '22

11 Mar '22

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

2 2

OsmoDevCall on Mar 11, 2022: USB-C: The connector and USB-PD
by Harald Welte 11 Mar '22

11 Mar '22

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)

1 0

OsmoDevCon 2022 ?
by Harald Welte 11 Mar '22

11 Mar '22

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)

9 22

ttcn3-bsc-test-latest failures / tag a release?
by Neels Hofmeyr 11 Mar '22

11 Mar '22

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

2 2

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

OpenBSC March 2022