gradiant / 5g-images Goto Github PK

Good day,

I am trying to run ngc.yaml in the open5gs-and-ueransim. Everything starts properly except the SMF container. When I check the logs, it displays this:

Based on the error, the problem is in the smf.conf file in the freeDiameter folder, specifically this line:

ConnectPeer = "pcrf.gradiant" { ConnectTo = "pcrf"; TcTimer = 60; TwTimer = 30; No_TLS; };

Would you know how to resolve this issue?

Thank you!

Best regards,
Marco

Good day,

I am trying to just deploy an Open5GS UPF container and connect it to my own Open5GS C-plane that is in the host computer. I have my own UE and gNB which connects to the Open5GS core that I have deployed. After starting my Open5GS UPF container, it properly connects to the SMF in my host computer. When I connect the UE to the network, a PDU session is setup but the UE cannot connect to the internet. I see in the UPF container logs that the ogstun device is created but still no internet connection.

Below is my docker compose file:

version: '3'

services:
upf:
image: gradiant/open5gs:2.7.0
command:
- open5gs-upfd
cap_add:
- all
privileged: true
restart: on-failure
ports:
- 2152:2152
sysctls:
- net.ipv4.ip_forward=1

I hope you'll be able to help me. Thank you very much for your creation and hope to hear from you soon.

Hi Gradiant/Openverso Team,

In case you are looking for a second gNB/UE Simulator or a 5G Core stress tester to evaluate the performance of the 5G Core, you may try my new open-source tool PacketRusher.
It supports the simulation of multiples UEs and gNodeBs right from a single tool, an high performance N3 tunnel, and it supports some advanced control plane features such as roaming (using open5gs's new roaming feature for example) and gNodeB handover.

If you need any help, feel free to reach out to me :-) I'm looking forward to collaborate!

Cheers,
Valentin

Hello,

I tried building the docker image using the docker file, but getting error on step 16.
Attached is the screenshot. Can you please tell where I am getting it wrong.

Hi,

After upgrading openverso/open5gs:2.6.1. most of containers keeps restarting all the time.

I suppose after upgrading to 2.6.1 (Release 17 open5gs) something changed and there is a problem in the images

As I suppose, the docker images versions of dockerhub are aligned to open5gs upgrades. After 2.6.1, Open5gs is in Rel-17, and as I see, the corresponding images with version >2.6.1 show problem.

Could you confirm if you have notice or something I could do?

Tested in ubuntu 22 with docker compose as provided in open5gs-and-ueransim folder, upgrading from 2.3.2 to 2.6.1.

Thanks !

Hi!,

I am testing to create a new image of open5gs-webui to create new configs to make Upf selection approach. Following:

https://github.com/Gradiant/openverso-images/tree/main/images/open5gs-webui

After create the new image I have use it for AMF in docker compose, but an error appears :

Do you know if there is something missing in Image creating script? I would like to create new images with x2,x3 UPFs in order to select the one of them configuring in smf.yaml file.

Thanks.

Hello!

Is there any plan to update images in dockerhub for Open5gs version 2.7.0 ?
I need some of upgrades of this version about UPF selection.

If there´s no plan can I handle with the Dockerfile included in this path?
https://github.com/Gradiant/openverso-images/blob/main/images/open5gs/image_info.sh

Thanks.

Hi,
I cloned the repo and just run the compose command:
docker-compose -f ngc.yaml up -d
Then, when trying to access the web UI via the address 0.0.0.0:3000 I get the following error, which I retrieved using docker logs -f open5gs-and-ueransim_webui_1:

ubuntu@gateway:~/openverso-images/docs/open5gs-and-ueransim$ docker logs -f open5gs-and-ueransim_webui_1
> Ready on http://0.0.0.0:3000
Unhandled rejection MongoError: Unsupported OP_QUERY command: listIndexes. The client driver may require an upgrade. For more details see https://dochub.mongodb.org/core/legacy-opcode-removal
    at Function.MongoError.create (/opt/open5gs-webui/node_modules/mongoose/node_modules/mongodb-core/lib/error.js:31:11)
    at queryCallback (/opt/open5gs-webui/node_modules/mongoose/node_modules/mongodb-core/lib/cursor.js:212:36)
    at /opt/open5gs-webui/node_modules/mongoose/node_modules/mongodb-core/lib/connection/pool.js:469:18
    at processTicksAndRejections (node:internal/process/task_queues:78:11)

I have been testing the images for Webui UERANSIM WebUI with normal credentials. admin/1432 but it is not working. Could you provide or inform what are the correct credentials for the ueransim image please?

Example: https://hub.docker.com/r/openverso/open5gs-webui/tags

Thanks in advance

Hello,

Thanks for the support. Following the steps in this documentation: https://github.com/Gradiant/openverso-images/tree/main/docs/open5gs-and-ueransim

Under the Test step. It seems the gnb and ue part is ok and new UE can be registered but, i don´t see the 'uesimtun0' interface created. How can I make a test to check if a ping is trought the UE-gNB interface? Is everything ok with the docker compose and interface is correctly created?

image: openverso/ueransim:3.2.6
command: ['ue','-n','3']

I hope you can check the issue , or tell me if any step is issing.

Thanks in advance

Hello Team,

I am trying to run the srslte.yaml and create enodeb and ue containers.
I found it in location https://github.com/Gradiant/openverso-images/tree/main/docs/open5gs-and-srslte

Following steps I followed:

1. Ran epc.yaml, which created all the open5gs containers but I am unable to login to the webUi the password is showing incorect. username: admin; password: 1423. But is is not working.
2. After running srslte.yaml, "ue" container is getting created but for "enb" is not. it is showing "Exit 1" when checking.

Not understanding why its happening. Can you please help.