Free5GC-Compose network configuration

Q/A
#1

Hi,
I have been using free5gc for about 3 months now for an University project and now I have the task to adapt the environtment that I had which was 3 VM of Ubuntu 18.04.
One of the machine runs free5gc 3.0.5 and its connected via 2 internal networks to the second VM which is running some software made by us and this second also is connected to the third machine via internal network.
The amf and the upf of the first machine are connected to this second machine.

Now that i have described my environtment I will tell you what I am having issues with.

The goal is to use free5gc-compose in this first machine. The installation works just fine and the tests are working fine but I am unable to reach the AMF and UPFB IP’s from the second machine.
I have read Docker Compose documentation but I still dont know what im missing after a bunch of modifications in the docker-compose.yaml that havent work for me.

¿Any ideas that could be helpful?

Thanks on advance for your attention.
Best regards, Jaime.

#2

Hi @JaimeBotiaLanzas,
If you want to communicate with different VMs, first thing is to make sure that your VMs’ virtual network interface works properly.
You can ping the other VM’s ip from one of the VM to check it.

In the free5gc-compose/docker-compose.yaml, it sets the network configuration of these NFs docker containers. If you want to connect to the free5gc containers, you only need to know the VM1(free5gc) veth ip and the NFs ip.
Command ifconfig and docker inspec {NF-name} in VM1 can be used to check your VM1’s veth ip and the ip of the specific NF container.

Futhermore, according to the type of your veth, you may need to set some ports to let outsider access the VM.

#3

Thank you so much for your reply, I made it work exposing the port of the containers but there was an error connecting to the AMF. The problem was related with the sctp exposed port on Docker. The issue was that the sctp port wont work if you expose the same port on container and host (example 38412:38412/sctp). To fix it I had to declare a different port on host (example 48412:38412/sctp).
Kinda weird but now it works

1 Like
#4