You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello, everyone. I'm trying to build a network with srsRAN_Project (in a Raspberry Pi4) and Open5GS (in a Raspberry Pi5) with ZMQ and srsUE, the document I followed is indicated bellow. The Raspberrys are conected with an Ethernet cable, but the problem is that although my network is running, when I test UE and CORE communication with Iperf3 the gNB trace shows a bitrate of 74Mbps for UL while Iperf3 shows a bitrate of 4Mbps. I know that Iperf3 only measures the payload of the test but the difference is too big, so I came to see if someone could help me.
Issue Description
Hello, everyone. I'm trying to build a network with srsRAN_Project (in a Raspberry Pi4) and Open5GS (in a Raspberry Pi5) with ZMQ and srsUE, the document I followed is indicated bellow. The Raspberrys are conected with an Ethernet cable, but the problem is that although my network is running, when I test UE and CORE communication with Iperf3 the gNB trace shows a bitrate of 74Mbps for UL while Iperf3 shows a bitrate of 4Mbps. I know that Iperf3 only measures the payload of the test but the difference is too big, so I came to see if someone could help me.
Document: https://docs.srsran.com/projects/project/en/latest/tutorials/source/srsUE/source/index.html#zeromq-based-setup
Setup Details
srsRAN (Raspberry Pi 4)
Open5GS (Raspberry Pi 5)
ZMQ
srsUE
Expected Behavior
That gNB trace and Iperf3 results have simmilar values for bitrate.
Actual Behaviour
gNB trace shows 74Mbps of bitrate while Iperf3 shows 4Mbps.
Steps to reproduce the problem
gNB config
srsUE config
Ip route config on Rasp Pi5
Iperf3 tests on Pi4
sudo ip netns exec ue1 iperf3 -c 10.45.0.1 -i 1 -t 60
sudo ip netns exec ue1 iperf3 -c 10.45.0.1 -i 1 -t 60 -u -b 5M
sudo ip netns exec ue1 iperf3 -c 10.45.0.1 -i 1 -t 60 --sctp
Additional Information
gNB trace
srsUE trace
iperf3 result
The text was updated successfully, but these errors were encountered: