fail iperf

[pchat-imm]

Previously, I successfully use CPE as UE to connect to the srsRAN network. The CPE can provide internet for a mobile phone. My next goal is to use Raspberry Pi with Quectel board as UE to connect to the srsRAN network. I want my RPI to be able to

• ping
• iperf
• access web browser
• run speedtest-cli command

Currently, the Raspberry Pi with Quectel can receive IP address as 10.45.0.2 and can successfully ping to different destinations, including: 1.1.1.1, 8.8.8.8, www.chula.ac.th. However, I cannot do iperf.

I cannot send iperf to both my own server, and to free server speedtest.singnet.com.sg. I have checked beforehand that these server can be iperf with my own Wi-Fi. But I have failed when try with srsRAN network. The results shows below that they have only one successful. I check on wireshark of the core network, it shows that the server send RST back after some times.

My question is

1. How to do iperf?
2. How to find core network IP address? So that I can try to ping to check. Currently

• I set AMF address as 127.0.0.1 on gnb config file
• set ogstun interface of the core network as 10.45.0.1
• have UE ip address of 10.45.0.2.
  But from UE (10.45.0.2) I cannot ping to either 10.45.0.1 nor 127.0.0.1.

system
Core network: open5gs
RAN: USRP B210
UE: Raspberry PI 3 with Quectel RM510Q-GL

gnb config

• gnb_config.txt

log:

• gnb.zip

• gnb_wireshark.zip

• core_network_wireshark.zip

• log show UE can connect showing on core network

05/24 14:47:05.875: [amf] INFO: [Removed] Number of gNB-UEs is now 0 (../src/amf/context.c:2663)
05/24 14:47:08.138: [amf] INFO: InitialUEMessage (../src/amf/ngap-handler.c:401)
05/24 14:47:08.138: [amf] INFO: [Added] Number of gNB-UEs is now 1 (../src/amf/context.c:2656)
05/24 14:47:08.138: [amf] INFO: [suci-0-901-70-0-0-0-0000062714]    5G-S_TMSI[AMF_ID:0x20040,M_TMSI:0xc0000572] (../src/amf/ngap-handler.c:482)
05/24 14:47:08.138: [amf] INFO:     RAN_UE_NGAP_ID[2] AMF_UE_NGAP_ID[3] TAC[7] CellID[0x66c000] (../src/amf/ngap-handler.c:562)
05/24 14:47:08.139: [gmm] INFO: Service request (../src/amf/gmm-sm.c:1410)
05/24 14:47:08.139: [gmm] INFO: [suci-0-901-70-0-0-0-0000062714]    5G-S_GUTI[AMF_ID:0x20040,M_TMSI:0xc0000572] (../src/amf/gmm-handler.c:651)
05/24 14:47:08.280: [amf] INFO: [Added] Number of AMF-Sessions is now 1 (../src/amf/context.c:2677)
05/24 14:47:08.280: [gmm] INFO: UE SUPI[imsi-901700000062714] DNN[internet] S_NSSAI[SST:1 SD:0xffffff] smContextRef [NULL] (../src/amf/gmm-handler.c:1285)
05/24 14:47:08.280: [gmm] INFO: No SMF Instance (../src/amf/gmm-handler.c:1322)
05/24 14:47:08.283: [sbi] WARNING: [SMF] (NRF-discover) NF has already been added [83b26914-19a1-41ef-a29b-0babbc054bc9:1] (../lib/sbi/nnrf-handler.c:1163)
05/24 14:47:08.283: [sbi] WARNING: NF EndPoint(addr) updated [127.0.0.4:80] (../lib/sbi/context.c:2210)
05/24 14:47:08.283: [sbi] WARNING: NF EndPoint(addr) updated [127.0.0.4:7777] (../lib/sbi/context.c:1946)
05/24 14:47:08.283: [sbi] INFO: [SMF] (NF-discover) NF Profile updated [83b26914-19a1-41ef-a29b-0babbc054bc9:1] (../lib/sbi/nnrf-handler.c:1201)
05/24 14:47:08.283: [smf] INFO: [Added] Number of SMF-UEs is now 1 (../src/smf/context.c:1019)
05/24 14:47:08.283: [smf] INFO: [Added] Number of SMF-Sessions is now 1 (../src/smf/context.c:3090)
05/24 14:47:08.288: [sbi] INFO: [SMF] (SCP-discover) NF registered [83b26914-19a1-41ef-a29b-0babbc054bc9:1] (../lib/sbi/path.c:211)
05/24 14:47:08.323: [smf] INFO: UE SUPI[imsi-901700000062714] DNN[internet] IPv4[10.45.0.2] IPv6[] (../src/smf/npcf-handler.c:542)
05/24 14:47:08.324: [upf] INFO: [Added] Number of UPF-Sessions is now 1 (../src/upf/context.c:208)
05/24 14:47:08.324: [gtp] INFO: gtp_connect() [127.0.0.4]:2152 (../lib/gtp/path.c:60)
05/24 14:47:08.324: [upf] INFO: UE F-SEID[UP:0xe07 CP:0xb99] APN[internet] PDN-Type[1] IPv4[10.45.0.2] IPv6[] (../src/upf/context.c:485)
05/24 14:47:08.324: [upf] INFO: UE F-SEID[UP:0xe07 CP:0xb99] APN[internet] PDN-Type[1] IPv4[10.45.0.2] IPv6[] (../src/upf/context.c:485)
05/24 14:47:08.324: [gtp] INFO: gtp_connect() [127.0.0.2]:2152 (../lib/gtp/path.c:60)
05/24 14:47:08.324: [smf] WARNING: Unknown PCO ID:(0x17) (../src/smf/context.c:3033)
05/24 14:47:08.324: [smf] WARNING: Unknown PCO ID:(0x23) (../src/smf/context.c:3033)
05/24 14:47:08.324: [smf] WARNING: Unknown PCO ID:(0x24) (../src/smf/context.c:3033)
05/24 14:47:08.399: [gtp] INFO: gtp_connect() [127.0.0.1]:2152 (../lib/gtp/path.c:60)
05/24 14:47:08.402: [amf] INFO: [imsi-901700000062714:1:11][0:0:NULL] /nsmf-pdusession/v1/sm-contexts/{smContextRef}/modify (../src/amf/nsmf-handler.c:867)

[pgawlowicz]

@pchat-imm any update on this issue?

[pgawlowicz]

any issues with the CPU load? did you execute this script on the srsgnb pc?

[pchat-imm]

yes, run performance script every time

[pgawlowicz]

could you send the logs from a test with the newest gnb release? this one is with commit 2f90c8b60 so from march.

[pchat-imm]

I pull the repo again and get commit 30775abc6
Then I change UE from Quectel on RPI to CPE with a mobile phone.
I can successfully iperf between mobile phone and the core network. Thank you

[herlesupreeth]

@pchat-imm I would suggest to run iperf (when using Quectel) as follows:

Testing Uplink

On open5gs UPF

iperf3 -s -B 10.45.0.1 -p 5201

On RPi connected to Quectel

iperf3 -c 10.45.0.1 -p 5201 -b 1M -B <UE_IP>

Testing Downlink

On RPi connected to Quectel

iperf3 -s -B <UE_IP> -p 5201

On open5gs UPF

iperf3 -c <UE_IP> -p 5201 -b 1M -B 10.45.0.1