Open Source Mobile Communications: Issues
https://projects.osmocom.org/
https://projects.osmocom.org/favicon.ico?1664741409
2023-07-12T20:37:17Z
Open Source Mobile Communications
Redmine
OsmoGGSN (former OpenGGSN) - Feature #6096 (In Progress): add support for kernel-GTP IPv6
https://projects.osmocom.org/issues/6096
2023-07-12T20:37:17Z
laforge
<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>
libosmo-sccp + libosmo-sigtran - Bug #6003 (Resolved): M3UA ASPAC/ASPIA encodes routing context 0...
https://projects.osmocom.org/issues/6003
2023-04-15T12:22:19Z
laforge
<p>In osmo-stp we always had the rule that setting the <em>routing context</em> to the magic value 0 meant <em>don't use a routing context IE</em>. This has been working (and is actually tested) for SG role.</p>
<p>However, for ASP role, the M3UA ASPAC/ASPIA messages currently <strong>do in fact contain a routing context IE with 0 value</strong>.</p>
osmo-ePDG - VoWifi Evolved Packet Data Gateway - Feature #5861 (In Progress): extend charon with ...
https://projects.osmocom.org/issues/5861
2023-01-17T15:53:09Z
laforge
<p>right now there's a charon plugin for eap-aka. It uses a local CSV file for storage of K/OP values, and it assumes it can synchronously access that and use it to derive AUTN challenges. so basically it includes a mini-hss/hlr.</p>
<p>We need to modify/replace that with a system where we get an asynchronous request for authentication over some external interface (currently called CEAI in my diagram at <a class="wiki-page" href="https://projects.osmocom.org/projects/osmo-epdg/wiki/EPDG_implementation_plan">EPDG_implementation_plan</a>), like a unix domain socket. Charon then needs to wait until whatever external application has obtained auth tuples, and proceed with EAP-AKA only once a tuple has been received.</p>
<p>This can be developed and tested independent of the actual ePDG by implementing a small stub program that for example reas key material from a local CSV file (again), or possibly even by asking osmo-hlr via GSUP (we do have all the related libraries in place for C and python, AFAIR). So the latter might actually be easier than the CSV approach, where again one needs to do key derviation etc.</p>
Core testing infrastructure - Bug #5796 (Resolved): ttcn3 tests are spawning >= 100x concurrent t...
https://projects.osmocom.org/issues/5796
2022-11-28T19:21:50Z
laforge
<p>One of our build slaves has >= 100x tcpdump running at the same time:</p>
<pre>
├─lxc-autostart───systemd─┬─5*[agetty]
│ ├─atd
│ ├─containerd─┬─containerd-shim─┬─docker-init───docuum───docker───14*[{docker}]
│ │ │ └─9*[{containerd-shim}]
│ │ ├─2*[containerd-shim─┬─sh───osmo-bsc]
│ │ │ └─9*[{containerd-shim}]]
│ │ ├─2*[containerd-shim─┬─sh───respawn.sh───osmo-bts-omldum]
│ │ │ └─9*[{containerd-shim}]]
│ │ ├─containerd-shim─┬─sh───respawn.sh───osmo-bts-omldum
│ │ │ └─10*[{containerd-shim}]
│ │ ├─containerd-shim─┬─sh─┬─111*[nc]
│ │ │ │ ├─111*[tcpdump]
│ │ │ │ ├─111*[tee]
│ │ │ │ └─ttcn3-docker-ru───start-testsuite───expect─┬─BSC_Tests───7*[BSC_Tests]
│ │ │ │ ├─mctr_cli───{mctr_cli}
│ │ │ │ └─{expect}
│ │ │ └─9*[{containerd-shim}]
│ │ ├─containerd-shim─┬─sh───respawn.sh───osmo-bts-trx
│ │ │ └─9*[{containerd-shim}]
│ │ ├─containerd-shim─┬─sh───python3───{python3}
│ │ │ └─9*[{containerd-shim}]
│ │ ├─containerd-shim─┬─sh───trxcon
│ │ │ └─9*[{containerd-shim}]
│ │ └─39*[{containerd}]
│ ├─cron
│ ├─dbus-daemon
│ ├─dockerd───35*[{dockerd}]
│ ├─docuum.sh───docker───18*[{docker}]
│ ├─exim4
│ ├─ntpd───{ntpd}
│ ├─sshd───sshd───sshd───bash───java─┬─sh───jenkins.sh───docker───17*[{docker}]
│ │ └─35*[{java}]
│ ├─systemd───(sd-pam)
│ ├─systemd-journal
│ └─systemd-logind
</pre>
<pre>
root@gtplab0:~# ps axuw | grep tcpdump
systemd+ 1801788 0.1 0.0 14216 6708 pts/1 S+ 19:40 0:02 /usr/bin/tcpdump -U -s 1500 -n -i any -w /data/BSC_Tests.TC_ctrl_msc_connection_status.pcap
systemd+ 1802101 0.1 0.0 14216 6632 pts/1 S+ 19:40 0:02 /usr/bin/tcpdump -U -s 1500 -n -i any -w /data/BSC_Tests.TC_ctrl_msc0_connection_status.pcap
systemd+ 1802151 0.1 0.0 14216 6596 pts/1 S+ 19:41 0:03 /usr/bin/tcpdump -U -s 1500 -n -i any -w /data/BSC_Tests.TC_stat_num_bts_connected_1.pcap
systemd+ 1802203 0.1 0.0 14216 6720 pts/1 S+ 19:41 0:03 /usr/bin/tcpdump -U -s 1500 -n -i any -w /data/BSC_Tests.TC_stat_num_bts_connected_2.pcap
systemd+ 1802259 0.1 0.0 14216 6648 pts/1 S+ 19:41 0:02 /usr/bin/tcpdump -U -s 1500 -n -i any -w /data/BSC_Tests.TC_stat_num_bts_connected_3.pcap
systemd+ 1802322 0.1 0.0 14216 6644 pts/1 S+ 19:41 0:03 /usr/bin/tcpdump -U -s 1500 -n -i any -w /data/BSC_Tests.TC_ctrl.pcap
systemd+ 1802374 0.1 0.0 14216 6592 pts/1 S+ 19:42 0:02 /usr/bin/tcpdump -U -s 1500 -n -i any -w /data/BSC_Tests.TC_ctrl_location.pcap
systemd+ 1802423 0.1 0.0 14216 6644 pts/1 S+ 19:42 0:02 /usr/bin/tcpdump -U -s 1500 -n -i any -w /data/BSC_Tests.TC_si_default.pcap
systemd+ 1802470 0.1 0.0 14216 6724 pts/1 S+ 19:42 0:02 /usr/bin/tcpdump -U -s 1500 -n -i any -w /data/BSC_Tests.TC_si2quater_2_earfcns.pcap
systemd+ 1802519 0.1 0.0 14216 6596 pts/1 S+ 19:42 0:02 /usr/bin/tcpdump -U -s 1500 -n -i any -w /data/BSC_Tests.TC_si2quater_3_earfcns.pcap
systemd+ 1802568 0.1 0.0 14216 6660 pts/1 S+ 19:43 0:02 /usr/bin/tcpdump -U -s 1500 -n -i any -w /data/BSC_Tests.TC_si2quater_4_earfcns.pcap
systemd+ 1802614 0.1 0.0 14216 6692 pts/1 S+ 19:43 0:02 /usr/bin/tcpdump -U -s 1500 -n -i any -w /data/BSC_Tests.TC_si2quater_5_earfcns.pcap
systemd+ 1802661 0.1 0.0 14216 6756 pts/1 S+ 19:43 0:02 /usr/bin/tcpdump -U -s 1500 -n -i any -w /data/BSC_Tests.TC_si2quater_6_earfcns.pcap
systemd+ 1802711 0.1 0.0 14216 6660 pts/1 S+ 19:44 0:02 /usr/bin/tcpdump -U -s 1500 -n -i any -w /data/BSC_Tests.TC_si2quater_12_earfcns.pcap
systemd+ 1802759 0.1 0.0 14216 6648 pts/1 S+ 19:44 0:02 /usr/bin/tcpdump -U -s 1500 -n -i any -w /data/BSC_Tests.TC_si2quater_23_earfcns.pcap
systemd+ 1802810 0.1 0.0 14216 6724 pts/1 S+ 19:44 0:02 /usr/bin/tcpdump -U -s 1500 -n -i any -w /data/BSC_Tests.TC_si2quater_32_earfcns.pcap
systemd+ 1802859 0.1 0.0 14216 6724 pts/1 S+ 19:45 0:02 /usr/bin/tcpdump -U -s 1500 -n -i any -w /data/BSC_Tests.TC_si2quater_33_earfcns.pcap
systemd+ 1802906 0.1 0.0 14216 6652 pts/1 S+ 19:45 0:02 /usr/bin/tcpdump -U -s 1500 -n -i any -w /data/BSC_Tests.TC_si2quater_42_earfcns.pcap
systemd+ 1802954 0.1 0.0 14216 6816 pts/1 S+ 19:45 0:02 /usr/bin/tcpdump -U -s 1500 -n -i any -w /data/BSC_Tests.TC_si2quater_48_earfcns.pcap
systemd+ 1803004 0.1 0.0 14216 6632 pts/1 S+ 19:46 0:02 /usr/bin/tcpdump -U -s 1500 -n -i any -w /data/BSC_Tests.TC_si2quater_49_earfcns.pcap
systemd+ 1803051 0.1 0.0 14216 6704 pts/1 S+ 19:46 0:02 /usr/bin/tcpdump -U -s 1500 -n -i any -w /data/BSC_Tests.TC_si_acc_rotate.pcap
systemd+ 1803105 0.1 0.0 14216 6640 pts/1 S+ 19:47 0:02 /usr/bin/tcpdump -U -s 1500 -n -i any -w /data/BSC_Tests.TC_si_acc_ramp_rotate.pcap
systemd+ 1803154 0.1 0.0 14216 6736 pts/1 S+ 19:47 0:02 /usr/bin/tcpdump -U -s 1500 -n -i any -w /data/BSC_Tests.TC_chan_act_noreply.pcap
systemd+ 1803203 0.1 0.0 14216 6664 pts/1 S+ 19:47 0:02 /usr/bin/tcpdump -U -s 1500 -n -i any -w /data/BSC_Tests.TC_chan_act_counter.pcap
systemd+ 1803884 0.1 0.0 14216 6636 pts/1 S+ 19:48 0:02 /usr/bin/tcpdump -U -s 1500 -n -i any -w /data/BSC_Tests.TC_chan_act_ack_noest.pcap
systemd+ 1807188 0.1 0.0 14216 6648 pts/1 S+ 19:48 0:02 /usr/bin/tcpdump -U -s 1500 -n -i any -w /data/BSC_Tests.TC_chan_act_ack_noest_emerg.pcap
systemd+ 1807237 0.1 0.0 14216 6756 pts/1 S+ 19:48 0:02 /usr/bin/tcpdump -U -s 1500 -n -i any -w /data/BSC_Tests.TC_chan_rqd_emerg_deny.pcap
systemd+ 1807284 0.1 0.0 14216 6680 pts/1 S+ 19:48 0:02 /usr/bin/tcpdump -U -s 1500 -n -i any -w /data/BSC_Tests.TC_chan_act_ack_est_ind_noreply.pcap
systemd+ 1807336 0.1 0.0 14216 6820 pts/1 S+ 19:49 0:02 /usr/bin/tcpdump -U -s 1500 -n -i any -w /data/BSC_Tests.TC_chan_act_ack_est_ind_refused.pcap
systemd+ 1807385 0.1 0.0 14216 6816 pts/1 S+ 19:49 0:02 /usr/bin/tcpdump -U -s 1500 -n -i any -w /data/BSC_Tests.TC_chan_act_nack.pcap
systemd+ 1807432 0.1 0.0 14216 6580 pts/1 S+ 19:49 0:02 /usr/bin/tcpdump -U -s 1500 -n -i any -w /data/BSC_Tests.TC_chan_exhaustion.pcap
systemd+ 1807481 0.1 0.0 14216 6656 pts/1 S+ 19:50 0:01 /usr/bin/tcpdump -U -s 1500 -n -i any -w /data/BSC_Tests.TC_chan_deact_silence.pcap
systemd+ 1807527 0.1 0.0 14216 6660 pts/1 S+ 19:50 0:01 /usr/bin/tcpdump -U -s 1500 -n -i any -w /data/BSC_Tests.TC_chan_rel_rll_rel_ind.pcap
systemd+ 1807577 0.0 0.0 14216 6724 pts/1 S+ 19:50 0:01 /usr/bin/tcpdump -U -s 1500 -n -i any -w /data/BSC_Tests.TC_chan_rel_conn_fail.pcap
systemd+ 1807627 0.0 0.0 14216 6632 pts/1 S+ 19:50 0:01 /usr/bin/tcpdump -U -s 1500 -n -i any -w /data/BSC_Tests.TC_chan_rel_hard_clear.pcap
systemd+ 1807674 0.1 0.0 14216 6688 pts/1 S+ 19:51 0:01 /usr/bin/tcpdump -U -s 1500 -n -i any -w /data/BSC_Tests.TC_chan_rel_last_eutran_plmn_hard_clear_no_csfb.pcap
systemd+ 1807720 0.1 0.0 14216 6712 pts/1 S+ 19:51 0:02 /usr/bin/tcpdump -U -s 1500 -n -i any -w /data/BSC_Tests.TC_chan_rel_last_eutran_plmn_hard_clear_csfb.pcap
systemd+ 1807767 0.1 0.0 14216 6712 pts/1 S+ 19:51 0:01 /usr/bin/tcpdump -U -s 1500 -n -i any -w /data/BSC_Tests.TC_chan_rel_hard_clear_csfb.pcap
systemd+ 1807813 0.1 0.0 14216 6816 pts/1 S+ 19:51 0:01 /usr/bin/tcpdump -U -s 1500 -n -i any -w /data/BSC_Tests.TC_chan_rel_hard_rlsd.pcap
systemd+ 1807860 0.1 0.0 14216 6636 pts/1 S+ 19:51 0:01 /usr/bin/tcpdump -U -s 1500 -n -i any -w /data/BSC_Tests.TC_chan_rel_hard_rlsd_ms_dead.pcap
systemd+ 1807909 0.1 0.0 14216 6648 pts/1 S+ 19:52 0:01 /usr/bin/tcpdump -U -s 1500 -n -i any -w /data/BSC_Tests.TC_chan_rel_a_reset.pcap
systemd+ 1808942 0.1 0.0 14216 6680 pts/1 S+ 19:52 0:01 /usr/bin/tcpdump -U -s 1500 -n -i any -w /data/BSC_Tests.TC_chan_rel_sccp_tiar_timeout.pcap
systemd+ 1808989 0.1 0.0 14216 6876 pts/1 S+ 19:52 0:01 /usr/bin/tcpdump -U -s 1500 -n -i any -w /data/BSC_Tests.TC_chan_rel_rr_cause.pcap
systemd+ 1809038 0.1 0.0 14216 6648 pts/1 S+ 19:53 0:01 /usr/bin/tcpdump -U -s 1500 -n -i any -w /data/BSC_Tests.TC_outbound_connect.pcap
systemd+ 1809088 0.1 0.0 14216 6696 pts/1 S+ 19:53 0:01 /usr/bin/tcpdump -U -s 1500 -n -i any -w /data/BSC_Tests.TC_assignment_cic_only.pcap
systemd+ 1809141 0.1 0.0 14216 6668 pts/1 S+ 19:53 0:01 /usr/bin/tcpdump -U -s 1500 -n -i any -w /data/BSC_Tests.TC_assignment_csd.pcap
systemd+ 1809189 0.1 0.0 14216 6788 pts/1 S+ 19:53 0:01 /usr/bin/tcpdump -U -s 1500 -n -i any -w /data/BSC_Tests.TC_assignment_ctm.pcap
systemd+ 1809236 0.1 0.0 14216 6876 pts/1 S+ 19:54 0:01 /usr/bin/tcpdump -U -s 1500 -n -i any -w /data/BSC_Tests.TC_assignment_sign.pcap
systemd+ 1809285 0.1 0.0 14216 6556 pts/1 S+ 19:54 0:01 /usr/bin/tcpdump -U -s 1500 -n -i any -w /data/BSC_Tests.TC_assignment_fr_a5_0.pcap
systemd+ 1809335 0.1 0.0 14216 6656 pts/1 S+ 19:54 0:01 /usr/bin/tcpdump -U -s 1500 -n -i any -w /data/BSC_Tests.TC_assignment_fr_a5_1.pcap
systemd+ 1809383 0.1 0.0 14216 6540 pts/1 S+ 19:55 0:01 /usr/bin/tcpdump -U -s 1500 -n -i any -w /data/BSC_Tests.TC_assignment_fr_a5_3.pcap
systemd+ 1809433 0.1 0.0 14216 6648 pts/1 S+ 19:55 0:02 /usr/bin/tcpdump -U -s 1500 -n -i any -w /data/BSC_Tests.TC_assignment_fr_a5_4.pcap
systemd+ 1809485 0.1 0.0 14216 6712 pts/1 S+ 19:55 0:02 /usr/bin/tcpdump -U -s 1500 -n -i any -w /data/BSC_Tests.TC_assignment_fr_a5_4_fail.pcap
systemd+ 1809535 0.1 0.0 14216 6660 pts/1 S+ 19:55 0:01 /usr/bin/tcpdump -U -s 1500 -n -i any -w /data/BSC_Tests.TC_assignment_fr_a5_not_sup.pcap
systemd+ 1809585 0.1 0.0 14216 6724 pts/1 S+ 19:56 0:01 /usr/bin/tcpdump -U -s 1500 -n -i any -w /data/BSC_Tests.TC_ciph_mode_a5_0.pcap
systemd+ 1809637 0.1 0.0 14216 6696 pts/1 S+ 19:56 0:01 /usr/bin/tcpdump -U -s 1500 -n -i any -w /data/BSC_Tests.TC_ciph_mode_a5_1.pcap
systemd+ 1809687 0.1 0.0 14216 6604 pts/1 S+ 19:56 0:01 /usr/bin/tcpdump -U -s 1500 -n -i any -w /data/BSC_Tests.TC_ciph_mode_a5_2_0.pcap
systemd+ 1809737 0.1 0.0 14216 6768 pts/1 S+ 19:56 0:01 /usr/bin/tcpdump -U -s 1500 -n -i any -w /data/BSC_Tests.TC_ciph_mode_a5_2_1.pcap
systemd+ 1809792 0.1 0.0 14216 6756 pts/1 S+ 19:57 0:01 /usr/bin/tcpdump -U -s 1500 -n -i any -w /data/BSC_Tests.TC_ciph_mode_a5_3.pcap
systemd+ 1809841 0.1 0.0 14216 6656 pts/1 S+ 19:57 0:01 /usr/bin/tcpdump -U -s 1500 -n -i any -w /data/BSC_Tests.TC_ciph_mode_a5_4.pcap
systemd+ 1809892 0.1 0.0 14216 6724 pts/1 S+ 19:57 0:01 /usr/bin/tcpdump -U -s 1500 -n -i any -w /data/BSC_Tests.TC_assignment_codec_fr.pcap
systemd+ 1809941 0.1 0.0 14216 6696 pts/1 S+ 19:57 0:01 /usr/bin/tcpdump -U -s 1500 -n -i any -w /data/BSC_Tests.TC_assignment_codec_fr_by_mode_modify.pcap
systemd+ 1809996 0.1 0.0 14216 6756 pts/1 S+ 19:58 0:01 /usr/bin/tcpdump -U -s 1500 -n -i any -w /data/BSC_Tests.TC_assignment_codec_hr.pcap
systemd+ 1810050 0.1 0.0 14216 6652 pts/1 S+ 19:58 0:01 /usr/bin/tcpdump -U -s 1500 -n -i any -w /data/BSC_Tests.TC_assignment_codec_efr.pcap
systemd+ 1810100 0.1 0.0 14216 6704 pts/1 S+ 19:58 0:01 /usr/bin/tcpdump -U -s 1500 -n -i any -w /data/BSC_Tests.TC_assignment_codec_amr_f.pcap
systemd+ 1810149 0.1 0.0 14216 6656 pts/1 S+ 19:59 0:01 /usr/bin/tcpdump -U -s 1500 -n -i any -w /data/BSC_Tests.TC_assignment_codec_amr_h.pcap
systemd+ 1810199 0.1 0.0 14216 6812 pts/1 S+ 19:59 0:01 /usr/bin/tcpdump -U -s 1500 -n -i any -w /data/BSC_Tests.TC_assignment_codec_fr_exhausted_req_hr.pcap
systemd+ 1810251 0.1 0.0 14216 6684 pts/1 S+ 19:59 0:01 /usr/bin/tcpdump -U -s 1500 -n -i any -w /data/BSC_Tests.TC_assignment_codec_fr_exhausted_req_fr.pcap
systemd+ 1810298 0.1 0.0 14216 6652 pts/1 S+ 19:59 0:01 /usr/bin/tcpdump -U -s 1500 -n -i any -w /data/BSC_Tests.TC_assignment_codec_fr_exhausted_req_fr_hr.pcap
systemd+ 1810351 0.1 0.0 14216 6876 pts/1 S+ 20:00 0:01 /usr/bin/tcpdump -U -s 1500 -n -i any -w /data/BSC_Tests.TC_assignment_codec_fr_exhausted_req_hr_fr.pcap
systemd+ 1810409 0.1 0.0 14216 6748 pts/1 S+ 20:00 0:01 /usr/bin/tcpdump -U -s 1500 -n -i any -w /data/BSC_Tests.TC_assignment_codec_hr_exhausted_req_fr.pcap
systemd+ 1810459 0.1 0.0 14216 6660 pts/1 S+ 20:00 0:01 /usr/bin/tcpdump -U -s 1500 -n -i any -w /data/BSC_Tests.TC_assignment_codec_hr_exhausted_req_hr.pcap
systemd+ 1810511 0.1 0.0 14216 6632 pts/1 S+ 20:01 0:01 /usr/bin/tcpdump -U -s 1500 -n -i any -w /data/BSC_Tests.TC_assignment_codec_hr_exhausted_req_hr_fr.pcap
systemd+ 1810561 0.1 0.0 14216 6664 pts/1 S+ 20:01 0:01 /usr/bin/tcpdump -U -s 1500 -n -i any -w /data/BSC_Tests.TC_assignment_codec_hr_exhausted_req_fr_hr.pcap
systemd+ 1810645 0.1 0.0 14216 6600 pts/1 S+ 20:01 0:01 /usr/bin/tcpdump -U -s 1500 -n -i any -w /data/BSC_Tests.TC_assignment_codec_req_hr_fr.pcap
systemd+ 1810695 0.1 0.0 14216 6748 pts/1 S+ 20:01 0:01 /usr/bin/tcpdump -U -s 1500 -n -i any -w /data/BSC_Tests.TC_assignment_codec_req_fr_hr.pcap
systemd+ 1810747 0.1 0.0 14216 6768 pts/1 S+ 20:02 0:01 /usr/bin/tcpdump -U -s 1500 -n -i any -w /data/BSC_Tests.TC_assignment_sdcch_exhausted_req_signalling.pcap
systemd+ 1810796 0.1 0.0 14216 6632 pts/1 S+ 20:02 0:01 /usr/bin/tcpdump -U -s 1500 -n -i any -w /data/BSC_Tests.TC_assignment_sdcch_exhausted_req_signalling_tch_forbidden.pcap
systemd+ 1810842 0.1 0.0 14216 6636 pts/1 S+ 20:02 0:01 /usr/bin/tcpdump -U -s 1500 -n -i any -w /data/BSC_Tests.TC_assignment_sdcch_exhausted_req_voice_tch_forbidden.pcap
systemd+ 1810892 0.1 0.0 14216 6664 pts/1 S+ 20:02 0:01 /usr/bin/tcpdump -U -s 1500 -n -i any -w /data/BSC_Tests.TC_assignment_codec_hr_osmux_on.pcap
systemd+ 1810942 0.1 0.0 14216 6712 pts/1 S+ 20:03 0:01 /usr/bin/tcpdump -U -s 1500 -n -i any -w /data/BSC_Tests.TC_assignment_osmux.pcap
systemd+ 1810999 0.1 0.0 14216 6704 pts/1 S+ 20:03 0:01 /usr/bin/tcpdump -U -s 1500 -n -i any -w /data/BSC_Tests.TC_assignment_osmux_cn.pcap
systemd+ 1811049 0.1 0.0 14216 6648 pts/1 S+ 20:03 0:01 /usr/bin/tcpdump -U -s 1500 -n -i any -w /data/BSC_Tests.TC_assignment_osmux_bts.pcap
systemd+ 1811098 0.1 0.0 14216 6648 pts/1 S+ 20:04 0:01 /usr/bin/tcpdump -U -s 1500 -n -i any -w /data/BSC_Tests.TC_rll_est_ind_inact_lchan.pcap
systemd+ 1811146 0.1 0.0 14216 6600 pts/1 S+ 20:04 0:01 /usr/bin/tcpdump -U -s 1500 -n -i any -w /data/BSC_Tests.TC_rll_est_ind_inval_sapi1.pcap
systemd+ 1811192 0.1 0.0 14216 6816 pts/1 S+ 20:04 0:01 /usr/bin/tcpdump -U -s 1500 -n -i any -w /data/BSC_Tests.TC_rll_est_ind_inval_sapi3.pcap
systemd+ 1811239 0.1 0.0 14216 6644 pts/1 S+ 20:04 0:01 /usr/bin/tcpdump -U -s 1500 -n -i any -w /data/BSC_Tests.TC_rll_est_ind_inval_sacch.pcap
systemd+ 1811286 0.1 0.0 14216 6652 pts/1 S+ 20:05 0:01 /usr/bin/tcpdump -U -s 1500 -n -i any -w /data/BSC_Tests.TC_tch_dlci_link_id_sapi.pcap
systemd+ 1811338 0.1 0.0 14216 6696 pts/1 S+ 20:05 0:01 /usr/bin/tcpdump -U -s 1500 -n -i any -w /data/BSC_Tests.TC_rll_rel_ind_sapi_n_reject.pcap
systemd+ 1811386 0.1 0.0 14216 6708 pts/1 S+ 20:05 0:01 /usr/bin/tcpdump -U -s 1500 -n -i any -w /data/BSC_Tests.TC_rll_err_ind_sapi_n_reject.pcap
systemd+ 1811434 0.1 0.0 14216 6724 pts/1 S+ 20:05 0:01 /usr/bin/tcpdump -U -s 1500 -n -i any -w /data/BSC_Tests.TC_rll_timeout_sapi_n_reject.pcap
systemd+ 1811497 0.1 0.0 14216 6648 pts/1 S+ 20:06 0:01 /usr/bin/tcpdump -U -s 1500 -n -i any -w /data/BSC_Tests.TC_rll_sapi_n_reject_dlci_cc.pcap
systemd+ 1811544 0.1 0.0 14216 6656 pts/1 S+ 20:06 0:01 /usr/bin/tcpdump -U -s 1500 -n -i any -w /data/BSC_Tests.TC_paging_imsi_nochan.pcap
systemd+ 1811914 0.1 0.0 14216 6652 pts/1 S+ 20:06 0:01 /usr/bin/tcpdump -U -s 1500 -n -i any -w /data/BSC_Tests.TC_paging_tmsi_nochan.pcap
systemd+ 1812960 0.1 0.0 14216 6812 pts/1 S+ 20:07 0:00 /usr/bin/tcpdump -U -s 1500 -n -i any -w /data/BSC_Tests.TC_paging_tmsi_any.pcap
systemd+ 1813541 0.1 0.0 14216 6596 pts/1 S+ 20:07 0:00 /usr/bin/tcpdump -U -s 1500 -n -i any -w /data/BSC_Tests.TC_paging_tmsi_sdcch.pcap
systemd+ 1813603 0.1 0.0 14216 6644 pts/1 S+ 20:08 0:00 /usr/bin/tcpdump -U -s 1500 -n -i any -w /data/BSC_Tests.TC_paging_tmsi_tch_f.pcap
systemd+ 1814378 0.1 0.0 14216 6664 pts/1 S+ 20:08 0:00 /usr/bin/tcpdump -U -s 1500 -n -i any -w /data/BSC_Tests.TC_paging_tmsi_tch_hf.pcap
systemd+ 1819299 0.1 0.0 14216 6744 pts/1 S+ 20:09 0:00 /usr/bin/tcpdump -U -s 1500 -n -i any -w /data/BSC_Tests.TC_paging_imsi_nochan_cgi.pcap
systemd+ 1823932 0.1 0.0 14216 6644 pts/1 S+ 20:09 0:00 /usr/bin/tcpdump -U -s 1500 -n -i any -w /data/BSC_Tests.TC_paging_imsi_nochan_lac_ci.pcap
systemd+ 1826971 0.1 0.0 14216 6652 pts/1 S+ 20:10 0:00 /usr/bin/tcpdump -U -s 1500 -n -i any -w /data/BSC_Tests.TC_paging_imsi_nochan_ci.pcap
systemd+ 1841069 0.1 0.0 14216 6616 pts/1 S+ 20:10 0:00 /usr/bin/tcpdump -U -s 1500 -n -i any -w /data/BSC_Tests.TC_paging_imsi_nochan_lai.pcap
systemd+ 1851377 0.1 0.0 14216 6660 pts/1 S+ 20:11 0:00 /usr/bin/tcpdump -U -s 1500 -n -i any -w /data/BSC_Tests.TC_paging_imsi_nochan_lac.pcap
systemd+ 1858283 0.1 0.0 14216 6624 pts/1 S+ 20:12 0:00 /usr/bin/tcpdump -U -s 1500 -n -i any -w /data/BSC_Tests.TC_paging_imsi_nochan_all.pcap
systemd+ 1859189 0.2 0.0 14216 6688 pts/1 S+ 20:15 0:00 /usr/bin/tcpdump -U -s 1500 -n -i any -w /data/BSC_Tests.TC_paging_imsi_nochan_plmn_lac_rnc.pcap
systemd+ 1859244 0.2 0.0 14216 6708 pts/1 S+ 20:15 0:00 /usr/bin/tcpdump -U -s 1500 -n -i any -w /data/BSC_Tests.TC_paging_imsi_nochan_rnc.pcap
systemd+ 1859300 0.2 0.0 14216 6772 pts/1 S+ 20:15 0:00 /usr/bin/tcpdump -U -s 1500 -n -i any -w /data/BSC_Tests.TC_paging_imsi_nochan_lac_rnc.pcap
systemd+ 1859355 0.2 0.0 14216 6660 pts/1 S+ 20:16 0:00 /usr/bin/tcpdump -U -s 1500 -n -i any -w /data/BSC_Tests.TC_paging_imsi_nochan_lacs.pcap
systemd+ 1859415 0.2 0.0 14216 6804 pts/1 S+ 20:16 0:00 /usr/bin/tcpdump -U -s 1500 -n -i any -w /data/BSC_Tests.TC_paging_imsi_nochan_lacs_empty.pcap
systemd+ 1859480 0.2 0.0 14216 6752 pts/1 S+ 20:16 0:00 /usr/bin/tcpdump -U -s 1500 -n -i any -w /data/BSC_Tests.TC_paging_imsi_nochan_cgi_unknown_cid.pcap
systemd+ 1859545 0.2 0.0 14216 6664 pts/1 S+ 20:17 0:00 /usr/bin/tcpdump -U -s 1500 -n -i any -w /data/BSC_Tests.TC_paging_imsi_a_reset.pcap
systemd+ 1859601 0.2 0.0 14216 6644 pts/1 S+ 20:17 0:00 /usr/bin/tcpdump -U -s 1500 -n -i any -w /data/BSC_Tests.TC_paging_imsi_load.pcap
systemd+ 1859658 0.2 0.0 14216 6660 pts/1 S+ 20:17 0:00 /usr/bin/tcpdump -U -s 1500 -n -i any -w /data/BSC_Tests.TC_paging_counter.pcap
</pre>
<p>IIRC @arehbein touched this last in <a class="external" href="https://gerrit.osmocom.org/c/osmo-ttcn3-hacks/+/30313">https://gerrit.osmocom.org/c/osmo-ttcn3-hacks/+/30313</a> and related patches. Please urgently investigate if they created this related regression. We always had one pcap file for one test case, and not tcpdumps running concurrently capturing various packets of testse at a later point in time.</p>
libosmo-sccp + libosmo-sigtran - Feature #5752 (Resolved): io_uring support in libosmo-sigtran
https://projects.osmocom.org/issues/5752
2022-11-09T12:38:26Z
laforge
<p>Once libosmocore provides the new API for the upcoming io_uring backend (<a class="issue tracker-2 status-3 priority-3 priority-high3 closed" title="Feature: io_uring support in libosmocore (Resolved)" href="https://projects.osmocom.org/issues/5751">#5751</a>) we will need to port libosmo-sccp over to this new API.</p>
<p>Currently we're using the following code-paths for I/O</p>
<table>
<tr>
<th>libosmo-sigtran function</th>
<th>I/O function</th>
<th>provided by</th>
</tr>
<tr>
<td>xua_srv_conn_cb</td>
<td>sctp_recvmsg</td>
<td>libsctp</td>
</tr>
<tr>
<td>ipa_cli_read_cb</td>
<td>ipa_msg_recv_buffered</td>
<td>libosmocore</td>
</tr>
<tr>
<td>osmo_ss7_asp_send</td>
<td>osmo_stream_srv_send</td>
<td>libosmo-netif</td>
</tr>
<tr>
<td>osmo_ss7_asp_send</td>
<td>osmo_stream_cli_send</td>
<td>libosmo-netif</td>
</tr>
</table>
<p>We need to analyze each of those and migrate, if possible.</p>
Core testing infrastructure - Bug #5619 (Resolved): osmocom OBS nightly job fails since 2 nights ago
https://projects.osmocom.org/issues/5619
2022-07-17T08:00:19Z
laforge
<p>lsat few lines are:</p>
<pre>
+ mv /home/osmocom-build/jenkins/workspace/Osmocom_OBS_nightly_build.opensuse.org/nightly-3g_54wL1i/repo/osc/network:osmocom:nightly/libosmo-dsp/libosmo-dsp.spec.new /home/osmocom-build/jenkins/workspace/Osmocom_OBS_nightly_build.opensuse.org/nightly-3g_54wL1i/repo/osc/network:osmocom:nightly/libosmo-dsp/libosmo-dsp.spec
++ grep '^Version: ' /home/osmocom-build/jenkins/workspace/Osmocom_OBS_nightly_build.opensuse.org/nightly-3g_54wL1i/repo/osc/network:osmocom:nightly/libosmo-dsp/libosmodsp_0.4.0.5.6bf7.202207170052.dsc
++ cut -d: -f2-
++ xargs
+ version=0.4.0.5.6bf7.202207170052
+ case $version in
+ '[' -n '' ']'
+ sed -i 's/^Version:.*/Version: 0.4.0.5.6bf7.202207170052/g' /home/osmocom-build/jenkins/workspace/Osmocom_OBS_nightly_build.opensuse.org/nightly-3g_54wL1i/repo/osc/network:osmocom:nightly/libosmo-dsp/libosmo-dsp.spec
++ cd /home/osmocom-build/jenkins/workspace/Osmocom_OBS_nightly_build.opensuse.org/nightly-3g_54wL1i/repo/osc/network:osmocom:nightly/libosmo-dsp
++ ls -1 'libosmo-dsp_*.tar.*'
ls: cannot access 'libosmo-dsp_*.tar.*': No such file or directory
+ tarball=
Build step 'Execute shell' marked build as failure
Sending e-mails to: jenkins-notifications@lists.osmocom.org
Finished: FAILURE
</pre>
<p>Didn't look at it in more detail, but could it be that the build job makes the blind assumption that an earlier tar.gz from the last night exists, but libosmo-dsp has none?</p>
<p>This might be the root cause of <a class="issue tracker-1 status-3 priority-2 priority-default closed" title="Bug: obs-nightly: centos8 fails to build / OBS nightly builds git from 2 days earlier (Resolved)" href="https://projects.osmocom.org/issues/5618">#5618</a></p>
<p>In general, I think it is somewhat sub-optimal of the OBS job (nightly/latest) has an error for one specific package, it shouldn't stop processing for all the other packages. can't we somehow trap/catch the error, memorize it and continue with the other packages, and then at the final exit report the non-success exit code so jenkins shows the job as failed but still have only one package affected by a problem?</p>
Retronetworking - Feature #5591 (Closed): Retronetworking related talk at VCFB 2022
https://projects.osmocom.org/issues/5591
2022-06-25T15:59:53Z
laforge
<p>I'm intrested in giving a retronetworking related talk at VCFB 2022 (<a class="external" href="https://vcfb.de/2022/call_for_participation.html">https://vcfb.de/2022/call_for_participation.html</a>)</p>
<p>The question now is: About which topic in general? Maybe some generic introduction into the OCTOI project? Working title could be along the lines of <em>Creating a community TDMoIP/ISDN network for retrocomputing</em>?</p>
<p>Any other ideas/suggestions? Any co-conspirators?</p>
OsmoMSC - Bug #5567 (Resolved): osmo-msc ignores validity period for SMS received via SMPP
https://projects.osmocom.org/issues/5567
2022-05-17T15:44:52Z
laforge
Open Source IMS Client - Feature #5481 (New): SIM card interface for doubango
https://projects.osmocom.org/issues/5481
2022-03-07T10:53:16Z
laforge
<p>The pre-existing <a class="wiki-page" href="https://projects.osmocom.org/projects/foss-ims-client/wiki/Doubango">doubango</a> library code assumes that the IMS client has knowledge of the secret key material (K + OP/OPc) in order to perform the authentication and IPsec key establoshment to the P-CSCF.</p>
<p>This may be the case in <em>some</em> testing/lab setups, but in general this key material is stored on the ISIM or USIM application of a SIM card.</p>
<p>If we want to use doubango with such standard cards, we need some kind of interface how doubango can perform authentication via ISIM/USIM.</p>
The interface should be rather generic, as the detailed interface for SIM access will be highly platform specific:
<ul>
<li>For development on a normal Linux laptop, a pcsc-lite based interface to a smart card reader will be used.</li>
<li>For execution inside a specific phone, phone specific interfaces for SIM card access may be used (QMI, AT+CSIM, ...)</li>
</ul>
OsmoHNodeB - Bug #5360 (Resolved): osmo-hnodeb makes repo-install jenknis test "nightly" fail
https://projects.osmocom.org/issues/5360
2021-12-19T11:10:37Z
laforge
<p>For four consecutive days, nightly package install tests are failing for centos8, deiban9, debian10</p>
<p>It seems to be related ot osmo-hnodeb trying to use the GTP port while we already have something else (ggsn?) bound to it?</p>
<pre>
Dec 19 10:05:35 7d890282e10c systemd[1]: Started Osmocom Home NodeB (hNodeB).
Dec 19 10:05:35 7d890282e10c osmo-hnodeb[468]: <0008> telnet_interface.c:100 Available via telnet 127.0.0.1 4273
Dec 19 10:05:35 7d890282e10c osmo-hnodeb[468]: <0010> gtp.c:909 GTP: gtp_newgsn() started at 0.0.0.0
Dec 19 10:05:35 7d890282e10c osmo-hnodeb[468]: <0010> gtp.c:866 State information file (/tmp/gsn_restart) not found. Creating new file.
Dec 19 10:05:35 7d890282e10c osmo-hnodeb[468]: <0010> gtp.c:962 addr(0.0.0.0:3386) bind(fd0=5) failed: Error = Address already in use
Dec 19 10:05:35 7d890282e10c osmo-hnodeb[468]: <0007> gtp.c:138 Failed to set up GTP socket: Address already in use
Dec 19 10:05:35 7d890282e10c osmo-hnodeb[468]: Error listening on GTP port: Address already in use
Dec 19 10:05:35 7d890282e10c systemd[1]: osmo-hnodeb.service: Main process exited, code=exited, status=1/FAILURE
Dec 19 10:05:35 7d890282e10c systemd[1]: osmo-hnodeb.service: Failed with result 'exit-code'.
Dec 19 10:05:37 7d890282e10c systemd[1]: osmo-hnodeb.service: Service RestartSec=2s expired, scheduling restart.
Dec 19 10:05:37 7d890282e10c systemd[1]: osmo-hnodeb.service: Scheduled restart job, restart counter is at 1.
Dec 19 10:05:37 7d890282e10c systemd[1]: Stopped Osmocom Home NodeB (hNodeB).
Dec 19 10:05:37 7d890282e10c systemd[1]: Started Osmocom Home NodeB (hNodeB).
Dec 19 10:05:37 7d890282e10c osmo-hnodeb[471]: <0008> telnet_interface.c:100 Available via telnet 127.0.0.1 4273
Dec 19 10:05:37 7d890282e10c osmo-hnodeb[471]: <0010> gtp.c:909 GTP: gtp_newgsn() started at 0.0.0.0
Dec 19 10:05:37 7d890282e10c osmo-hnodeb[471]: <0010> gtp.c:962 addr(0.0.0.0:3386) bind(fd0=5) failed: Error = Address already in use
Dec 19 10:05:37 7d890282e10c osmo-hnodeb[471]: <0007> gtp.c:138 Failed to set up GTP socket: Address already in use
Dec 19 10:05:37 7d890282e10c osmo-hnodeb[471]: Error listening on GTP port: Address already in use
Dec 19 10:05:37 7d890282e10c systemd[1]: osmo-hnodeb.service: Main process exited, code=exited, status=1/FAILURE
Dec 19 10:05:37 7d890282e10c systemd[1]: osmo-hnodeb.service: Failed with result 'exit-code'.
+ systemctl stop osmo-bsc osmo-bts-virtual osmo-gbproxy osmo-gtphub osmo-hlr osmo-hnbgw osmo-mgw osmo-msc osmo-pcap-client osmo-pcu osmo-sgsn osmo-sip-connector osmo-stp osmo-pcap-server osmo-hnodeb
ERROR: services failed to start: osmo-hnodeb
</pre>
libosmocore - Bug #5328 (Resolved): log_file_msg related memory leak
https://projects.osmocom.org/issues/5328
2021-11-25T12:11:48Z
laforge
<p>After running osmo-bts-trx some 24 hours and then issuing a SIGUSR1, I get tons of talloc reports about <code>log_file_ms</code>:</p>
<pre>
log_file_msg contains 4232 bytes in 1 blocks (ref 0) 0x6210014e2560
log_file_msg contains 4232 bytes in 1 blocks (ref 0) 0x6210014e3960
log_file_msg contains 4232 bytes in 1 blocks (ref 0) 0x6210014e4d60
log_file_msg contains 4232 bytes in 1 blocks (ref 0) 0x6210014e6160
log_file_msg contains 4232 bytes in 1 blocks (ref 0) 0x6210014e8960
log_file_msg contains 4232 bytes in 1 blocks (ref 0) 0x6210014e9d60
log_file_msg contains 4232 bytes in 1 blocks (ref 0) 0x6210014eb160
log_file_msg contains 4232 bytes in 1 blocks (ref 0) 0x6210014ec560
log_file_msg contains 4232 bytes in 1 blocks (ref 0) 0x6210014ed960
log_file_msg contains 4232 bytes in 1 blocks (ref 0) 0x6210014f0160
log_file_msg contains 4232 bytes in 1 blocks (ref 0) 0x6210014f1560
log_file_msg contains 4232 bytes in 1 blocks (ref 0) 0x6210014f3d60 log_file_msg contains 4232 bytes in 1 blocks (ref 0) 0x621005e5b160
log_file_msg contains 4232 bytes in 1 blocks (ref 0) 0x621005e59d60
log_file_msg contains 4232 bytes in 1 blocks (ref 0) 0x621005e58960
log_file_msg contains 4232 bytes in 1 blocks (ref 0) 0x621005e57560
log_file_msg contains 4232 bytes in 1 blocks (ref 0) 0x621005e56160
log_file_msg contains 4232 bytes in 1 blocks (ref 0) 0x621005e54d60
log_file_msg contains 4232 bytes in 1 blocks (ref 0) 0x621005e53960
log_file_msg contains 4232 bytes in 1 blocks (ref 0) 0x621005e52560
log_file_msg contains 4232 bytes in 1 blocks (ref 0) 0x621005e51160
log_file_msg contains 4232 bytes in 1 blocks (ref 0) 0x621005e4fd60
log_file_msg contains 4232 bytes in 1 blocks (ref 0) 0x621005e4d560
log_file_msg contains 4232 bytes in 1 blocks (ref 0) 0x621005e4c160
log_file_msg contains 4232 bytes in 1 blocks (ref 0) 0x621005e4ad60
log_file_msg contains 4232 bytes in 1 blocks (ref 0) 0x621005e49960
log_file_msg contains 4232 bytes in 1 blocks (ref 0) 0x621005e48560
log_file_msg contains 4232 bytes in 1 blocks (ref 0) 0x621005e47160
log_file_msg contains 4232 bytes in 1 blocks (ref 0) 0x621005e45d60
log_file_msg contains 4232 bytes in 1 blocks (ref 0) 0x621005e44960
log_file_msg contains 4232 bytes in 1 blocks (ref 0) 0x621005e43560
log_file_msg contains 4232 bytes in 1 blocks (ref 0) 0x621005e42160
log_file_msg contains 4232 bytes in 1 blocks (ref 0) 0x621005e40d60
log_file_msg contains 4232 bytes in 1 blocks (ref 0) 0x621005e3f960
log_file_msg contains 4232 bytes in 1 blocks (ref 0) 0x621005e3d160
log_file_msg contains 4232 bytes in 1 blocks (ref 0) 0x621005e3bd60
log_file_msg contains 4232 bytes in 1 blocks (ref 0) 0x621005e3a960
log_file_msg contains 4232 bytes in 1 blocks (ref 0) 0x621005e39560
log_file_msg contains 4232 bytes in 1 blocks (ref 0) 0x621005e38160
log_file_msg contains 4232 bytes in 1 blocks (ref 0) 0x621005e36d60
log_file_msg contains 4232 bytes in 1 blocks (ref 0) 0x621005e35960
log_file_msg contains 4232 bytes in 1 blocks (ref 0) 0x621005e34560
log_file_msg contains 4232 bytes in 1 blocks (ref 0) 0x621005e33160
log_file_msg contains 4232 bytes in 1 blocks (ref 0) 0x621005e31d60
log_file_msg contains 4232 bytes in 1 blocks (ref 0) 0x621005e30960
log_file_msg contains 4232 bytes in 1 blocks (ref 0) 0x621005e2f560
log_file_msg contains 4232 bytes in 1 blocks (ref 0) 0x621005e2cd60
log_file_msg contains 4232 bytes in 1 blocks (ref 0) 0x621005e2b960 log_file_msg contains 4232 bytes in 1 blocks (ref 0) 0x621005373d60
log_file_msg contains 4232 bytes in 1 blocks (ref 0) 0x621005372960
log_file_msg contains 4232 bytes in 1 blocks (ref 0) 0x621005371560
log_file_msg contains 4232 bytes in 1 blocks (ref 0) 0x621005370160
log_file_msg contains 4232 bytes in 1 blocks (ref 0) 0x62100529e160
log_file_msg contains 4232 bytes in 1 blocks (ref 0) 0x6210052ae560
log_file_msg contains 4232 bytes in 1 blocks (ref 0) 0x6210052be960
log_file_msg contains 4232 bytes in 1 blocks (ref 0) 0x6210052ced60
log_file_msg contains 4232 bytes in 1 blocks (ref 0) 0x6210052ee160
log_file_msg contains 4232 bytes in 1 blocks (ref 0) 0x6210052fe560
log_file_msg contains 4232 bytes in 1 blocks (ref 0) 0x62100530e960
log_file_msg contains 4232 bytes in 1 blocks (ref 0) 0x62100531ed60
log_file_msg contains 4232 bytes in 1 blocks (ref 0) 0x62100533e160
log_file_msg contains 4232 bytes in 1 blocks (ref 0) 0x62100534e560
log_file_msg contains 4232 bytes in 1 blocks (ref 0) 0x62100535e960
log_file_msg contains 4232 bytes in 1 blocks (ref 0) 0x62100536ed60
log_file_msg contains 4232 bytes in 1 blocks (ref 0) 0x62100536d960
log_file_msg contains 4232 bytes in 1 blocks (ref 0) 0x62100536c560
log_file_msg contains 4232 bytes in 1 blocks (ref 0) 0x62100536b160
log_file_msg contains 4232 bytes in 1 blocks (ref 0) 0x621005369d60
log_file_msg contains 4232 bytes in 1 blocks (ref 0) 0x621005368960
log_file_msg contains 4232 bytes in 1 blocks (ref 0) 0x621005367560
log_file_msg contains 4232 bytes in 1 blocks (ref 0) 0x621005366160
log_file_msg contains 4232 bytes in 1 blocks (ref 0) 0x621005364d60
log_file_msg contains 4232 bytes in 1 blocks (ref 0) 0x6210048ae560
log_file_msg contains 4232 bytes in 1 blocks (ref 0) 0x6210048be960
log_file_msg contains 4232 bytes in 1 blocks (ref 0) 0x6210048ced60
log_file_msg contains 4232 bytes in 1 blocks (ref 0) 0x6210048ee160
log_file_msg contains 4232 bytes in 1 blocks (ref 0) 0x6210048fe560
log_file_msg contains 4232 bytes in 1 blocks (ref 0) 0x62100490e960
log_file_msg contains 4232 bytes in 1 blocks (ref 0) 0x62100491ed60
log_file_msg contains 4232 bytes in 1 blocks (ref 0) 0x62100491d960
log_file_msg contains 4232 bytes in 1 blocks (ref 0) 0x62100491c560
log_file_msg contains 4232 bytes in 1 blocks (ref 0) 0x62100491b160
log_file_msg contains 4232 bytes in 1 blocks (ref 0) 0x621004919d60
log_file_msg contains 4232 bytes in 1 blocks (ref 0) 0x621004918960
log_file_msg contains 4232 bytes in 1 blocks (ref 0) 0x621004917560
log_file_msg contains 4232 bytes in 1 blocks (ref 0) 0x621004916160
log_file_msg contains 4232 bytes in 1 blocks (ref 0) 0x621004914d60
log_file_msg contains 4232 bytes in 1 blocks (ref 0) 0x621004913960 log_file_msg contains 4232 bytes in 1 blocks (ref 0) 0x621004868560
log_file_msg contains 4232 bytes in 1 blocks (ref 0) 0x621004867160
log_file_msg contains 4232 bytes in 1 blocks (ref 0) 0x621004865d60
log_file_msg contains 4232 bytes in 1 blocks (ref 0) 0x621004864960
log_file_msg contains 4232 bytes in 1 blocks (ref 0) 0x621004863560
log_file_msg contains 4232 bytes in 1 blocks (ref 0) 0x621004862160
log_file_msg contains 4232 bytes in 1 blocks (ref 0) 0x621004860d60
log_file_msg contains 4232 bytes in 1 blocks (ref 0) 0x62100485f960
log_file_msg contains 4232 bytes in 1 blocks (ref 0) 0x62100485d160
log_file_msg contains 4232 bytes in 1 blocks (ref 0) 0x62100485bd60
log_file_msg contains 4232 bytes in 1 blocks (ref 0) 0x62100485a960
log_file_msg contains 4232 bytes in 1 blocks (ref 0) 0x621004859560
log_file_msg contains 4232 bytes in 1 blocks (ref 0) 0x621004858160
log_file_msg contains 4232 bytes in 1 blocks (ref 0) 0x621004856d60
log_file_msg contains 4232 bytes in 1 blocks (ref 0) 0x621004855960
log_file_msg contains 4232 bytes in 1 blocks (ref 0) 0x621004854560
log_file_msg contains 4232 bytes in 1 blocks (ref 0) 0x621004853160
log_file_msg contains 4232 bytes in 1 blocks (ref 0) 0x621004851d60
log_file_msg contains 4232 bytes in 1 blocks (ref 0) 0x621004850960
log_file_msg contains 4232 bytes in 1 blocks (ref 0) 0x62100484f560
log_file_msg contains 4232 bytes in 1 blocks (ref 0) 0x62100484cd60
log_file_msg contains 4232 bytes in 1 blocks (ref 0) 0x621003e60d60
log_file_msg contains 4232 bytes in 1 blocks (ref 0) 0x621003e5f960
log_file_msg contains 4232 bytes in 1 blocks (ref 0) 0x621003e5d160
log_file_msg contains 4232 bytes in 1 blocks (ref 0) 0x621003e5bd60
log_file_msg contains 4232 bytes in 1 blocks (ref 0) 0x621003e5a960
log_file_msg contains 4232 bytes in 1 blocks (ref 0) 0x621003e59560
log_file_msg contains 4232 bytes in 1 blocks (ref 0) 0x621003e58160
log_file_msg contains 4232 bytes in 1 blocks (ref 0) 0x621003e56d60
log_file_msg contains 4232 bytes in 1 blocks (ref 0) 0x621003e55960
log_file_msg contains 4232 bytes in 1 blocks (ref 0) 0x621003e54560
log_file_msg contains 4232 bytes in 1 blocks (ref 0) 0x621003e53160
log_file_msg contains 4232 bytes in 1 blocks (ref 0) 0x621003e51d60
log_file_msg contains 4232 bytes in 1 blocks (ref 0) 0x621003e50960
log_file_msg contains 4232 bytes in 1 blocks (ref 0) 0x621003e4f560
log_file_msg contains 4232 bytes in 1 blocks (ref 0) 0x621003e4cd60 log_file_msg contains 4232 bytes in 1 blocks (ref 0) 0x621001da3960
log_file_msg contains 4232 bytes in 1 blocks (ref 0) 0x621001da2560
log_file_msg contains 4232 bytes in 1 blocks (ref 0) 0x621001da1160
log_file_msg contains 4232 bytes in 1 blocks (ref 0) 0x621001d9fd60
log_file_msg contains 4232 bytes in 1 blocks (ref 0) 0x621001d9d560
log_file_msg contains 4232 bytes in 1 blocks (ref 0) 0x621001d9c160
log_file_msg contains 4232 bytes in 1 blocks (ref 0) 0x621001d9ad60
log_file_msg contains 4232 bytes in 1 blocks (ref 0) 0x621001d99960
log_file_msg contains 4232 bytes in 1 blocks (ref 0) 0x621001d98560
log_file_msg contains 4232 bytes in 1 blocks (ref 0) 0x621001d97160
log_file_msg contains 4232 bytes in 1 blocks (ref 0) 0x621001d95d60
log_file_msg contains 4232 bytes in 1 blocks (ref 0) 0x621001d94960
log_file_msg contains 4232 bytes in 1 blocks (ref 0) 0x621001d93560
log_file_msg contains 4232 bytes in 1 blocks (ref 0) 0x621001d92160
log_file_msg contains 4232 bytes in 1 blocks (ref 0) 0x621001d90d60
log_file_msg contains 4232 bytes in 1 blocks (ref 0) 0x621001d8f960
log_file_msg contains 4232 bytes in 1 blocks (ref 0) 0x621001d8d160
log_file_msg contains 4232 bytes in 1 blocks (ref 0) 0x621001d8bd60
log_file_msg contains 4232 bytes in 1 blocks (ref 0) 0x621001d8a960
log_file_msg contains 4232 bytes in 1 blocks (ref 0) 0x621001d89560
log_file_msg contains 4232 bytes in 1 blocks (ref 0) 0x621001d88160
log_file_msg contains 4232 bytes in 1 blocks (ref 0) 0x621001d86d60
log_file_msg contains 4232 bytes in 1 blocks (ref 0) 0x621001d85960
log_file_msg contains 4232 bytes in 1 blocks (ref 0) 0x621001d84560
log_file_msg contains 4232 bytes in 1 blocks (ref 0) 0x621001d83160
log_file_msg contains 4232 bytes in 1 blocks (ref 0) 0x621001d81d60
log_file_msg contains 4232 bytes in 1 blocks (ref 0) 0x621001d80960
log_file_msg contains 4232 bytes in 1 blocks (ref 0) 0x621001d7f560
log_file_msg contains 4232 bytes in 1 blocks (ref 0) 0x621001d7cd60
log_file_msg contains 4232 bytes in 1 blocks (ref 0) 0x621001d7b960
log_file_msg contains 4232 bytes in 1 blocks (ref 0) 0x621001d7a560
log_file_msg contains 4232 bytes in 1 blocks (ref 0) 0x621001d79160
log_file_msg contains 4232 bytes in 1 blocks (ref 0) 0x621001d77d60
log_file_msg contains 4232 bytes in 1 blocks (ref 0) 0x621001d76960
log_file_msg contains 4232 bytes in 1 blocks (ref 0) 0x621001d75560
log_file_msg contains 4232 bytes in 1 blocks (ref 0) 0x621001d74160
log_file_msg contains 4232 bytes in 1 blocks (ref 0) 0x621001d72d60
log_file_msg contains 4232 bytes in 1 blocks (ref 0) 0x621001d71960
log_file_msg contains 4232 bytes in 1 blocks (ref 0) 0x621001d70560
log_file_msg contains 4232 bytes in 1 blocks (ref 0) 0x621001d6f16
</pre>
<p>I'm wondering why nobody has seend this so far. I've not been doing much develpment in recent months, but I would expect everyone would call SIGUSR1 every so often and look at suspicious leaks?</p>
OsmoGSMTester - Bug #5082 (Resolved): osmo-gsm-tester_virtual job fails for 5 consecutive days
https://projects.osmocom.org/issues/5082
2021-03-20T11:05:02Z
laforge
<pre>
22:48:54.830651 run osmo-msc_127.0.42.6(pid=29): ERR: Terminated: ERROR {rc=127} [trial-6400↪netreg_mass↪register_default_mass.py:24↪register_default_mass.py↪osmo-msc_127.0.42.6↪osmo-msc_127.0.42.6(pid=29)]
22:48:54.847791 run osmo-msc_127.0.42.6(pid=29): stdout:
| (launched: 2021-03-19_22:48:54.796500)
22:48:54.862465 run osmo-msc_127.0.42.6(pid=29): stderr:
| (launched: 2021-03-19_22:48:54.801775)
| /build/trial-6400/inst/osmo-msc/bin/osmo-msc: error while loading shared libraries: libasan.so.5: cannot open shared object file: No such file or directory
22:48:54.877112 run osmo-msc_127.0.42.6(pid=29): stdout:
| (launched: 2021-03-19_22:48:54.796500)
22:48:54.891014 run osmo-msc_127.0.42.6(pid=29): stderr:
| (launched: 2021-03-19_22:48:54.801775)
| /build/trial-6400/inst/osmo-msc/bin/osmo-msc: error while loading shared libraries: libasan.so.5: cannot open shared object file: No such file or directory
22:48:54.907674 tst register_default_mass.py:24: ERR: Error: osmo-msc_127.0.42.6(pid=29): Process ended prematurely: osmo-msc_127.0.42.6(pid=29) [trial-6400↪netreg_mass↪register_default_mass.py:24↪register_default_mass.py↪osmo-msc_127.0.42.6↪osmo-msc_127.0.42.6(pid=29)] [trial-6400↪netreg_mass↪register_default_mass.py:24]
22:48:54.908808 tst register_default_mass.py:24: Test FAILED (3.0 sec)
22:48:54.912335 run osmo-hlr_127.0.42.2(pid=25): ERR: Terminated: ERROR {rc=127} [trial-6400↪netreg_mass↪register_default_mass.py↪register_default_mass.py↪osmo-hlr_127.0.42.2↪osmo-hlr_127.0.42.2(pid=25)]
22:48:54.918759 run osmo-hlr_127.0.42.2(pid=25): stdout:
| (launched: 2021-03-19_22:48:53.594781)
22:48:54.925323 run osmo-hlr_127.0.42.2(pid=25): stderr:
| (launched: 2021-03-19_22:48:53.600678)
| /build/trial-6400/inst/osmo-hlr/bin/osmo-hlr: error while loading shared libraries: libasan.so.5: cannot open shared object file: No such file or directory
22:48:54.934490 run osmo-stp_127.0.42.5(pid=27): ERR: Terminated: ERROR {rc=127} [trial-6400↪netreg_mass↪register_default_mass.py↪register_default_mass.py↪osmo-stp_127.0.42.5↪osmo-stp_127.0.42.5(pid=27)]
22:48:54.940851 run osmo-stp_127.0.42.5(pid=27): stdout:
| (launched: 2021-03-19_22:48:54.017382)
22:48:54.947465 run osmo-stp_127.0.42.5(pid=27): stderr:
| (launched: 2021-03-19_22:48:54.022698)
| /build/trial-6400/inst/osmo-stp/bin/osmo-stp: error while loading shared libraries: libasan.so.5: cannot open shared object file: No such file or directory
</pre>
Cellular Network Infrastructure - Bug #5052 (Resolved): Osmocom release tarballs jenkins job fails
https://projects.osmocom.org/issues/5052
2021-02-28T09:14:15Z
laforge
<p>fails already for 5 consecutive buidlds <br /><a class="external" href="https://jenkins.osmocom.org/jenkins/view/All%20no%20Gerrit/job/Osmocom-release-tarballs/">https://jenkins.osmocom.org/jenkins/view/All%20no%20Gerrit/job/Osmocom-release-tarballs/</a></p>
Cellular Network Infrastructure - Bug #5051 (Resolved): repo-install-debian10 and -debian9 latest...
https://projects.osmocom.org/issues/5051
2021-02-28T09:11:42Z
laforge
<p>This has been failing for 5 consecutive days already, i.e. since the last release tags were made:</p>
<p><a class="external" href="https://jenkins.osmocom.org/jenkins/view/All%20no%20Gerrit/job/Osmocom-repo-install-debian10/feed=latest,label=repo-install-test/">https://jenkins.osmocom.org/jenkins/view/All%20no%20Gerrit/job/Osmocom-repo-install-debian10/feed=latest,label=repo-install-test/</a></p>
libosmocore - Bug #4995 (Resolved): handle ENOBUFS on write to AF_PACKET socket
https://projects.osmocom.org/issues/4995
2021-01-30T10:25:23Z
laforge
AF_PACKET sockets have the following "incredible" semantics:
<ul>
<li>even when marked write-able by select/poll, they still many return -1 / ENOBUFS in case the socket buffer and/or tx-queue of the driver is full</li>
<li>there is no way to safely/sanely wait for buffer space to become available again</li>
<li>the only option is to re-try until it finally succeeds, preferably after a "reasonable" amount of sleep, considering the data rate of the underlying transport medium</li>
</ul>
<p>I'm attaching a reproducer to demonstrate the problem, both with select() and without.</p>
<p>See also SYS#5343</p>
<p>The problem is further increased due to the fact that libosmocore/ns2 doesn't even notice if this happens.</p>
The call chain looks like this:
<ul>
<li><code>frame_relay.c:osmo_fr_tx_dlc()</code> is used to transmit NS messages by the NS2 core</li>
<li><code>frame_relay.c</code> will do whatever handling internaly</li>
<li><code>gprs_ns2fr.c:fr_tx_cb()</code> is the call-back we register with the frame_relay.c cre
<ul>
<li>puts msgb into osmo_wqueue</li>
</ul>
</li>
<li>wqueue code calls <code>gprs_ns2_fr.c:handle_netif_write()</code> as write-callback when the FD is write-able (always!)
<ul>
<li>we directlry retunr te result of the write() syscall (which is -1 in case of error)</li>
<li><code>osmo_wqueue_bfd_cb()</code> calls that write_cb(), but
<ul>
<li>it expects a -errno type return value, not the return value of a syscall that's likely just -1.</li>
<li>only treats "-EAGAIN" as a trigger to re-enqueue the just-dequeued message</li>
</ul></li>
</ul></li>
</ul>
<p>So all in all, we are using a write_queue, but it will never really queue anything, as the socket is always writable and we don't realize if the write actually fails.</p>
What makes this even worse: A shared write_queue for user traffic and Q.933 LMI (or even NS-ALIVE) traffic is actively dangerous
<ul>
<li>if Q.933 starts to fail ,the entire link will be marked dead at the FR level</li>
<li>if NS-ALIVE starts to fail, the NS-VC will be marked as DEAD</li>
</ul>
Now the question is what to do about it:
<ol>
<li>as an absolute minimum, we should have a counter and/or error messages if ENOBUFS or any other error happens</li>
<li>users of osmo_wqueue should always return a "-errno" style return value. We should audit all our code, not just this example</li>
<li>there should be some notification of the uppwer layers/application when ENOBUFS happens</li>
<li>have separate queues or some other prioritization that prefers Q.933 LMI traffic and NS-signaling (ALIVE/ALIVE-ACK) over all user traffic (NS-UNITDATA)</li>
</ol>
osmo-gbproxy - Bug #4965 (Resolved): osmo-gbproxy segfaults in ttcn3-gbproxy-test
https://projects.osmocom.org/issues/4965
2021-01-21T11:31:33Z
laforge
<p>See <a class="external" href="https://jenkins.osmocom.org/jenkins/view/TTCN3/job/ttcn3-gbproxy-test/107/console">https://jenkins.osmocom.org/jenkins/view/TTCN3/job/ttcn3-gbproxy-test/107/console</a></p>
<p>It happens really soon after start-up:<br /><pre>
20210121111035629 DLGLOBAL <0013> telnet_interface.c:104 Available via telnet 0.0.0.0 4246
20210121111035630 DLCTRL <001a> control_if.c:915 CTRL at 127.0.0.1 4263
20210121111038666 DGPRS <0004> gb_proxy.c:1382 NS: Unknown NS-STATUS.ind cause=NSVC failure from NS
20210121111038667 DLNS <0026> gprs_ns2_sns.c:1359 GPRS-NS2-SNS-BSS(NSE00101-SNS)[0x55f9c0834300]{SIZE}: NSE 101: no remaining NSVC, resetting SNS FSM
20210121111038667 DGPRS <0004> gb_proxy.c:1382 NS: Unknown NS-STATUS.ind cause=NSVC failure from NS
20210121111038667 DLNS <0026> gprs_ns2_sns.c:1359 GPRS-NS2-SNS-BSS(NSE00102-SNS)[0x55f9c0835380]{SIZE}: NSE 102: no remaining NSVC, resetting SNS FSM
20210121111041692 DGPRS <0004> gb_proxy.c:1382 NS: Unknown NS-STATUS.ind cause=NSVC recovery from NS
20210121111041698 DLNS <0026> gprs_ns2_vc_fsm.c:823 GPRS-NS2-VC(UDP-NSE00102-remote-172_18_24_103:24000)[0x55f9c0834e70]{UNBLOCKED}: NSEI=102 Rx unknown NS PDU type NS-STATUS
20210121111041700 DGPRS <0004> gb_proxy.c:1382 NS: Unknown NS-STATUS.ind cause=NSVC recovery from NS
20210121111041707 DLNS <0026> gprs_ns2_vc_fsm.c:823 GPRS-NS2-VC(UDP-NSE00101-remote-172_18_24_103:23000)[0x55f9c0837790]{UNBLOCKED}: NSEI=101 Rx unknown NS PDU type NS-STATUS
20210121111042928 DGPRS <0004> gb_proxy.c:1344 NS-NSE 2001 became available
20210121111042928 DGPRS <0004> gb_proxy.c:1382 NS: Unknown NS-STATUS.ind cause=NSVC recovery from NS
Segmentation fault (core dumped)
</pre></p>
<p>a decoded core dump (no sources in the container):<br /><pre>
#0 gprs_ns2_vc_rx (nsvc=nsvc@entry=0x55f9c0837070, msg=msg@entry=0x55f9c083d6d0, tp=tp@entry=0x0)
at gprs_ns2_vc_fsm.c:766
766 gprs_ns2_vc_fsm.c: No such file or directory.
(gdb) bt
#0 gprs_ns2_vc_rx (nsvc=nsvc@entry=0x55f9c0837070, msg=msg@entry=0x55f9c083d6d0, tp=tp@entry=0x0)
at gprs_ns2_vc_fsm.c:766
#1 0x00007f800f099d65 in ns2_recv_vc (nsvc=0x55f9c0837070, msg=msg@entry=0x55f9c083d6d0)
at gprs_ns2.c:1102
#2 0x00007f800f09b456 in handle_nsip_read (bfd=0x55f9c0834120) at gprs_ns2_udp.c:251
#3 nsip_fd_cb (bfd=0x55f9c0834120, what=1) at gprs_ns2_udp.c:269
#4 0x00007f800ec2ca18 in poll_disp_fds (n_fd=<optimized out>) at select.c:350
#5 _osmo_select_main (polling=<optimized out>) at select.c:378
#6 0x00007f800ec2ca96 in osmo_select_main (polling=<optimized out>) at select.c:417
#7 0x000055f9c02a8491 in main (argc=3, argv=0x7ffc86df1308) at gb_proxy_main.c:332
</pre></p>
libosmocore - Bug #4949 (Resolved): List of "remote IPv4 endpoints" grows every time a peer recon...
https://projects.osmocom.org/issues/4949
2021-01-14T17:01:49Z
laforge
<p>After running the better part of the GBProxy_Tests test suite, the VTY output of osmo-gboroxy <code>show ns</code> looks like this:</p>
<pre>
NSEI 02003: UDP, DEAD
NSVCI 02103: RESET DYNAMIC data_weight=1 sig_weight=1 udp)[127.0.0.1]:23000<2103>[127.0.0.1]:21030
NSEI 02002: UDP, DEAD
NSVCI 02102: RESET DYNAMIC data_weight=1 sig_weight=1 udp)[127.0.0.1]:23000<2102>[127.0.0.1]:21020
NSEI 02001: UDP, DEAD
NSVCI 02101: RESET DYNAMIC data_weight=1 sig_weight=1 udp)[127.0.0.1]:23000<2101>[127.0.0.1]:21010
NSEI 00102: UDP, DEAD
FSM Instance Name: 'GPRS-NS2-SNS-BSS(NSE00102-SNS)[0x6120000018a0]', ID: 'NSE00102-SNS'
Log-Level: 'DEBUG', State: 'SIZE'
Timer: 1
Maximum number of remote NS-VCs: 8, IPv4 Endpoints: 4, IPv6 Endpoints: 0
Local IPv4 Endpoints:
127.0.0.1:23000, Signalling Weight: 2, Data Weight: 1
Remote IPv4 Endpoints:
127.0.0.1:8888, Signalling Weight: 1, Data Weight: 1
127.0.0.1:8888, Signalling Weight: 1, Data Weight: 1
127.0.0.1:8888, Signalling Weight: 1, Data Weight: 1
127.0.0.1:8888, Signalling Weight: 1, Data Weight: 1
127.0.0.1:8888, Signalling Weight: 1, Data Weight: 1
127.0.0.1:8888, Signalling Weight: 1, Data Weight: 1
127.0.0.1:8888, Signalling Weight: 1, Data Weight: 1
127.0.0.1:8888, Signalling Weight: 1, Data Weight: 1
127.0.0.1:8888, Signalling Weight: 1, Data Weight: 1
127.0.0.1:8888, Signalling Weight: 1, Data Weight: 1
127.0.0.1:8888, Signalling Weight: 1, Data Weight: 1
127.0.0.1:8888, Signalling Weight: 1, Data Weight: 1
127.0.0.1:8888, Signalling Weight: 1, Data Weight: 1
127.0.0.1:8888, Signalling Weight: 1, Data Weight: 1
127.0.0.1:8888, Signalling Weight: 1, Data Weight: 1
127.0.0.1:8888, Signalling Weight: 1, Data Weight: 1
127.0.0.1:8888, Signalling Weight: 1, Data Weight: 1
127.0.0.1:8888, Signalling Weight: 1, Data Weight: 1
127.0.0.1:8888, Signalling Weight: 1, Data Weight: 1
127.0.0.1:8888, Signalling Weight: 1, Data Weight: 1
127.0.0.1:8888, Signalling Weight: 1, Data Weight: 1
127.0.0.1:8888, Signalling Weight: 1, Data Weight: 1
127.0.0.1:8888, Signalling Weight: 1, Data Weight: 1
127.0.0.1:8888, Signalling Weight: 1, Data Weight: 1
127.0.0.1:8888, Signalling Weight: 1, Data Weight: 1
127.0.0.1:8888, Signalling Weight: 1, Data Weight: 1
127.0.0.1:8888, Signalling Weight: 1, Data Weight: 1
127.0.0.1:8888, Signalling Weight: 1, Data Weight: 1
127.0.0.1:8888, Signalling Weight: 1, Data Weight: 1
127.0.0.1:8888, Signalling Weight: 1, Data Weight: 1
127.0.0.1:8888, Signalling Weight: 1, Data Weight: 1
127.0.0.1:8888, Signalling Weight: 1, Data Weight: 1
127.0.0.1:8888, Signalling Weight: 1, Data Weight: 1
127.0.0.1:8888, Signalling Weight: 1, Data Weight: 1
127.0.0.1:8888, Signalling Weight: 1, Data Weight: 1
NSVCI none: UNCONFIGURED DYNAMIC data_weight=1 sig_weight=1 udp)[127.0.0.1]:23000<>[127.0.0.1]:8888
NSEI 00101: UDP, DEAD
FSM Instance Name: 'GPRS-NS2-SNS-BSS(NSE00101-SNS)[0x6120000015a0]', ID: 'NSE00101-SNS'
Log-Level: 'DEBUG', State: 'SIZE'
Timer: 1
Maximum number of remote NS-VCs: 8, IPv4 Endpoints: 4, IPv6 Endpoints: 0
Local IPv4 Endpoints:
127.0.0.1:23000, Signalling Weight: 2, Data Weight: 1
Remote IPv4 Endpoints:
127.0.0.1:7777, Signalling Weight: 1, Data Weight: 1
127.0.0.1:7777, Signalling Weight: 1, Data Weight: 1
127.0.0.1:7777, Signalling Weight: 1, Data Weight: 1
127.0.0.1:7777, Signalling Weight: 1, Data Weight: 1
127.0.0.1:7777, Signalling Weight: 1, Data Weight: 1
127.0.0.1:7777, Signalling Weight: 1, Data Weight: 1
127.0.0.1:7777, Signalling Weight: 1, Data Weight: 1
127.0.0.1:7777, Signalling Weight: 1, Data Weight: 1
127.0.0.1:7777, Signalling Weight: 1, Data Weight: 1
127.0.0.1:7777, Signalling Weight: 1, Data Weight: 1
127.0.0.1:7777, Signalling Weight: 1, Data Weight: 1
127.0.0.1:7777, Signalling Weight: 1, Data Weight: 1
127.0.0.1:7777, Signalling Weight: 1, Data Weight: 1
127.0.0.1:7777, Signalling Weight: 1, Data Weight: 1
127.0.0.1:7777, Signalling Weight: 1, Data Weight: 1
127.0.0.1:7777, Signalling Weight: 1, Data Weight: 1
127.0.0.1:7777, Signalling Weight: 1, Data Weight: 1
127.0.0.1:7777, Signalling Weight: 1, Data Weight: 1
127.0.0.1:7777, Signalling Weight: 1, Data Weight: 1
127.0.0.1:7777, Signalling Weight: 1, Data Weight: 1
127.0.0.1:7777, Signalling Weight: 1, Data Weight: 1
127.0.0.1:7777, Signalling Weight: 1, Data Weight: 1
127.0.0.1:7777, Signalling Weight: 1, Data Weight: 1
127.0.0.1:7777, Signalling Weight: 1, Data Weight: 1
127.0.0.1:7777, Signalling Weight: 1, Data Weight: 1
127.0.0.1:7777, Signalling Weight: 1, Data Weight: 1
127.0.0.1:7777, Signalling Weight: 1, Data Weight: 1
127.0.0.1:7777, Signalling Weight: 1, Data Weight: 1
127.0.0.1:7777, Signalling Weight: 1, Data Weight: 1
127.0.0.1:7777, Signalling Weight: 1, Data Weight: 1
127.0.0.1:7777, Signalling Weight: 1, Data Weight: 1
127.0.0.1:7777, Signalling Weight: 1, Data Weight: 1
127.0.0.1:7777, Signalling Weight: 1, Data Weight: 1
127.0.0.1:7777, Signalling Weight: 1, Data Weight: 1
127.0.0.1:7777, Signalling Weight: 1, Data Weight: 1
NSVCI none: UNCONFIGURED DYNAMIC data_weight=1 sig_weight=1 udp)[127.0.0.1]:23000<>[127.0.0.1]:7777
UDP bind: 127.0.0.1:23000 DSCP: 0
5 NS-VC:
NSVCI 00000: udp)[127.0.0.1]:23000<>[127.0.0.1]:8888
NSVCI 00000: udp)[127.0.0.1]:23000<>[127.0.0.1]:7777
NSVCI 02103: udp)[127.0.0.1]:23000<2103>[127.0.0.1]:21030
NSVCI 02102: udp)[127.0.0.1]:23000<2102>[127.0.0.1]:21020
NSVCI 02101: udp)[127.0.0.1]:23000<2101>[127.0.0.1]:21010
</pre>
<p>As we can see, there seems to be some bug that causes new <br /><pre>
127.0.0.1:7777, Signalling Weight: 1, Data Weight: 1
</pre><br />to show up for every test case execution.</p>
I guess during the SNS-CONFIG procedure we somehow unconditionally create new objects rather than either
<ol>
<li>first delete all objects, then create new ones, or</li>
<li>check if the identical object already exists, and only create one if it doesn't</li>
</ol>
E1/T1 Hardware Interface (including icE1usb) - Bug #4943 (Resolved): jenkins job for osmo-e1-hard...
https://projects.osmocom.org/issues/4943
2021-01-13T08:08:29Z
laforge
<p>Hi oliver,</p>
<p>the recent changes related to osmo-gsm-manuals seem to have introduced a regression as can be seen at <br /><a class="external" href="https://jenkins.osmocom.org/jenkins/job/master-osmo-e1-hardware/a1=default,a2=default,a3=default,a4=default,label=osmocom-master-debian9/49/console">https://jenkins.osmocom.org/jenkins/job/master-osmo-e1-hardware/a1=default,a2=default,a3=default,a4=default,label=osmocom-master-debian9/49/console</a></p>
<p>please fix.</p>
OsmoPCU - Bug #4936 (Resolved): osmo-pcu OBS nightly builds all fail "/usr/bin/ld: cannot find -l...
https://projects.osmocom.org/issues/4936
2021-01-08T09:51:02Z
laforge
<p>Tonight, <strong>all</strong> our osmo-pcu (and osmo-sgsn) builds started to fail with:</p>
<pre>
[ 308s] CXX pcu_main.o
[ 308s] CXX gprs_debug.lo
[ 308s] CC csn1.lo
[ 308s] CC gsm_rlcmac.lo
[ 308s] CXX gprs_bssgp_pcu.lo
[ 308s] CXX gprs_rlcmac.lo
[ 308s] CXX gprs_rlcmac_sched.lo
[ 308s] CXX gprs_rlcmac_meas.lo
[ 310s] CXX gprs_rlcmac_ts_alloc.lo
[ 312s] CC gprs_ms.lo
[ 312s] CXX gprs_ms_storage.lo
[ 312s] CXX gsm_timer.lo
[ 313s] CXX pcu_l1_if.lo
[ 313s] CC pcu_vty.lo
[ 314s] CXX pcu_vty_functions.lo
[ 315s] CC mslot_class.lo
[ 315s] CXX tbf.lo
[ 316s] CXX tbf_ul.lo
[ 316s] CXX tbf_dl.lo
[ 316s] CXX bts.lo
[ 317s] CXX pdch.lo
[ 318s] CXX poll_controller.lo
[ 318s] CXX encoding.lo
[ 318s] CXX sba.lo
[ 321s] CXX decoding.lo
[ 322s] CXX llc.lo
[ 322s] CXX rlc.lo
[ 322s] CXX osmobts_sock.lo
[ 323s] CC gprs_codel.lo
[ 323s] CC coding_scheme.lo
[ 324s] CXX egprs_rlc_compression.lo
[ 327s] CXXLD libgprs.la
[ 327s] copying selected object files to avoid basename conflicts...
[ 327s] CXXLD osmo-pcu
[ 328s] /usr/bin/ld: cannot find -lmnl
[ 328s] collect2: error: ld returned 1 exit status
[ 328s] make[1]: *** [Makefile:723: osmo-pcu] Error 1
</pre>
<p>I don't really get why this is happening. libosmocore.so.* is linked with libmnl.so.x.y.z, so there is absolutely no need to link each application explicitly against "-lmnl". The latter would require libmnl-dev to be installed, which it is not (and which it should not required to be).</p>
<p>So where does the sudden "-lmnl" come from?</p>
osmo-gbproxy - Bug #4904 (Resolved): osmo-gbproxy segfault in GBProxy_Tests.TC_paging_ps_sig_lac_...
https://projects.osmocom.org/issues/4904
2020-12-12T14:54:06Z
laforge
<pre>
DGPRS DEBUG NSE(00101/SGSN)-BVC(00000/??) Rx PAGING-PS (gb_proxy.c:952)
gb_proxy.c:901:3: runtime error: member access within null pointer of type 'struct gbproxy_nse'
AddressSanitizer:DEADLYSIGNAL
=================================================================
==945943==ERROR: AddressSanitizer: SEGV on unknown address 0x00000000001a (pc 0x55e3c9b15ce5 bp 0x623000000960 sp 0x7fff413340a0 T0)
==945943==The signal is caused by a READ memory access.
==945943==Hint: address points to the zero page.
#0 0x55e3c9b15ce5 in gbprox_rx_paging /space/home/laforge/projects/git/osmo-sgsn/src/gbproxy/gb_proxy.c:901
#1 0x55e3c9b15ce5 in gbprox_rx_sig_from_sgsn /space/home/laforge/projects/git/osmo-sgsn/src/gbproxy/gb_proxy.c:1020
#2 0x55e3c9b1a8a6 in gprs_ns2_prim_cb /space/home/laforge/projects/git/osmo-sgsn/src/gbproxy/gb_proxy.c:1231
#3 0x7f7760596983 in gprs_ns2_recv_unitdata /space/home/laforge/projects/git/libosmocore/src/gb/gprs_ns2_vc_fsm.c:500
#4 0x7f776059931a in gprs_ns2_vc_fsm_allstate_action /space/home/laforge/projects/git/libosmocore/src/gb/gprs_ns2_vc_fsm.c:551
#5 0x7f77600820f5 in _osmo_fsm_inst_dispatch /space/home/laforge/projects/git/libosmocore/src/fsm.c:877
#6 0x7f776059ad54 in gprs_ns2_vc_rx /space/home/laforge/projects/git/libosmocore/src/gb/gprs_ns2_vc_fsm.c:702
#7 0x7f7760583e0c in ns2_recv_vc /space/home/laforge/projects/git/libosmocore/src/gb/gprs_ns2.c:1068
#8 0x7f776058810d in handle_nsip_read /space/home/laforge/projects/git/libosmocore/src/gb/gprs_ns2_udp.c:243
#9 0x7f776058810d in nsip_fd_cb /space/home/laforge/projects/git/libosmocore/src/gb/gprs_ns2_udp.c:261
#10 0x7f77600660c1 in poll_disp_fds /space/home/laforge/projects/git/libosmocore/src/select.c:350
#11 0x7f77600660c1 in _osmo_select_main /space/home/laforge/projects/git/libosmocore/src/select.c:378
#12 0x7f7760066458 in osmo_select_main /space/home/laforge/projects/git/libosmocore/src/select.c:417
#13 0x55e3c9b0b49f in main /space/home/laforge/projects/git/osmo-sgsn/src/gbproxy/gb_proxy_main.c:333
#14 0x7f775f456d09 in __libc_start_main ../csu/libc-start.c:308
#15 0x55e3c9b0ba29 in _start (/space/home/laforge/projects/git/osmo-sgsn/src/gbproxy/osmo-gbproxy+0x37a29)
AddressSanitizer can not provide additional info.
SUMMARY: AddressSanitizer: SEGV /space/home/laforge/projects/git/osmo-sgsn/src/gbproxy/gb_proxy.c:901 in gbprox_rx_paging
==945943==ABORTING
</pre>
OsmoBTS - Bug #4681 (Resolved): >= 100 BTS_Tests.ttcn failures / regressions since July 23rd
https://projects.osmocom.org/issues/4681
2020-07-26T18:34:24Z
laforge
<p>since July 23rd, almost all of our tests are failing with a regression (100 new failures from July 22nd -> 23rd): <a class="external" href="https://jenkins.osmocom.org/jenkins/view/TTCN3/job/ttcn3-bts-test/963/#showFailuresLink">https://jenkins.osmocom.org/jenkins/view/TTCN3/job/ttcn3-bts-test/963/#showFailuresLink</a></p>
<p>Regressions of this s cale are not acceptable at all, particularly not if they are not resolved for several days in a row.</p>
OsmocomBB - Feature #4575 (Closed): Build + Test CP2102 GTM900 breakout board prototype
https://projects.osmocom.org/issues/4575
2020-06-02T08:24:58Z
laforge
<p>3 PCBs and associated components are on their way to the sysmocom office (arriving today around noon).</p>
<p>Pleae assemble ASAP one board for initial testing (see checklist)</p>
<p>Once the first board appears working, please assemble the other two.</p>
<p>Report any issues that require fixing in the design on the design to <a class="user active" href="https://projects.osmocom.org/users/128">mschramm</a> in <a class="issue tracker-2 status-2 priority-2 priority-default" title="Feature: design breakout board for GTM900-B (In Progress)" href="https://projects.osmocom.org/issues/4030">#4030</a></p>
OsmoMGW - Bug #4441 (Resolved): osmo-mgw lacks CTRL interface
https://projects.osmocom.org/issues/4441
2020-03-08T09:42:07Z
laforge
<p>OsmoMGW has a lot of nice built-in statistics (rate_ctr,...) but it seems the only way to look at them is via the VTY. While libosmocore contains automatic exposure of all rate counters via CTRL, the CTRL interface simply is not present/active.</p>
osmo-remsim - Support #4021 (Resolved): long-term end-to-end osmo-remsim test setup
https://projects.osmocom.org/issues/4021
2019-05-23T16:07:31Z
laforge
let's build a setup consisting of:
<ul>
<li>5-slot CCID card reader</li>
<li>sysmoQMOD with four Gobi2000 modems
<ul>
<li>four random SIM cards</li>
</ul>
</li>
<li>APU2 with Debian9</li>
<li>one instance of remsim-server from osmocom:nightly feed running on the host</li>
<li>Debian 9 VM for remsim-bankd
<ul>
<li>USB port towards card reader routed to this VM</li>
<li>one instance of osmo-bankd from osmocom:nightly feed running</li>
</ul>
</li>
<li>Debian 9 VM for remsim-client
<ul>
<li>USB port towards QMOD routed to this VM</li>
<li>four instances of osmo-remsmim from osmocom:nightly feed running</li>
</ul></li>
</ul>
<p>The host machine should run <code>tc netem</code> to simulate a non-zero latency, such as 200ms between client/server/bankd</p>
<p>All software should automatically start up after boot.</p>
OsmoBTS - Bug #3255 (Rejected): osmo-bts build verification broken
https://projects.osmocom.org/issues/3255
2018-05-09T18:34:21Z
laforge
<p>All build verification by jenkins for osmo-bts is broken, as a new version of the OCTPHY headers was pushed to <code>octphy-2g-headers/master</code> without previously merging the osmo-bts related patches to actually support those headers.</p>
<p>see e.g. <a class="external" href="https://jenkins.osmocom.org/jenkins/job/gerrit-osmo-bts/382/BTS_MODEL=oct,FIRMWARE_VERSION=master,a3=default,a4=default,label=osmocom-gerrit-debian9/console">https://jenkins.osmocom.org/jenkins/job/gerrit-osmo-bts/382/BTS_MODEL=oct,FIRMWARE_VERSION=master,a3=default,a4=default,label=osmocom-gerrit-debian9/console</a></p>
<p>I've now force-pushed an older version to "master" and started a new "next" branch for the latest (but not yet supported by osmo-bts!) version of the headers that was pushed on April 14.</p>
OsmoMSC - Bug #2892 (Resolved): TTCN-3 test suite for OsmoMSC not yet automatically executed
https://projects.osmocom.org/issues/2892
2018-01-27T15:46:10Z
laforge
<p>We have a growing suite of tests for OsmoMSC which are not yet automatically executed. This should change soon so we can track (at least) daily progress or regressions as we develop along.</p>
OsmoPCU - Bug #2407 (Closed): N3101 not implemented in OsmoPCU
https://projects.osmocom.org/issues/2407
2017-07-29T12:11:49Z
laforge
<p>N3101 is a counter. It counts up for every time no uplink data is received for an assigned USF.</p>
<p>Every time uplik data for an assigned USF is received, the counter is reset to zero.</p>
<p>If the counter ever reaches N3101_MAX, then the USF is no longer placed on the downlink, T3169 started and runs to expiry. After T3169 expiration, the USF is released and can be used by other TBF/MS.</p>
OsmoSDR - Feature #1467 (Rejected): place "sysmocom" name into copper layer (back side)
https://projects.osmocom.org/issues/1467
2016-02-19T22:50:52Z
laforge
<p>For WEEE reasons, if sysmocom sells the product, the brand name "sysmocom" has to be present on the device in a way that is difficult to remove. The copper layer might be best.</p>
SIMtrace - Bug #1437 (Closed): on resistance of bus switch not acceptable, at least not for Vcc
https://projects.osmocom.org/issues/1437
2016-02-19T22:48:41Z
laforge
<p>As can be seen from the IDTQS3244 data sheet, the ON resistance is higher tham 16 ohms in case of a 3.3V power input (VCC_PHONE).</p>
<p>This causes significant voltage drop over the switch, resulting in way too low supply voltage arriving at the SIM card.</p>
<p>It seems like we really need to re-think the switching concept. A short-time fix might be to supply power from the SIMTRACE to the sim, rather than passing it through. However, even for the CLK/IO/RST signals the 16Ohms might cause significant signal degradation.</p>
OpenBSC - Feature #1 (Closed): port Dieter's windows code to mISDN
https://projects.osmocom.org/issues/1
2016-02-19T22:47:29Z
laforge
<p>This is just a 1:1 port to replicate the functionality of Dieter's code based on mISDN/Linux.</p>