search

herlesupreeth / docker_open5gs

Docker files to run open5gs + IMS + eNB + gNB + NR-UE in a docker
BSD 2-Clause "Simplified" License
279 stars 156 forks source link

HEARTBEAT from AMF is not exiting docker container after NGAP REQ/RESP #218

Open NUCLEAR-WAR opened 10 months ago

NUCLEAR-WAR commented 10 months ago

Hi,

I'm new to docker open5gs and tying to build a test 5G SA Network, I already done it for 4G VoLTE with srsENB on other PC it perfectly worked fine, for 5G I installed srsRAN for the srsGNB and configure the address to connect to the docker host on the other PC.

After lunching srsGNB, i can see that the NGAP connecting is established, but directlly after the AMF says connection refused to gNB :

08/28 20:07:37.492: [amf] INFO: gNB-N2 accepted[192.168.199.167]:43895 in ng-path module (../src/amf/ngap-sctp.c:113) 08/28 20:07:37.492: [amf] INFO: gNB-N2 accepted[192.168.199.167] in master_sm module (../src/amf/amf-sm.c:741) 08/28 20:07:37.492: [amf] INFO: [Added] Number of gNBs is now 1 (../src/amf/context.c:1185) 08/28 20:07:37.493: [amf] INFO: gNB-N2[192.168.199.167] max_num_of_ostreams : 30 (../src/amf/amf-sm.c:780) 08/28 20:07:39.661: [amf] INFO: gNB-N2[192.168.199.167] connection refused!!! (../src/amf/amf-sm.c:

I did also tcp dump on the container and on the physical machine, i notice after NGAP REQ/RESP on the container pcap that AMF sent a HEARBEAT packet but it did not get a respond, on the physical machine pcap this packet is not there, after that i closed gNB, i see in the pcap taken in the container that the SHUTDOWN Message is reaching AMF container.

not sure what is messing here, i followed the instructions in the README file to deploy the 5G SA including uncomenting the ports under UPF and AMF and also change the UPF_ADVERTISE_IP.

I attach the logs/sa-depoly.yaml/env/pcaps from container and from Physical pc.

pcaps_yaml_env.zip log.zip

Docker Host IP : 192.168.199.133 srsGNB Host IP : 192.168.199.167

herlesupreeth commented 10 months ago

If you are running gNB in another host then I highly recommend to not use the docker for gNB as it a mess with docker NATing all the traffic between gNB and 5GC. In the meantime I will take a look and let you know if its easy solution for the above issue.