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.
The machine hosting the Open5GS must be direct connected to the side network (TN A/TN B) and have the following IPs configured:
|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 address 169.254.1.3/16 gateway 169.254.1.15 auto eth1 iface eth1 inet static address 10.23.0.1/24 post-up ip a a 10.23.0.2/24 dev eth1 post-up ip a a 10.23.0.3/24 dev eth1 post-up ip a a 10.23.0.4/24 dev eth1 post-up ip a a 10.23.0.5/24 dev eth1 post-up ip a a 10.23.0.6/24 dev eth1 post-up ip a a 10.23.0.7/24 dev eth1 post-up ip a a 10.23.0.8/24 dev eth1 post-up ip a a 10.23.0.9/24 dev eth1 post-up ip a a 10.23.0.10/24 dev eth1 post-up ip a a 10.23.0.11/24 dev eth1 post-up ip a a 10.23.0.12/24 dev eth1 post-up ip a a 10.23.0.13/24 dev eth1 auto eth2 iface eth2 inet dhcp post-up iptables -A POSTROUTING -j MASQUERADE -s 10.45.0.0/16 -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*' Desired=Unknown/Install/Remove/Purge/Hold | 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 10.23.0.2/10.23.0.3 as NTP server.
For testing chrony was used using the attached chrony.conf.
apt-get install chrony