DUL Open5GS configuration

The DUL doesn't need any special Open5GS configuration. The eNodeB and cells must be present with the correct mcc/mnc/tac settings in the mme.yaml which has been configured via the managed objects.
Attach are example configuration files matching the enodeB/cell configuration on DUL 20 Configuration.

network configuration

The machine hosting the Open5GS must be direct connected to the side network (TN A/TN B) and have the following IPs configured:

iface description
eth0 optional interface to LMT, not needed
eth1 side network TN A/TN B for enodeB traffc
eth2 uplink to the internet. NAT for UE traffic
  • example /etc/network/interfaces.conf
auto lo
iface lo inet loopback

auto eth0
iface eth0 inet static

auto eth1
iface eth1 inet static
        post-up ip a a dev eth1
        post-up ip a a dev eth1
        post-up ip a a dev eth1
        post-up ip a a dev eth1
        post-up ip a a dev eth1
        post-up ip a a dev eth1
        post-up ip a a dev eth1
        post-up ip a a dev eth1
        post-up ip a a dev eth1
        post-up ip a a dev eth1
        post-up ip a a dev eth1
        post-up ip a a dev eth1

auto eth2
iface eth2 inet dhcp
        post-up iptables -A POSTROUTING -j MASQUERADE -s -t nat


Open5GS was installed following the Quickstart manual
The configuration was tested on debian buster with the following versions.

root@rbs-open5gs:/# dpkg -l '*open5gs*'
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name                 Version      Architecture Description
ii  open5gs:amd64        2.0.20       amd64        5G Core and EPC (metapackage)
ii  open5gs-amf:amd64    2.0.20       amd64        AMF (Access and Mobility Management Function)
ii  open5gs-ausf:amd64   2.0.20       amd64        AUSF (Authentication Server Function)
ii  open5gs-common:amd64 2.0.20       amd64        5G Core and EPC (Shared Files)
ii  open5gs-hss:amd64    2.0.20       amd64        HSS (Home Subscriber Server)
ii  open5gs-mme:amd64    2.0.20       amd64        MME (Mobility Management Entity)
ii  open5gs-nrf:amd64    2.0.20       amd64        NRF (Network Repository Function)
ii  open5gs-pcrf:amd64   2.0.20       amd64        PCRF (Policy and Charging Rules Function)
ii  open5gs-sgwc:amd64   2.0.20       amd64        SGW-C (Serving Gateway - Control Plane)
ii  open5gs-sgwu:amd64   2.0.20       amd64        SGW-U (Serving Gateway - User Plane)
ii  open5gs-smf:amd64    2.0.20       amd64        SMF (Session Management Function)
ii  open5gs-udm:amd64    2.0.20       amd64        UDM (Unified Data Management)
ii  open5gs-udr:amd64    2.0.20       amd64        UDR (Unified Data Repository)
ii  open5gs-upf:amd64    2.0.20       amd64        UPF (User Plane Function)

Running a NTP server

The eNodeB is configured to use as NTP server.
For testing chrony was used using the attached chrony.conf.

apt-get install chrony
Files (2)
open5gs-configs.tar.gz open5gs-configs.tar.gz 5.58 KB lynxis, 11/11/2020 10:50 PM
chrony.conf chrony.conf 967 Bytes lynxis, 11/11/2020 11:03 PM

Updated by lynxis over 3 years ago · 2 revisions

Add picture from clipboard (Maximum size: 48.8 MB)