search

herlesupreeth / docker_open5gs

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

MME Connection Refused #94

Closed raphaelsander closed 1 year ago

raphaelsander commented 2 years ago

Hi @herlesupreeth,

I getting an issue, sometimes happens and sometimes works fine...

A lot of time the MME returns connection refused: connection_refused

Looking to SCTP HEARTBEAT, it's getting out using all interfaces that my server has, but some of this interfaces is used to data link, management or others containers network.

image

186.229.58.2 (internet or data link) 10.70.0.181 (management)

Bellow our connection between eNB and Open5GS Core: 4g_parallel_wireless

Sniffer with SCTP filter: sctp_open5gs_docker.zip Open5GS Logs: log.zip Netplan config of host: network.zip Docker compose and env file: docker-compose.zip

Open5GS without Docker works fine. Did you have this problem before? Any idea to solve this issue?

herlesupreeth commented 2 years ago

image

HEARTBEAT from MME is not replied by your eNB. That's why MME is sending SHUTDOWN towards eNB

Can you send me the trace taken on 'any' interface and dont put any capture filters?

bhuvaneshnexn commented 2 years ago

Hi @herlesupreeth, I am trying to connect dockerized open 5gs core having ip 192.168.1.180 and (dockerized bridge adapter has 172.22.0.1) to non-dockerized environment RAN (enb) having ip 192.168.1.190.Both r in separate machine connected through ethernet cable and having connectivity. when i try to start core and RAN ,RAN try to find core, RAN dont get attached to core. Could u pls help for solving the problem?

herlesupreeth commented 2 years ago

https://github.com/herlesupreeth/docker_open5gs#configuration

@bhuvaneshnexn refer to README section in above link.

bhuvaneshnexn commented 2 years ago

Thanks alot for ur valuable reply and considering me

On Thu, 6 Oct 2022 at 14:07, Supreeth Herle @.***> wrote:

https://github.com/herlesupreeth/docker_open5gs#configuration

@bhuvaneshnexn https://github.com/bhuvaneshnexn refer to README section in above link.

— Reply to this email directly, view it on GitHub https://github.com/herlesupreeth/docker_open5gs/issues/94#issuecomment-1269591477, or unsubscribe https://github.com/notifications/unsubscribe-auth/A2NR73FTFMG7NF5ZJSE5KYDWB2FWPANCNFSM546AXBYA . You are receiving this because you were mentioned.Message ID: @.***>

bhuvaneshnexn commented 2 years ago

Hi @herlesupreeth, If i following these steps, ################################################################################ For the quick run (eNB/gNB, CN in same docker network), edit only the following parameters in .env as per your setup MCC MNC TEST_NETWORK --> Change this only if it clashes with the internal network at your home/office DOCKER_HOST_IP --> This is the IP address of the host running your docker setup SGWU_ADVERTISE_IP --> Change this to value of DOCKER_HOST_IP set above only if eNB/gNB is not running the same docker network/host UPF_ADVERTISE_IP --> Change this to value of DOCKER_HOST_IP set above only if eNB/gNB is not running the same docker network/host If eNB/gNB is NOT running in the same docker network/host as the host running the dockerized Core/IMS then follow the below additional steps Under mme section in docker compose file (docker-compose.yaml, nsa-deploy.yaml), uncomment the following part ...

ports:

#   - "36412:36412/sctp"

... Under amf section in docker compose file (docker-compose.yaml, nsa-deploy.yaml, sa-deploy.yaml), uncomment the following part ...

ports:

#   - "38412:38412/sctp"

... ...

ports:

#   - "2152:2152/udp"

... ############################################################################### I have been facing these kind of errors when “sudo docker-compose up”

ERROR: The Compose file './docker-compose.yaml' is invalid because: services.sgwu.expose is invalid: should be of the format 'PORT[/PROTOCOL]' services.mme.expose is invalid: should be of the format 'PORT[/PROTOCOL]' services.amf.expose is invalid: should be of the format 'PORT[/PROTOCOL]'

bhuvaneshnexn commented 2 years ago

Hello sir, There is problem when building srsenb in specifically

eNB

docker-compose -f srsenb_zmq.yaml up -d && docker attach srsenb_zmq

Is it necessary to build in same dockerized open5gs machine?

herlesupreeth commented 2 years ago

@bhuvaneshnexn whenever there is an issue please post the error message and relevant configuration files (e.g. .env file and docker-compose.yaml file). Without those no one can solve your issues

Is it necessary to build in same dockerized open5gs machine?

No

I have been facing these kind of errors when “sudo docker-compose up”

Check whether you have installed latest versions of docker-ce and docker-compose

bhuvaneshnexn commented 2 years ago

Thank you for your response.

On Thu, 6 Oct 2022 at 19:28, Supreeth Herle @.***> wrote:

@bhuvaneshnexn https://github.com/bhuvaneshnexn whenever there is an issue please post the error message and relevant configuration files (e.g. .env file and docker-compose.yaml file). Without those no one can solve your issues

Is it necessary to build in same dockerized open5gs machine?

No

I have been facing these kind of errors when “sudo docker-compose up”

Check whether you have installed latest versions of docker-ce and docker-compose

— Reply to this email directly, view it on GitHub https://github.com/herlesupreeth/docker_open5gs/issues/94#issuecomment-1270101861, or unsubscribe https://github.com/notifications/unsubscribe-auth/A2NR73FDAGNUZUZ2FHDTYNDWB3LIDANCNFSM546AXBYA . You are receiving this because you were mentioned.Message ID: @.***>

bhuvaneshnexn commented 2 years ago

sir,

Exactly sir, i had “docker-compose version 1.25.0, build unknown”.Then i updated it now i have “Docker version 20.10.18, build b40c2f6”

ERROR: The Compose file './docker-compose.yaml' is invalid because:

services.sgwu.expose is invalid: should be of the format 'PORT[/PROTOCOL]'

services.mme.expose is invalid: should be of the format 'PORT[/PROTOCOL]'

services.amf.expose is invalid: should be of the format 'PORT[/PROTOCOL]'

This wont come up again. Thank you. But still am getting s1 connection failed.....in RAN (192.168.1.190). I am also attached enb.conf file in RAN.

According to my setup, (core)

MCC--> 999MNC--> 70TEST_NETWORK --> 172.22.0.0/24DOCKER_HOST_IP --> 192.168.1.180SGWU_ADVERTISE_IP --> 192.168.1.180UPF_ADVERTISE_IP --> 192.168.1.180i also attached .env,docker-compose.yaml and nsa-deploy.yaml

On Fri, 7 Oct 2022 at 09:59, bhuvanesh nexn @.***> wrote:

Thank you for your response.

On Thu, 6 Oct 2022 at 19:28, Supreeth Herle @.***> wrote:

@bhuvaneshnexn https://github.com/bhuvaneshnexn whenever there is an issue please post the error message and relevant configuration files (e.g. .env file and docker-compose.yaml file). Without those no one can solve your issues

Is it necessary to build in same dockerized open5gs machine?

No

I have been facing these kind of errors when “sudo docker-compose up”

Check whether you have installed latest versions of docker-ce and docker-compose

— Reply to this email directly, view it on GitHub https://github.com/herlesupreeth/docker_open5gs/issues/94#issuecomment-1270101861, or unsubscribe https://github.com/notifications/unsubscribe-auth/A2NR73FDAGNUZUZ2FHDTYNDWB3LIDANCNFSM546AXBYA . You are receiving this because you were mentioned.Message ID: @.***>

bhuvaneshnexn commented 2 years ago

Respected sir,

Error in core while running

###########################

cscf | 0(35) INFO: ims_ipsec_pcscf [ims_ipsec_pcscf_mod.c:168]: ipsec_print_all_socket_lists(): tcp: 172.22.0.21 [172.22.0.21]:5109

pcscf | 0(35) INFO: ims_ipsec_pcscf [ims_ipsec_pcscf_mod.c:168]: ipsec_print_all_socket_lists(): tcp: 172.22.0.21 [172.22.0.21]:6109

pcscf | 0(35) ERROR: ims_ipsec_pcscf [ipsec.c:582]: clean_sa(): Error sending delete SAs command via netlink socket: No data available

pcscf | 0(35) WARNING: ims_ipsec_pcscf [cmd.c:1167]: ipsec_cleanall(): Error cleaning IPSec Security associations during startup.

pcscf | 0(35) ERROR: ims_ipsec_pcscf [ipsec.c:624]: clean_policy(): Error sending delete policies command via netlink socket: No data available

pcscf | 0(35) WARNING: ims_ipsec_pcscf [cmd.c:1171]: ipsec_cleanall(): Error cleaning IPSec Policies during startup.

pcscf | 0(35) INFO: ims_registrar_pcscf [ims_registrar_pcscf_mod.c:275]: mod_init(): Successfully bound to PCSCF IPSEC module

smsc exited with code 255

pcscf | 0(35) INFO: jsonrpcs [jsonrpcs_sock.c:197]: jsonrpc_dgram_mod_init(): the socket /var/run/kamailio/kamailio_rpc.sock already exists, trying to delete it...

pcscf | 0(35) INFO: [main.c:2779]: main(): processes (at least): 111

pcscf | 0(35) WARNING: tm [tm.c:507]: fixup_routes(): t_on_failure("NATMANAGE"): empty/non existing route

pcscf | 0(35) ERROR: Githubissues.

  • Githubissues is a development platform for aggregating issues.