Skip to content

Configuration

Jump to bottom
Valentin edited this page Apr 14, 2024 · 4 revisions

Configuration

Configuration File

You must configure in $PACKETRUSHER/config/config.yml the parameters that'll be used by your simulated UE(s) and gNodeB(s) prior to running PacketRusher.

gNodeB Configuration:

  • controlif: IP and Port for N2 interface for gNodeB. PacketRusher will use IP and Port to communicates with AMF and receive NAS/NGAP packets from AMF via SCTP socket. It's usually your machine's ip. Change depending on your environment.
  • dataif: IP and Port for N3 interface for gNodeB. PacketRusher will use IP and Port to communicates with UPF and receive GTP packets from UPF via UDP socket. It's usually your machine's ip. Change depending on your environment.
  • plmnlist: contains MCC (Mobile Country Code value)/ MNC (Mobile Network Code), TAC (Tracking Area Code) and gnbid information. These information must be consistent with 5G Core, AMF and UE's configuration.
  • slicesupportlist: The list of slices supported by this gNodeB by tracking area. It's usually the slice that you will want to connect in the 5G Core. sd field is optional.

UE Configuration:

  • msin: MSIN number of the UE. If your UE's SUPI is imsi-999700000000120, then MSIN will be "0000000120", MCC = "999" and MNC = "70". The MCC and MNC must be included in hplmn field.
  • key: Permanent Subscription Key. This is the key that must have been provisioned for the UE. This field is used for authentication of UE. Currently the PacketRushers only supports 5G-AKA authentication method.
  • opc: Operator Code Value. This is the opc that must have been provisioned for the UE. This field is used for authentication of UE. The usage of an op is not yet supported.
  • amf: Authentication Management Field (AMF). This is the AMF value that must have been configured for the UE. This field is used for authentication of UE.
  • sqn: Sequence Number. The default value will work in the basics case, e.g, registration of UE. If you want to trigger resynchronization of Sequence Number (SQN) in authentication process with 5GC, try to change this value.
  • dnn: refers information about PDU Session. In this case, specifies the data network for the PDU Session and can be used for SMF/UPF selection.
  • hplmn: the MCC and MNC part of IMSI information for the UE.
  • snssai: refers information about PDU Session. In this case, specifies the slice for the PDU Session and can be used for SMF/UPF selection. sd field is optional.

AMF Configuration:

  • Ip: The AMF's IP Address on N2.
  • Port: The AMF N2 endpoint's port, the default is 38412.

Configuration example

Here is an example of PacketRusher configuration for the following setup:

  • 5G SA Core Network
  • MCC is 999, MNC is 70
  • Default slice is SST 01 SD 000001 (Slice N°01-000001)

AMF/UPF Configuration

In this 5G Core under test, N2 and N3 are the same network:

Network Function NETWORK NAME IP ADDRESS
AMF N2 192.168.11.30
UPF N3 192.168.11.31

gNodeB

INTERFACE NAME NETWORK NAME IP ADDRESS
gNodeB controlif N2 192.168.11.13
gNodeB dataif N3 192.168.11.13

In this setup, PacketRusher's gNodeB uses the same IP/network to reach both AMF and UPF.
The IP specified in controlif should be able to reach AMF's N2 interface, and the IP specified in dataif should be able to access UPF's N3 data interface.

UE

In this setup, we assume the following SUPI (imsi-999700000000120) was provisioned in the 5G Core:

Device MCC MNC MSIN KEY OPC AMF SQN
UE0 999 70 0000000120 00112233445566778899AABBCCDDEEFF 00112233445566778899AABBCCDDEEFF 8000 00000000

If you are running PacketRusher with --multi-ue --number-of-ues 5, then you shall have 5 UEs provisioned with exactly the same provisioning information, but with their MSIN being sequential from 0000000120 to 0000000124:

Device MCC MNC MSIN KEY OPC AMF SQN
UE0 999 70 0000000120 00112233445566778899AABBCCDDEEFF 00112233445566778899AABBCCDDEEFF 8000 00000000
UE1 999 70 0000000121 00112233445566778899AABBCCDDEEFF 00112233445566778899AABBCCDDEEFF 8000 00000000
UE2 999 70 0000000122 00112233445566778899AABBCCDDEEFF 00112233445566778899AABBCCDDEEFF 8000 00000000
UE3 999 70 0000000123 00112233445566778899AABBCCDDEEFF 00112233445566778899AABBCCDDEEFF 8000 00000000
UE4 999 70 0000000124 00112233445566778899AABBCCDDEEFF 00112233445566778899AABBCCDDEEFF 8000 00000000

YAML Example

gnodeb:
  controlif:
    ip: "192.168.11.13"
    port: 9487
  dataif:
    ip: "192.168.11.13"
    port: 2152
  plmnlist:
    mcc: "999"
    mnc: "70"
    tac: "000001"
    gnbid: "000008"
  slicesupportlist:
    sst: "01"
    sd: "000001" # optional, can be removed if not used

ue:
  msin: "0000000120"
  key: "00112233445566778899AABBCCDDEEFF"
  opc: "00112233445566778899AABBCCDDEEFF"
  amf: "8000"
  sqn: "00000000"
  dnn: "internet"
  routingindicator: "4567"
  hplmn:
    mcc: "999"
    mnc: "70"
  snssai:
    sst: 01
    sd: "000001" # optional, can be removed if not used
  integrity:
    nia0: false
    nia1: false
    nia2: true
    nia3: false
  ciphering:
    nea0: true
    nea1: false
    nea2: true
    nea3: false
amfif:
  - ip: "192.168.11.30"
    port: 38412
logs:
    level: 4

This wiki page is based upon https://github.com/my5G/my5G-RANTester/wiki/Configuration

Clone this wiki locally