OpenBSC March 2022

openbsc@lists.osmocom.org

8 participants
24 discussions

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 10 Mar '22

10 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 10 Mar '22

10 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 10 Mar '22

10 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

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

OpenBSC March 2022