Open Source Mobile Communications: Issueshttps://projects.osmocom.org/https://projects.osmocom.org/favicon.ico?16647414092024-03-02T15:54:57ZOpen Source Mobile Communications
Redmine Core testing infrastructure - Bug #6386 (In Progress): eclipse-titan 9.0.0 not building in debian...https://projects.osmocom.org/issues/63862024-03-02T15:54:57Zlaforge
<p>I just ran into bugs caused by running a too old version of eclipse-titan (8.2.0 provided by debian), since our 9.0.0 is not building on unstable: <a class="external" href="https://obs.osmocom.org/package/show/osmocom:latest/eclipse-titan">https://obs.osmocom.org/package/show/osmocom:latest/eclipse-titan</a></p>
<p>Please have a look, thanks!</p> Cellular Network Infrastructure - Bug #6352 (Stalled): ttcn3-bts-test[-latest] is broken since Fe...https://projects.osmocom.org/issues/63522024-02-05T09:25:36Zfixeria
<p>ttcn3-bts-test[-latest] is failing for a few days already:</p>
<p><a class="external" href="https://jenkins.osmocom.org/jenkins/view/TTCN3/job/ttcn3-bts-test/2293/">https://jenkins.osmocom.org/jenkins/view/TTCN3/job/ttcn3-bts-test/2293/</a><br /><a class="external" href="https://jenkins.osmocom.org/jenkins/view/TTCN3/job/ttcn3-bts-test-latest/1953/">https://jenkins.osmocom.org/jenkins/view/TTCN3/job/ttcn3-bts-test-latest/1953/</a></p>
<p>The console log (<a class="external" href="https://jenkins.osmocom.org/jenkins/view/TTCN3/job/ttcn3-bts-test/2293/console">https://jenkins.osmocom.org/jenkins/view/TTCN3/job/ttcn3-bts-test/2293/console</a>) tells us about problems with the virtphy:</p>
<pre>
+ docker kill jenkins-ttcn3-bts-test-2293-virtphy
Error response from daemon: Cannot kill container: jenkins-ttcn3-bts-test-2293-virtphy: No such container: jenkins-ttcn3-bts-test-2293-virtphy
</pre>
<p>Here is the related logging (<a class="external" href="https://jenkins.osmocom.org/jenkins/view/TTCN3/job/ttcn3-bts-test/2293/artifact/logs/bts/osmo-bts.log">https://jenkins.osmocom.org/jenkins/view/TTCN3/job/ttcn3-bts-test/2293/artifact/logs/bts/osmo-bts.log</a>):</p>
<pre>
0: starting: osmo-bts-virtual -c /data/osmo-bts.gen.cfg
((*))
|
/ \ OsmoBTS
20240201061853485 DLGLOBAL NOTICE Unimplemented bts_model_phy_instance_set_defaults (main.c:156)
20240201061853485 DLGLOBAL NOTICE Unimplemented bts_model_phy_instance_set_defaults (main.c:156)
20240201061853485 DLGLOBAL NOTICE Unimplemented bts_model_phy_instance_set_defaults (main.c:156)
20240201061853485 DLGLOBAL NOTICE Unimplemented bts_model_phy_instance_set_defaults (main.c:156)
20240201061853486 DLGLOBAL NOTICE Setting up GSMTAP Um forwarding '(null)->'172.18.29.10:4729' (main.c:363)
20240201061853486 DLCTRL NOTICE CTRL at 0.0.0.0 4238 (control_if.c:1014)
20240201061853487 DL1C NOTICE Unimplemented bts_model_ctrl_cmds_install (bts_model.c:222)
20240201061853487 DLGLOBAL NOTICE Available via telnet 0.0.0.0 4241 (telnet_interface.c:88)
20240201061853487 DPCU INFO Started listening on PCU socket (PCU IF v12): /data/unix/pcu_sock (pcu_sock.c:1237)
20240201061853487 DOSMUX INFO Osmux socket listening on 172.18.29.20:1984 (osmux.c:352)
20240201061853487 DABIS NOTICE A-bis connection establishment to BSC (127.0.0.11) in progress... (abis.c:161)
20240201061853487 DLINP NOTICE enabling ipaccess BTS mode, OML connecting to 127.0.0.11:3002 (ipaccess.c:1098)
20240201061853487 DL1C INFO phy0: PHY link state change shutdown -> connecting (phy_link.c:58)
Failed to join to mcast goup: No such device
Unable to create VirtualUm multicast socket: No such device
20240201061853487 DL1C INFO phy0: PHY link state change connecting -> shutdown (phy_link.c:58)
unable to open PHY link(s)
0: stopped pid 8 with status 2
</pre>
<p>The virtphy container (<a class="external" href="https://jenkins.osmocom.org/jenkins/view/TTCN3/job/ttcn3-bts-test/2293/artifact/logs/virtphy/virtphy.log">https://jenkins.osmocom.org/jenkins/view/TTCN3/job/ttcn3-bts-test/2293/artifact/logs/virtphy/virtphy.log</a>) fails to start:</p>
<pre>
Thu Feb 1 06:18:53 2024 DVIRPHY virtphy.c:248 Virtual physical layer starting up...
Failed to join to mcast goup: No such device
Unable to create VirtualUm multicast socket: No such device
Segmentation fault (core dumped)
</pre> Cellular Network Infrastructure - Feature #6327 (New): Osmocom-build-tags-against-master job buil...https://projects.osmocom.org/issues/63272024-01-11T20:17:59Zfixeria
<p>The idea behind this job is to check if [a limited set of] old tagged versions of various Osmocom projects can still compile with the most recent versions of Osmocom libraries.</p>
<p>I checked the build logs and found out that it's building the default configurations for Osmocom projects (no <code>--with-foo</code> flags passed to configure scripts).<br />For instance, the default build configuration for osmo-bts does not include any models except the <code>-virtual</code>, so <code>osmo-bts-{trx,sysmo,...}</code> are not covered.<br />Same applies to osmo-trx: we build only the common code, but not the <code>-uhd/-lms</code> variants.</p>
<p>The more complete configurations we build, the more chances we have to catch various backwards compatibility problems.<br />A good example is <a class="external" href="https://cgit.osmocom.org/osmo-ci/tree/coverity/build_Osmocom.sh">https://cgit.osmocom.org/osmo-ci/tree/coverity/build_Osmocom.sh</a>, where we do enable much more features / variants.<br />Maybe this code can be generalized and re-used somehow?</p> OsmoBSC - Bug #6324 (New): Making a data call results in B0RKEN lchanshttps://projects.osmocom.org/issues/63242024-01-05T20:31:49Zkeith
<p>I made a data call from a GSM modem and ended up with a CHAN NACK from osmo-bts (as is to be expected, I suppose)</p>
<p>Should we enhance osmo-bsc's NACK handling to do something a little more helpful than just B0RK the channel?</p> OsmoSGSN - Bug #6295 (New): TMSI realloc complete leads to SecurityModeRejecthttps://projects.osmocom.org/issues/62952023-12-07T15:15:38Zosmith
<p>With osmo-sgsn 1.11.1 and nano3g, I'm observing the following sccp traffic (pcap in SYS#6582):</p>
<ul>
<li>SecurityModeCommand</li>
<li>SecurityModeComplete</li>
<li>TMSI realloc complete</li>
<li>SecurityModeCommand</li>
<li>SecurityModeReject with error code conflict-with-already-existing-integrity-protection-and-or-ciphering-information (13)</li>
</ul>
<p>I guess we should tell the hnb to forget the ciphering information when doing a tmsi realloc? or there might be a way to not have SecurityModeCommand after TMSI realloc?</p>
<p>Creating the issue for future reference, currently looking into another problem.</p> libosmocore - Bug #6232 (New): jenkins should give all libosmocore config options a tryhttps://projects.osmocom.org/issues/62322023-10-22T16:16:56ZHoernchen
<p>Neither --enable-embedded nor the --disable-* flags currently work as expected, so all of those options should be built once per week to ensure that they still work.</p>
<p>(embedded currently still requires uring headers, socket/io implodes due to sctp defines, ...)</p>
<p>The tricky part is that testing the flags requires not installing (or masking) the libs/header packages, to ensure they are not silently used anyway, which is currently the case.</p> rtl-sdr - Bug #6225 (New): rtl-sdr reelase tarballs missing from https://ftp.osmocom.org/releases/https://projects.osmocom.org/issues/62252023-10-18T17:05:38ZlaforgeOsmoGGSN (former OpenGGSN) - Feature #6223 (In Progress): TTCN3 unit test[s] for GTPv1U with exte...https://projects.osmocom.org/issues/62232023-10-18T15:03:43Zlaforge
<p>Let's generate GTPv1U trffic with one or even multiple extension headers and see if osmo-ggsn (in both kernel and userspace case) pass the user data as normally expected.</p> Cellular Network Infrastructure - Bug #6188 (New): Osmocom manuals have "draft" in debian package...https://projects.osmocom.org/issues/61882023-09-21T16:37:08Zosmith
<p>The "draft" watermark on the first page is currently only getting removed when uploading the manuals here, for the released versions (not master):<br /><a class="external" href="https://ftp.osmocom.org/docs/">https://ftp.osmocom.org/docs/</a></p>
<p>However the debian packages still have the "draft" watermark in osmocom:latest.</p> OsmoGSMTester - Bug #6149 (New): osmo-gsm-tester gerrit verifications currently broken, not runni...https://projects.osmocom.org/issues/61492023-08-25T09:13:18Zosmith
<p>The gerrit verifications for osmo-gsm-tester.git are currently failing, because the job tries to build the osmo-gsm-tester manuals (outside of the usual/any docker container) and doesn't have rsvg-convert installed (<a class="external" href="https://gerrit.osmocom.org/c/osmo-gsm-manuals/+/34158">https://gerrit.osmocom.org/c/osmo-gsm-manuals/+/34158</a>).</p>
<pre>
Image 'dblatex' not found
rsvg-convert -a -f pdf -o fig0.pdf /home/jenkins/workspace/osmo-gsm-tester_gerrit/osmo-gsm-tester/_manuals_temp/osmo-gsm-tester-manual__1.svg
A possible reason for transformation failure is invalid DocBook
(as reported by xmllint)
Error: [Errno 2] No such file or directory
</pre>
<p>This job should run in docker, like pretty much all other gerrit verification jobs we have now. This will fix the problem that we don't have the dependencies available.</p> Cellular Network Infrastructure - Bug #6122 (New): remove big endian supporthttps://projects.osmocom.org/issues/61222023-07-31T09:46:32Zosmith
<p>Follow-up to <a class="external" href="https://lists.osmocom.org/hyperkitty/list/openbsc@lists.osmocom.org/thread/ORBO2FWVVPCHTAXSPZTQLSSM4YB76ITB/">https://lists.osmocom.org/hyperkitty/list/openbsc@lists.osmocom.org/thread/ORBO2FWVVPCHTAXSPZTQLSSM4YB76ITB/</a></p> OsmoGGSN (former OpenGGSN) - Feature #6096 (In Progress): add support for kernel-GTP IPv6https://projects.osmocom.org/issues/60962023-07-12T20:37:17Zlaforge
<p><a class="user active" href="https://projects.osmocom.org/users/21027">pablo</a> has implemented [inner] IPv6 support in the kernel GTP driver and libgtpnl, see <a class="issue tracker-1 status-2 priority-3 priority-high3" title="Bug: IPv6 support for inner (user) IP layer missing (In Progress)" href="https://projects.osmocom.org/issues/1952">#1952</a></p>
<p>In order to end-to-end test it in our TTCN3 test suite (which already tests ipv6 when used with userspace GTP), we would need to add supprot for it to osmo-ggsn</p>
<p>I think <a class="user active" href="https://projects.osmocom.org/users/30187">pespin</a> is currently too busy to look at this, hence assigned to <a class="user active" href="https://projects.osmocom.org/users/301771">osmith</a>, but that's not mandatory. Feel free to pass around as needed.</p> Core testing infrastructure - Bug #5919 (New): osmo-python-tests: Update/fix README or setup processhttps://projects.osmocom.org/issues/59192023-02-22T18:25:53Zarehbein
<p><code>osmo-python-tests/README</code> states three ways of installation. Two of these failed for me:</p>
<pre>
$ pip3 install --verbose --user -e .
...
Installing collected packages: osmopython
Running setup.py develop for osmopython
Running command /usr/bin/python3 -c 'import sys, setuptools, tokenize; sys.argv[0] = '"'"'/home/somedir/osmo-python-tests/setup.py'"'"'; __file__='"'"'/home/somedir/osmo-python-tests/setup.py'"'"';f=getattr(tokenize, '"'"'open'"'"', open)(__file__);code=f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, __file__, '"'"'exec'"'"'))' develop --no-deps --user --prefix=
running develop
running egg_info
error: [Errno 13] Permission denied
ERROR: Command errored out with exit status 1: /usr/bin/python3 -c 'import sys, setuptools, tokenize; sys.argv[0] = '"'"'/home/somedir/osmo-python-tests/setup.py'"'"'; __file__='"'"'/home/somedir/osmo-python-tests/setup.py'"'"';f=getattr(tokenize, '"'"'open'"'"', open)(__file__);code=f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, __file__, '"'"'exec'"'"'))' develop --no-deps --user --prefix= Check the logs for full command output.
Exception information:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/pip/_internal/cli/base_command.py", line 223, in _main
status = self.run(options, args)
File "/usr/lib/python3/dist-packages/pip/_internal/cli/req_command.py", line 180, in wrapper
return func(self, options, args)
File "/usr/lib/python3/dist-packages/pip/_internal/commands/install.py", line 421, in run
installed = install_given_reqs(
File "/usr/lib/python3/dist-packages/pip/_internal/req/__init__.py", line 82, in install_given_reqs
requirement.install(
File "/usr/lib/python3/dist-packages/pip/_internal/req/req_install.py", line 800, in install
install_editable_legacy(
File "/usr/lib/python3/dist-packages/pip/_internal/operations/install/editable_legacy.py", line 49, in install_editable
call_subprocess(
File "/usr/lib/python3/dist-packages/pip/_internal/utils/subprocess.py", line 261, in call_subprocess
raise InstallationSubprocessError(proc.returncode, command_desc)
</pre>
<p>Seems like the command is throwing an error, because the prefix option is passed with an empty argument, but I don't know.</p>
<p>For checkinstall, the Debian package isn't built if one leaves the default value for version (<code>test</code>), since it hast to begin with a digit:</p>
<pre>
dpkg-deb: error: parsing file '/var/tmp/tmp.6EyaipPJOV/package/DEBIAN/control' near line 7 package 'osmo-python':
'Version' field value 'tests-1': version number does not start with digit
</pre>
<p>Outputs for each command are attached.</p> libosmo-sccp + libosmo-sigtran - Bug #5899 (New): ttcn3-sccp-test-latest is actually running code...https://projects.osmocom.org/issues/58992023-02-09T16:40:05Zosmith
<p>In jenkins.sh:</p>
<pre>
# Always require osmo-stp-master since is the only with sccp_demo_user installed
docker_images_require \
"osmo-stp-master" \
"ttcn3-sccp-test"
</pre>
<p>A way to resolve this would be packaging the demo programs sccp_demo_user (and _server?) in a -demos subpackage.</p>
<p>We only have one test in the testsuite, so this doesn't have much of an impact, just noting for future reference.</p> Cellular Network Infrastructure - Bug #5887 (New): coverity: build everything in docker container...https://projects.osmocom.org/issues/58872023-02-01T10:25:23Zosmith
<p>Currently the coverity scripts are not automatically tested before merging, and when they fail it is quite some effort to reproduce the errors as one has to manually install all dependencies (and missing ones only show up half-way through the build when something fails). Also libusrp requires sdcc 3, while e.g. on this system I have sdcc 4 installed.</p> Cellular Network Infrastructure - Bug #5809 (Feedback): applications disrespect potentially VTY-c...https://projects.osmocom.org/issues/58092022-12-05T18:25:49Zlaforge
<p>Originally we had the <code>telnet_init()</code> function, which later on was replaced by <code>telnet_init_dynif()</code> - both requiring the application to know the TCP port (and possibly local address)</p>
<p>Later we added VTY commands for this, and there is <code>telnet_init_default()</code> which uses <code>vty_get_bind{port,addr}()</code> to make sur the VTY-configured IP/port are used.</p>
<p>The problem is that most if not all applications still use <code>telnet_init_dynif()</code> to which they pass the "normal" port like <code>OSMO_VTY_PORT_HNODEB</code>.</p>
<p>This means the user may configure a different port in the VTY, but that port won't actually be used.</p>
<p>All the osmo-* projects need to be converted to <code>telnet_init_default()</code>.</p>
<p>We should also [marc ase] deprecate the old <code>telnet_init()</code> and <code>telnet_init_dynif()</code> functions for exactly that reason.</p> Cellular Network Infrastructure - Feature #5771 (New): series of presentations about the invididu...https://projects.osmocom.org/issues/57712022-11-14T19:25:57Zlaforge
<p>Most of the talks we ever gave on setting up and running the Osmocom CNI are ages old and hence relatively outdated.</p>
<p>Given the number of network elements and the relate complexity, I think we should consider doing a talk on each of them. The talk doesn't have to be of a particular length, so some network elements might have shorter or longer presentations.</p>
<p>Looking at the checklist below, we already have 14 items. Covering this in OsmoDevCall is not an option, it would take too long (14 months if no other topic would be covered in between). So it is going to be on a separate schedule.</p>
<p>I would consider each presentation should then be prominently linked from the redmine project page of each network element, next to the user manual.</p>
<p>We may of course still be publishing those via the OsmoDevCall "event" on media.ccc.de, so all videos are in one location.</p>
<p>I think every presentation should start with a quick picture at the overal diagram of netwokr elements, describe the surrounding elements and their interfaces to then look in detail at the specific element that ist he subject of the talk.</p>
It should cover
<ul>
<li>basic configuration to get it started / connected</li>
<li>VTY for state introspection ("ar alle connections up?", ...)</li>
<li>looking at logs / protocol traces</li>
<li>practical demo; looking at what happens in pcaps + logs for some basic transaction like LU, SMS, voice call.</li>
</ul> Cellular Network Infrastructure - Bug #5685 (Feedback): Dropping debian 10 (buster)https://projects.osmocom.org/issues/56852022-09-19T13:09:00Zosmith
<p>Debian 10 was EOL in 2022-08. It still has LTS support (<a class="external" href="https://wiki.debian.org/DebianReleases">https://wiki.debian.org/DebianReleases</a>).</p>
<a class="user active" href="https://projects.osmocom.org/users/7">laforge</a>:
<ul>
<li>Do we want to remove it form OBS now? (after migrating all docker containers to debian 11)</li>
<li>In general, when do we want to stop supporting old Debian releases?</li>
</ul>
<p>Currently it is still in use by various docker containers:<br /><pre>
$ git grep debian-buster
debian-buster-build/Makefile:DISTRO=debian-buster
debian-buster-jenkins/Makefile:DISTRO=debian-buster
debian-buster-simtrace2/Dockerfile:FROM $USER/debian-buster-build
fpga-build/Dockerfile:FROM $USER/debian-buster-build
jenkins-common.sh: debian-buster-*) echo "debian-buster" ;;
jenkins-common.sh: debian-buster-*) echo "debian:buster" ;;
nplab-m3ua-test/jenkins.sh: "debian-buster-build" \
nplab-sua-test/jenkins.sh: "debian-buster-build" \
osmo-gsm-tester/Dockerfile:FROM $USER/debian-buster-jenkins
osmo-gsm-tester/jenkins.sh: "debian-buster-jenkins" \
sigtran-tests/Dockerfile:FROM $USER/debian-buster-build
</pre></p> OsmoMSC - Bug #5568 (Stalled): SMPP socket doesn't use TCP_NODELAYhttps://projects.osmocom.org/issues/55682022-05-17T18:33:30Zlaforge
<p>The SMPP socket uses sockets directly (without relying on libosmo-netif/stream) and fails to setsockopt(TCP_NODELAY). This is not critical (SMS is sloooow), but it does add unintended latency to all SMPP messages sent.</p>
<p>The quick fix is to add the setsockopt for every socket we accept(). The clean-up would be to use libosmo-netif/stream...</p> OsmoBSCNAT - Bug #5492 (New): Support MSC poolinghttps://projects.osmocom.org/issues/54922022-03-21T10:41:34Zosmith
<p>Harald wrote in <a class="external" href="https://gerrit.osmocom.org/c/osmo-bsc-nat/+/27473">https://gerrit.osmocom.org/c/osmo-bsc-nat/+/27473</a>:</p>
<blockquote>
<p>Please note that we cannot assume just one MSC, but have to consider the situation of MSC pooling, too. Most if not all real netwokrs use MSC pooling, and we support it in the BSC as well just as we support SGSN pooling in the PCU and gbproxy.</p>
</blockquote>
<blockquote>
<p>any vty configuration regarding pooling should look as much as possible identical to how it is done in other places (gbproxy, for example)</p>
</blockquote>
<p>Related: <a class="external" href="https://osmocom.org/projects/osmo-bscnat/wiki/AoIP_OsmoBSCNAT#MSC-pooling">https://osmocom.org/projects/osmo-bscnat/wiki/AoIP_OsmoBSCNAT#MSC-pooling</a></p> Core testing infrastructure - Bug #5301 (Stalled): Run TTCN3 docker tests with sanitizer enabledhttps://projects.osmocom.org/issues/53012021-11-10T10:49:12Zdaniel
<p>After updating libosmocore I noticed that the TTCN3 GbProxy tests start to fail with an ASan issue when run locally.</p>
<p>I think at least for the TTCN3 tests on master we should enable <code>*San</code> to catch hidden bugs early. Unfortunately this has a large impact on how the <code>osmo-*-master</code> docker images are built if we want to enable it for the libraries as well - currently we install the nightly packages and build the target from master.</p>
<p>Instead we could build an image that builds all the libraries from master (with sanitizer enabled) and installs those and then use that as base for osmo-*-master.</p>
<p>Not sure what the downsides are, any ideas?</p> OsmoMGW - Feature #5279 (New): systemd service / unit for multiple osmo-mgw on one machinehttps://projects.osmocom.org/issues/52792021-10-25T11:41:42Zlaforge
<p>Now that some deployments run multiple instances of osmo-mgw in parallel on one machine (to scale out over multiple processors), the question is how to properly handle this from a systemd unit/service point of view.</p>
<p><a class="user active" href="https://projects.osmocom.org/users/732038">iedemam</a> might have some ideas and has already done some work in that direction.</p> OsmocomBB - Bug #4834 (New): package cp210x-program as part of network:osmocom:{nightly,latest}https://projects.osmocom.org/issues/48342020-10-26T18:01:48Zlaforge
<p>The cp210x-program utility is used to program the CP210x cables with custom baud rates.</p>
<a class="wiki-page" href="https://projects.osmocom.org/projects/baseband/wiki/HardwareCP210xTutorial">HardwareCP210xTutorial</a> is slightly outdated and still points to a sourceforge version of the tool, which
<ul>
<li>is python2 only</li>
<li>tries to do ELF parsing of libusb.so, which at least on my Debian unstable x86_64 doesn't seem to work anymore</li>
</ul>
<p>Let's instead use the maintained fork at <a class="external" href="https://github.com/VCTLabs/cp210x-program">https://github.com/VCTLabs/cp210x-program</a> and package it in our feeds.</p>
<p>Assigning to <a class="user active" href="https://projects.osmocom.org/users/301771">osmith</a>, knowing that he only starts to work on Osmocom topics again from January 1st, 2021 onwards. If somebody else wants to pick this up, feel free to do so.</p>
<p>The wiki page should then subsequently be updated, too.</p> OsmoSGSN - Bug #4599 (New): counter group sgsn:pdpctx already exists for index X, instead using Yhttps://projects.osmocom.org/issues/45992020-06-08T18:05:33Zlaforge
<p>When using OsmoSGSN (current nightly) in a setup with 3rd party 2G BSS and 3G RAN, we are running quite often into the following error message:</p>
<pre>
<0020> rate_ctr.c:224 counter group 'sgsn:pdpctx' already exists for index 5, instead using index 8. This is a software bug that needs fixing.
</pre>
<p>I wonder how this happens. It basically means we want to allocate a PDP context for the same NSAPI where we already have a PDP context.</p>
<p>The only path that calls sgsn_pdp_ctx_alloc() is sgsn_create_pdp_ctx() via activate_ggsn() originating from do_act_pdp_req() and the latter actually chekcs if we already have a PDP context fro the NSAPI in sgsn_pdp_ctx_by_nsapi. weird.</p>
<p><a class="user active" href="https://projects.osmocom.org/users/1741">lynxis</a> any ideas?</p> OsmoMGW - Bug #4447 (New): DSCP value should be a 6 bit fieldhttps://projects.osmocom.org/issues/44472020-03-09T09:11:24Zosmith
<p>TOS was 8bits, but only the upper 6 bits became DSCP. The VTY command for DSCP in OsmoMGW accepts an 8 bit value. We are setting the setsockopt for TOS with that value without bit-shifting.</p>
<p>This came up while writing a <a href="https://gerrit.osmocom.org/c/osmo-bts/+/17401" class="external">similar patch</a> for setting DSCP for OsmoBTS.</p>
<p>Should we</p>
<p>a) shift it two bits up and adjust the command syntax (and config template) to restrict to 0..63 (backwards incompatible)</p>
<p>or</p>
<p>b) change the description of the VTY command, so it is obvious that we are actually setting the TOS? (probably confusing)</p>
<p>CC: <a class="user active" href="https://projects.osmocom.org/users/7">laforge</a></p> OsmoMSC - Bug #4167 (Feedback): Event VLR_ULA_E_ID_IMEISV not permittedhttps://projects.osmocom.org/issues/41672019-08-22T13:11:47Zfixeria
<p>We're running Osmocom based network at the CCCamp 2019. I noticed the following errors happening quite often:</p>
<pre>
Thu Aug 22 14:03:29 2019 DVLR ERROR libvlr/vlr.c:1180 vlr_lu_fsm(IMSI-26242340300XXXX:MSISDN-XXXX:TMSI-0x7F53E4C2:GERAN-A-70445:LU)[0x5563947582c0]{VLR_ULA_S_WAIT_HLR_UPD}: Event VLR_ULA_E_ID_IMEISV not permitted
Thu Aug 22 14:20:59 2019 DVLR ERROR libvlr/vlr.c:1180 vlr_lu_fsm(IMSI-262423403003705:MSISDN-7968:TMSI-0x0FB923BC:GERAN-A-71816:LU)[0x55639482b3a0]{VLR_ULA_S_WAIT_HLR_UPD}: Event VLR_ULA_E_ID_IMEISV not permitted
Thu Aug 22 14:21:51 2019 DVLR ERROR libvlr/vlr.c:1180 vlr_lu_fsm(IMSI-262423103001767:MSISDN-2404:TMSI-0x916773EF:GERAN-A-71882:LU)[0x5563947752d0]{VLR_ULA_S_WAIT_HLR_UPD}: Event VLR_ULA_E_ID_IMEISV not permitted
</pre>
<p><a class="user active" href="https://projects.osmocom.org/users/301771">osmith</a> any ideas?</p> OsmoHLR - Bug #4163 (New): Subscriber on demand: "Error while deleting subscriber data for IMSI" ...https://projects.osmocom.org/issues/41632019-08-21T07:54:44Zosmith
<p>Reported by Rafael:<br /><a class="external" href="https://lists.osmocom.org/pipermail/openbsc/2019-August/012997.html">https://lists.osmocom.org/pipermail/openbsc/2019-August/012997.html</a></p>
<blockquote>
<p>And after giving "cs+ps" permission, when trying to set to "none" again,<br />I get:</p>
</blockquote>
<pre>
<0000> hlr.c:651 Error while deleting subscriber data for IMSI724056816211859
<0007> input/ipa.c:370 127.0.0.1:60216 sending data
<0007> input/ipa.c:390 connected read/write
<0007> input/ipa.c:346 127.0.0.1:60210 message received
<0000> hlr.c:651 Error while deleting subscriber data for IMSI724056816211859
<0007> input/ipa.c:390 connected read/write
<0007> input/ipa.c:346 127.0.0.1:60216 message received
<0000> hlr.c:651 Error while deleting subscriber data for IMSI724056816211859
<0007> input/ipa.c:390 connected read/write
<0007> input/ipa.c:346 127.0.0.1:60210 message received
<0000> hlr.c:651 Error while deleting subscriber data for IMSI724056816211859
</pre> Cellular Network Infrastructure - Bug #4141 (New): No osmux specific code in place during codec n...https://projects.osmocom.org/issues/41412019-08-05T15:57:19Zpespin
<p>Current code in OsmoBSC and OsmoMSC doesn't take into account that Osmux is to be used when codec negotiation goes one. That means that supported codec list needs to be correctly configured manually in VTY in order to avoid selecting incorrect codecs (like non-AMR). Moreover if an MS doesn't support AMR, since we don't have transcoding yet, the call cannot take place.</p>
<p>Different scenarios need to be listed here and think about what we want to do in each case.</p> Cellular Network Infrastructure - Bug #4131 (Stalled): osmo-gsm-manuals: Use leveloffset attribut...https://projects.osmocom.org/issues/41312019-07-26T13:04:49Zpespin
<p>Right now, all documents under osmo-gsm-manuals.git/commons/ start with title level 1 (==). However, if one wishes to add a document with level 2 (===) so it can also be included in other repository document, it will make osmo-gsm-manuals.git "make check" fail due to osmo-gsm-manuals/tests/Makefile.am:22:<br /><pre>
echo "include::$${chapter}[]" >> $@; \
</pre></p>
<p>Which includes stuff under a test document with level 0 (=). If a document with level different than 1 (==) is added, then it will fail on some versions (like jenkins):<br /><pre>
"asciidoc: WARNING: mgcp_extension_osmux.adoc: line 2: section title out of sequence: expected level 1, got level 2"
</pre></p>
<p>See for instance commit osmo-gsm-manuals.git 061cca4d7345bc4f496324d0b4d30bc51e1f8d23, which had to be fixed up later.</p>
<p>The solution here is to use "leveloffset" attribute. To make our life easier in the future, we need to move all documents under common/ to start with level 0 (=), and then use "leveloffset" on all includes in all other repositories using them. This way same document can easily be added on different levels on different documents.</p>
<p>Important! It seems this syntax doesn't work for me:<br /><pre>
include::chapter2.adoc[leveloffset=+1]
</pre></p>
<p>However, this does and it's basically the same:<br /><pre>
:leveloffset: 1
include::chapter1.adoc[]
:leveloffset: 0
</pre></p>
<p>Related information:<br /><a class="external" href="https://github.com/asciidoctor/asciidoctor.org/blob/master/docs/_includes/include-directive.adoc">https://github.com/asciidoctor/asciidoctor.org/blob/master/docs/_includes/include-directive.adoc</a><br /><a class="external" href="https://mrhaki.blogspot.com/2016/09/awesome-asciidoctor-change-level-offset.html">https://mrhaki.blogspot.com/2016/09/awesome-asciidoctor-change-level-offset.html</a><br /><a class="external" href="http://asciidoc.org/userguide.txt">http://asciidoc.org/userguide.txt</a></p> Cellular Network Infrastructure - Feature #4109 (New): debian-repo-install-test: start a virtual ...https://projects.osmocom.org/issues/41092019-07-16T12:36:01Zosmith
<p>We could extend <a class="issue tracker-1 status-3 priority-2 priority-default closed" title="Bug: no automatic testing of Debian/Ubuntu packages (Resolved)" href="https://projects.osmocom.org/issues/3369">#3369</a> (which made debian-repo-install-test start up all systemd services of Osmocom programs) to also start a virtual mobile subscriber (phone) and do a location update.</p>