LoginSignup
0
0
@s5uishida(Shigeru Ishida)in株式会社インテック

free5GC 5GCとUERANSIM UE/RANでeUPF(eBPF/XDP UPF)を試す

Posted at

本記事では、ローカル5G SAを想定して、free5GCとeBPF/XDP対応UPFのeUPFを連携動作させるための簡単な構成について説明します。 eUPFのインストールと設定については、こちらを参照してください。

free5GC 5GCのシミュレーション携帯網の概要

今回、free5GC 5GCのC-Plane、eUPF(eBPF/XDP UPF)、およびData Network Gatewayの簡単な構成について説明します。この構成はVirtualbox VMを使用して実装されることに注意して下さい。
このシミュレーション環境は以下の条件を満たす最小構成になります。

  • 1つのUPFとData Network Gateway
  • 1つのUEと1つのDNN

構築したシミュレーション環境は以下の通りです。

network-overview.png

5GC、eUPFとUE/RANに使用しているOSSは以下の通りです。

各VMは以下の通りです。

VM SW & Role IP address OS CPU
(Min)		 Memory
(Min)		 HDD
(Min)
VM1 free5GC 5GC
C-Plane		 192.168.0.141/24 Ubuntu
22.04		 1 2GB 20GB
VM-UP eUPF U-Plane 192.168.0.151/24 Ubuntu
22.04		 1 2GB 20GB
VM-DN Data Network
Gateway		 192.168.0.152/24 Ubuntu
22.04		 1 1GB 10GB
VM2 UERANSIM RAN
(gNodeB)		 192.168.0.131/24 Ubuntu
22.04		 1 1GB 10GB
VM3 UERANSIM UE 192.168.0.132/24 Ubuntu
22.04		 1 1GB 10GB

各VMのネットワークインターフェースは以下の通りです。

VM Device Network
Adapter		 IP address Interface XDP
VM1 enp0s3 NAT(default) 10.0.2.15/24 (VM default NW) --
enp0s8 Bridged Adapter 192.168.0.141/24 (Mgmt NW) --
enp0s9 NAT Network 192.168.14.141/24 N4 --
VM-UP enp0s3 NAT(default) 10.0.2.15/24 (VM default NW)
down 		--
enp0s8 Bridged Adapter 192.168.0.151/24 (Mgmt NW) --
enp0s9 NAT Network 192.168.13.151/24 N3 x
enp0s10 NAT Network 192.168.14.151/24 N4 --
enp0s16 NAT Network 192.168.16.151/24 N6 x
VM-DN enp0s3 NAT(default) 10.0.2.15/24 (VM default NW) --
enp0s8 Bridged Adapter 192.168.0.152/24 (Mgmt NW) --
enp0s9 NAT Network 192.168.16.152/24 N6,
default GW
for VM-UP 		--
VM2 enp0s3 NAT(default) 10.0.2.15/24 (VM default NW) --
enp0s8 Bridged Adapter 192.168.0.131/24 (Mgmt NW) --
enp0s9 NAT Network 192.168.13.131/24 N3 --
VM3 enp0s3 NAT(default) 10.0.2.15/24 (VM default NW) --
enp0s8 Bridged Adapter 192.168.0.132/24 (Mgmt NW) --

5GのNF間のインターフェースの内、N3、N4、N6については、VirtualboxのNATネットワークで以下の通りに設定しました。

Network Name Network CIDR
N3 192.168.13.0/24
N4 192.168.14.0/24
N6 192.168.16.0/24

network instanceをinternetに設定しています。

Network Instance
internet

加入者情報は以下の通りです。(その他の項目はデフォルト値)
UERANSIMのUEの設定に合わせて、OPあるいはOPcを選択してください。

UE IMSI DNN OP/OPc
UE 001010000000000 internet OPc

これらの情報の登録には、free5GCが提供するWebUIを使用しました。なお、3GPP認証とキー生成機能(MILENAGE)の試験データとして、3GPP TS 35.208 "4.3 Test Sets"が公開されています。

DNは以下の通りです。

DN DNN TUNnel interface of UE
10.60.0.0/16 internet uesimtun0

free5GC 5GC、eUPFとUERANSIM UE/RANの設定ファイルの変更点

free5GC、eUPFとUERANSIMのビルド方法は以下を参照して下さい。

free5GCでは、PFCPの接続先としてUPFを選択するロジックに使用可能なパラメータは以下の通りです。PFCP(Packet Forwarding Control Protocol)とは、5GCでCU分離のために導入されたプロトコルです。

  • DNN
  • S-NSSAI

話を簡単にするために、今回はDNNのみ使用しています。ここに登場する全てのUEのS-NSSAIは、SST=1とSD=010203に固定しています。

  • free5gc/config/amfcfg.yaml
--- amfcfg.yaml.orig    2023-11-10 23:13:08.456735624 +0900
+++ amfcfg.yaml 2023-11-10 23:26:10.862955424 +0900
@@ -5,7 +5,7 @@
 configuration:
   amfName: AMF # the name of this AMF
   ngapIpList:  # the IP list of N2 interfaces on this AMF
-    - 127.0.0.18
+    - 192.168.0.141
   ngapPort: 38412 # the SCTP port listened by NGAP
   sbi: # Service-based interface information
     scheme: http # the protocol for sbi (http or https)
@@ -24,18 +24,18 @@
   servedGuamiList: # Guami (Globally Unique AMF ID) list supported by this AMF
     # <GUAMI> = <MCC><MNC><AMF ID>
     - plmnId: # Public Land Mobile Network ID, <PLMN ID> = <MCC><MNC>
-        mcc: 208 # Mobile Country Code (3 digits string, digit: 0~9)
-        mnc: 93 # Mobile Network Code (2 or 3 digits string, digit: 0~9)
+        mcc: 001 # Mobile Country Code (3 digits string, digit: 0~9)
+        mnc: 01 # Mobile Network Code (2 or 3 digits string, digit: 0~9)
       amfId: cafe00 # AMF identifier (3 bytes hex string, range: 000000~FFFFFF)
   supportTaiList:  # the TAI (Tracking Area Identifier) list supported by this AMF
     - plmnId: # Public Land Mobile Network ID, <PLMN ID> = <MCC><MNC>
-        mcc: 208 # Mobile Country Code (3 digits string, digit: 0~9)
-        mnc: 93 # Mobile Network Code (2 or 3 digits string, digit: 0~9)
+        mcc: 001 # Mobile Country Code (3 digits string, digit: 0~9)
+        mnc: 01 # Mobile Network Code (2 or 3 digits string, digit: 0~9)
       tac: 000001 # Tracking Area Code (3 bytes hex string, range: 000000~FFFFFF)
   plmnSupportList: # the PLMNs (Public land mobile network) list supported by this AMF
     - plmnId: # Public Land Mobile Network ID, <PLMN ID> = <MCC><MNC>
-        mcc: 208 # Mobile Country Code (3 digits string, digit: 0~9)
-        mnc: 93 # Mobile Network Code (2 or 3 digits string, digit: 0~9)
+        mcc: 001 # Mobile Country Code (3 digits string, digit: 0~9)
+        mnc: 01 # Mobile Network Code (2 or 3 digits string, digit: 0~9)
       snssaiList: # the S-NSSAI (Single Network Slice Selection Assistance Information) list supported by this AMF
         - sst: 1 # Slice/Service Type (uinteger, range: 0~255)
           sd: 010203 # Slice Differentiator (3 bytes hex string, range: 000000~FFFFFF)
  • free5gc/config/ausfcfg.yaml
--- ausfcfg.yaml.orig   2023-10-28 22:09:20.479542560 +0900
+++ ausfcfg.yaml        2023-10-28 22:16:35.947533214 +0900
@@ -15,8 +15,8 @@
     - nausf-auth # Nausf_UEAuthentication service
   nrfUri: http://127.0.0.10:8000 # a valid URI of NRF
   plmnSupportList: # the PLMNs (Public Land Mobile Network) list supported by this AUSF
-    - mcc: 208 # Mobile Country Code (3 digits string, digit: 0~9)
-      mnc: 93  # Mobile Network Code (2 or 3 digits string, digit: 0~9)
+    - mcc: 001 # Mobile Country Code (3 digits string, digit: 0~9)
+      mnc: 01  # Mobile Network Code (2 or 3 digits string, digit: 0~9)
     - mcc: 123 # Mobile Country Code (3 digits string, digit: 0~9)
       mnc: 45  # Mobile Network Code (2 or 3 digits string, digit: 0~9)
   groupId: ausfGroup001 # ID for the group of the AUSF
  • free5gc/config/nrfcfg.yaml
--- nrfcfg.yaml.orig    2023-10-28 22:09:20.480542536 +0900
+++ nrfcfg.yaml 2023-10-28 22:16:42.051592773 +0900
@@ -14,8 +14,8 @@
       pem: cert/nrf.pem # NRF TLS Certificate
       key: cert/nrf.key # NRF TLS Private key
   DefaultPlmnId:
-    mcc: 208 # Mobile Country Code (3 digits string, digit: 0~9)
-    mnc: 93 # Mobile Network Code (2 or 3 digits string, digit: 0~9)
+    mcc: 001 # Mobile Country Code (3 digits string, digit: 0~9)
+    mnc: 01 # Mobile Network Code (2 or 3 digits string, digit: 0~9)
   serviceNameList: # the SBI services provided by this NRF, refer to TS 29.510
     - nnrf-nfm # Nnrf_NFManagement service
     - nnrf-disc # Nnrf_NFDiscovery service
  • free5gc/config/nssfcfg.yaml
--- nssfcfg.yaml.orig   2023-10-28 22:09:20.480542536 +0900
+++ nssfcfg.yaml        2023-10-28 22:16:46.708638917 +0900
@@ -17,12 +17,12 @@
     - nnssf-nssaiavailability # Nnssf_NSSAIAvailability service
   nrfUri: http://127.0.0.10:8000 # a valid URI of NRF
   supportedPlmnList: # the PLMNs (Public land mobile network) list supported by this NSSF
-    - mcc: 208 # Mobile Country Code (3 digits string, digit: 0~9)
-      mnc: 93 # Mobile Network Code (2 or 3 digits string, digit: 0~9)
+    - mcc: 001 # Mobile Country Code (3 digits string, digit: 0~9)
+      mnc: 01 # Mobile Network Code (2 or 3 digits string, digit: 0~9)
   supportedNssaiInPlmnList: # Supported S-NSSAI List for each PLMN
     - plmnId: # Public Land Mobile Network ID, <PLMN ID> = <MCC><MNC>
-        mcc: 208 # Mobile Country Code (3 digits string, digit: 0~9)
-        mnc: 93 # Mobile Network Code (2 or 3 digits string, digit: 0~9)
+        mcc: 001 # Mobile Country Code (3 digits string, digit: 0~9)
+        mnc: 01 # Mobile Network Code (2 or 3 digits string, digit: 0~9)
       supportedSnssaiList: # Supported S-NSSAIs of the PLMN
         - sst: 1 # Slice/Service Type (uinteger, range: 0~255)
           sd: 010203 # Slice Differentiator (3 bytes hex string, range: 000000~FFFFFF)
  • free5gc/config/smfcfg.yaml
--- smfcfg.yaml.orig    2023-10-28 22:09:20.480542536 +0900
+++ smfcfg.yaml 2023-10-28 22:16:51.996692030 +0900
@@ -34,22 +34,22 @@
             ipv4: 8.8.8.8
             ipv6: 2001:4860:4860::8888
   plmnList: # the list of PLMN IDs that this SMF belongs to (optional, remove this key when unnecessary)
-    - mcc: 208 # Mobile Country Code (3 digits string, digit: 0~9)
-      mnc: 93 # Mobile Network Code (2 or 3 digits string, digit: 0~9)
+    - mcc: 001 # Mobile Country Code (3 digits string, digit: 0~9)
+      mnc: 01 # Mobile Network Code (2 or 3 digits string, digit: 0~9)
   locality: area1 # Name of the location where a set of AMF, SMF, PCF and UPFs are located
   pfcp: # the IP address of N4 interface on this SMF (PFCP)
     # addr config is deprecated in smf config v1.0.3, please use the following config
-    nodeID: 127.0.0.1 # the Node ID of this SMF
-    listenAddr: 127.0.0.1 # the IP/FQDN of N4 interface on this SMF (PFCP)
-    externalAddr: 127.0.0.1 # the IP/FQDN of N4 interface on this SMF (PFCP)
+    nodeID: 192.168.14.141 # the Node ID of this SMF
+    listenAddr: 192.168.14.141 # the IP/FQDN of N4 interface on this SMF (PFCP)
+    externalAddr: 192.168.14.141 # the IP/FQDN of N4 interface on this SMF (PFCP)
   userplaneInformation: # list of userplane information
     upNodes: # information of userplane node (AN or UPF)
       gNB1: # the name of the node
         type: AN # the type of the node (AN or UPF)
       UPF: # the name of the node
         type: UPF # the type of the node (AN or UPF)
-        nodeID: 127.0.0.8 # the Node ID of this UPF
-        addr: 127.0.0.8 # the IP/FQDN of N4 interface on this UPF (PFCP)
+        nodeID: 192.168.14.151 # the Node ID of this UPF
+        addr: 192.168.14.151 # the IP/FQDN of N4 interface on this UPF (PFCP)
         sNssaiUpfInfos: # S-NSSAI information list for this UPF
           - sNssai: # S-NSSAI (Single Network Slice Selection Assistance Information)
               sst: 1 # Slice/Service Type (uinteger, range: 0~255)
@@ -72,7 +72,7 @@
         interfaces: # Interface list for this UPF
           - interfaceType: N3 # the type of the interface (N3 or N9)
             endpoints: # the IP address of this N3/N9 interface on this UPF
-              - 127.0.0.8
+              - 192.168.13.151
             networkInstances:  # Data Network Name (DNN)
               - internet
     links: # the topology graph of userplane, A and B represent the two nodes of each link
@@ -89,8 +89,10 @@
     expireTime: 16s   # default is 6 seconds
     maxRetryTimes: 3 # the max number of retransmission
   nrfUri: http://127.0.0.10:8000 # a valid URI of NRF
-  #urrPeriod: 10 # default usage report period in seconds
-  #urrThreshold: 1000 # default usage report threshold in bytes
+  urrPeriod: 10 # default usage report period in seconds
+  urrThreshold: 1000 # default usage report threshold in bytes
+  ulcl: false
+  nwInstFqdnEncoding: true
 
 logger: # log output setting
   enable: true # true or false

eUPFの設定ファイルの変更点

元の設定ファイルは、こちらを参照して下さい。

  • eupf/config.yml
    元ファイルからの変更はありません。

UERANSIM UE/RANの設定ファイルの変更点

RANの設定ファイルの変更点

  • UERANSIM/config/free5gc-gnb.yaml
--- free5gc-gnb.yaml.orig       2021-02-12 09:47:56.000000000 +0900
+++ free5gc-gnb.yaml    2023-06-15 22:24:00.297158446 +0900
@@ -1,17 +1,17 @@
-mcc: '208'          # Mobile Country Code value
-mnc: '93'           # Mobile Network Code value (2 or 3 digits)
+mcc: '001'          # Mobile Country Code value
+mnc: '01'           # Mobile Network Code value (2 or 3 digits)
 
 nci: '0x000000010'  # NR Cell Identity (36-bit)
 idLength: 32        # NR gNB ID length in bits [22...32]
 tac: 1              # Tracking Area Code
 
-linkIp: 127.0.0.1   # gNB's local IP address for Radio Link Simulation (Usually same with local IP)
-ngapIp: 127.0.0.1   # gNB's local IP address for N2 Interface (Usually same with local IP)
-gtpIp: 127.0.0.1    # gNB's local IP address for N3 Interface (Usually same with local IP)
+linkIp: 192.168.0.131   # gNB's local IP address for Radio Link Simulation (Usually same with local IP)
+ngapIp: 192.168.0.131   # gNB's local IP address for N2 Interface (Usually same with local IP)
+gtpIp: 192.168.13.131    # gNB's local IP address for N3 Interface (Usually same with local IP)
 
 # List of AMF address information
 amfConfigs:
-  - address: 127.0.0.1
+  - address: 192.168.0.141
     port: 38412
 
 # List of supported S-NSSAIs by this gNB

UE(IMSI-001010000000000)の設定ファイルの変更点

  • UERANSIM/config/free5gc-ue.yaml
--- free5gc-ue.yaml.orig        2023-05-10 14:51:54.000000000 +0900
+++ free5gc-ue.yaml     2023-06-15 22:24:48.016816988 +0900
@@ -1,9 +1,9 @@
 # IMSI number of the UE. IMSI = [MCC|MNC|MSISDN] (In total 15 digits)
-supi: 'imsi-208930000000003'
+supi: 'imsi-001010000000000'
 # Mobile Country Code value of HPLMN
-mcc: '208'
+mcc: '001'
 # Mobile Network Code value of HPLMN (2 or 3 digits)
-mnc: '93'
+mnc: '01'
 # SUCI Protection Scheme : 0 for Null-scheme, 1 for Profile A and 2 for Profile B
 protectionScheme: 0
 # Home Network Public Key for protecting with SUCI Profile A
@@ -28,7 +28,7 @@
 
 # List of gNB IP addresses for Radio Link Simulation
 gnbSearchList:
-  - 127.0.0.1
+  - 192.168.0.131
 
 # UAC Access Identities Configuration
 uacAic:

free5GC 5GC、eUPFとUERANSIM UE/RANのネットワーク設定

eUPFとData Network Gatewayのネットワーク設定

こちらとこちらを参照して下さい。

free5GC、eUPFとUERANSIMのビルド

free5GC、eUPFとUERANSIMのビルド方法は以下を参考にして下さい。

free5GC 5GC C-PlaneマシンにMongoDBをインストールして下さい。なお、MongoDBのデータベースを簡単に確認するには、MongoDB Compassが便利です。

free5GC 5GC、eUPFとUERANSIM UE/RANを実行

最初にeUPFを起動し、次にfree5GC 5GC、UERANSIM(UEとRANのシミュレータ)を起動します。

eUPFを実行

こちらを参考にして下さい。

free5GC 5GC C-Planeを実行

次に、free5GC 5GC C-Planeを起動します。次のスクリプトを作成して、実行します。

#!/usr/bin/env bash

PID_LIST=()

NF_LIST="nrf amf smf udr pcf udm nssf ausf"

export GIN_MODE=release

for NF in ${NF_LIST}; do
    ./bin/${NF} &
    PID_LIST+=($!)
    sleep 1
done

function terminate()
{
    sudo kill -SIGTERM ${PID_LIST[${#PID_LIST[@]}-2]} ${PID_LIST[${#PID_LIST[@]}-1]}
    sleep 2
}

trap terminate SIGINT
wait ${PID_LIST}

eUPFとfree5GC SMF間のPFCP Associationログは以下の通りです。

2023/12/04 21:06:26 INF Got Association Setup Request from: 192.168.14.141. 

2023/12/04 21:06:26 INF 
Association Setup Request:
  Node ID: 192.168.14.141
  Recovery Time: 2023-12-04 21:06:26 +0900 JST

2023/12/04 21:06:26 INF Saving new association: &{ID:192.168.14.141 Addr:192.168.14.141 NextSessionID:1 NextSequenceID:1 Sessions:map[] HeartbeatRetries:0 cancelRetries:<nil>}

UERANSIMを実行

ここでは、UE(IMSI-001010000000000)とRANを実行する場合を説明します。まず、gNodeBと5GCの間でNG-Setupし、5GCにUEを登録し、PDUセッションを確立します。

UERANSIMの使い方は以下を参照して下さい。

gNBを起動

次のようにgNBを起動します。

# ./nr-gnb -c ../config/free5gc-gnb.yaml
UERANSIM v3.2.6
[2023-12-04 21:07:19.335] [sctp] [info] Trying to establish SCTP connection... (192.168.0.141:38412)
[2023-12-04 21:07:19.337] [sctp] [info] SCTP connection established (192.168.0.141:38412)
[2023-12-04 21:07:19.338] [sctp] [debug] SCTP association setup ascId[4]
[2023-12-04 21:07:19.338] [ngap] [debug] Sending NG Setup Request
[2023-12-04 21:07:19.340] [ngap] [debug] NG Setup Response received
[2023-12-04 21:07:19.340] [ngap] [info] NG Setup procedure is successful

free5GC C-Planeのログは以下の通りです。

2023-12-04T21:07:19.350433537+09:00 [INFO][AMF][Ngap] [AMF] SCTP Accept from: 192.168.0.131:34534
2023-12-04T21:07:19.351129135+09:00 [INFO][AMF][Ngap] Create a new NG connection for: 192.168.0.131:34534
2023-12-04T21:07:19.351803196+09:00 [INFO][AMF][Ngap][ran_addr:192.168.0.131:34534] Handle NGSetupRequest
2023-12-04T21:07:19.351838555+09:00 [INFO][AMF][Ngap][ran_addr:192.168.0.131:34534] Send NG-Setup response

UEを起動

次のようにUEを起動します。これにより、5GCにUEが登録され、PDUセッションが確立します。

# ./nr-ue -c ../config/free5gc-ue.yaml
UERANSIM v3.2.6
[2023-12-04 21:07:57.525] [nas] [info] UE switches to state [MM-DEREGISTERED/PLMN-SEARCH]
[2023-12-04 21:07:57.525] [rrc] [debug] New signal detected for cell[1], total [1] cells in coverage
[2023-12-04 21:07:57.525] [nas] [info] Selected plmn[001/01]
[2023-12-04 21:07:57.526] [rrc] [info] Selected cell plmn[001/01] tac[1] category[SUITABLE]
[2023-12-04 21:07:57.526] [nas] [info] UE switches to state [MM-DEREGISTERED/PS]
[2023-12-04 21:07:57.526] [nas] [info] UE switches to state [MM-DEREGISTERED/NORMAL-SERVICE]
[2023-12-04 21:07:57.526] [nas] [debug] Initial registration required due to [MM-DEREG-NORMAL-SERVICE]
[2023-12-04 21:07:57.526] [nas] [debug] UAC access attempt is allowed for identity[0], category[MO_sig]
[2023-12-04 21:07:57.526] [nas] [debug] Sending Initial Registration
[2023-12-04 21:07:57.527] [nas] [info] UE switches to state [MM-REGISTER-INITIATED]
[2023-12-04 21:07:57.527] [rrc] [debug] Sending RRC Setup Request
[2023-12-04 21:07:57.527] [rrc] [info] RRC connection established
[2023-12-04 21:07:57.527] [rrc] [info] UE switches to state [RRC-CONNECTED]
[2023-12-04 21:07:57.528] [nas] [info] UE switches to state [CM-CONNECTED]
[2023-12-04 21:07:57.552] [nas] [debug] Authentication Request received
[2023-12-04 21:07:57.552] [nas] [debug] Received SQN [000000000075]
[2023-12-04 21:07:57.552] [nas] [debug] SQN-MS [000000000000]
[2023-12-04 21:07:57.561] [nas] [debug] Security Mode Command received
[2023-12-04 21:07:57.561] [nas] [debug] Selected integrity[2] ciphering[0]
[2023-12-04 21:07:57.600] [nas] [debug] Registration accept received
[2023-12-04 21:07:57.601] [nas] [info] UE switches to state [MM-REGISTERED/NORMAL-SERVICE]
[2023-12-04 21:07:57.601] [nas] [debug] Sending Registration Complete
[2023-12-04 21:07:57.601] [nas] [info] Initial Registration is successful
[2023-12-04 21:07:57.601] [nas] [debug] Sending PDU Session Establishment Request
[2023-12-04 21:07:57.604] [nas] [debug] UAC access attempt is allowed for identity[0], category[MO_sig]
[2023-12-04 21:07:57.811] [nas] [debug] Configuration Update Command received
[2023-12-04 21:07:57.920] [nas] [debug] PDU Session Establishment Accept received
[2023-12-04 21:07:57.925] [nas] [info] PDU Session establishment is successful PSI[1]
[2023-12-04 21:07:57.953] [app] [info] Connection setup for PDU session[1] is successful, TUN interface[uesimtun0, 10.60.0.1] is up.

free5GC C-Planeのログは以下の通りです。

2023-12-04T21:07:57.536754923+09:00 [INFO][AMF][Ngap][ran_addr:192.168.0.131:34534] Handle InitialUEMessage
2023-12-04T21:07:57.537092447+09:00 [INFO][AMF][Ngap][amf_ue_ngap_id:RU:1,AU:1(3GPP)][ran_addr:192.168.0.131:34534] New RanUe [RanUeNgapID:1][AmfUeNgapID:1]
2023-12-04T21:07:57.537462522+09:00 [INFO][AMF][Ngap][ran_addr:192.168.0.131:34534] 5GSMobileIdentity ["SUCI":"suci-0-001-01-0000-0-0-0000000000", err: <nil>]
2023-12-04T21:07:57.538324164+09:00 [INFO][AMF][CTX] New AmfUe [supi:][guti:00101cafe0000000001]
2023-12-04T21:07:57.538577142+09:00 [INFO][AMF][Gmm] Handle event[Gmm Message], transition from [Deregistered] to [Deregistered]
2023-12-04T21:07:57.538903978+09:00 [INFO][AMF][Gmm][amf_ue_ngap_id:RU:1,AU:1(3GPP)][supi:SUPI:] Handle Registration Request
2023-12-04T21:07:57.539087293+09:00 [INFO][AMF][Gmm][amf_ue_ngap_id:RU:1,AU:1(3GPP)][supi:SUPI:] RegistrationType: Initial Registration
2023-12-04T21:07:57.539374317+09:00 [INFO][AMF][Gmm][amf_ue_ngap_id:RU:1,AU:1(3GPP)][supi:SUPI:] MobileIdentity5GS: SUCI[suci-0-001-01-0000-0-0-0000000000]
2023-12-04T21:07:57.539567720+09:00 [INFO][AMF][Gmm] Handle event[Start Authentication], transition from [Deregistered] to [Authentication]
2023-12-04T21:07:57.539862177+09:00 [INFO][AMF][Gmm][amf_ue_ngap_id:RU:1,AU:1(3GPP)][supi:SUPI:] Authentication procedure
2023-12-04T21:07:57.540877631+09:00 [INFO][NRF][DISC] Handle NFDiscoveryRequest
2023-12-04T21:07:57.542149929+09:00 [INFO][NRF][GIN] | 200 |       127.0.0.1 | GET     | /nnrf-disc/v1/nf-instances?requester-nf-type=AMF&target-nf-type=AUSF |
2023-12-04T21:07:57.544218154+09:00 [INFO][AUSF][UeAuth] HandleUeAuthPostRequest
2023-12-04T21:07:57.544682025+09:00 [INFO][AUSF][UeAuth] Serving network authorized
2023-12-04T21:07:57.546448695+09:00 [INFO][NRF][DISC] Handle NFDiscoveryRequest
2023-12-04T21:07:57.548240624+09:00 [INFO][NRF][GIN] | 200 |       127.0.0.1 | GET     | /nnrf-disc/v1/nf-instances?requester-nf-type=AUSF&service-names=nudm-ueau&target-nf-type=UDM |
2023-12-04T21:07:57.549850247+09:00 [INFO][UDM][UEAU] Handle GenerateAuthDataRequest
2023-12-04T21:07:57.550083018+09:00 [INFO][UDM][Suci] suciPart: [suci 0 001 01 0000 0 0 0000000000]
2023-12-04T21:07:57.550255089+09:00 [INFO][UDM][Suci] scheme 0
2023-12-04T21:07:57.550582987+09:00 [INFO][UDM][Suci] SUPI type is IMSI
http://127.0.0.10:8000
2023-12-04T21:07:57.551652558+09:00 [INFO][NRF][DISC] Handle NFDiscoveryRequest
2023-12-04T21:07:57.552554062+09:00 [INFO][NRF][GIN] | 200 |       127.0.0.1 | GET     | /nnrf-disc/v1/nf-instances?requester-nf-type=UDM&target-nf-type=UDR |
2023-12-04T21:07:57.553470018+09:00 [INFO][UDR][DataRepo] Handle QueryAuthSubsData
2023-12-04T21:07:57.555117128+09:00 [INFO][UDR][GIN] | 200 |       127.0.0.1 | GET     | /nudr-dr/v1/subscription-data/imsi-001010000000000/authentication-data/authentication-subscription |
2023-12-04T21:07:57.555914337+09:00 [INFO][UDM][UEAU] Nil Op
2023-12-04T21:07:57.556576507+09:00 [INFO][UDR][DataRepo] Handle ModifyAuthentication
2023-12-04T21:07:57.558227160+09:00 [INFO][UDR][GIN] | 204 |       127.0.0.1 | PATCH   | /nudr-dr/v1/subscription-data/imsi-001010000000000/authentication-data/authentication-subscription |
2023-12-04T21:07:57.558765048+09:00 [INFO][UDM][GIN] | 200 |       127.0.0.1 | POST    | /nudm-ueau/v1/suci-0-001-01-0000-0-0-0000000000/security-information/generate-auth-data |
2023-12-04T21:07:57.558985521+09:00 [INFO][AUSF][UeAuth] Add SuciSupiPair (suci-0-001-01-0000-0-0-0000000000, imsi-001010000000000) to map.
2023-12-04T21:07:57.559022871+09:00 [INFO][AUSF][UeAuth] Use 5G AKA auth method
2023-12-04T21:07:57.559037949+09:00 [INFO][AUSF][5gAka] XresStar = 6137616430653836636164393736653133306563653333366566353639373761
2023-12-04T21:07:57.559122591+09:00 [INFO][AUSF][GIN] | 201 |       127.0.0.1 | POST    | /nausf-auth/v1/ue-authentications |
2023-12-04T21:07:57.559426193+09:00 [INFO][AMF][Gmm][amf_ue_ngap_id:RU:1,AU:1(3GPP)][supi:SUPI:] Send Authentication Request
2023-12-04T21:07:57.559507137+09:00 [INFO][AMF][Ngap][amf_ue_ngap_id:RU:1,AU:1(3GPP)][ran_addr:192.168.0.131:34534] Send Downlink Nas Transport
2023-12-04T21:07:57.559860487+09:00 [INFO][AMF][Gmm][amf_ue_ngap_id:RU:1,AU:1(3GPP)][supi:SUPI:] Start T3560 timer
2023-12-04T21:07:57.561701202+09:00 [INFO][AMF][Ngap][ran_addr:192.168.0.131:34534] Handle UplinkNASTransport
2023-12-04T21:07:57.561885127+09:00 [INFO][AMF][Ngap][amf_ue_ngap_id:RU:1,AU:1(3GPP)][ran_addr:192.168.0.131:34534] Handle UplinkNASTransport (RAN UE NGAP ID: 1)
2023-12-04T21:07:57.562117019+09:00 [INFO][AMF][Gmm] Handle event[Gmm Message], transition from [Authentication] to [Authentication]
2023-12-04T21:07:57.562318881+09:00 [INFO][AMF][Gmm][amf_ue_ngap_id:RU:1,AU:1(3GPP)][supi:SUPI:] Handle Authentication Response
2023-12-04T21:07:57.562551794+09:00 [INFO][AMF][Gmm][amf_ue_ngap_id:RU:1,AU:1(3GPP)][supi:SUPI:] Stop T3560 timer
2023-12-04T21:07:57.563387140+09:00 [INFO][AUSF][5gAka] Auth5gAkaComfirmRequest
2023-12-04T21:07:57.563412066+09:00 [INFO][AUSF][5gAka] res*: 6137616430653836636164393736653133306563653333366566353639373761
Xres*: 6137616430653836636164393736653133306563653333366566353639373761
2023-12-04T21:07:57.563451415+09:00 [INFO][AUSF][5gAka] 5G AKA confirmation succeeded
2023-12-04T21:07:57.563991542+09:00 [INFO][UDM][UEAU] Handle ConfirmAuthDataRequest
2023-12-04T21:07:57.564870949+09:00 [INFO][UDR][DataRepo] Handle CreateAuthenticationStatus
2023-12-04T21:07:57.566258354+09:00 [INFO][UDR][GIN] | 204 |       127.0.0.1 | PUT     | /nudr-dr/v1/subscription-data/imsi-001010000000000/authentication-data/authentication-status |
2023-12-04T21:07:57.566609715+09:00 [INFO][UDM][GIN] | 201 |       127.0.0.1 | POST    | /nudm-ueau/v1/imsi-001010000000000/auth-events |
2023-12-04T21:07:57.567052995+09:00 [INFO][AUSF][GIN] | 200 |       127.0.0.1 | PUT     | /nausf-auth/v1/ue-authentications/suci-0-001-01-0000-0-0-0000000000/5g-aka-confirmation |
2023-12-04T21:07:57.567573047+09:00 [INFO][AMF][Gmm] Handle event[Authentication Success], transition from [Authentication] to [SecurityMode]
2023-12-04T21:07:57.567637606+09:00 [INFO][AMF][Gmm][amf_ue_ngap_id:RU:1,AU:1(3GPP)][supi:SUPI:imsi-001010000000000] Send Security Mode Command
2023-12-04T21:07:57.567683450+09:00 [INFO][AMF][Ngap][amf_ue_ngap_id:RU:1,AU:1(3GPP)][ran_addr:192.168.0.131:34534] Send Downlink Nas Transport
2023-12-04T21:07:57.568408353+09:00 [INFO][AMF][Gmm][amf_ue_ngap_id:RU:1,AU:1(3GPP)][supi:SUPI:imsi-001010000000000] Start T3560 timer
2023-12-04T21:07:57.570080471+09:00 [INFO][AMF][Ngap][ran_addr:192.168.0.131:34534] Handle UplinkNASTransport
2023-12-04T21:07:57.571138352+09:00 [INFO][AMF][Ngap][amf_ue_ngap_id:RU:1,AU:1(3GPP)][ran_addr:192.168.0.131:34534] Handle UplinkNASTransport (RAN UE NGAP ID: 1)
2023-12-04T21:07:57.571527049+09:00 [INFO][AMF][Gmm] Handle event[Gmm Message], transition from [SecurityMode] to [SecurityMode]
2023-12-04T21:07:57.571736172+09:00 [INFO][AMF][Gmm][amf_ue_ngap_id:RU:1,AU:1(3GPP)][supi:SUPI:imsi-001010000000000] Handle Security Mode Complete
2023-12-04T21:07:57.571904089+09:00 [INFO][AMF][Gmm][amf_ue_ngap_id:RU:1,AU:1(3GPP)][supi:SUPI:imsi-001010000000000] Stop T3560 timer
2023-12-04T21:07:57.572164346+09:00 [INFO][AMF][Gmm] Handle event[SecurityMode Success], transition from [SecurityMode] to [ContextSetup]
2023-12-04T21:07:57.572344679+09:00 [INFO][AMF][Gmm][amf_ue_ngap_id:RU:1,AU:1(3GPP)][supi:SUPI:imsi-001010000000000] Handle InitialRegistration
2023-12-04T21:07:57.573154968+09:00 [INFO][NRF][DISC] Handle NFDiscoveryRequest
2023-12-04T21:07:57.574383304+09:00 [INFO][NRF][GIN] | 200 |       127.0.0.1 | GET     | /nnrf-disc/v1/nf-instances?requester-nf-type=AMF&supi=imsi-001010000000000&target-nf-type=UDM |
2023-12-04T21:07:57.575543541+09:00 [INFO][UDM][SDM] Handle GetNssai
2023-12-04T21:07:57.576002213+09:00 [INFO][UDR][DataRepo] Handle QueryAmData
2023-12-04T21:07:57.576535543+09:00 [INFO][UDR][GIN] | 200 |       127.0.0.1 | GET     | /nudr-dr/v1/subscription-data/imsi-001010000000000/00101/provisioned-data/am-data |
2023-12-04T21:07:57.576932450+09:00 [INFO][UDM][GIN] | 200 |       127.0.0.1 | GET     | /nudm-sdm/v1/imsi-001010000000000/nssai?plmn-id=%7B%22mcc%22%3A%22001%22%2C%22mnc%22%3A%2201%22%7D |
2023-12-04T21:07:57.577436446+09:00 [INFO][AMF][Gmm][amf_ue_ngap_id:RU:1,AU:1(3GPP)][supi:SUPI:imsi-001010000000000] RequestedNssai - ServingSnssai: &{Sst:1 Sd:010203}, HomeSnssai: <nil>
2023-12-04T21:07:57.578407143+09:00 [INFO][NRF][DISC] Handle NFDiscoveryRequest
2023-12-04T21:07:57.579698911+09:00 [INFO][NRF][GIN] | 200 |       127.0.0.1 | GET     | /nnrf-disc/v1/nf-instances?requester-nf-type=AMF&supi=imsi-001010000000000&target-nf-type=UDM |
2023-12-04T21:07:57.581036247+09:00 [INFO][UDM][UECM] Handle RegistrationAmf3gppAccess
2023-12-04T21:07:57.581244401+09:00 [INFO][UDM][UECM] UEID: imsi-001010000000000
2023-12-04T21:07:57.582293928+09:00 [INFO][UDR][DataRepo] Handle CreateAmfContext3gpp
2023-12-04T21:07:57.583279507+09:00 [INFO][UDR][GIN] | 204 |       127.0.0.1 | PUT     | /nudr-dr/v1/subscription-data/imsi-001010000000000/context-data/amf-3gpp-access |
2023-12-04T21:07:57.583781940+09:00 [INFO][UDM][GIN] | 201 |       127.0.0.1 | PUT     | /nudm-uecm/v1/imsi-001010000000000/registrations/amf-3gpp-access |
2023-12-04T21:07:57.584665003+09:00 [INFO][UDM][SDM] Handle GetAmData
2023-12-04T21:07:57.585059758+09:00 [INFO][UDR][DataRepo] Handle QueryAmData
2023-12-04T21:07:57.585517010+09:00 [INFO][UDR][GIN] | 200 |       127.0.0.1 | GET     | /nudr-dr/v1/subscription-data/imsi-001010000000000/00101/provisioned-data/am-data?supported-features=%7B%22mcc%22%3A%22001%22%2C%22mnc%22%3A%2201%22%7D |
2023-12-04T21:07:57.586123075+09:00 [INFO][UDM][GIN] | 200 |       127.0.0.1 | GET     | /nudm-sdm/v1/imsi-001010000000000/am-data?plmn-id=%7B%22mcc%22%3A%22001%22%2C%22mnc%22%3A%2201%22%7D |
2023-12-04T21:07:57.586689659+09:00 [INFO][UDM][SDM] Handle GetSmfSelectData
2023-12-04T21:07:57.587501134+09:00 [INFO][UDR][DataRepo] Handle QuerySmfSelectData
2023-12-04T21:07:57.588038454+09:00 [INFO][UDR][GIN] | 200 |       127.0.0.1 | GET     | /nudr-dr/v1/subscription-data/imsi-001010000000000/00101/provisioned-data/smf-selection-subscription-data |
2023-12-04T21:07:57.588612294+09:00 [INFO][UDM][GIN] | 200 |       127.0.0.1 | GET     | /nudm-sdm/v1/imsi-001010000000000/smf-select-data?plmn-id=%7B%22mcc%22%3A%22001%22%2C%22mnc%22%3A%2201%22%7D |
2023-12-04T21:07:57.589089037+09:00 [INFO][UDM][SDM] Handle GetUeContextInSmfData
2023-12-04T21:07:57.589575420+09:00 [INFO][UDR][DataRepo] Handle QuerySmfRegList
2023-12-04T21:07:57.590055797+09:00 [INFO][UDR][GIN] | 200 |       127.0.0.1 | GET     | /nudr-dr/v1/subscription-data/imsi-001010000000000/context-data/smf-registrations |
2023-12-04T21:07:57.590643305+09:00 [INFO][UDM][GIN] | 200 |       127.0.0.1 | GET     | /nudm-sdm/v1/imsi-001010000000000/ue-context-in-smf-data |
2023-12-04T21:07:57.591250696+09:00 [INFO][UDM][SDM] Handle Subscribe
2023-12-04T21:07:57.592189194+09:00 [INFO][UDR][DataRepo] Handle CreateSdmSubscriptions
2023-12-04T21:07:57.592434294+09:00 [INFO][UDR][GIN] | 201 |       127.0.0.1 | POST    | /nudr-dr/v1/subscription-data/imsi-001010000000000/context-data/sdm-subscriptions |
2023-12-04T21:07:57.592941270+09:00 [INFO][UDM][GIN] | 201 |       127.0.0.1 | POST    | /nudm-sdm/v1/imsi-001010000000000/sdm-subscriptions |
2023-12-04T21:07:57.593790406+09:00 [INFO][NRF][DISC] Handle NFDiscoveryRequest
2023-12-04T21:07:57.595483839+09:00 [INFO][NRF][GIN] | 200 |       127.0.0.1 | GET     | /nnrf-disc/v1/nf-instances?preferred-locality=area1&requester-nf-type=AMF&supi=imsi-001010000000000&target-nf-type=PCF |
2023-12-04T21:07:57.597189519+09:00 [INFO][PCF][AmPol] Handle AM Policy Create Request
2023-12-04T21:07:57.598083251+09:00 [INFO][NRF][DISC] Handle NFDiscoveryRequest
2023-12-04T21:07:57.598923272+09:00 [INFO][NRF][GIN] | 200 |       127.0.0.1 | GET     | /nnrf-disc/v1/nf-instances?requester-nf-type=PCF&target-nf-type=UDR |
2023-12-04T21:07:57.600222464+09:00 [INFO][UDR][DataRepo] Handle PolicyDataUesUeIdAmDataGet
2023-12-04T21:07:57.600963656+09:00 [INFO][UDR][GIN] | 200 |       127.0.0.1 | GET     | /nudr-dr/v1/policy-data/ues/imsi-001010000000000/am-data |
2023-12-04T21:07:57.602105680+09:00 [INFO][NRF][DISC] Handle NFDiscoveryRequest
2023-12-04T21:07:57.603502857+09:00 [INFO][NRF][GIN] | 200 |       127.0.0.1 | GET     | /nnrf-disc/v1/nf-instances?guami=%7B%22plmnId%22%3A%7B%22mcc%22%3A%22001%22%2C%22mnc%22%3A%2201%22%7D%2C%22amfId%22%3A%22cafe00%22%7D&requester-nf-type=PCF&target-nf-type=AMF |
2023-12-04T21:07:57.604508950+09:00 [INFO][AMF][Comm] Handle AMF Status Change Subscribe Request
2023-12-04T21:07:57.604792415+09:00 [INFO][AMF][Comm] new AMF Status Subscription[1]
2023-12-04T21:07:57.605151883+09:00 [INFO][AMF][GIN] | 201 |       127.0.0.1 | POST    | /namf-comm/v1/subscriptions |
2023-12-04T21:07:57.605577020+09:00 [INFO][PCF][GIN] | 201 |       127.0.0.1 | POST    | /npcf-am-policy-control/v1/policies |
2023-12-04T21:07:57.606116573+09:00 [INFO][AMF][Gmm][amf_ue_ngap_id:RU:1,AU:1(3GPP)][supi:SUPI:imsi-001010000000000] Send Registration Accept
2023-12-04T21:07:57.606366509+09:00 [INFO][AMF][Ngap][amf_ue_ngap_id:RU:1,AU:1(3GPP)][ran_addr:192.168.0.131:34534] Send Initial Context Setup Request
2023-12-04T21:07:57.607740600+09:00 [INFO][AMF][Gmm][amf_ue_ngap_id:RU:1,AU:1(3GPP)][supi:SUPI:imsi-001010000000000] Start T3550 timer
2023-12-04T21:07:57.608636043+09:00 [INFO][AMF][Ngap][ran_addr:192.168.0.131:34534] Handle InitialContextSetupResponse
2023-12-04T21:07:57.608912031+09:00 [INFO][AMF][Ngap][amf_ue_ngap_id:RU:1,AU:1(3GPP)][ran_addr:192.168.0.131:34534] Handle InitialContextSetupResponse (RAN UE NGAP ID: 1)
2023-12-04T21:07:57.813456928+09:00 [INFO][AMF][Ngap][ran_addr:192.168.0.131:34534] Handle UplinkNASTransport
2023-12-04T21:07:57.813958829+09:00 [INFO][AMF][Ngap][amf_ue_ngap_id:RU:1,AU:1(3GPP)][ran_addr:192.168.0.131:34534] Handle UplinkNASTransport (RAN UE NGAP ID: 1)
2023-12-04T21:07:57.814640365+09:00 [INFO][AMF][Gmm] Handle event[Gmm Message], transition from [ContextSetup] to [ContextSetup]
2023-12-04T21:07:57.815021329+09:00 [INFO][AMF][Gmm][amf_ue_ngap_id:RU:1,AU:1(3GPP)][supi:SUPI:imsi-001010000000000] Handle Registration Complete
2023-12-04T21:07:57.815643929+09:00 [INFO][AMF][Gmm][amf_ue_ngap_id:RU:1,AU:1(3GPP)][supi:SUPI:imsi-001010000000000] Stop T3550 timer
2023-12-04T21:07:57.816063716+09:00 [INFO][AMF][Gmm][amf_ue_ngap_id:RU:1,AU:1(3GPP)][supi:SUPI:imsi-001010000000000] Send Configuration Update Command
2023-12-04T21:07:57.816624288+09:00 [INFO][AMF][Ngap][amf_ue_ngap_id:RU:1,AU:1(3GPP)][ran_addr:192.168.0.131:34534] Send Downlink Nas Transport
2023-12-04T21:07:57.818451868+09:00 [INFO][AMF][Gmm] Handle event[ContextSetup Success], transition from [ContextSetup] to [Registered]
2023-12-04T21:07:57.819842811+09:00 [INFO][AMF][Ngap][ran_addr:192.168.0.131:34534] Handle UplinkNASTransport
2023-12-04T21:07:57.820064034+09:00 [INFO][AMF][Ngap][amf_ue_ngap_id:RU:1,AU:1(3GPP)][ran_addr:192.168.0.131:34534] Handle UplinkNASTransport (RAN UE NGAP ID: 1)
2023-12-04T21:07:57.820460206+09:00 [INFO][AMF][Gmm] Handle event[Gmm Message], transition from [Registered] to [Registered]
2023-12-04T21:07:57.820654572+09:00 [INFO][AMF][Gmm][amf_ue_ngap_id:RU:1,AU:1(3GPP)][supi:SUPI:imsi-001010000000000] Handle UL NAS Transport
2023-12-04T21:07:57.820845611+09:00 [INFO][AMF][Gmm][amf_ue_ngap_id:RU:1,AU:1(3GPP)][supi:SUPI:imsi-001010000000000] Transport 5GSM Message to SMF
2023-12-04T21:07:57.821075405+09:00 [INFO][AMF][Gmm][amf_ue_ngap_id:RU:1,AU:1(3GPP)][supi:SUPI:imsi-001010000000000] Select SMF [snssai: {Sst:1 Sd:010203}, dnn: internet]
2023-12-04T21:07:57.823468344+09:00 [INFO][NRF][DISC] Handle NFDiscoveryRequest
2023-12-04T21:07:57.825527878+09:00 [INFO][NRF][GIN] | 200 |       127.0.0.1 | GET     | /nnrf-disc/v1/nf-instances?requester-nf-type=AMF&target-nf-type=NSSF |
2023-12-04T21:07:57.827162899+09:00 [INFO][NSSF][NsSel] Handle NSSelectionGet
2023-12-04T21:07:57.827741344+09:00 [INFO][NSSF][GIN] | 200 |       127.0.0.1 | GET     | /nnssf-nsselection/v1/network-slice-information?nf-id=fdbf2175-1724-422c-9c30-8e6bc69d9536&nf-type=AMF&slice-info-request-for-pdu-session=%7B%22sNssai%22%3A%7B%22sst%22%3A1%2C%22sd%22%3A%22010203%22%7D%2C%22roamingIndication%22%3A%22NON_ROAMING%22%7D |
2023-12-04T21:07:57.829053778+09:00 [INFO][NRF][DISC] Handle NFDiscoveryRequest
2023-12-04T21:07:57.830510530+09:00 [INFO][NRF][GIN] | 200 |       127.0.0.1 | GET     | /nnrf-disc/v1/nf-instances?dnn=internet&preferred-locality=area1&requester-nf-type=AMF&service-names=nsmf-pdusession&snssais=%7B%22sst%22%3A1%2C%22sd%22%3A%22010203%22%7D&target-nf-type=SMF&target-plmn-list=%7B%22mcc%22%3A%22001%22%2C%22mnc%22%3A%2201%22%7D |
2023-12-04T21:07:57.831769318+09:00 [INFO][SMF][PduSess] Receive Create SM Context Request
2023-12-04T21:07:57.832731036+09:00 [INFO][SMF][PduSess] In HandlePDUSessionSMContextCreate
2023-12-04T21:07:57.832981733+09:00 [INFO][SMF][CTX] UrrPeriod: 10s
2023-12-04T21:07:57.833152733+09:00 [INFO][SMF][CTX] UrrThreshold: 1000
2023-12-04T21:07:57.833824824+09:00 [INFO][NRF][DISC] Handle NFDiscoveryRequest
2023-12-04T21:07:57.835446377+09:00 [INFO][NRF][GIN] | 200 |       127.0.0.1 | GET     | /nnrf-disc/v1/nf-instances?requester-nf-type=SMF&target-nf-type=UDM |
2023-12-04T21:07:57.836438810+09:00 [INFO][SMF][PduSess][pdu_session_id:1][supi:imsi-001010000000000] Send NF Discovery Serving UDM Successfully
2023-12-04T21:07:57.838295116+09:00 [INFO][UDM][SDM] Handle GetSmData
2023-12-04T21:07:57.838449962+09:00 [INFO][UDM][SDM] getSmDataProcedure: SUPI[imsi-001010000000000] PLMNID[00101] DNN[internet] SNssai[{"sst":1,"sd":"010203"}]
2023-12-04T21:07:57.838926455+09:00 [INFO][UDR][DataRepo] Handle QuerySmData
2023-12-04T21:07:57.839879563+09:00 [INFO][UDR][GIN] | 200 |       127.0.0.1 | GET     | /nudr-dr/v1/subscription-data/imsi-001010000000000/00101/provisioned-data/sm-data?single-nssai=%7B%22sst%22%3A1%2C%22sd%22%3A%22010203%22%7D |
2023-12-04T21:07:57.840561500+09:00 [INFO][UDM][GIN] | 200 |       127.0.0.1 | GET     | /nudm-sdm/v1/imsi-001010000000000/sm-data?dnn=internet&plmn-id=%7B%22mcc%22%3A%22001%22%2C%22mnc%22%3A%2201%22%7D&single-nssai=%7B%22sst%22%3A1%2C%22sd%22%3A%22010203%22%7D |
2023-12-04T21:07:57.841107574+09:00 [INFO][SMF][GSM] In HandlePDUSessionEstablishmentRequest
2023-12-04T21:07:57+09:00 [INFO][NAS][Convert] ProtocolOrContainerList:  [0xc000308c20 0xc000308c40]
2023-12-04T21:07:57.841589003+09:00 [INFO][SMF][GSM] Protocol Configuration Options
2023-12-04T21:07:57.841772114+09:00 [INFO][SMF][GSM] &{[0xc000308c20 0xc000308c40]}
2023-12-04T21:07:57.841955189+09:00 [INFO][SMF][GSM] Didn't Implement container type IPAddressAllocationViaNASSignallingUL
2023-12-04T21:07:57.842975776+09:00 [INFO][NRF][DISC] Handle NFDiscoveryRequest
2023-12-04T21:07:57.844564309+09:00 [INFO][NRF][GIN] | 200 |       127.0.0.1 | GET     | /nnrf-disc/v1/nf-instances?requester-nf-type=SMF&target-nf-instance-id=fdbf2175-1724-422c-9c30-8e6bc69d9536&target-nf-type=AMF |
2023-12-04T21:07:57.844948125+09:00 [INFO][SMF][Consumer] SendNFDiscoveryServingAMF ok
2023-12-04T21:07:57.845251405+09:00 [INFO][SMF][CTX] Allocated UE IP address: 10.60.0.1
2023-12-04T21:07:57.845532126+09:00 [INFO][SMF][CTX] Selected UPF: UPF
2023-12-04T21:07:57.845760012+09:00 [INFO][SMF][PduSess][pdu_session_id:1][supi:imsi-001010000000000] Allocated PDUAdress[10.60.0.1]
2023-12-04T21:07:57.846618547+09:00 [INFO][NRF][DISC] Handle NFDiscoveryRequest
2023-12-04T21:07:57.847781077+09:00 [INFO][NRF][GIN] | 200 |       127.0.0.1 | GET     | /nnrf-disc/v1/nf-instances?preferred-locality=area1&requester-nf-type=SMF&target-nf-type=PCF |
2023-12-04T21:07:57.849166912+09:00 [INFO][PCF][SMpolicy] Handle CreateSmPolicy
2023-12-04T21:07:57.849890205+09:00 [INFO][UDR][DataRepo] Handle PolicyDataUesUeIdSmDataGet
2023-12-04T21:07:57.851403862+09:00 [INFO][UDR][GIN] | 200 |       127.0.0.1 | GET     | /nudr-dr/v1/policy-data/ues/imsi-001010000000000/sm-data?dnn=internet&snssai=%7B%22sst%22%3A1%2C%22sd%22%3A%22010203%22%7D |
2023-12-04T21:07:57.854111346+09:00 [INFO][UDR][DataRepo] Handle ApplicationDataInfluenceDataGet
2023-12-04T21:07:57.854823554+09:00 [INFO][UDR][GIN] | 200 |       127.0.0.1 | GET     | /nudr-dr/v1/application-data/influenceData?dnns=internet&internal-Group-Ids=&snssais=%7B%22sst%22%3A1%2C%22sd%22%3A%22010203%22%7D&supis=imsi-001010000000000 |
2023-12-04T21:07:57.855135836+09:00 [INFO][PCF][SMpolicy] Matched [0] trafficInfluDatas from UDR
2023-12-04T21:07:57.855675483+09:00 [INFO][UDR][DataRepo] Handle ApplicationDataInfluenceDataSubsToNotifyPost
2023-12-04T21:07:57.855860764+09:00 [INFO][UDR][GIN] | 201 |       127.0.0.1 | POST    | /nudr-dr/v1/application-data/influenceData/subs-to-notify |
2023-12-04T21:07:57.856990995+09:00 [INFO][NRF][DISC] Handle NFDiscoveryRequest
2023-12-04T21:07:57.857531212+09:00 [INFO][NRF][GIN] | 200 |       127.0.0.1 | GET     | /nnrf-disc/v1/nf-instances?requester-nf-type=PCF&target-nf-type=BSF |
2023-12-04T21:07:57.860622294+09:00 [INFO][PCF][GIN] | 201 |       127.0.0.1 | POST    | /npcf-smpolicycontrol/v1/sm-policies |
2023-12-04T21:07:57.862263568+09:00 [INFO][SMF][PduSess][pdu_session_id:1][supi:imsi-001010000000000] Has no pre-config route
2023-12-04T21:07:57.864525693+09:00 [WARN][SMF][PduSess] Create URR
2023-12-04T21:07:57.864709456+09:00 [WARN][SMF][PduSess] Create URR
2023-12-04T21:07:57.864884492+09:00 [INFO][SMF][PduSess][pdu_session_id:1][supi:imsi-001010000000000] Install PCCRule[PccRuleId-1]
2023-12-04T21:07:57.865068493+09:00 [INFO][SMF][PduSess][pdu_session_id:1][supi:imsi-001010000000000] No srcTcData and tgtTcData. Nothing to do
2023-12-04T21:07:57.865391801+09:00 [INFO][SMF][GIN] | 201 |       127.0.0.1 | POST    | /nsmf-pdusession/v1/sm-contexts |
2023-12-04T21:07:57.865781389+09:00 [INFO][SMF][PduSess] Sending PFCP Session Establishment Request
2023-12-04T21:07:57.866588348+09:00 [INFO][AMF][Gmm][amf_ue_ngap_id:RU:1,AU:1(3GPP)][supi:SUPI:imsi-001010000000000] create smContext[pduSessionID: 1] Success
2023-12-04T21:07:57.881287904+09:00 [INFO][SMF][PduSess] Received PFCP Session Establishment Accepted Response
2023-12-04T21:07:57.884623352+09:00 [INFO][AMF][Producer] Handle N1N2 Message Transfer Request
2023-12-04T21:07:57.884844705+09:00 [INFO][AMF][Ngap][amf_ue_ngap_id:RU:1,AU:1(3GPP)][ran_addr:192.168.0.131:34534] Send PDU Session Resource Setup Request
2023-12-04T21:07:57.885811325+09:00 [INFO][AMF][GIN] | 200 |       127.0.0.1 | POST    | /namf-comm/v1/ue-contexts/imsi-001010000000000/n1-n2-messages |
2023-12-04T21:07:57.928568267+09:00 [INFO][AMF][Ngap][ran_addr:192.168.0.131:34534] Handle PDUSessionResourceSetupResponse
2023-12-04T21:07:57.928983548+09:00 [INFO][AMF][Ngap][amf_ue_ngap_id:RU:1,AU:1(3GPP)][ran_addr:192.168.0.131:34534] Handle PDUSessionResourceSetupResponse (RAN UE NGAP ID: 1)
2023-12-04T21:07:57.930895028+09:00 [INFO][SMF][PduSess] Receive Update SM Context Request
2023-12-04T21:07:57.941033883+09:00 [INFO][SMF][PduSess] Received PFCP Session Modification Accepted Response from AN UPF
2023-12-04T21:07:57.941511455+09:00 [INFO][SMF][GIN] | 200 |       127.0.0.1 | POST    | /nsmf-pdusession/v1/sm-contexts/urn:uuid:25cea406-5a36-4817-a5e7-3c68bacbc89e/modify |

eUPFのPDUセッション確立のログは以下の通りです。

2023/12/04 21:07:57 INF Got Session Establishment Request from: 192.168.14.141.
2023/12/04 21:07:57 INF 
Session Establishment Request:
  CreatePDR ID: 1 
    Outer Header Removal: 0 
    FAR ID: 1 
    QER ID: 2 
    QER ID: 1 
    URR ID: 1 
    Source Interface: 0 
    TEID: 1 
    Ipv4: 192.168.13.151 
    Ipv6: <nil> 
    UE IPv4 Address: 10.60.0.1 
  CreatePDR ID: 2 
    FAR ID: 2 
    QER ID: 2 
    QER ID: 1 
    URR ID: 1 
    Source Interface: 2 
    UE IPv4 Address: 10.60.0.1 
  CreatePDR ID: 3 
    Outer Header Removal: 0 
    FAR ID: 3 
    QER ID: 1 
    QER ID: 3 
    URR ID: 1 
    Source Interface: 0 
    TEID: 1 
    Ipv4: 192.168.13.151 
    Ipv6: <nil> 
    UE IPv4 Address: 10.60.0.1 
    SDF Filter: permit out ip from 10.60.0.0/16 to any 
  CreatePDR ID: 4 
    FAR ID: 4 
    QER ID: 1 
    QER ID: 3 
    URR ID: 1 
    Source Interface: 2 
    UE IPv4 Address: 10.60.0.1 
    SDF Filter: permit out ip from any to 10.60.0.0/16 
  CreateFAR ID: 1 
    Apply Action: [2] 
    Forwarding Parameters:
      Network Instance:internet 
  CreateFAR ID: 2 
    Apply Action: [2] 
    Forwarding Parameters:
  CreateFAR ID: 3 
    Apply Action: [2] 
    Forwarding Parameters:
      Network Instance:internet 
  CreateFAR ID: 4 
    Apply Action: [2] 
    Forwarding Parameters:
  CreateQER ID: 2 
    Gate Status DL: 0 
    Gate Status UL: 0 
    QFI: 1 
  CreateQER ID: 1 
    Gate Status DL: 0 
    Gate Status UL: 0 
    Max Bitrate DL: 1000000 
    Max Bitrate UL: 1000000 
    QFI: 0 
  CreateQER ID: 3 
    Gate Status DL: 0 
    Gate Status UL: 0 
    QFI: 2 
  CreateURR ID: 1 
    Measurement Method: 2 
    Volume Threshold: &{Flags:6 TotalVolume:0 UplinkVolume:1000 DownlinkVolume:1000} 
  CreateURR ID: 2 
    Measurement Method: 2 
    Volume Threshold: &{Flags:6 TotalVolume:0 UplinkVolume:1000 DownlinkVolume:1000} 

2023/12/04 21:07:57 INF WARN: No OuterHeaderCreation
2023/12/04 21:07:57 INF Saving FAR info to session: 1, {Action:2 OuterHeaderCreation:0 Teid:0 RemoteIP:0 LocalIP:2534254784 TransportLevelMarking:0}
2023/12/04 21:07:57 INF WARN: No OuterHeaderCreation
2023/12/04 21:07:57 INF Saving FAR info to session: 2, {Action:2 OuterHeaderCreation:0 Teid:0 RemoteIP:0 LocalIP:2534254784 TransportLevelMarking:0}
2023/12/04 21:07:57 INF WARN: No OuterHeaderCreation
2023/12/04 21:07:57 INF Saving FAR info to session: 3, {Action:2 OuterHeaderCreation:0 Teid:0 RemoteIP:0 LocalIP:2534254784 TransportLevelMarking:0}
2023/12/04 21:07:57 INF WARN: No OuterHeaderCreation
2023/12/04 21:07:57 INF Saving FAR info to session: 4, {Action:2 OuterHeaderCreation:0 Teid:0 RemoteIP:0 LocalIP:2534254784 TransportLevelMarking:0}
2023/12/04 21:07:57 INF Saving QER info to session: 2, {GateStatusUL:0 GateStatusDL:0 Qfi:1 MaxBitrateUL:0 MaxBitrateDL:0 StartUL:0 StartDL:0}
2023/12/04 21:07:57 INF Saving QER info to session: 1, {GateStatusUL:0 GateStatusDL:0 Qfi:0 MaxBitrateUL:1000000000 MaxBitrateDL:1000000000 StartUL:0 StartDL:0}
2023/12/04 21:07:57 INF Saving QER info to session: 3, {GateStatusUL:0 GateStatusDL:0 Qfi:2 MaxBitrateUL:0 MaxBitrateDL:0 StartUL:0 StartDL:0}
2023/12/04 21:07:57 Matched groups: [permit out ip from 10.60.0.0/16 to any ip 10.60.0.0 16  any  ]
2023/12/04 21:07:57 Matched groups: [permit out ip from any to 10.60.0.0/16 ip any   10.60.0.0 16 ]
2023/12/04 21:07:57 INF Session Establishment Request from 192.168.14.141 accepted.
2023/12/04 21:07:57 INF Got Session Modification Request from: 192.168.14.141. 

2023/12/04 21:07:57 INF Finding association for 192.168.14.141
2023/12/04 21:07:57 INF Finding session 2
2023/12/04 21:07:57 INF 
Session Modification Request:
  UpdatePDR ID: 2 
    FAR ID: 2 
    Source Interface: 2 
    UE IPv4 Address: 10.60.0.1 
  UpdatePDR ID: 4 
    FAR ID: 4 
    Source Interface: 2 
    UE IPv4 Address: 10.60.0.1 
    SDF Filter: permit out ip from any to 10.60.0.0/16 
  UpdateFAR ID: 2 
    Apply Action: [2] 
    Update forwarding Parameters:
      Network Instance:internet 
      Outer Header Creation: &{OuterHeaderCreationDescription:256 TEID:1 IPv4Address:192.168.13.131 IPv6Address:<nil> PortNumber:0 CTag:0 STag:0} 
  UpdateFAR ID: 4 
    Apply Action: [2] 
    Update forwarding Parameters:
      Network Instance:internet 
      Outer Header Creation: &{OuterHeaderCreationDescription:256 TEID:1 IPv4Address:192.168.13.131 IPv6Address:<nil> PortNumber:0 CTag:0 STag:0} 

2023/12/04 21:07:57 INF Updating FAR info: 2, {FarInfo:{Action:2 OuterHeaderCreation:1 Teid:1 RemoteIP:2198710464 LocalIP:2534254784 TransportLevelMarking:0} GlobalId:1}
2023/12/04 21:07:57 INF Updating FAR info: 4, {FarInfo:{Action:2 OuterHeaderCreation:1 Teid:1 RemoteIP:2198710464 LocalIP:2534254784 TransportLevelMarking:0} GlobalId:3}
2023/12/04 21:07:57 INF Both F-TEID IE and UE IP Address IE are missing
2023/12/04 21:07:57 INF Both F-TEID IE and UE IP Address IE are missing

nr-ueコマンドのコンソールログから、free5GC 5GCからIPアドレス10.60.0.1がUEに割り当てられたことが分かります。

[2023-12-04 21:07:57.953] [app] [info] Connection setup for PDU session[1] is successful, TUN interface[uesimtun0, 10.60.0.1] is up.

念のため、UEのTUNインターフェースに割り当てられたIPアドレスと一致していることを確認して下さい。

# ip addr show
...
5: uesimtun0: <POINTOPOINT,PROMISC,NOTRAILERS,UP,LOWER_UP> mtu 1400 qdisc fq_codel state UNKNOWN group default qlen 500
    link/none 
    inet 10.60.0.1/32 scope global uesimtun0
       valid_lft forever preferred_lft forever
    inet6 fe80::6992:6a38:50cb:112c/64 scope link stable-privacy 
       valid_lft forever preferred_lft forever
...

google.comにpingする

UEのTUNインターフェースを指定して、pingしてみます。

TUNインターフェースの使い方は以下を参照して下さい。

DN=10.60.0.0/16を経由する場合

VM-DNでtcpdumpを実行し、パケットがN6インターフェースenp0s9を通過することを確認します。

  • VM3(UE)でping google.com 
# ping google.com -I uesimtun0 -n
PING google.com (142.251.222.46) from 10.60.0.1 uesimtun0: 56(84) bytes of data.
64 bytes from 142.251.222.46: icmp_seq=1 ttl=61 time=19.8 ms
64 bytes from 142.251.222.46: icmp_seq=2 ttl=61 time=18.8 ms
64 bytes from 142.251.222.46: icmp_seq=3 ttl=61 time=19.1 ms
  • VM-DNでtcpdumpを実行
# tcpdump -i enp0s9 -n
tcpdump: verbose output suppressed, use -v[v]... for full protocol decode
listening on enp0s9, link-type EN10MB (Ethernet), snapshot length 262144 bytes
21:12:08.597345 IP 10.60.0.1 > 142.251.222.46: ICMP echo request, id 2, seq 1, length 64
21:12:08.614931 IP 142.251.222.46 > 10.60.0.1: ICMP echo reply, id 2, seq 1, length 64
21:12:09.598169 IP 10.60.0.1 > 142.251.222.46: ICMP echo request, id 2, seq 2, length 64
21:12:09.615155 IP 142.251.222.46 > 10.60.0.1: ICMP echo reply, id 2, seq 2, length 64
21:12:10.598976 IP 10.60.0.1 > 142.251.222.46: ICMP echo request, id 2, seq 3, length 64
21:12:10.616388 IP 142.251.222.46 > 10.60.0.1: ICMP echo reply, id 2, seq 3, length 64
  • VM-UPで/sys/kernel/debug/tracing/trace_pipeを確認
# cat /sys/kernel/debug/tracing/trace_pipe
...
          <idle>-0       [000] d.s31  3740.908049: bpf_trace_printk: upf: gtp-u received
          <idle>-0       [000] d.s31  3740.908054: bpf_trace_printk: SDF: filter protocol: 1
          <idle>-0       [000] d.s31  3740.908059: bpf_trace_printk: SDF: filter source ip: 10.60.0.0, destination ip: 0.0.0.0
          <idle>-0       [000] d.s31  3740.908061: bpf_trace_printk: SDF: filter source ip mask: 255.255.0.0, destination ip mask: 0.0.0.0
          <idle>-0       [000] d.s31  3740.908063: bpf_trace_printk: SDF: filter source port lower bound: 0, source port upper bound: 65535
          <idle>-0       [000] d.s31  3740.908064: bpf_trace_printk: SDF: filter destination port lower bound: 0, destination port upper bound: 65535
          <idle>-0       [000] d.s31  3740.908065: bpf_trace_printk: SDF: packet protocol: 0
          <idle>-0       [000] d.s31  3740.908068: bpf_trace_printk: SDF: packet source ip: 10.60.0.1, destination ip: 142.251.222.46
          <idle>-0       [000] d.s31  3740.908069: bpf_trace_printk: SDF: packet source port: 0, destination port: 0
          <idle>-0       [000] d.s31  3740.908071: bpf_trace_printk: Packet with source ip: 10.60.0.1, destination ip: 142.251.222.46 matches SDF filter
          <idle>-0       [000] d.s31  3740.908073: bpf_trace_printk: upf: sdf filter matches teid:1
          <idle>-0       [000] d.s31  3740.908074: bpf_trace_printk: upf: far:2 action:2 outer_header_creation:0
          <idle>-0       [000] d.s31  3740.908076: bpf_trace_printk: upf: qer:1 gate_status:0 mbr:1000000000
          <idle>-0       [000] d.s31  3740.908078: bpf_trace_printk: upf: session for teid:1 far:0 outer_header_removal:0
          <idle>-0       [000] d.s31  3740.908088: bpf_trace_printk: upf: bpf_fib_lookup 10.60.0.1 -> 142.251.222.46: nexthop: 192.168.16.152
          <idle>-0       [000] d.s31  3740.926087: bpf_trace_printk: SDF: filter protocol: 1
          <idle>-0       [000] d.s31  3740.926093: bpf_trace_printk: SDF: filter source ip: 0.0.0.0, destination ip: 10.60.0.0
          <idle>-0       [000] d.s31  3740.926096: bpf_trace_printk: SDF: filter source ip mask: 0.0.0.0, destination ip mask: 255.255.0.0
          <idle>-0       [000] d.s31  3740.926098: bpf_trace_printk: SDF: filter source port lower bound: 0, source port upper bound: 65535
          <idle>-0       [000] d.s31  3740.926100: bpf_trace_printk: SDF: filter destination port lower bound: 0, destination port upper bound: 65535
          <idle>-0       [000] d.s31  3740.926101: bpf_trace_printk: SDF: packet protocol: 0
          <idle>-0       [000] d.s31  3740.926104: bpf_trace_printk: SDF: packet source ip: 142.251.222.46, destination ip: 10.60.0.1
          <idle>-0       [000] d.s31  3740.926105: bpf_trace_printk: SDF: packet source port: 0, destination port: 0
          <idle>-0       [000] d.s31  3740.926108: bpf_trace_printk: Packet with source ip: 142.251.222.46, destination ip: 10.60.0.1 matches SDF filter
          <idle>-0       [000] d.s31  3740.926111: bpf_trace_printk: Packet with source ip:142.251.222.46 and destination ip:10.60.0.1 matches SDF filter
          <idle>-0       [000] d.s31  3740.926114: bpf_trace_printk: upf: downlink session for ip:10.60.0.1  far:3 action:2
          <idle>-0       [000] d.s31  3740.926116: bpf_trace_printk: upf: qer:1 gate_status:0 mbr:1000000000
          <idle>-0       [000] d.s31  3740.926118: bpf_trace_printk: upf: use mapping 10.60.0.1 -> TEID:1
          <idle>-0       [000] d.s31  3740.926122: bpf_trace_printk: upf: send gtp pdu 192.168.13.151 -> 192.168.13.131
          <idle>-0       [000] d.s31  3740.926131: bpf_trace_printk: upf: bpf_fib_lookup 192.168.13.151 -> 192.168.13.131: nexthop: 192.168.13.131
          <idle>-0       [000] d.s31  3741.908769: bpf_trace_printk: upf: gtp-u received
          <idle>-0       [000] d.s31  3741.908777: bpf_trace_printk: SDF: filter protocol: 1
          <idle>-0       [000] d.s31  3741.908783: bpf_trace_printk: SDF: filter source ip: 10.60.0.0, destination ip: 0.0.0.0
          <idle>-0       [000] d.s31  3741.908786: bpf_trace_printk: SDF: filter source ip mask: 255.255.0.0, destination ip mask: 0.0.0.0
          <idle>-0       [000] d.s31  3741.908789: bpf_trace_printk: SDF: filter source port lower bound: 0, source port upper bound: 65535
          <idle>-0       [000] d.s31  3741.908791: bpf_trace_printk: SDF: filter destination port lower bound: 0, destination port upper bound: 65535
          <idle>-0       [000] d.s31  3741.908792: bpf_trace_printk: SDF: packet protocol: 0
          <idle>-0       [000] d.s31  3741.908795: bpf_trace_printk: SDF: packet source ip: 10.60.0.1, destination ip: 142.251.222.46
          <idle>-0       [000] d.s31  3741.908796: bpf_trace_printk: SDF: packet source port: 0, destination port: 0
          <idle>-0       [000] d.s31  3741.908801: bpf_trace_printk: Packet with source ip: 10.60.0.1, destination ip: 142.251.222.46 matches SDF filter
          <idle>-0       [000] d.s31  3741.908802: bpf_trace_printk: upf: sdf filter matches teid:1
          <idle>-0       [000] d.s31  3741.908805: bpf_trace_printk: upf: far:2 action:2 outer_header_creation:0
          <idle>-0       [000] d.s31  3741.908807: bpf_trace_printk: upf: qer:1 gate_status:0 mbr:1000000000
          <idle>-0       [000] d.s31  3741.908809: bpf_trace_printk: upf: session for teid:1 far:0 outer_header_removal:0
          <idle>-0       [000] d.s31  3741.908886: bpf_trace_printk: upf: bpf_fib_lookup 10.60.0.1 -> 142.251.222.46: nexthop: 192.168.16.152
          <idle>-0       [000] d.s31  3741.926186: bpf_trace_printk: SDF: filter protocol: 1
          <idle>-0       [000] d.s31  3741.926191: bpf_trace_printk: SDF: filter source ip: 0.0.0.0, destination ip: 10.60.0.0
          <idle>-0       [000] d.s31  3741.926193: bpf_trace_printk: SDF: filter source ip mask: 0.0.0.0, destination ip mask: 255.255.0.0
          <idle>-0       [000] d.s31  3741.926195: bpf_trace_printk: SDF: filter source port lower bound: 0, source port upper bound: 65535
          <idle>-0       [000] d.s31  3741.926197: bpf_trace_printk: SDF: filter destination port lower bound: 0, destination port upper bound: 65535
          <idle>-0       [000] d.s31  3741.926198: bpf_trace_printk: SDF: packet protocol: 0
          <idle>-0       [000] d.s31  3741.926200: bpf_trace_printk: SDF: packet source ip: 142.251.222.46, destination ip: 10.60.0.1
          <idle>-0       [000] d.s31  3741.926201: bpf_trace_printk: SDF: packet source port: 0, destination port: 0
          <idle>-0       [000] d.s31  3741.926204: bpf_trace_printk: Packet with source ip: 142.251.222.46, destination ip: 10.60.0.1 matches SDF filter
          <idle>-0       [000] d.s31  3741.926206: bpf_trace_printk: Packet with source ip:142.251.222.46 and destination ip:10.60.0.1 matches SDF filter
          <idle>-0       [000] d.s31  3741.926208: bpf_trace_printk: upf: downlink session for ip:10.60.0.1  far:3 action:2
          <idle>-0       [000] d.s31  3741.926210: bpf_trace_printk: upf: qer:1 gate_status:0 mbr:1000000000
          <idle>-0       [000] d.s31  3741.926212: bpf_trace_printk: upf: use mapping 10.60.0.1 -> TEID:1
          <idle>-0       [000] d.s31  3741.926215: bpf_trace_printk: upf: send gtp pdu 192.168.13.151 -> 192.168.13.131
          <idle>-0       [000] d.s31  3741.926223: bpf_trace_printk: upf: bpf_fib_lookup 192.168.13.151 -> 192.168.13.131: nexthop: 192.168.13.131
          <idle>-0       [000] d.s31  3742.909660: bpf_trace_printk: upf: gtp-u received
          <idle>-0       [000] d.s31  3742.909666: bpf_trace_printk: SDF: filter protocol: 1
          <idle>-0       [000] d.s31  3742.909670: bpf_trace_printk: SDF: filter source ip: 10.60.0.0, destination ip: 0.0.0.0
          <idle>-0       [000] d.s31  3742.909673: bpf_trace_printk: SDF: filter source ip mask: 255.255.0.0, destination ip mask: 0.0.0.0
          <idle>-0       [000] d.s31  3742.909675: bpf_trace_printk: SDF: filter source port lower bound: 0, source port upper bound: 65535
          <idle>-0       [000] d.s31  3742.909677: bpf_trace_printk: SDF: filter destination port lower bound: 0, destination port upper bound: 65535
          <idle>-0       [000] d.s31  3742.909678: bpf_trace_printk: SDF: packet protocol: 0
          <idle>-0       [000] d.s31  3742.909680: bpf_trace_printk: SDF: packet source ip: 10.60.0.1, destination ip: 142.251.222.46
          <idle>-0       [000] d.s31  3742.909681: bpf_trace_printk: SDF: packet source port: 0, destination port: 0
          <idle>-0       [000] d.s31  3742.909683: bpf_trace_printk: Packet with source ip: 10.60.0.1, destination ip: 142.251.222.46 matches SDF filter
          <idle>-0       [000] d.s31  3742.909685: bpf_trace_printk: upf: sdf filter matches teid:1
          <idle>-0       [000] d.s31  3742.909687: bpf_trace_printk: upf: far:2 action:2 outer_header_creation:0
          <idle>-0       [000] d.s31  3742.909688: bpf_trace_printk: upf: qer:1 gate_status:0 mbr:1000000000
          <idle>-0       [000] d.s31  3742.909690: bpf_trace_printk: upf: session for teid:1 far:0 outer_header_removal:0
          <idle>-0       [000] d.s31  3742.909701: bpf_trace_printk: upf: bpf_fib_lookup 10.60.0.1 -> 142.251.222.46: nexthop: 192.168.16.152
          <idle>-0       [000] d.s31  3742.927411: bpf_trace_printk: SDF: filter protocol: 1
          <idle>-0       [000] d.s31  3742.927415: bpf_trace_printk: SDF: filter source ip: 0.0.0.0, destination ip: 10.60.0.0
          <idle>-0       [000] d.s31  3742.927418: bpf_trace_printk: SDF: filter source ip mask: 0.0.0.0, destination ip mask: 255.255.0.0
          <idle>-0       [000] d.s31  3742.927419: bpf_trace_printk: SDF: filter source port lower bound: 0, source port upper bound: 65535
          <idle>-0       [000] d.s31  3742.927421: bpf_trace_printk: SDF: filter destination port lower bound: 0, destination port upper bound: 65535
          <idle>-0       [000] d.s31  3742.927422: bpf_trace_printk: SDF: packet protocol: 0
          <idle>-0       [000] d.s31  3742.927424: bpf_trace_printk: SDF: packet source ip: 142.251.222.46, destination ip: 10.60.0.1
          <idle>-0       [000] d.s31  3742.927425: bpf_trace_printk: SDF: packet source port: 0, destination port: 0
          <idle>-0       [000] d.s31  3742.927427: bpf_trace_printk: Packet with source ip: 142.251.222.46, destination ip: 10.60.0.1 matches SDF filter
          <idle>-0       [000] d.s31  3742.927430: bpf_trace_printk: Packet with source ip:142.251.222.46 and destination ip:10.60.0.1 matches SDF filter
          <idle>-0       [000] d.s31  3742.927432: bpf_trace_printk: upf: downlink session for ip:10.60.0.1  far:3 action:2
          <idle>-0       [000] d.s31  3742.927433: bpf_trace_printk: upf: qer:1 gate_status:0 mbr:1000000000
          <idle>-0       [000] d.s31  3742.927435: bpf_trace_printk: upf: use mapping 10.60.0.1 -> TEID:1
          <idle>-0       [000] d.s31  3742.927438: bpf_trace_printk: upf: send gtp pdu 192.168.13.151 -> 192.168.13.131
          <idle>-0       [000] d.s31  3742.927446: bpf_trace_printk: upf: bpf_fib_lookup 192.168.13.151 -> 192.168.13.131: nexthop: 192.168.13.131
...

また、以下のようにnr-binderツールにおいて、TUNインターフェースに割り当てられたIPアドレスを指定して、大半のアプリケーションを使用することができます。

  • VM3(UE)でcurl google.comを実行
# sh nr-binder 10.60.0.1 curl google.com
<HTML><HEAD><meta http-equiv="content-type" content="text/html;charset=utf-8">
<TITLE>301 Moved</TITLE></HEAD><BODY>
<H1>301 Moved</H1>
The document has moved
<A HREF="http://www.google.com/">here</A>.
</BODY></HTML>
  • VM-DNでtcpdumpを実行
21:14:25.076320 IP 10.60.0.1.60767 > 142.251.222.46.80: Flags [S], seq 1801703051, win 65280, options [mss 1360,sackOK,TS val 443440134 ecr 0,nop,wscale 7], length 0
21:14:25.097415 IP 142.251.222.46.80 > 10.60.0.1.60767: Flags [S.], seq 2368001, ack 1801703052, win 65535, options [mss 1460], length 0
21:14:25.099172 IP 10.60.0.1.60767 > 142.251.222.46.80: Flags [.], ack 1, win 65280, length 0
21:14:25.099422 IP 10.60.0.1.60767 > 142.251.222.46.80: Flags [P.], seq 1:75, ack 1, win 65280, length 74: HTTP: GET / HTTP/1.1
21:14:25.099589 IP 142.251.222.46.80 > 10.60.0.1.60767: Flags [.], ack 75, win 65535, length 0
21:14:25.167051 IP 142.251.222.46.80 > 10.60.0.1.60767: Flags [P.], seq 1:774, ack 75, win 65535, length 773: HTTP: HTTP/1.1 301 Moved Permanently
21:14:25.169529 IP 10.60.0.1.60767 > 142.251.222.46.80: Flags [.], ack 774, win 64507, length 0
21:14:25.170902 IP 10.60.0.1.60767 > 142.251.222.46.80: Flags [F.], seq 75, ack 774, win 64507, length 0
21:14:25.171165 IP 142.251.222.46.80 > 10.60.0.1.60767: Flags [.], ack 76, win 65535, length 0
21:14:25.194697 IP 142.251.222.46.80 > 10.60.0.1.60767: Flags [F.], seq 774, ack 76, win 65535, length 0
21:14:25.196364 IP 10.60.0.1.60767 > 142.251.222.46.80: Flags [.], ack 775, win 64507, length 0

なお、nr-binderはpingでは機能しません。理由はこちらを参照して下さい。

以上で、eBPF/XDP対応UPFのeUPFのDNに接続し、DNに任意のパケットを流せるようになり、SA構成のローカル5Gを想定した5GCのシミュレーション携帯網として、MECを試す環境を構築できました。

最後に

eBPF/XDP対応UPFのeUPFは、U-Planeのデータネットワークを高速化する技術と期待しています。本記事では、Virtualbox VM上の設定例を書いてみましたが、XDP対応のdriverやNICを搭載したサーバを設定する際のご参考になれれば幸いです。

最後に、元記事はGithubに書いたものです。

主な変更履歴

  • [2024.02.15] 初版。
0
0
0

Register as a new user and use Qiita more conveniently

  1. You get articles that match your needs
  2. You can efficiently read back useful information
  3. You can use dark theme
What you can do with signing up
Sign upLogin
0
0