Closed meenaresh19 closed 4 months ago
If I connect to core in bare metal machine (separate laptop), its working fine. Not sure whats going wrong when I connect to core in AWS cloud
Can you ping the AWS host from the gNB host? Maybe you need to add a routing entry.
Able to ping. Infact SCTP INIT reached core node, and core node responded with INIT ACK. After that SRS RAN node sent COOKIE_ECHO, which is not received by 5G core node.
Do you bind the gnb to a proper IP address? here:
amf:
addr: x.x.x.x # The address or hostname of the AMF.
bind_addr: x.x.x.x
Yes, addr : AMF node IP address bind_addr : Local machine IP address where srsRAN is running
Is the bind_addr :
an IP address of an interface connected to the internet?
Is the
bind_addr :
an IP address of an interface connected to the internet?
Should it work, if we create a static ip address?
Could you provide the NGAP PCAP file?
@dhiaboujebha Hi, any updates on this issue?
Issue Description
SCTP connection is timing out, COOKIE_ECHO is not reaching 5G core
Client (srsGNB) sent INIT to Core (AMF) --> Detected in pcap of both client and core Core responded with INIT_ACK(+cookie) --> Detected in pcap of both client and core Client sends COOKIE_ECHO --> Detected only in pcap of the client.
COOKIE_ECHO didnt reach AMF.
Same is tested with UERANSIM, SCTP connection is established successfully.
Setup Details
srsRAN is installed on Ubuntu 22.04 (Core i7) [Client laptop] 5G Core: Open5GS deployed on EKS cluster in AWS cloud Client laptop connected to AWS VPC using VPN (OpenVPN). Able to ping IP of AMF node from client laptop. SCTP port : 38412
Expected Behavior
SCTP connection should be successful
Actual Behaviour
SCTP connection timeout
Steps to reproduce the problem
Connect srsGNB to open5GS core in AWS EKS cluster.
Additional Information