osmocom-announce

osmocom-announce@lists.osmocom.org

76 discussions

osmo-smlc 0.3.2 released
by Oliver Smith 06 Mar '25

06 Mar '25

Hello all, today we've released osmo-smlc 0.3.2. The change over 0.3.1 is as follows: > osmo-smlc (0.3.2) unstable; urgency=medium > > [ Oliver Smith ] > * contrib/jenkins: libosmo-abis after libosmo-netif > > [ Pau Espin Pedrol ] > * jenkins.sh: Skip building unneeded libosmo-abis > * jenkins.sh: No need to build libosmo-sigtran with doxygen > * Add missing required vty go_parent_cb for libosmo-sigtran > > -- Oliver Smith <osmith(a)sysmocom.de> Wed, 05 Mar 2025 11:35:11 +0100 -- - Oliver Smith <osmith(a)sysmocom.de> https://www.sysmocom.de/ ======================================================================= * sysmocom - systems for mobile communications GmbH * Siemensstr. 26a * 10551 Berlin, Germany * Sitz / Registered office: Berlin, HRB 134158 B * Geschaeftsfuehrer / Managing Director: Harald Welte

1 0

osmo-upf 0.3.0 released
by Oliver Smith 18 Feb '25

18 Feb '25

Hello all, today we have released osmo-upf 0.3.0. The changelog over 0.2.0 is as follows: > osmo-upf (0.3.0) unstable; urgency=medium > > [ Oliver Smith ] > * upf_gtp: automatically delete old gtp devices > > [ Pau Espin Pedrol ] > * Improve logging reading packets from gtp device > * Remove unused file up_session_to_gtp.c > * Simplify up_session_choose_f_teid() with early returns > * Introduce hashtable to lookup session by F-TEID > * Introduce hashtable to lookup chain_id > * Introduce hashtable to look up gtp_tundev by local TEID > > -- Oliver Smith <osmith(a)sysmocom.de> Tue, 18 Feb 2025 12:20:35 +0100 -- - Oliver Smith <osmith(a)sysmocom.de> https://www.sysmocom.de/ ======================================================================= * sysmocom - systems for mobile communications GmbH * Siemensstr. 26a * 10551 Berlin, Germany * Sitz / Registered office: Berlin, HRB 134158 B * Geschaeftsfuehrer / Managing Director: Harald Welte

1 0

February 2025 Osmocom CNI releases
by Oliver Smith 14 Feb '25

14 Feb '25

Hello all, the Osmocom project has released new version 202502 of the CNI (Cellular Network Infrastructure) software. Those new tagged/released versions contain 7 months of work since the previous versions released during July 2024. See https://osmocom.org/news/293 for details. Thanks to everybody who has contributed to these releases! Best regards, Oliver -- - Oliver Smith <osmith(a)sysmocom.de> https://www.sysmocom.de/ ======================================================================= * sysmocom - systems for mobile communications GmbH * Siemensstr. 26a * 10551 Berlin, Germany * Sitz / Registered office: Berlin, HRB 134158 B * Geschaeftsfuehrer / Managing Director: Harald Welte

1 0

osmo-upf 0.2.0 released
by Oliver Smith 13 Dec '24

13 Dec '24

Today we've released osmo-upf 0.2.0. The changelog over 0.1.1 is as follows: > osmo-upf (0.2.0) unstable; urgency=medium > > [ Neels Hofmeyr ] > * improve manual: PFCP and GTP interfaces > * example cfg: tweak logging > > [ Oliver Smith ] > * osmo_pfcp_tool: fix osmo_pfcp_tool_copyright error > * debian: add osmo-pfcp-tool to osmo-upf package > * Run struct_endianness.py > * contrib/jenkins: build nftables without python > * contrib/jenkins: clone netfilter repos with https > * contrib/jenkins: netfilter: use PARALLEL_MAKE > * debian: set compat level to 10 > * systemd: depend on networking-online.target > * .deb/.rpm: various fixes related to non-root > * contrib/systemd: AmbientCapabilities=CAP_NET_ADMIN > * contrib: remove rpm spec file > * debian/postinst: add checks, be verbose > > [ Neels Janosch Hofmeyr ] > * Allow running without a GTP dev > * drop charts/, duplicated from libosmo-pfcp.git > * manual: add/fix running.adoc > * manual: add 'Configure Primary Links' > * vty doc: indicate default nft table name > * silence misleading error: "HEARTBEAT_REQ: Unknown message type" > * drop unused enum up_session_kind > * tests/upf.vty: add some missing nodes to the test > * VTY: rename 'gtp' to 'tunend' > * VTY: rename 'nft' to 'tunmap' > * osmo-pfcp-tool VTY: rename 'endecaps' to 'tunend' > * cosmetic: in code, rename 'endecaps' to 'tunend' > * cosmetic: rename upf_gtp_tun to upf_gtp_tunend > * drop unused upf_gtp_dev_is_tunnel_active() > * cosmetic: rename upf_gtp_dev_tunnel_* to upf_gtp_dev_tunend_* > * vty: revert rename of 'show gtp' > * VTY: show gtp: still list tunmap if no tunend device is open > * up_gtp_action_to_str_buf(): always print PDR IDs > * use osmo_pfcp_ie_outer_header_creation_to_str_buf() > * gtpu_echo: do not osmo_fd_register twice > * VTY 'show gtp': more accurately identify local/remote IP > * fix access/core mixup of PDR IDs / tunmap FAR > * clarify comments and naming around PDR+FAR classification > * tunmap: choose local GTP addr by Network Instance IEs > * log: add missing sep in far_to_str > * fix PFCP Session Mod: Update FAR > * in GTP actions, also store local GTP addrs > * nft: rename addr to addr_remote, add addr_local > * nft: incoming GTP-U: match on local IP, not remote IP > * nft: rewrite source IP in outgoing GTP-U > * nft: log nft rulesets on debug log > * nft: end each rule in semicolon > * nft: ensure to assign rule id only once > * GTP,UE addrs in osmo_sockaddr: assert( port == 0 ) > * nft: allow to get the ruleset string without running > * vty: add: show nft-rule tunmap example > * add cfg: tunmap / nft-rule append > * nft: append 'accept' to each rule > * tunend: choose local GTP addr by Network Instance IEs > * manual: use 'tunend' and 'tunmap' > * manual: explain new netinst cfg > * manual: tweak 'running' for new netinst feature > * manual: add charts explaining tunend and tunmap > * manual: some tweaks in overview > * manual: fix broken reference to netinst section > * fix copy-paste bug in up_endpoint.c > * fix deprecation: use telnet_init_default() > * check rc of osmo_use_count_get_put() > * error log: fix msg for gtp_del_tunnel() failure > * fix various crashes on osmo_pfcp_endpoint_tx() err handling > * osmo-pfcp-tool: avoid stale pointers on msg copy > * fix some PFCP peer,session error handling paths > * drop unused function up_peer_tx > * move GTP port definitions to upf.h > * deprecate cfg 'nft rule tunmap append' > * tunmap: prep new nft ruleset: log only mapping id > * tunmap: refactor nft ruleset: fix "martians" and "1024" > * tunmap: ensure nft table is removed on program exit > * osmo_pfcp_tool: make usable again > * minor api doc > * cosmetic: simplify naming: struct upf_tunmap, struct upf_tunend > * cosmetic: reduce dup in tunnel struct definitions > * cosmetic: rename g_upf->gtp to tunend, ->nft to tunmap > * move next_teid from up_endpoint to g_upf > * cosmetic: rename next_seid to next_up_seid > * build: drop LIBOSMO_GTLV > * build: add libupf.la (noinst) > * add unique_ids_test.c > * tunmap: ensure assigned chain_id is unused > * cosmetic: clarify session active / partially active semantics > * unique_ids_test.c: fix coverity ASSERT_SIDE_EFFECT > * manual: fix typo in running.adoc > * manual: 'Running': flatten section depths a bit > * manual: 'Running': tweak, mention 'tunmap' and 'tunend' > * manual: 'Running': tweak word, fix ws at line end > * manual: explain GTP Echo workaround for tunmap > * manual: explain IP forwarding > * tunmap: always set GTP-U source port to 2152 when forwarding > * vty doc fix > * pfcp-tool: fix extra newline in vty_out > * fix msgb memleak on GTP echo response > * fix EXTRA_DIST for vty test scripts > * drop unreachable statement > * contrib/pfcp-tool-scripts: adjust tunend_session_est.vty and upf cfg to match up > * upf gtp-u echo: improve loging > * upf gtp-u echo: rx Echo Response messages > * pfcp-tool: always use specific PDR ids for access and core > * nft: batch nftables commands > * osmo-upf: add VTY 'gtp-echo' command > > [ Max ] > * Set working directory in systemd service file > * ctrl: take both address and port from vty config > * .deb/.rpm: add osmocom user during package install > > [ Vadim Yanitskiy ] > * update git URLs (git -> https; gitea) > * contrib/jenkins.sh: clone libnftnl and libnftables via git:// > * copyright: fix typo: sysmocom s/s.m.f.c./s.f.m.c./ GmbH > > [ arehbein ] > * osmo-pfcp-tool: Fix call to strerror > * up_session: Silence coverity warning > > [ Andreas Eversberg ] > * Use uniform log format for default config files > > -- Oliver Smith <osmith(a)sysmocom.de> Wed, 11 Dec 2024 16:37:06 +0100 -- - Oliver Smith <osmith(a)sysmocom.de> https://www.sysmocom.de/ ======================================================================= * sysmocom - systems for mobile communications GmbH * Siemensstr. 26a * 10551 Berlin, Germany * Sitz / Registered office: Berlin, HRB 134158 B * Geschaeftsfuehrer / Managing Director: Harald Welte

1 0

RetroNetCall on Sept 4, 2024: Interactive DIVF testing
by Harald Welte 03 Sep '24

03 Sep '24

Dear Osmocom community, we're happy to announce the next incarnation of RetroNetCall[1], the retronetworking oriented spin-off of OsmoDevCall[2]. when: Sept 4, 2024 at 20:00 CEST where: https://osmocom.org/RetroNetCall This time, we won't have a presentation but intead a joint, collaborative session where we're analyzing and debugging any potentially remaining (or new?) issues with divf.retronetworking.org, our central soft-switch of the OCTOI community TDMoIP network. Participants are invited to try making certain calls and we will look at logs/traces and see what we can fix or improve. This meeting will have the following schedule: 20:00 meet + greet 20:10 presentation as outlined above 21:00 unstructured supplementary social event [3] Attendance is free of charge and open to anyone with an interest in Osmocom or open source cellular technologies. More information about RetroNetCall, including the schedule for further upcoming events can be found at https://osmocom.org/projects/retronetworking/wiki/RetroNetCall Looking forward to meeting you soon! Best regards, Harald [1] https://osmocom.org/projects/retronetworking/wiki/RetroNetCall [2] https://osmocom.org/projects/osmo-dev-con/wiki/OsmoDevCall [3] this is how we started to call the "unstructured" part of osmocom developer conferences in the past, basically where anyone can talk about anything, no formal schedule or structure. -- - Harald Welte <laforge(a)osmocom.org> http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6)

1 0

OsmoDevCall 2024-08-21: TCH Rx error flags
by Harald Welte 22 Aug '24

22 Aug '24

Dear Osmocom community, we're happy to announce the next incarnation of OsmoDevCall. when: August 21, 2024 at 20:00 CEST where: https://osmocom.org/OsmoDevCall (Big Blue Button) This time, @falconia will be presenting on TCH Rx error flags This meeting will have the following schedule: 20:00 meet + greet 20:10 topic as outlined above 21:00 unstructured supplementary social event [*] Attendance is free of charge and open to anyone with an interest in Osmocom or open source cellular technologies. More information about OsmoDevCall, including the schedule for further upcoming events can be found at https://osmocom.org/projects/osmo-dev-con/wiki/OsmoDevCall Looking forward to meeting you soon! Best regards, Harald [*] this is how we started to call the "unstructured" part of osmocom developer conferences in the past, basically where anyone can talk about anything, no formal schedule or structure. -- - Harald Welte <laforge(a)osmocom.org> http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6)

1 0

RetroNetCall on Aug 8, 2024: classic PCM30 trunks with CAS signaling
by Harald Welte 10 Aug '24

10 Aug '24

Dear Osmocom community, we're happy to announce the next incarnation of RetroNetCall[1], the retronetworking oriented spin-off of OsmoDevCall[2]. when: Aug 8, 2024 at 20:00 CEST where: https://osmocom.org/RetroNetCall This time, @laforge will be presenting on *classic PCM30 trunks with channel-associated signaling* followed by a discussion how to potentially implement this using the icE1usb (See also: #6526 [4]). This meeting will have the following schedule: 20:00 meet + greet 20:10 presentation as outlined above 21:00 unstructured supplementary social event [3] Attendance is free of charge and open to anyone with an interest in Osmocom or open source cellular technologies. More information about RetroNetCall, including the schedule for further upcoming events can be found at https://osmocom.org/projects/retronetworking/wiki/RetroNetCall Looking forward to meeting you soon! Best regards, Harald [1] https://osmocom.org/projects/retronetworking/wiki/RetroNetCall [2] https://osmocom.org/projects/osmo-dev-con/wiki/OsmoDevCall [3] this is how we started to call the "unstructured" part of osmocom developer conferences in the past, basically where anyone can talk about anything, no formal schedule or structure. [4] https://osmocom.org/issues/6526 -- - Harald Welte <laforge(a)osmocom.org> http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6)

1 0

RetroNetCall on Aug 7, 2024: classic PCM30 trunks with CAS signaling
by Harald Welte 10 Aug '24

10 Aug '24

[My apologies, I misread the calendar. It's August 7, not August 8] Dear Osmocom community, we're happy to announce the next incarnation of RetroNetCall[1], the retronetworking oriented spin-off of OsmoDevCall[2]. when: Aug 7, 2024 at 20:00 CEST where: https://osmocom.org/RetroNetCall This time, @laforge will be presenting on *classic PCM30 trunks with channel-associated signaling* followed by a discussion how to potentially implement this using the icE1usb (See also: #6526 [4]). This meeting will have the following schedule: 20:00 meet + greet 20:10 presentation as outlined above 21:00 unstructured supplementary social event [3] Attendance is free of charge and open to anyone with an interest in Osmocom or open source cellular technologies. More information about RetroNetCall, including the schedule for further upcoming events can be found at https://osmocom.org/projects/retronetworking/wiki/RetroNetCall Looking forward to meeting you soon! Best regards, Harald [1] https://osmocom.org/projects/retronetworking/wiki/RetroNetCall [2] https://osmocom.org/projects/osmo-dev-con/wiki/OsmoDevCall [3] this is how we started to call the "unstructured" part of osmocom developer conferences in the past, basically where anyone can talk about anything, no formal schedule or structure. [4] https://osmocom.org/issues/6526 -- - Harald Welte <laforge(a)osmocom.org> http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6)

1 0

RetroNetCall on Jun 5, 2024: Nokia TCSM2 Initial examination
by Harald Welte 05 Jun '24

05 Jun '24

Dear Osmocom community, we're happy to announce the next incarnation of RetroNetCall[1], the retronetworking oriented spin-off of OsmoDevCall[2]. when: Jun 5, 2024 at 20:00 CEST where: https://osmocom.org/RetroNetCall This time, @falconia will be presenting on Nokia TCSM2, a bank of TRAUs with E1 interfaces: Part 1, initial examination of the hardware This meeting will have the following schedule: 20:00 meet + greet 20:10 presentation as outlined above 21:00 unstructured supplementary social event [3] Attendance is free of charge and open to anyone with an interest in Osmocom or open source cellular technologies. More information about RetroNetCall, including the schedule for further upcoming events can be found at https://osmocom.org/projects/retronetworking/wiki/RetroNetCall Looking forward to meeting you soon! Best regards, Harald [1] https://osmocom.org/projects/retronetworking/wiki/RetroNetCall [2] https://osmocom.org/projects/osmo-dev-con/wiki/OsmoDevCall [3] this is how we started to call the "unstructured" part of osmocom developer conferences in the past, basically where anyone can talk about anything, no formal schedule or structure. -- - Harald Welte <laforge(a)osmocom.org> http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6)

1 0

RetroNetCall on Mar 6, 2024: Telefax G4 protocol trace decoding
by Harald Welte 04 Mar '24

04 Mar '24

Dear Osmocom community, we're happy to announce the next incarnation of RetroNetCall[1], the retronetworking oriented spin-off of OsmoDevCall[2]. when: Mar 6, 2024 at 20:00 CET where: https://osmocom.org/RetroNetCall This time, @laforge will be presenting on Decoding of Telefax G4 protocol traces. We'll look into the ITU-specs of Group 4 Facsimile Service as well as at an actual B-channel protocol trace taken a few days ago. This meeting will have the following schedule: 20:00 meet + greet 20:10 presentation as outlined above 21:00 unstructured supplementary social event [3] Attendance is free of charge and open to anyone with an interest in Osmocom or open source cellular technologies. More information about RetroNetCall, including the schedule for further upcoming events can be found at https://osmocom.org/projects/retronetworking/wiki/RetroNetCall Looking forward to meeting you soon! Best regards, Harald [1] https://osmocom.org/projects/retronetworking/wiki/RetroNetCall [2] https://osmocom.org/projects/osmo-dev-con/wiki/OsmoDevCall [3] this is how we started to call the "unstructured" part of osmocom developer conferences in the past, basically where anyone can talk about anything, no formal schedule or structure. -- - Harald Welte <laforge(a)osmocom.org> http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6)

1 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

osmocom-announce