1edb0a09bb
A DRB may have an uplink SDAP header but no downlink header (valid TS 38.331). The old entity->enable_sdap flag was true if either direction had a header, so UE downlink wrongly read byte 0 as QFI. IPv4 payloads start with 0x45 -> bogus QFI 5 and dropped traffic before the TUN (PR !158). Header presence must follow TS 37.324 §5.2.1/§5.2.2 per DRB and direction, not a single PDU-session-wide enable-sdap. Also, store the default DRB as a `qfi2drb_t` mapping in the SDAP entity and use it directly for fallback paths. Changes: - Add nr_sdap_drb_lookup() to return first qfi2drb_table row for a DRB - nr_sdap_rx_entity(): parse QFI only when the receiving direction has a header, drop if the DRB has no table row - nr_sdap_tx_entity(): UL/DL TX header bits from qfi2drb_map() (drb_id + entity_role), including default-DRB fallback - nr_sdap_qfi2drb(): const qfi2drb_t *, remove SDAP_MAP_RULE_EMPTY - nr_sdap_map_ctrl_pdu(): handle NULL from qfi2drb_map - nr_sdap_qfi2drb_map_update(): sync entity_role on all QFIs for the DRB. At most one DRB when both headers absent. - nr_sdap_entity_update_qos_flows(): keep per-DRB role from nr_sdap_drb_lookup(), skip update when DRB has no row - Cleanup entity->enable_sdap - nr_sdap.c: remove TUN-thread QFI drop, tx_entity owns unmappable-QFI handling - replace default_drb with qfi2drb_t default_drb in SDAP entity and init default DRB id+role at SDAP entity creation Refs: - PR #158 - TS 37.324 §5.2.1, §5.2.2, §6.2.2.1 - TS 38.331 SDAP-Config (sdap-HeaderUL / sdap-HeaderDL) Signed-off-by: Guido Casati <guido.casati@openairinterface.org>
Duranta - OpenAirInterface
Duranta OpenAirInterface RAN delivers and maintains an open-source cellular wireless software stack for 4G, 5G and future networking technologies. It supports simulation, prototyping, and end-to-end deployments on Commercial-Off-The-Shelf (COTS) hardware. Built for research and experimentation, it provides standard-compliant interfaces and is released under the Collaborative Standards Software License (CSSL).
License
The source code is distributed under CSSL v1.0. Some files, such as for orchestration, are distributed under MIT license. Documentation is distributed under Creative Commons Attribution 4.0 International license.
All the files without an explicit copyright header have an implicit "Copyright of OpenAirInterface Authors".
Please see NOTICE for other licenses which are used in the software.
In the past OAI source code has been re-licensed sometimes, here is the history:
- CSSL v1.0 starting tag 2026.w14
- OAI Public License v1.1 starting tag v1.0 till
af4b0d53 - OAI Public License v1.0: starting tag v.04 till v1.0
- GPL 3: starting tag v.0 till v.04 (only initial implementation of 4G)
Where to Start
- General overview of documentation
- The implemented features
- System Requirements for Using OAI Stack
- How to build
- How to run the modems
Not all information is available in a central place, and information for specific sub-systems might be available in the corresponding sub-directories. To find all READMEs, this command might be handy:
find . -iname "readme*"
RAN repository structure
The OpenAirInterface (OAI) software is composed of the following parts:
openairinterface5g
├── charts
├── ci-scripts : Meta-scripts used by the OSA CI process. Contains also configuration files used day-to-day by CI.
├── CMakeLists.txt : Top-level CMakeLists.txt for building
├── cmake_targets : Build utilities to compile (simulation, emulation and real-time platforms), and generated build files.
├── common : Some common OAI utilities, some other tools can be found at openair2/UTILS.
├── doc : Documentation
├── docker : Dockerfiles to build for Ubuntu and RHEL
├── executables : Top-level executable source files (gNB, eNB, ...)
├── maketags : Script to generate emacs tags.
├── nfapi : (n)FAPI code for MAC-PHY interface
├── openair1 : Layer 1 (3GPP LTE Rel-10/12 PHY, NR Rel-15 PHY)
├── openair2 : Layer 2 (3GPP LTE Rel-10 MAC/RLC/PDCP/RRC/X2AP, LTE Rel-14 M2AP, NR Rel-15+ MAC/RLC/PDCP/SDAP/RRC/X2AP/F1AP/E1AP), E2AP
├── openair3 : Layer 3 (3GPP LTE Rel-10 S1AP/GTP, NR Rel-15 NGAP/GTP)
├── openshift : OpenShift helm charts for some deployment options of OAI
├── radio : Drivers for various radios such as USRP, AW2S, RFsim, 7.2 FHI, ...
├── targets : Some configuration files; only historical relevance, and might be deleted in the future
└── tools : Tools for use by the developers/ci machines: code analysis and formatting
How to get support from the Community
You can ask your question on the mailing lists.
Your email should contain below information:
- A clear subject in your email.
- For all the queries there should be [Query] in the subject of the email and for problems there should be [Problem].
- In case of a problem, add a small description.
- Do not share any photos unless you want to share a diagram.
- OAI gNB/DU/CU/CU-CP/CU-UP configuration file in
.confformat only. - Logs of OAI gNB/DU/CU/CU-CP/CU-UP in
.logor.txtformat only. - In case your question is related to performance, include a small description of the machine (Operating System, Kernel version, CPU, RAM and networking card) and diagram of your testing environment.
- Known/open issues are present on Github, so keep checking.
Always remember a structured email will help us understand your issues quickly.