<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
  xmlns:content="http://purl.org/rss/1.0/modules/content/"
  xmlns:dc="http://purl.org/dc/elements/1.1/"
  xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd"
  xmlns:trackback="http://madskills.com/public/xml/rss/module/trackback/">
  <channel>
    <title>Chaos Computer Club - OsmoDevCon 2024 (opus)</title>
    <link>https://media.ccc.de/c/osmodevcon2024</link>
    <description> This feed contains all events from osmodevcon2024 as opus</description>
    <copyright>see video outro</copyright>
    <lastBuildDate>Thu, 23 Jan 2025 18:44:52 -0000</lastBuildDate>
    <image>
      <url>https://static.media.ccc.de/media/conferences/osmodevcon/2024/logo.png</url>
      <title>Chaos Computer Club - OsmoDevCon 2024 (opus)</title>
      <link>https://media.ccc.de/c/osmodevcon2024</link>
    </image>
    <item>
      <title>First impression of eUPF (osmodevcon2024)</title>
      <link>https://media.ccc.de/v/osmodevcon2024-202-first-impression-of-eupf</link>
      <description>[eUPF](https://github.com/edgecomllc/eupf) is a rather new implementation of a 3GPP User Plane Function. It is implemented in go and uses eBPF and AF_XDP in order to perform all the GTP-U handling inside the Linux kernel.

This talk is about the first impression from setting it up (in combination with open5gs)
about this event: https://pretalx.sysmocom.de/osmodevcon2024/talk/SWEM3V/
</description>
      <enclosure url="https://cdn.media.ccc.de/events/osmodevcon/2024/opus/osmodevcon2024-202-eng-First_impression_of_eUPF_opus.opus"
        length="22020096"
        type="audio/opus"/>
      <pubDate>Sun, 05 May 2024 15:15:00 +0200</pubDate>
      <guid isPermaLink="true">https://cdn.media.ccc.de/events/osmodevcon/2024/opus/osmodevcon2024-202-eng-First_impression_of_eUPF_opus.opus?1717839963</guid>
      <dc:identifier>026ae717-700a-50c9-b24f-f430ccead662</dc:identifier>
      <dc:date>2024-05-05T15:15:00+02:00</dc:date>
      <itunes:author>Neels Hofmeyr</itunes:author>
      <itunes:explicit>No</itunes:explicit>
      <itunes:keywords>osmodevcon2024, 202, 2024, osmodevcon2024, osmocom</itunes:keywords>
      <itunes:summary>[eUPF](https://github.com/edgecomllc/eupf) is a rather new implementation of a 3GPP User Plane Function. It is implemented in go and uses eBPF and AF_XDP in order to perform all the GTP-U handling inside the Linux kernel.

This talk is about the first impression from setting it up (in combination with open5gs)
about this event: https://pretalx.sysmocom.de/osmodevcon2024/talk/SWEM3V/
</itunes:summary>
      <itunes:duration>00:33:13</itunes:duration>
    </item>
    <item>
      <title>GPRS support in osmocom-bb (osmodevcon2024)</title>
      <link>https://media.ccc.de/v/osmodevcon2024-198-gprs-support-in-osmocom-bb</link>
      <description>The sysmocom team has been working on implementing an open source GPRS modem for DARC on behalf of a grant by ARDC. This talk will present the current state of the implementation and demonstrate how to use it.
about this event: https://pretalx.sysmocom.de/osmodevcon2024/talk/SAX3FE/
</description>
      <enclosure url="https://cdn.media.ccc.de/events/osmodevcon/2024/opus/osmodevcon2024-198-eng-GPRS_support_in_osmocom-bb_opus.opus"
        length="25165824"
        type="audio/opus"/>
      <pubDate>Fri, 03 May 2024 11:30:00 +0200</pubDate>
      <guid isPermaLink="true">https://cdn.media.ccc.de/events/osmodevcon/2024/opus/osmodevcon2024-198-eng-GPRS_support_in_osmocom-bb_opus.opus?1717411022</guid>
      <dc:identifier>f1c4ffaa-d654-59bf-a36b-386c4bbb8214</dc:identifier>
      <dc:date>2024-05-03T11:30:00+02:00</dc:date>
      <itunes:author>Vadim Yanitskiy, Pau Espin Pedrol</itunes:author>
      <itunes:explicit>No</itunes:explicit>
      <itunes:keywords>osmodevcon2024, 198, 2024, osmodevcon2024, osmocom</itunes:keywords>
      <itunes:summary>The sysmocom team has been working on implementing an open source GPRS modem for DARC on behalf of a grant by ARDC. This talk will present the current state of the implementation and demonstrate how to use it.
about this event: https://pretalx.sysmocom.de/osmodevcon2024/talk/SAX3FE/
</itunes:summary>
      <itunes:duration>00:36:16</itunes:duration>
    </item>
    <item>
      <title>Introduction to XDP, eBPF and AF_XDP (osmodevcon2024)</title>
      <link>https://media.ccc.de/v/osmodevcon2024-204-introduction-to-xdp-ebpf-and-afxdp</link>
      <description>This talk provides a generic introduction to a set of modern Linux kernel technologies:

* [eBPF](https://ebpf.io/what-is-ebpf/) (extended Berkeley Packet Filter) is a kind of virtual machine that runs sandboxed programs inside the Linux kernel.
* [XDP](https://docs.cilium.io/en/latest/bpf/progtypes/#xdp) (eXpress Data Path) is a framework for eBPF that enables high-performance programmable packet processing in the Linux kernel
* [AF_XDP](https://www.kernel.org/doc/html/next/networking/af_xdp.html) is an *address family* that is optimized for high-performance packet processing. It allows in-kernel XDP eBPF programs to efficiently pass packets to userspace via memory-mapped ring buffers.

The talk will provide a high-level overview. It should provide some basics before the other/later talks on bpftrace and eUPF.
about this event: https://pretalx.sysmocom.de/osmodevcon2024/talk/RBXC3V/
</description>
      <enclosure url="https://cdn.media.ccc.de/events/osmodevcon/2024/opus/osmodevcon2024-204-eng-Introduction_to_XDP_eBPF_and_AF_XDP_opus.opus"
        length="54525952"
        type="audio/opus"/>
      <pubDate>Sun, 05 May 2024 11:00:00 +0200</pubDate>
      <guid isPermaLink="true">https://cdn.media.ccc.de/events/osmodevcon/2024/opus/osmodevcon2024-204-eng-Introduction_to_XDP_eBPF_and_AF_XDP_opus.opus?1717402843</guid>
      <dc:identifier>bfce510e-1dab-50b3-972b-8f59d50ce150</dc:identifier>
      <dc:date>2024-05-05T11:00:00+02:00</dc:date>
      <itunes:author>Harald Welte (sysmocom)</itunes:author>
      <itunes:explicit>No</itunes:explicit>
      <itunes:keywords>osmodevcon2024, 204, 2024, osmodevcon2024, osmocom</itunes:keywords>
      <itunes:summary>This talk provides a generic introduction to a set of modern Linux kernel technologies:

* [eBPF](https://ebpf.io/what-is-ebpf/) (extended Berkeley Packet Filter) is a kind of virtual machine that runs sandboxed programs inside the Linux kernel.
* [XDP](https://docs.cilium.io/en/latest/bpf/progtypes/#xdp) (eXpress Data Path) is a framework for eBPF that enables high-performance programmable packet processing in the Linux kernel
* [AF_XDP](https://www.kernel.org/doc/html/next/networking/af_xdp.html) is an *address family* that is optimized for high-performance packet processing. It allows in-kernel XDP eBPF programs to efficiently pass packets to userspace via memory-mapped ring buffers.

The talk will provide a high-level overview. It should provide some basics before the other/later talks on bpftrace and eUPF.
about this event: https://pretalx.sysmocom.de/osmodevcon2024/talk/RBXC3V/
</itunes:summary>
      <itunes:duration>01:12:50</itunes:duration>
    </item>
    <item>
      <title>Sky130 and TinyTapeout : A quick intro (osmodevcon2024)</title>
      <link>https://media.ccc.de/v/osmodevcon2024-215-sky130-and-tinytapeout-a-quick-intro</link>
      <description>Just a few words about the Sky130 Open PDK and associated tooling as well as the related TinyTapeout program
about this event: https://pretalx.sysmocom.de/osmodevcon2024/talk/TUFJPD/
</description>
      <enclosure url="https://cdn.media.ccc.de/events/osmodevcon/2024/opus/osmodevcon2024-215-eng-Sky130_and_TinyTapeout_A_quick_intro_opus.opus"
        length="27262976"
        type="audio/opus"/>
      <pubDate>Sat, 04 May 2024 17:45:00 +0200</pubDate>
      <guid isPermaLink="true">https://cdn.media.ccc.de/events/osmodevcon/2024/opus/osmodevcon2024-215-eng-Sky130_and_TinyTapeout_A_quick_intro_opus.opus?1717381322</guid>
      <dc:identifier>8121c110-2fd4-5cdc-86f0-77540acdd318</dc:identifier>
      <dc:date>2024-05-04T17:45:00+02:00</dc:date>
      <itunes:author>Sylvain Munaut</itunes:author>
      <itunes:explicit>No</itunes:explicit>
      <itunes:keywords>osmodevcon2024, 215, 2024, osmodevcon2024, osmocom</itunes:keywords>
      <itunes:summary>Just a few words about the Sky130 Open PDK and associated tooling as well as the related TinyTapeout program
about this event: https://pretalx.sysmocom.de/osmodevcon2024/talk/TUFJPD/
</itunes:summary>
      <itunes:duration>00:38:43</itunes:duration>
    </item>
    <item>
      <title>Your favorite Osmocom related productivity tips and tools (osmodevcon2024)</title>
      <link>https://media.ccc.de/v/osmodevcon2024-201-your-favorite-osmocom-related-productivity-tips-and-tools</link>
      <description>Everybody can quickly talk about / present their favorite tooling and other tips and tricks that make a good development workflow for working on Osmocom related software.
about this event: https://pretalx.sysmocom.de/osmodevcon2024/talk/DUR7GS/
</description>
      <enclosure url="https://cdn.media.ccc.de/events/osmodevcon/2024/opus/osmodevcon2024-201-eng-Your_favorite_Osmocom_related_productivity_tips_and_tools_opus.opus"
        length="38797312"
        type="audio/opus"/>
      <pubDate>Mon, 06 May 2024 10:15:00 +0200</pubDate>
      <guid isPermaLink="true">https://cdn.media.ccc.de/events/osmodevcon/2024/opus/osmodevcon2024-201-eng-Your_favorite_Osmocom_related_productivity_tips_and_tools_opus.opus?1717421641</guid>
      <dc:identifier>a47cab26-418f-5b11-9f47-90fe346185fb</dc:identifier>
      <dc:date>2024-05-06T10:15:00+02:00</dc:date>
      <itunes:author>Oliver Smith</itunes:author>
      <itunes:explicit>No</itunes:explicit>
      <itunes:keywords>osmodevcon2024, 201, 2024, osmodevcon2024, osmocom</itunes:keywords>
      <itunes:summary>Everybody can quickly talk about / present their favorite tooling and other tips and tricks that make a good development workflow for working on Osmocom related software.
about this event: https://pretalx.sysmocom.de/osmodevcon2024/talk/DUR7GS/
</itunes:summary>
      <itunes:duration>00:55:38</itunes:duration>
    </item>
    <item>
      <title>Digital Telecommunication in HF band - WWWAN - World-Wide Wireless Area Network (osmodevcon2024)</title>
      <link>https://media.ccc.de/v/osmodevcon2024-218-digital-telecommunication-in-hf-band-wwwan-world-wide-wireless-area-network</link>
      <description>We at Rhizomatica are running the High-frequency Emergency and Rural Multimedia Exchange System (HERMES) already for some years, based on P2P connections in a star topology, using UUCP. Now it is time to move forward. This workshop is focused on the next generation HERMES network stack, which hopefully will allow for worldwide deployment of the network.

HERMES project provides a software stack (and hardware integration) for very-long distance telecommunication on HF band. Our focus currently are isolated communities (in terms of telecommunication access), especially in Amazon rain forest communities and Central Africa.

Our current setup uses a proprietary P2P HF software-modem (called VARA) and UUCP on top of it, basically for email exchange, and ad-hoc file transfer and remote command execution.

Our next-generation system will use an open-source modem (called Mercury) we are developing, together new upper network layers, which we are still evaluating (for eg., NNCP and Reticulum). We aim to expand the network world wide, for providing accessibility anywhere in the world through HF, and towards this goal, we&#39;ll carry this discussion / workshop for evaluation which would be the best options to take.

We are taking a couple of radios (sBitx v3) for a full chain demonstration, and also a fully functional board (without the enclosure) to donate to anyone who wants to play with HF telecom.
about this event: https://pretalx.sysmocom.de/osmodevcon2024/talk/BBZBGM/
</description>
      <enclosure url="https://cdn.media.ccc.de/events/osmodevcon/2024/opus/osmodevcon2024-218-eng-Digital_Telecommunication_in_HF_band_-_WWWAN_-_World-Wide_Wireless_Area_Network_opus.opus"
        length="39845888"
        type="audio/opus"/>
      <pubDate>Sun, 05 May 2024 19:00:00 +0200</pubDate>
      <guid isPermaLink="true">https://cdn.media.ccc.de/events/osmodevcon/2024/opus/osmodevcon2024-218-eng-Digital_Telecommunication_in_HF_band_-_WWWAN_-_World-Wide_Wireless_Area_Network_opus.opus?1717414744</guid>
      <dc:identifier>f445dedf-233e-5d2e-a753-2e2ebeef4be3</dc:identifier>
      <dc:date>2024-05-05T19:00:00+02:00</dc:date>
      <itunes:author>Rafael Diniz, Keith Whyte</itunes:author>
      <itunes:explicit>No</itunes:explicit>
      <itunes:keywords>osmodevcon2024, 218, 2024, osmodevcon2024, osmocom</itunes:keywords>
      <itunes:summary>We at Rhizomatica are running the High-frequency Emergency and Rural Multimedia Exchange System (HERMES) already for some years, based on P2P connections in a star topology, using UUCP. Now it is time to move forward. This workshop is focused on the next generation HERMES network stack, which hopefully will allow for worldwide deployment of the network.

HERMES project provides a software stack (and hardware integration) for very-long distance telecommunication on HF band. Our focus currently are isolated communities (in terms of telecommunication access), especially in Amazon rain forest communities and Central Africa.

Our current setup uses a proprietary P2P HF software-modem (called VARA) and UUCP on top of it, basically for email exchange, and ad-hoc file transfer and remote command execution.

Our next-generation system will use an open-source modem (called Mercury) we are developing, together new upper network layers, which we are still evaluating (for eg., NNCP and Reticulum). We aim to expand the network world wide, for providing accessibility anywhere in the world through HF, and towards this goal, we&#39;ll carry this discussion / workshop for evaluation which would be the best options to take.

We are taking a couple of radios (sBitx v3) for a full chain demonstration, and also a fully functional board (without the enclosure) to donate to anyone who wants to play with HF telecom.
about this event: https://pretalx.sysmocom.de/osmodevcon2024/talk/BBZBGM/
</itunes:summary>
      <itunes:duration>01:01:47</itunes:duration>
    </item>
    <item>
      <title>JESD204B : Interfacing to modern ADC/DAC with LiteX (osmodevcon2024)</title>
      <link>https://media.ccc.de/v/osmodevcon2024-165-jesd204b-interfacing-to-modern-adc-dac-with-litex</link>
      <description>JESD204B is a pretty common interface to higher speed ADC/DAC used in software defined radio.
I&#39;d like to take a moment to explain how it works and how to use the open-hardware LiteJESD204B core to interface to them.
about this event: https://pretalx.sysmocom.de/osmodevcon2024/talk/DQRNVM/
</description>
      <enclosure url="https://cdn.media.ccc.de/events/osmodevcon/2024/opus/osmodevcon2024-165-eng-JESD204B_Interfacing_to_modern_ADC_DAC_with_LiteX_opus.opus"
        length="23068672"
        type="audio/opus"/>
      <pubDate>Sat, 04 May 2024 15:40:00 +0200</pubDate>
      <guid isPermaLink="true">https://cdn.media.ccc.de/events/osmodevcon/2024/opus/osmodevcon2024-165-eng-JESD204B_Interfacing_to_modern_ADC_DAC_with_LiteX_opus.opus?1717372904</guid>
      <dc:identifier>3ee2c456-1073-5e00-9ca5-e7b10d84e865</dc:identifier>
      <dc:date>2024-05-04T15:40:00+02:00</dc:date>
      <itunes:author>Sylvain Munaut</itunes:author>
      <itunes:explicit>No</itunes:explicit>
      <itunes:keywords>osmodevcon2024, 165, 2024, osmodevcon2024, osmocom</itunes:keywords>
      <itunes:summary>JESD204B is a pretty common interface to higher speed ADC/DAC used in software defined radio.
I&#39;d like to take a moment to explain how it works and how to use the open-hardware LiteJESD204B core to interface to them.
about this event: https://pretalx.sysmocom.de/osmodevcon2024/talk/DQRNVM/
</itunes:summary>
      <itunes:duration>00:33:08</itunes:duration>
    </item>
    <item>
      <title>GlobalPlatform in USIM and eUICC (osmodevcon2024)</title>
      <link>https://media.ccc.de/v/osmodevcon2024-173-globalplatform-in-usim-and-euicc</link>
      <description>The GlobalPlatform Card Specification and its many amendments play a significant role in most real-world USIM/ISIM, and even more so in eUICC.

The talk will try to provide an overview of what GlobalPlatform does in the telecommunications context.  

Topics include:
* security domains
* key loading
* card and application life cycle
* loading and installation of applications
* Secure Channel Protocols SCP02, SCP03
about this event: https://pretalx.sysmocom.de/osmodevcon2024/talk/DYGQXN/
</description>
      <enclosure url="https://cdn.media.ccc.de/events/osmodevcon/2024/opus/osmodevcon2024-173-eng-GlobalPlatform_in_USIM_and_eUICC_opus.opus"
        length="25165824"
        type="audio/opus"/>
      <pubDate>Sat, 04 May 2024 10:15:00 +0200</pubDate>
      <guid isPermaLink="true">https://cdn.media.ccc.de/events/osmodevcon/2024/opus/osmodevcon2024-173-eng-GlobalPlatform_in_USIM_and_eUICC_opus.opus?1717351243</guid>
      <dc:identifier>6a57657c-4517-5d08-b185-c2d9107712db</dc:identifier>
      <dc:date>2024-05-04T10:15:00+02:00</dc:date>
      <itunes:author>Harald Welte (sysmocom)</itunes:author>
      <itunes:explicit>No</itunes:explicit>
      <itunes:keywords>osmodevcon2024, 173, 2024, osmodevcon2024, osmocom</itunes:keywords>
      <itunes:summary>The GlobalPlatform Card Specification and its many amendments play a significant role in most real-world USIM/ISIM, and even more so in eUICC.

The talk will try to provide an overview of what GlobalPlatform does in the telecommunications context.  

Topics include:
* security domains
* key loading
* card and application life cycle
* loading and installation of applications
* Secure Channel Protocols SCP02, SCP03
about this event: https://pretalx.sysmocom.de/osmodevcon2024/talk/DYGQXN/
</itunes:summary>
      <itunes:duration>00:34:19</itunes:duration>
    </item>
    <item>
      <title>open5gs status: recent, current and future developments (osmodevcon2024)</title>
      <link>https://media.ccc.de/v/osmodevcon2024-211-open5gs-status-recent-current-and-future-developments</link>
      <description>The talk will provide an overview over
* recent developments in open5gs (2023)
* current areas of work
* outlook / roadmap
about this event: https://pretalx.sysmocom.de/osmodevcon2024/talk/TKCAPQ/
</description>
      <enclosure url="https://cdn.media.ccc.de/events/osmodevcon/2024/opus/osmodevcon2024-211-eng-open5gs_status_recent_current_and_future_developments_opus.opus"
        length="16777216"
        type="audio/opus"/>
      <pubDate>Fri, 03 May 2024 17:45:00 +0200</pubDate>
      <guid isPermaLink="true">https://cdn.media.ccc.de/events/osmodevcon/2024/opus/osmodevcon2024-211-eng-open5gs_status_recent_current_and_future_developments_opus.opus?1717016042</guid>
      <dc:identifier>17e2fc5b-bf9f-58e4-a0ab-c950b37babc7</dc:identifier>
      <dc:date>2024-05-03T17:45:00+02:00</dc:date>
      <itunes:author>Sukchan Lee</itunes:author>
      <itunes:explicit>No</itunes:explicit>
      <itunes:keywords>osmodevcon2024, 211, 2024, osmodevcon2024, osmocom</itunes:keywords>
      <itunes:summary>The talk will provide an overview over
* recent developments in open5gs (2023)
* current areas of work
* outlook / roadmap
about this event: https://pretalx.sysmocom.de/osmodevcon2024/talk/TKCAPQ/
</itunes:summary>
      <itunes:duration>00:27:07</itunes:duration>
    </item>
    <item>
      <title>Operating Open Source Mobile Networks at Scale (osmodevcon2024)</title>
      <link>https://media.ccc.de/v/osmodevcon2024-213-operating-open-source-mobile-networks-at-scale</link>
      <description>TBD
about this event: https://pretalx.sysmocom.de/osmodevcon2024/talk/CGVEVM/
</description>
      <enclosure url="https://cdn.media.ccc.de/events/osmodevcon/2024/opus/osmodevcon2024-213-eng-Operating_Open_Source_Mobile_Networks_at_Scale_opus.opus"
        length="29360128"
        type="audio/opus"/>
      <pubDate>Fri, 03 May 2024 12:00:00 +0200</pubDate>
      <guid isPermaLink="true">https://cdn.media.ccc.de/events/osmodevcon/2024/opus/osmodevcon2024-213-eng-Operating_Open_Source_Mobile_Networks_at_Scale_opus.opus?1717324202</guid>
      <dc:identifier>cc04bb45-f6b5-5286-971f-c4dd2aa138f8</dc:identifier>
      <dc:date>2024-05-03T12:00:00+02:00</dc:date>
      <itunes:author>Michael Iedema</itunes:author>
      <itunes:explicit>No</itunes:explicit>
      <itunes:keywords>osmodevcon2024, 213, 2024, osmodevcon2024, osmocom</itunes:keywords>
      <itunes:summary>TBD
about this event: https://pretalx.sysmocom.de/osmodevcon2024/talk/CGVEVM/
</itunes:summary>
      <itunes:duration>00:43:33</itunes:duration>
    </item>
    <item>
      <title>High-performance I/O using io_uring via osmo_io (osmodevcon2024)</title>
      <link>https://media.ccc.de/v/osmodevcon2024-209-high-performance-i-o-using-iouring-via-osmoio</link>
      <description>Traditional socket I/O via `read/write/recvfrom/sendto/recvmsg/sendmsg` and friends creates a very high system call load.  A highly-loaded osmo-bsc spends most of its time in syscall entry and syscall exit.

`io_uring` is a modern Linux kernel mechanism to avoid this syscall overhead. We have introduced the `osmo_io`API to libosmocore as a generic back-end for non-blocking/asynchronous I/O and a back-end for our classic `osmo_fd` / `poll` approach as well as a new backend for `io_uring`.

The talk will cover
* a very basic io_uring introduction
* a description of the osmo_io API
* the difficulties porting from osmo_fd to osmo_io
* status of porting various sub-systems over to osmo_io
about this event: https://pretalx.sysmocom.de/osmodevcon2024/talk/ZBJWUP/
</description>
      <enclosure url="https://cdn.media.ccc.de/events/osmodevcon/2024/opus/osmodevcon2024-209-eng-High-performance_I_O_using_io_uring_via_osmo_io_opus.opus"
        length="23068672"
        type="audio/opus"/>
      <pubDate>Fri, 03 May 2024 17:00:00 +0200</pubDate>
      <guid isPermaLink="true">https://cdn.media.ccc.de/events/osmodevcon/2024/opus/osmodevcon2024-209-eng-High-performance_I_O_using_io_uring_via_osmo_io_opus.opus?1717341693</guid>
      <dc:identifier>bcc6dea4-f8d1-5c14-b5fd-40dae9eae0fa</dc:identifier>
      <dc:date>2024-05-03T17:00:00+02:00</dc:date>
      <itunes:author>Andreas Eversberg, Harald Welte (sysmocom)</itunes:author>
      <itunes:explicit>No</itunes:explicit>
      <itunes:keywords>osmodevcon2024, 209, 2024, osmodevcon2024, osmocom</itunes:keywords>
      <itunes:summary>Traditional socket I/O via `read/write/recvfrom/sendto/recvmsg/sendmsg` and friends creates a very high system call load.  A highly-loaded osmo-bsc spends most of its time in syscall entry and syscall exit.

`io_uring` is a modern Linux kernel mechanism to avoid this syscall overhead. We have introduced the `osmo_io`API to libosmocore as a generic back-end for non-blocking/asynchronous I/O and a back-end for our classic `osmo_fd` / `poll` approach as well as a new backend for `io_uring`.

The talk will cover
* a very basic io_uring introduction
* a description of the osmo_io API
* the difficulties porting from osmo_fd to osmo_io
* status of porting various sub-systems over to osmo_io
about this event: https://pretalx.sysmocom.de/osmodevcon2024/talk/ZBJWUP/
</itunes:summary>
      <itunes:duration>00:36:15</itunes:duration>
    </item>
    <item>
      <title>OsmoPCU: past, present and future (osmodevcon2024)</title>
      <link>https://media.ccc.de/v/osmodevcon2024-206-osmopcu-past-present-and-future</link>
      <description>Summary of the architectural changes done over osmo-pcu code base over last years, what we accomplished and possible next steps.
about this event: https://pretalx.sysmocom.de/osmodevcon2024/talk/KLWCKH/
</description>
      <enclosure url="https://cdn.media.ccc.de/events/osmodevcon/2024/opus/osmodevcon2024-206-eng-OsmoPCU_past_present_and_future_opus.opus"
        length="26214400"
        type="audio/opus"/>
      <pubDate>Fri, 03 May 2024 15:45:00 +0200</pubDate>
      <guid isPermaLink="true">https://cdn.media.ccc.de/events/osmodevcon/2024/opus/osmodevcon2024-206-eng-OsmoPCU_past_present_and_future_opus.opus?1717335463</guid>
      <dc:identifier>e4dee8ed-e146-5b0d-a6df-4a9a10d2af56</dc:identifier>
      <dc:date>2024-05-03T15:45:00+02:00</dc:date>
      <itunes:author>Pau Espin Pedrol</itunes:author>
      <itunes:explicit>No</itunes:explicit>
      <itunes:keywords>osmodevcon2024, 206, 2024, osmodevcon2024, osmocom</itunes:keywords>
      <itunes:summary>Summary of the architectural changes done over osmo-pcu code base over last years, what we accomplished and possible next steps.
about this event: https://pretalx.sysmocom.de/osmodevcon2024/talk/KLWCKH/
</itunes:summary>
      <itunes:duration>00:38:41</itunes:duration>
    </item>
    <item>
      <title>2.024 G (osmodevcon2024)</title>
      <link>https://media.ccc.de/v/osmodevcon2024-196-2-024-g</link>
      <description>It&#39;s the year **2024**, so that&#39;s 2.024K (or G for *grand*), right?

What does it mean to use 2.024 G data (aka EDGE 2.5G) in the year 2024?

Our Osmocom 2G Data stack seems pretty mature at this point. 
Within the limits of the technology one can still use a remote ssh session, download email, do &quot;instant messaging&quot;, including sending photos and short audio messages.

All this works fine with one or two UE connected on a lab desk to a TRX configured for *high* capacity, 

However, introduce some TCH &quot;stealing&quot; the PDCH, some several 100&#39;s of UE (even just trying to attach) and some non optimal RF conditions and the capacity of the TRX is severely reduced. 

In these conditions, modern Android phones will saturate the TRX&#39; capacity even with only their DNS lookups for &quot;connectivity.google.com&quot; - Maybe somewhat ironically?

I&#39;ve considered various steps to try to mitigate this situation.

A common goto is to interfere with DNS, but this is disastrous. 

* In some cases, if Android cannot reach 8.8.8.8, regardless of what the network said to use for DNS, it will simply try again.  - Of course, that can&#39;t be right. right?
* If connectivity.google.com doesn&#39;t resolve, well that can&#39;t be right either, so try again. 
* If connectivity.google.com resolves, then HTTP GET /generate_204, and if this doesn&#39;t work, report to upper layer that there is no &quot;Internet&quot; and... you guessed it, try again.

So we have to allow these things, which in itself is OK, as once the 204 is received, the phone will (probably) leave that alone, at least for a few minutes, but what comes next is all of what one might imagine is in the various phones, checks for system updates, app stores updates, uploading all the surveillance info that the google &quot;services&quot; cached while disconnected, and *who knows what else. 

  *those running HTTP toolkit ;-)

And that&#39;s before we even consider whatever is installed in &quot;user space&quot; (if such a thing can really be considered to exist on an Android device) starts.

My current solution to this is to allow a limited amount of services, and then use netfilter&#39;s TARPIT module to get the phones to back off from everything else.

Let&#39;s look a little a that, and maybe discuss what other optimizations could be done - For example netfilter scheduling and queues at the GGSN&#39;s IP interface. How about limiting the DL bandwidth per IP at this point? Give ACKs and short packets priority? We could limit the bandwidth here to the TRX capacity, but what if there is more than one SGSN, maybe an unknown number of SGSN (and TRX) connected at any one time?

Now I&#39;ve pretty much said everything I had to say in this description! But if would be good to discuss it, you all probably have some ideas!
about this event: https://pretalx.sysmocom.de/osmodevcon2024/talk/L3BXTR/
</description>
      <enclosure url="https://cdn.media.ccc.de/events/osmodevcon/2024/opus/osmodevcon2024-196-eng-2024_G_opus.opus"
        length="24117248"
        type="audio/opus"/>
      <pubDate>Fri, 03 May 2024 14:30:00 +0200</pubDate>
      <guid isPermaLink="true">https://cdn.media.ccc.de/events/osmodevcon/2024/opus/osmodevcon2024-196-eng-2024_G_opus.opus?1717119344</guid>
      <dc:identifier>367ac5aa-8dbe-50d8-b62c-65555ebcaa95</dc:identifier>
      <dc:date>2024-05-03T14:30:00+02:00</dc:date>
      <itunes:author>Keith Whyte</itunes:author>
      <itunes:explicit>No</itunes:explicit>
      <itunes:keywords>osmodevcon2024, 196, 2024, osmodevcon2024, osmocom</itunes:keywords>
      <itunes:summary>It&#39;s the year **2024**, so that&#39;s 2.024K (or G for *grand*), right?

What does it mean to use 2.024 G data (aka EDGE 2.5G) in the year 2024?

Our Osmocom 2G Data stack seems pretty mature at this point. 
Within the limits of the technology one can still use a remote ssh session, download email, do &quot;instant messaging&quot;, including sending photos and short audio messages.

All this works fine with one or two UE connected on a lab desk to a TRX configured for *high* capacity, 

However, introduce some TCH &quot;stealing&quot; the PDCH, some several 100&#39;s of UE (even just trying to attach) and some non optimal RF conditions and the capacity of the TRX is severely reduced. 

In these conditions, modern Android phones will saturate the TRX&#39; capacity even with only their DNS lookups for &quot;connectivity.google.com&quot; - Maybe somewhat ironically?

I&#39;ve considered various steps to try to mitigate this situation.

A common goto is to interfere with DNS, but this is disastrous. 

* In some cases, if Android cannot reach 8.8.8.8, regardless of what the network said to use for DNS, it will simply try again.  - Of course, that can&#39;t be right. right?
* If connectivity.google.com doesn&#39;t resolve, well that can&#39;t be right either, so try again. 
* If connectivity.google.com resolves, then HTTP GET /generate_204, and if this doesn&#39;t work, report to upper layer that there is no &quot;Internet&quot; and... you guessed it, try again.

So we have to allow these things, which in itself is OK, as once the 204 is received, the phone will (probably) leave that alone, at least for a few minutes, but what comes next is all of what one might imagine is in the various phones, checks for system updates, app stores updates, uploading all the surveillance info that the google &quot;services&quot; cached while disconnected, and *who knows what else. 

  *those running HTTP toolkit ;-)

And that&#39;s before we even consider whatever is installed in &quot;user space&quot; (if such a thing can really be considered to exist on an Android device) starts.

My current solution to this is to allow a limited amount of services, and then use netfilter&#39;s TARPIT module to get the phones to back off from everything else.

Let&#39;s look a little a that, and maybe discuss what other optimizations could be done - For example netfilter scheduling and queues at the GGSN&#39;s IP interface. How about limiting the DL bandwidth per IP at this point? Give ACKs and short packets priority? We could limit the bandwidth here to the TRX capacity, but what if there is more than one SGSN, maybe an unknown number of SGSN (and TRX) connected at any one time?

Now I&#39;ve pretty much said everything I had to say in this description! But if would be good to discuss it, you all probably have some ideas!
about this event: https://pretalx.sysmocom.de/osmodevcon2024/talk/L3BXTR/
</itunes:summary>
      <itunes:duration>00:35:33</itunes:duration>
    </item>
    <item>
      <title>Codec resolution: AMR rates in 2G, 3G and SIP (osmodevcon2024)</title>
      <link>https://media.ccc.de/v/osmodevcon2024-193-codec-resolution-amr-rates-in-2g-3g-and-sip</link>
      <description>AMR requires out-of-band negotiation of a set of bitrates.
Let&#39;s take a tour of the various ways AMR rates are represented across our technologies.
How do we, in detail, navigate this perilous landscape to select AMR rates so that call legs match?
about this event: https://pretalx.sysmocom.de/osmodevcon2024/talk/RUHNZU/
</description>
      <enclosure url="https://cdn.media.ccc.de/events/osmodevcon/2024/opus/osmodevcon2024-193-eng-Codec_resolution_AMR_rates_in_2G_3G_and_SIP_opus.opus"
        length="26214400"
        type="audio/opus"/>
      <pubDate>Fri, 03 May 2024 15:15:00 +0200</pubDate>
      <guid isPermaLink="true">https://cdn.media.ccc.de/events/osmodevcon/2024/opus/osmodevcon2024-193-eng-Codec_resolution_AMR_rates_in_2G_3G_and_SIP_opus.opus?1717332482</guid>
      <dc:identifier>759d6e67-4e54-5e2f-8cb8-38f7cea392b7</dc:identifier>
      <dc:date>2024-05-03T15:15:00+02:00</dc:date>
      <itunes:author>Neels Hofmeyr</itunes:author>
      <itunes:explicit>No</itunes:explicit>
      <itunes:keywords>osmodevcon2024, 193, 2024, osmodevcon2024, osmocom</itunes:keywords>
      <itunes:summary>AMR requires out-of-band negotiation of a set of bitrates.
Let&#39;s take a tour of the various ways AMR rates are represented across our technologies.
How do we, in detail, navigate this perilous landscape to select AMR rates so that call legs match?
about this event: https://pretalx.sysmocom.de/osmodevcon2024/talk/RUHNZU/
</itunes:summary>
      <itunes:duration>00:39:51</itunes:duration>
    </item>
    <item>
      <title>Low cost, high speed data acquisition over HDMI (osmodevcon2024)</title>
      <link>https://media.ccc.de/v/osmodevcon2024-200-low-cost-high-speed-data-acquisition-over-hdmi</link>
      <description>Through a reverse-engineering effort it is possible to (ab)use a combination of cheap USB 3.2 HDMI video grabbers based on the Macrosilicon MS2130 in combination with small FPGA dev boards like the Sipeed Tang nano series (both ~10 USD each) to capture arbitrary data by connecting them via an HDMI cable. This can be used as a low cost, high speed logic analyzer, ADC capture, DIY SDR etc.
about this event: https://pretalx.sysmocom.de/osmodevcon2024/talk/UBCQFC/
</description>
      <enclosure url="https://cdn.media.ccc.de/events/osmodevcon/2024/opus/osmodevcon2024-200-eng-Low_cost_high_speed_data_acquisition_over_HDMI_opus.opus"
        length="25165824"
        type="audio/opus"/>
      <pubDate>Sun, 05 May 2024 12:30:00 +0200</pubDate>
      <guid isPermaLink="true">https://cdn.media.ccc.de/events/osmodevcon/2024/opus/osmodevcon2024-200-eng-Low_cost_high_speed_data_acquisition_over_HDMI_opus.opus?1717413824</guid>
      <dc:identifier>690003c5-0b29-5864-ba13-d7587f5e225b</dc:identifier>
      <dc:date>2024-05-05T12:30:00+02:00</dc:date>
      <itunes:author>Steve Markgraf</itunes:author>
      <itunes:explicit>No</itunes:explicit>
      <itunes:keywords>osmodevcon2024, 200, 2024, osmodevcon2024, osmocom</itunes:keywords>
      <itunes:summary>Through a reverse-engineering effort it is possible to (ab)use a combination of cheap USB 3.2 HDMI video grabbers based on the Macrosilicon MS2130 in combination with small FPGA dev boards like the Sipeed Tang nano series (both ~10 USD each) to capture arbitrary data by connecting them via an HDMI cable. This can be used as a low cost, high speed logic analyzer, ADC capture, DIY SDR etc.
about this event: https://pretalx.sysmocom.de/osmodevcon2024/talk/UBCQFC/
</itunes:summary>
      <itunes:duration>00:34:20</itunes:duration>
    </item>
    <item>
      <title>Using bpftrace to analyze osmocom performance (osmodevcon2024)</title>
      <link>https://media.ccc.de/v/osmodevcon2024-203-using-bpftrace-to-analyze-osmocom-performance</link>
      <description>[bpftrace](https://github.com/bpftrace/bpftrace) is a utility that uses the Linux kernel tracing infrastructure (and eBPF) in order to provide tracing capabilities within the kernel, like uprobe, kprobe, tracepoints, etc.  

bpftrace can help us to analyze the performance of [unmodified] Osmocom programs and quickly provide information like, for example:
* Histogram of time spent in a specific system call
* Histogram of any argument or return value of any system call
about this event: https://pretalx.sysmocom.de/osmodevcon2024/talk/SGKKAA/
</description>
      <enclosure url="https://cdn.media.ccc.de/events/osmodevcon/2024/opus/osmodevcon2024-203-eng-Using_bpftrace_to_analyze_osmocom_performance_opus.opus"
        length="20971520"
        type="audio/opus"/>
      <pubDate>Sun, 05 May 2024 11:45:00 +0200</pubDate>
      <guid isPermaLink="true">https://cdn.media.ccc.de/events/osmodevcon/2024/opus/osmodevcon2024-203-eng-Using_bpftrace_to_analyze_osmocom_performance_opus.opus?1717403443</guid>
      <dc:identifier>e2615ac3-ae2f-5389-9577-80289e27e7ba</dc:identifier>
      <dc:date>2024-05-05T11:45:00+02:00</dc:date>
      <itunes:author>Harald Welte (sysmocom)</itunes:author>
      <itunes:explicit>No</itunes:explicit>
      <itunes:keywords>osmodevcon2024, 203, 2024, osmodevcon2024, osmocom</itunes:keywords>
      <itunes:summary>[bpftrace](https://github.com/bpftrace/bpftrace) is a utility that uses the Linux kernel tracing infrastructure (and eBPF) in order to provide tracing capabilities within the kernel, like uprobe, kprobe, tracepoints, etc.  

bpftrace can help us to analyze the performance of [unmodified] Osmocom programs and quickly provide information like, for example:
* Histogram of time spent in a specific system call
* Histogram of any argument or return value of any system call
about this event: https://pretalx.sysmocom.de/osmodevcon2024/talk/SGKKAA/
</itunes:summary>
      <itunes:duration>00:29:21</itunes:duration>
    </item>
    <item>
      <title>osmo-epdg: The osmocom ePDG for VoWiFi (osmodevcon2024)</title>
      <link>https://media.ccc.de/v/osmodevcon2024-179-osmo-epdg-the-osmocom-epdg-for-vowifi</link>
      <description>After working on it on and off during 2023, we finally have a working ePDG in the Osmocom universe.  Let&#39;s have  a look at its internal architecture, how it integrates with other network elements and have a look at a demo and protocol traces.
about this event: https://pretalx.sysmocom.de/osmodevcon2024/talk/YJWERZ/
</description>
      <enclosure url="https://cdn.media.ccc.de/events/osmodevcon/2024/opus/osmodevcon2024-179-eng-osmo-epdg_The_osmocom_ePDG_for_VoWiFi_opus.opus"
        length="30408704"
        type="audio/opus"/>
      <pubDate>Sun, 05 May 2024 10:15:00 +0200</pubDate>
      <guid isPermaLink="true">https://cdn.media.ccc.de/events/osmodevcon/2024/opus/osmodevcon2024-179-eng-osmo-epdg_The_osmocom_ePDG_for_VoWiFi_opus.opus?1717396262</guid>
      <dc:identifier>f7e57ec6-4937-5e9c-84cf-ae6cd42c0139</dc:identifier>
      <dc:date>2024-05-05T10:15:00+02:00</dc:date>
      <itunes:author>Pau Espin Pedrol, Alexander Couzens</itunes:author>
      <itunes:explicit>No</itunes:explicit>
      <itunes:keywords>osmodevcon2024, 179, 2024, osmodevcon2024, osmocom</itunes:keywords>
      <itunes:summary>After working on it on and off during 2023, we finally have a working ePDG in the Osmocom universe.  Let&#39;s have  a look at its internal architecture, how it integrates with other network elements and have a look at a demo and protocol traces.
about this event: https://pretalx.sysmocom.de/osmodevcon2024/talk/YJWERZ/
</itunes:summary>
      <itunes:duration>00:45:34</itunes:duration>
    </item>
    <item>
      <title>Anatomy of the eSIM profile (osmodevcon2024)</title>
      <link>https://media.ccc.de/v/osmodevcon2024-174-anatomy-of-the-esim-profile</link>
      <description>In the eSIM universe, *eSIM profiles* are the virtualised content of a classic USIM (possibly with ISIM, CSIM, applets, etc.).

Let&#39;s have a look what an eSIM profile is:
* how is the data structured / organized?
* what data can be represented in it?
* how to handle features provided by eUICC, how can the eSIM profile mandate some of them?
* how does personalization of eSIM profiles work?

There will be some hands-on navigation through profiles, based on the `pySim.esim.saip` module.
about this event: https://pretalx.sysmocom.de/osmodevcon2024/talk/J888MC/
</description>
      <enclosure url="https://cdn.media.ccc.de/events/osmodevcon/2024/opus/osmodevcon2024-174-eng-Anatomy_of_the_eSIM_profile_opus.opus"
        length="37748736"
        type="audio/opus"/>
      <pubDate>Sat, 04 May 2024 19:15:00 +0200</pubDate>
      <guid isPermaLink="true">https://cdn.media.ccc.de/events/osmodevcon/2024/opus/osmodevcon2024-174-eng-Anatomy_of_the_eSIM_profile_opus.opus?1717392144</guid>
      <dc:identifier>f86cf95c-1ff3-54e3-8643-04527c61fc72</dc:identifier>
      <dc:date>2024-05-04T19:15:00+02:00</dc:date>
      <itunes:author>Harald Welte (sysmocom)</itunes:author>
      <itunes:explicit>No</itunes:explicit>
      <itunes:keywords>osmodevcon2024, 174, 2024, osmodevcon2024, osmocom</itunes:keywords>
      <itunes:summary>In the eSIM universe, *eSIM profiles* are the virtualised content of a classic USIM (possibly with ISIM, CSIM, applets, etc.).

Let&#39;s have a look what an eSIM profile is:
* how is the data structured / organized?
* what data can be represented in it?
* how to handle features provided by eUICC, how can the eSIM profile mandate some of them?
* how does personalization of eSIM profiles work?

There will be some hands-on navigation through profiles, based on the `pySim.esim.saip` module.
about this event: https://pretalx.sysmocom.de/osmodevcon2024/talk/J888MC/
</itunes:summary>
      <itunes:duration>00:51:16</itunes:duration>
    </item>
    <item>
      <title>my hobby dabbles at examining network traces (osmodevcon2024)</title>
      <link>https://media.ccc.de/v/osmodevcon2024-195-my-hobby-dabbles-at-examining-network-traces</link>
      <description>Often I get a 3GPP related network trace (pcap), and have to manually gather leads to find out what exactly is going on in it. I have tried different ways to automate the analysis part, and will share what I ended up with.

I&#39;ll show my little tools that I played with to trace and visualize GSM network activity.
Immature as all of it is, maybe it is interesting to share and form a vision of a helpful tool.

For example, when the task is to find out: at which network edge of a call leg do the RTP packets drop.
First I need to know the chain of RTP ports that one particular subscriber uses.
Then I need to count RTP packets arriving at each of them.

Another example, there are a bunch of {PFCP,MGCP} conversations, setting up the user plane vectors.
Are all the ports configured correctly? I have to read through the entire {PFCP,MGCP} session to overlay all the bits that form the final result.

Another example, in a very active network, a particular voice call has a problem. How do I efficiently examine only those packets that are directly related to this particular TMSI / IMSI / RTP packet / RSL-ChanRef / ...
about this event: https://pretalx.sysmocom.de/osmodevcon2024/talk/QRBB9Y/
</description>
      <enclosure url="https://cdn.media.ccc.de/events/osmodevcon/2024/opus/osmodevcon2024-195-eng-my_hobby_dabbles_at_examining_network_traces_opus.opus"
        length="13631488"
        type="audio/opus"/>
      <pubDate>Sat, 04 May 2024 18:15:00 +0200</pubDate>
      <guid isPermaLink="true">https://cdn.media.ccc.de/events/osmodevcon/2024/opus/osmodevcon2024-195-eng-my_hobby_dabbles_at_examining_network_traces_opus.opus?1717387517</guid>
      <dc:identifier>6afe9919-dd80-507d-8ab6-16df8e487920</dc:identifier>
      <dc:date>2024-05-04T18:15:00+02:00</dc:date>
      <itunes:author>Neels Hofmeyr</itunes:author>
      <itunes:explicit>No</itunes:explicit>
      <itunes:keywords>osmodevcon2024, 195, 2024, osmodevcon2024, osmocom</itunes:keywords>
      <itunes:summary>Often I get a 3GPP related network trace (pcap), and have to manually gather leads to find out what exactly is going on in it. I have tried different ways to automate the analysis part, and will share what I ended up with.

I&#39;ll show my little tools that I played with to trace and visualize GSM network activity.
Immature as all of it is, maybe it is interesting to share and form a vision of a helpful tool.

For example, when the task is to find out: at which network edge of a call leg do the RTP packets drop.
First I need to know the chain of RTP ports that one particular subscriber uses.
Then I need to count RTP packets arriving at each of them.

Another example, there are a bunch of {PFCP,MGCP} conversations, setting up the user plane vectors.
Are all the ports configured correctly? I have to read through the entire {PFCP,MGCP} session to overlay all the bits that form the final result.

Another example, in a very active network, a particular voice call has a problem. How do I efficiently examine only those packets that are directly related to this particular TMSI / IMSI / RTP packet / RSL-ChanRef / ...
about this event: https://pretalx.sysmocom.de/osmodevcon2024/talk/QRBB9Y/
</itunes:summary>
      <itunes:duration>00:21:35</itunes:duration>
    </item>
    <item>
      <title>fx2adc: Using USB oscilloscopes as general purpose ADC (osmodevcon2024)</title>
      <link>https://media.ccc.de/v/osmodevcon2024-210-fx2adc-using-usb-oscilloscopes-as-general-purpose-adc</link>
      <description>There are several USB oscilloscopes based on the Cypress FX2 + AD9288 (e.g. Hantek 6022BE). So far, most of them were supported by the open source sigrok project, but not for continuous acquisition of samples. This talk will show how those devices can be used to digitize SDR IF signals, and for projects like vhsdecode.

For more information, see:
https://github.com/steve-m/fx2adc
about this event: https://pretalx.sysmocom.de/osmodevcon2024/talk/F7CZPM/
</description>
      <enclosure url="https://cdn.media.ccc.de/events/osmodevcon/2024/opus/osmodevcon2024-210-eng-fx2adc_Using_USB_oscilloscopes_as_general_purpose_ADC_opus.opus"
        length="14680064"
        type="audio/opus"/>
      <pubDate>Sat, 04 May 2024 16:10:00 +0200</pubDate>
      <guid isPermaLink="true">https://cdn.media.ccc.de/events/osmodevcon/2024/opus/osmodevcon2024-210-eng-fx2adc_Using_USB_oscilloscopes_as_general_purpose_ADC_opus.opus?1717379582</guid>
      <dc:identifier>2c9bb83e-6ada-5ed7-909d-594e785e1769</dc:identifier>
      <dc:date>2024-05-04T16:10:00+02:00</dc:date>
      <itunes:author>Steve Markgraf</itunes:author>
      <itunes:explicit>No</itunes:explicit>
      <itunes:keywords>osmodevcon2024, 210, 2024, osmodevcon2024, osmocom</itunes:keywords>
      <itunes:summary>There are several USB oscilloscopes based on the Cypress FX2 + AD9288 (e.g. Hantek 6022BE). So far, most of them were supported by the open source sigrok project, but not for continuous acquisition of samples. This talk will show how those devices can be used to digitize SDR IF signals, and for projects like vhsdecode.

For more information, see:
https://github.com/steve-m/fx2adc
about this event: https://pretalx.sysmocom.de/osmodevcon2024/talk/F7CZPM/
</itunes:summary>
      <itunes:duration>00:19:11</itunes:duration>
    </item>
    <item>
      <title>GSMTAPv3 - The long-awaited successor (osmodevcon2024)</title>
      <link>https://media.ccc.de/v/osmodevcon2024-181-gsmtapv3-the-long-awaited-successor</link>
      <description>We all know the inherent problems of GSMTAP (v2) as we know it.  Can we finally tackle the much desired successor GSMTAPv3 in 2024?
about this event: https://pretalx.sysmocom.de/osmodevcon2024/talk/Q3XYVC/
</description>
      <enclosure url="https://cdn.media.ccc.de/events/osmodevcon/2024/opus/osmodevcon2024-181-eng-GSMTAPv3_-_The_long-awaited_successor_opus.opus"
        length="32505856"
        type="audio/opus"/>
      <pubDate>Sat, 04 May 2024 15:10:00 +0200</pubDate>
      <guid isPermaLink="true">https://cdn.media.ccc.de/events/osmodevcon/2024/opus/osmodevcon2024-181-eng-GSMTAPv3_-_The_long-awaited_successor_opus.opus?1717371788</guid>
      <dc:identifier>32363bfa-8cdc-5ec8-b250-0e5bbfc65b8b</dc:identifier>
      <dc:date>2024-05-04T15:10:00+02:00</dc:date>
      <itunes:author>Shinjo Park</itunes:author>
      <itunes:explicit>No</itunes:explicit>
      <itunes:keywords>osmodevcon2024, 181, 2024, osmodevcon2024, osmocom</itunes:keywords>
      <itunes:summary>We all know the inherent problems of GSMTAP (v2) as we know it.  Can we finally tackle the much desired successor GSMTAPv3 in 2024?
about this event: https://pretalx.sysmocom.de/osmodevcon2024/talk/Q3XYVC/
</itunes:summary>
      <itunes:duration>00:43:01</itunes:duration>
    </item>
    <item>
      <title>Lower Layer of osmo-trx-ms (osmodevcon2024)</title>
      <link>https://media.ccc.de/v/osmodevcon2024-220-lower-layer-of-osmo-trx-ms</link>
      <description>Brief talk about the lower layers of osmo-trx-ms, the mobile-station side GSM transceiver
about this event: https://pretalx.sysmocom.de/osmodevcon2024/talk/3SYDHF/
</description>
      <enclosure url="https://cdn.media.ccc.de/events/osmodevcon/2024/opus/osmodevcon2024-220-eng-Lower_Layer_of_osmo-trx-ms_opus.opus"
        length="12582912"
        type="audio/opus"/>
      <pubDate>Sat, 04 May 2024 14:30:00 +0200</pubDate>
      <guid isPermaLink="true">https://cdn.media.ccc.de/events/osmodevcon/2024/opus/osmodevcon2024-220-eng-Lower_Layer_of_osmo-trx-ms_opus.opus?1717367744</guid>
      <dc:identifier>3ffe7392-fdc2-5a14-be13-8f7f708bd6c8</dc:identifier>
      <dc:date>2024-05-04T14:30:00+02:00</dc:date>
      <itunes:author>Eric Wild</itunes:author>
      <itunes:explicit>No</itunes:explicit>
      <itunes:keywords>osmodevcon2024, 220, 2024, osmodevcon2024, osmocom</itunes:keywords>
      <itunes:summary>Brief talk about the lower layers of osmo-trx-ms, the mobile-station side GSM transceiver
about this event: https://pretalx.sysmocom.de/osmodevcon2024/talk/3SYDHF/
</itunes:summary>
      <itunes:duration>00:19:14</itunes:duration>
    </item>
    <item>
      <title>onomondo softsim: A software USIM implementation (osmodevcon2024)</title>
      <link>https://media.ccc.de/v/osmodevcon2024-180-onomondo-softsim-a-software-usim-implementation</link>
      <description>During 2022, sysmocom was tasked by IoT operator Onomondo to develop a software implementation of a rather fully-featured 3GPP USIM (and ETSI UICC).  The idea of this project is that one would run it inside an existing trusted execution environment / secure element of an IoT device, removing the need for a physical chip or slot.

After some grace period, this project was released as open source software in 2024.  Let&#39;s have a look on what it can do and how it can be used.
about this event: https://pretalx.sysmocom.de/osmodevcon2024/talk/TRWXYF/
</description>
      <enclosure url="https://cdn.media.ccc.de/events/osmodevcon/2024/opus/osmodevcon2024-180-eng-onomondo_softsim_A_software_USIM_implementation_opus.opus"
        length="24117248"
        type="audio/opus"/>
      <pubDate>Sat, 04 May 2024 12:30:00 +0200</pubDate>
      <guid isPermaLink="true">https://cdn.media.ccc.de/events/osmodevcon/2024/opus/osmodevcon2024-180-eng-onomondo_softsim_A_software_USIM_implementation_opus.opus?1717366124</guid>
      <dc:identifier>72425462-4094-5812-a417-af91d3a6a29b</dc:identifier>
      <dc:date>2024-05-04T12:30:00+02:00</dc:date>
      <itunes:author>Philipp Maier</itunes:author>
      <itunes:explicit>No</itunes:explicit>
      <itunes:keywords>osmodevcon2024, 180, 2024, osmodevcon2024, osmocom</itunes:keywords>
      <itunes:summary>During 2022, sysmocom was tasked by IoT operator Onomondo to develop a software implementation of a rather fully-featured 3GPP USIM (and ETSI UICC).  The idea of this project is that one would run it inside an existing trusted execution environment / secure element of an IoT device, removing the need for a physical chip or slot.

After some grace period, this project was released as open source software in 2024.  Let&#39;s have a look on what it can do and how it can be used.
about this event: https://pretalx.sysmocom.de/osmodevcon2024/talk/TRWXYF/
</itunes:summary>
      <itunes:duration>00:35:52</itunes:duration>
    </item>
    <item>
      <title>Detailed workings of OTA for SIM/USIM/eUICC (osmodevcon2024)</title>
      <link>https://media.ccc.de/v/osmodevcon2024-175-detailed-workings-of-ota-for-sim-usim-euicc</link>
      <description>Everyone knows that OTA (over the air) access to SIM cards exists for decades, and that somehow authenticated APDUs can be sent via SMS.

But let&#39;s look at the OTA architecture in more detail:
* OTA transport (SCP80) over SMS, USSD, CellBroadcast, CAT-TP, BIP
* The *new* SCP81 transport (HTTPS via TLS-PSK)
* how to address individal applications on the card via their TAR
  * common applications like RFM and RAM
  * custom applications on the card
* OTA in the world of eUICCs
  * talking to the ECASD
  * talking to the ISD-R
  * talking to the ISD-P/MNO-SD or applications therein
about this event: https://pretalx.sysmocom.de/osmodevcon2024/talk/W9X8XH/
</description>
      <enclosure url="https://cdn.media.ccc.de/events/osmodevcon/2024/opus/osmodevcon2024-175-eng-Detailed_workings_of_OTA_for_SIM_USIM_eUICC_opus.opus"
        length="19922944"
        type="audio/opus"/>
      <pubDate>Sat, 04 May 2024 12:00:00 +0200</pubDate>
      <guid isPermaLink="true">https://cdn.media.ccc.de/events/osmodevcon/2024/opus/osmodevcon2024-175-eng-Detailed_workings_of_OTA_for_SIM_USIM_eUICC_opus.opus?1717362164</guid>
      <dc:identifier>645c3a8f-51a2-556f-8a2b-9d741108cfea</dc:identifier>
      <dc:date>2024-05-04T12:00:00+02:00</dc:date>
      <itunes:author>Harald Welte (sysmocom)</itunes:author>
      <itunes:explicit>No</itunes:explicit>
      <itunes:keywords>osmodevcon2024, 175, 2024, osmodevcon2024, osmocom</itunes:keywords>
      <itunes:summary>Everyone knows that OTA (over the air) access to SIM cards exists for decades, and that somehow authenticated APDUs can be sent via SMS.

But let&#39;s look at the OTA architecture in more detail:
* OTA transport (SCP80) over SMS, USSD, CellBroadcast, CAT-TP, BIP
* The *new* SCP81 transport (HTTPS via TLS-PSK)
* how to address individal applications on the card via their TAR
  * common applications like RFM and RAM
  * custom applications on the card
* OTA in the world of eUICCs
  * talking to the ECASD
  * talking to the ISD-R
  * talking to the ISD-P/MNO-SD or applications therein
about this event: https://pretalx.sysmocom.de/osmodevcon2024/talk/W9X8XH/
</itunes:summary>
      <itunes:duration>00:28:49</itunes:duration>
    </item>
    <item>
      <title>My Kamailio Config (osmodevcon2024)</title>
      <link>https://media.ccc.de/v/osmodevcon2024-207-my-kamailio-config</link>
      <description>This talk should maybe be titled &quot;How (NOT) to write a Kamailio Config&quot; :-)

Some of us at Osmocom have had reason to use Kamailio in recent years, even if only as a basic endpoint for osmo-sip-connector to loop back to itself.

Kamailio is quite powerful, and it might be of interest to briefly go through the things I did with it, and also two other related FOSS projects: **SEMS** and **RTPENGINE**

* Routing DID
* Routing with Osmo dGSM
* Gateway to Jitsi Conferences
* Mangling Caller ID
* Failover routing (Terrestrial/vSAT switch)
* Codec Transcoding decisions (with multiple transcoding hosts and optional direct RTP without transcoding)

*All this can be learned by reading Kamailo docs, however, there&#39;s nothing like learning from real experience, right? (or sharing that experience, and examples)*
about this event: https://pretalx.sysmocom.de/osmodevcon2024/talk/BUWUKG/
</description>
      <enclosure url="https://cdn.media.ccc.de/events/osmodevcon/2024/opus/osmodevcon2024-207-eng-My_Kamailio_Config_opus.opus"
        length="26214400"
        type="audio/opus"/>
      <pubDate>Sat, 04 May 2024 11:30:00 +0200</pubDate>
      <guid isPermaLink="true">https://cdn.media.ccc.de/events/osmodevcon/2024/opus/osmodevcon2024-207-eng-My_Kamailio_Config_opus.opus?1717359105</guid>
      <dc:identifier>992de5fa-298f-5930-8d43-d78c1e7fc576</dc:identifier>
      <dc:date>2024-05-04T11:30:00+02:00</dc:date>
      <itunes:author>Keith Whyte</itunes:author>
      <itunes:explicit>No</itunes:explicit>
      <itunes:keywords>osmodevcon2024, 207, 2024, osmodevcon2024, osmocom</itunes:keywords>
      <itunes:summary>This talk should maybe be titled &quot;How (NOT) to write a Kamailio Config&quot; :-)

Some of us at Osmocom have had reason to use Kamailio in recent years, even if only as a basic endpoint for osmo-sip-connector to loop back to itself.

Kamailio is quite powerful, and it might be of interest to briefly go through the things I did with it, and also two other related FOSS projects: **SEMS** and **RTPENGINE**

* Routing DID
* Routing with Osmo dGSM
* Gateway to Jitsi Conferences
* Mangling Caller ID
* Failover routing (Terrestrial/vSAT switch)
* Codec Transcoding decisions (with multiple transcoding hosts and optional direct RTP without transcoding)

*All this can be learned by reading Kamailo docs, however, there&#39;s nothing like learning from real experience, right? (or sharing that experience, and examples)*
about this event: https://pretalx.sysmocom.de/osmodevcon2024/talk/BUWUKG/
</itunes:summary>
      <itunes:duration>00:36:30</itunes:duration>
    </item>
    <item>
      <title>srsRAN Project - Application in UL heavy traffic scenarios (osmodevcon2024)</title>
      <link>https://media.ccc.de/v/osmodevcon2024-214-srsran-project-application-in-ul-heavy-traffic-scenarios</link>
      <description>First, we explore the usecase of Uplink heavy traffic scenarios. Then, describe the approach taken in srsRAN Project to meet the needs of these scenarios and finally showcase its working in a demo
about this event: https://pretalx.sysmocom.de/osmodevcon2024/talk/HZVJQK/
</description>
      <enclosure url="https://cdn.media.ccc.de/events/osmodevcon/2024/opus/osmodevcon2024-214-eng-srsRAN_Project_-_Application_in_UL_heavy_traffic_scenarios_opus.opus"
        length="24117248"
        type="audio/opus"/>
      <pubDate>Sat, 04 May 2024 11:00:00 +0200</pubDate>
      <guid isPermaLink="true">https://cdn.media.ccc.de/events/osmodevcon/2024/opus/osmodevcon2024-214-eng-srsRAN_Project_-_Application_in_UL_heavy_traffic_scenarios_opus.opus?1717351862</guid>
      <dc:identifier>b3a96fc1-e91e-5413-8093-70a011db8df6</dc:identifier>
      <dc:date>2024-05-04T11:00:00+02:00</dc:date>
      <itunes:author>Supreeth Herle</itunes:author>
      <itunes:explicit>No</itunes:explicit>
      <itunes:keywords>osmodevcon2024, 214, 2024, osmodevcon2024, osmocom</itunes:keywords>
      <itunes:summary>First, we explore the usecase of Uplink heavy traffic scenarios. Then, describe the approach taken in srsRAN Project to meet the needs of these scenarios and finally showcase its working in a demo
about this event: https://pretalx.sysmocom.de/osmodevcon2024/talk/HZVJQK/
</itunes:summary>
      <itunes:duration>00:36:30</itunes:duration>
    </item>
    <item>
      <title>DebugMux: getting baseband logs from old Sony Ericsson phones (osmodevcon2024)</title>
      <link>https://media.ccc.de/v/osmodevcon2024-185-debugmux-getting-baseband-logs-from-old-sony-ericsson-phones</link>
      <description>DebugMux is a vendor specific interface/protocol exposed by [Sony] Ericsson phones and modems. Similar to QMI (Qualcomm MSM Interface), it allows debugging the GSM/GPRS/UMTS stack at run-time. In this talk I will demonstrate an open source DebugMux client software and share my findings about this interface, as well as other interfaces working on top of it.
about this event: https://pretalx.sysmocom.de/osmodevcon2024/talk/XB9MRJ/
</description>
      <enclosure url="https://cdn.media.ccc.de/events/osmodevcon/2024/opus/osmodevcon2024-185-eng-DebugMux_getting_baseband_logs_from_old_Sony_Ericsson_phones_opus.opus"
        length="22020096"
        type="audio/opus"/>
      <pubDate>Fri, 03 May 2024 18:30:00 +0200</pubDate>
      <guid isPermaLink="true">https://cdn.media.ccc.de/events/osmodevcon/2024/opus/osmodevcon2024-185-eng-DebugMux_getting_baseband_logs_from_old_Sony_Ericsson_phones_opus.opus?1717346582</guid>
      <dc:identifier>542c905f-d5a2-5cac-8c3e-a95aab25dbb5</dc:identifier>
      <dc:date>2024-05-03T18:30:00+02:00</dc:date>
      <itunes:author>Vadim Yanitskiy</itunes:author>
      <itunes:explicit>No</itunes:explicit>
      <itunes:keywords>osmodevcon2024, 185, 2024, osmodevcon2024, osmocom</itunes:keywords>
      <itunes:summary>DebugMux is a vendor specific interface/protocol exposed by [Sony] Ericsson phones and modems. Similar to QMI (Qualcomm MSM Interface), it allows debugging the GSM/GPRS/UMTS stack at run-time. In this talk I will demonstrate an open source DebugMux client software and share my findings about this interface, as well as other interfaces working on top of it.
about this event: https://pretalx.sysmocom.de/osmodevcon2024/talk/XB9MRJ/
</itunes:summary>
      <itunes:duration>00:34:41</itunes:duration>
    </item>
    <item>
      <title>Welcome to OsmoDevCon 2024 (osmodevcon2024)</title>
      <link>https://media.ccc.de/v/osmodevcon2024-189-welcome-to-osmodevcon-2024</link>
      <description>Welcome to the event, organizational matters, thanks to sponsors, ...
about this event: https://pretalx.sysmocom.de/osmodevcon2024/talk/NRLXAB/
</description>
      <enclosure url="https://cdn.media.ccc.de/events/osmodevcon/2024/opus/osmodevcon2024-189-eng-Welcome_to_OsmoDevCon_2024_opus.opus"
        length="11534336"
        type="audio/opus"/>
      <pubDate>Fri, 03 May 2024 11:00:00 +0200</pubDate>
      <guid isPermaLink="true">https://cdn.media.ccc.de/events/osmodevcon/2024/opus/osmodevcon2024-189-eng-Welcome_to_OsmoDevCon_2024_opus.opus?1717002399</guid>
      <dc:identifier>b42f726f-49a7-594d-9266-3bdcb73265b0</dc:identifier>
      <dc:date>2024-05-03T11:00:00+02:00</dc:date>
      <itunes:author>Harald Welte (sysmocom)</itunes:author>
      <itunes:explicit>No</itunes:explicit>
      <itunes:keywords>osmodevcon2024, 189, 2024, osmodevcon2024, osmocom</itunes:keywords>
      <itunes:summary>Welcome to the event, organizational matters, thanks to sponsors, ...
about this event: https://pretalx.sysmocom.de/osmodevcon2024/talk/NRLXAB/
</itunes:summary>
      <itunes:duration>00:16:12</itunes:duration>
    </item>
    <generator>media.ccc.de / RSS 0.3.1</generator>
    <itunes:category text="Technology"/>
    <itunes:image href="https://static.media.ccc.de/media/conferences/osmodevcon/2024/logo.png"/>
    <itunes:owner>
      <itunes:name>CCC media team</itunes:name>
      <itunes:email>media@c3voc.de</itunes:email>
    </itunes:owner>
    <itunes:author>CCC media team</itunes:author>
    <itunes:explicit>No</itunes:explicit>
    <itunes:keywords>CCC Congress Hacking Security Netzpolitik</itunes:keywords>
    <itunes:subtitle>A wide variety of video material distributed by the CCC. All content is taken from cdn.media.ccc.de and media.ccc.de</itunes:subtitle>
    <itunes:summary>A wide variety of video material distributed by the Chaos Computer Club. This feed contains all events from osmodevcon2024 as opus</itunes:summary>
  </channel>
</rss>