GNB failed to bind SCTP socket, Cannot assign requested address about srsran_project HOT 4 CLOSED

Check the bind IP address you have configured in gnb.yml.
You need to use an IP that:

1. It's available on the host you are running gnb from
2. It's reachable from the AMF

amf:
  addr: a.b.c.d                 # The address or hostname of the AMF. 
  bind_addr:  a.b.c.d        # A local IP that the gNB binds to for traffic from the AMF.  <<<<<<< here

from srsran_project.

Are you sure you are binding to an IP available on your system? Generally one has to modify the IP in the default config files.

You should use the IP address associated to your default route

$ ip route
default via a.b.c.d dev enx70b5e804da99 <<<<
$ ip add show dev enx70b5e804da99
4: enx70b5e804da99: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether MAC ff:ff:ff:ff:ff:ff
    inet a.b.c.d scope global dynamic noprefixroute enx70b5e804da99 <<<<<<<<<<<

from srsran_project.

I just had this issue today and I managed to bypass it by setting a route so that the sctp messages were sent through a specific device.

Before setting the route, the sctp messages were sent through a network that had no connectivity with the AMF IP.

Something like "ip route add a.b.c.d/24 via ensx" and make sure that a.b.c.d is set on interface ensx.

from srsran_project.

Hallo again...

Y tested several addresses, and I realized that the GNB app only can bind the socket if its local IP address is in the 127.b.c.d segment.

I don't know what else to do, because when the UE obtains an IP is in the 10.45.0.x segment and I'm unable to test de uplink.

from srsran_project.