mas-oliveira
commented
4 months ago Hello @pgawlowicz,
Sorry but I still having some problems. I don't know what's happening. I uploaded the docker-compose to new version.
5gc:
container_name: open5gs_5gc
build:
context: open5gs
target: open5gs
args:
OS_VERSION: "22.04"
OPEN5GS_VERSION: "v2.7.0"
env_file:
- ${OPEN_5GS_ENV_FILE:-open5gs/open5gs.env}
privileged: true
ports:
- "9999:9999/tcp"
# Uncomment port to use the 5gc from outside the docker network
- "15356:15356"
- "54558:54558" ### socket ping info
- "54559:54559" ### socket udp iperf info
# Uncomment port to use the 5gc from outside the docker network
- "38412:38412/sctp"
- "2152:2152/udp"The gNB and UEs still can connect to the core. When I try to ping 10.45.1.1 from UE1 I still can't reach the IP. Using TCP dump inside the docker 5GC image it's possible to observe that there's some error happening related with the port 2152:
root@9158e7c6600a:/open5gs# tcpdump -i any icmp
tcpdump: data link type LINUX_SLL2
tcpdump: verbose output suppressed, use -v[v]... for full protocol decode
listening on any, link-type LINUX_SLL2 (Linux cooked v2), snapshot length 262144 bytes
15:44:54.461047 ogstun In IP 10.45.1.2 > 10.45.1.1: ICMP echo request, id 15851, seq 1, length 64
15:44:54.461069 ogstun Out IP 10.45.1.1 > 10.45.1.2: ICMP echo reply, id 15851, seq 1, length 64
15:44:54.461123 eth0 In IP marco-NUC7i7BNH > 9158e7c6600a: ICMP 10.42.0.130 udp port 2152 unreachable, length 136
15:44:55.500701 ogstun In IP 10.45.1.2 > 10.45.1.1: ICMP echo request, id 15851, seq 2, length 64
15:44:55.500718 ogstun Out IP 10.45.1.1 > 10.45.1.2: ICMP echo reply, id 15851, seq 2, length 64
15:44:55.500773 eth0 In IP marco-NUC7i7BNH > 9158e7c6600a: ICMP 10.42.0.130 udp port 2152 unreachable, length 136About the interfaces on the docker 5GC image I think that the ogstun is ok and configured with all subnets.
23: ogstun: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 500
link/none
inet 10.45.0.1/24 scope global ogstun
valid_lft forever preferred_lft forever
inet 10.45.1.1/24 scope global ogstun
valid_lft forever preferred_lft forever
.................root@9158e7c6600a:/open5gs# ip ro
default via 10.53.1.1 dev eth0
10.45.0.0/24 dev ogstun proto kernel scope link src 10.45.0.1
10.45.1.0/24 dev ogstun proto kernel scope link src 10.45.1.1 This is the result of the ip ro command on the core computer:
marco@marco-NUC7i7BNH:~/srsRAN_Project/docker$ ip ro
default via 10.3.10.1 dev wlp58s0 proto dhcp metric 600
10.0.2.0/24 dev br-0ae98bbb2186 proto kernel scope link src 10.0.2.1 linkdown
10.3.10.0/24 dev wlp58s0 proto kernel scope link src 10.3.10.76 metric 600
10.42.0.0/24 dev eno1 proto kernel scope link src 10.42.0.1 metric 100
10.45.0.0/16 via 10.53.1.2 dev br-26141c6f72a5
10.53.1.0/24 dev br-26141c6f72a5 proto kernel scope link src 10.53.1.1
169.254.0.0/16 dev wlp58s0 scope link metric 1000
172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown
172.19.1.0/24 dev br-60b9fad393f0 proto kernel scope link src 172.19.1.1 I have the ip forwarding enable in both machines. And we can also check that the icmp packets are arriving the core. I guess that the error could be related with any route related with the core, but I can't check which one could be wrong.
About the port 2152 it's not being used on any computer: Core computer
marco@marco-NUC7i7BNH:~/srsRAN_Project/docker$ lsof -i -n | grep 2152
marco@marco-NUC7i7BNH:~/srsRAN_Project/docker$ gNB + UEs computer
marco@darlene-G5-KC:~/srsRAN_4G/build/srsue/src/ue_zmq_confs$ lsof -i -n | grep 2152
marco@darlene-G5-KC:~/srsRAN_4G/build/srsue/src/ue_zmq_confs$Thanks
pgawlowicz
Issue Description
Hello, I connected 3 UEs to the gNB, now I was trying to ping the core through the UEs but I can't.
Setup Details
I have the O-RAN SC RIC and the 5G Core running on one machine and the UEs + gNB are running on another machine.
The gNB can connect to the core and the RIC correctly. And all the UEs can connect to the gNB:
These are the routes of the UEs
And these are the interfaces available on the machine with the gNB + UEs
Shouldn't be here a dev tun_srsue interface?
EDIT I added the ogstun interface on the machine with gNB + UEs: ogstun: flags=4241<UP,POINTOPOINT,NOARP,MULTICAST> mtu 1500 unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 txqueuelen 500 (UNSPEC) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
And I have the following route table on UE1: $ sudo ip netns exec ue1 route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 0.0.0.0 10.45.1.1 0.0.0.0 UG 0 0 0 tun_srsue 10.45.1.0 0.0.0.0 255.255.255.0 U 0 0 0 tun_srsue
But I still can't reach the core $ sudo ip netns exec ue1 ping 10.45.1.1 PING 10.45.1.1 (10.45.1.1) 56(84) bytes of data. ^C --- 10.45.1.1 ping statistics --- 3 packets transmitted, 0 received, 100% packet loss, time 2043ms
Should I add a rule where the packet that hit the ogstun interface should be forward to the interface where is connected the computer with the core and the RIC?
Expected Behavior
While performing the sudo ip netns exec ue1 ping 10.45.1.1 command the UE was able to reach the core network.
Actual Behaviour
marco@darlene-G5-KC:~/Downloads$ sudo ip netns exec ue1 ping 10.45.1.1 PING 10.45.1.1 (10.45.1.1) 56(84) bytes of data. ^C --- 10.45.1.1 ping statistics --- 4 packets transmitted, 0 received, 100% packet loss, time 3072ms