-
-
Notifications
You must be signed in to change notification settings - Fork 696
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: AMF Cannot find client When Using TLS #2252
Labels
Comments
infinitydon
changed the title
[Bug]: AMF Authentication failure(Synch failure) When Using TLS
[Bug]: AMF Cannot find client When Using TLS
Apr 16, 2023
I also tested with using SCP,
Behavior is same, AMF debug logs attached below |
There seems to be a bug in open5gs. If you need to use it before bug patch, you can modify and use it as below. $ diff --git a/lib/sbi/context.c b/lib/sbi/context.c
index 587f3056d..79a646fb0 100644
--- a/lib/sbi/context.c
+++ b/lib/sbi/context.c
@@ -122,7 +122,7 @@ ogs_sbi_context_t *ogs_sbi_self(void)
static int ogs_sbi_context_prepare(void)
{
- self.sbi_port = OGS_SBI_HTTP_PORT;
+ self.sbi_port = OGS_SBI_HTTPS_PORT;
#if ENABLE_ACCEPT_ENCODING
self.content_encoding = "gzip"; I hope to have this issue resolved soon. Thanks a lot! |
acetcom
added
Housekeeping:BugToReview
Housekeeping: Possible bug that might still be open
type:bug
Open5GS bug
and removed
triage
Triage label for new issues and feature requests
labels
Apr 17, 2023
Thanks @acetcom - Patch works. |
acetcom
added a commit
that referenced
this issue
Apr 21, 2023
acetcom
added a commit
that referenced
this issue
Apr 21, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Open5GS Release, Revision, or Tag
v2.6.2
Steps to reproduce
I tried to deploy open5gs using TLS mode, AMF keeps complaining that it can't connect to AUSF on port 443:
ERROR: [AUSF:ce9a7e50-dc01-41ed-ad8e-e9655557325a] Cannot find client [10.96.18.36:443]
04/16 02:53:30.810: [sbi] ERROR: [AUSF:ce9a7e50-dc01-41ed-ad8e-e9655557325a] Cannot find client [10.96.18.36:443] (../lib/sbi/path.c:421)
04/16 02:53:30.810: [amf] ERROR: amf_nnrf_handle_nf_discover: Expectation `true == amf_sbi_send_request(nf_instance, xact)' failed. (../src/amf/nnrf-handler.c:110)
04/16 02:53:40.813: [amf] ERROR: [suci-0-208-93-0000-0-0-0000000031] Cannot receive SBI message (../src/amf/amf-sm.c:680)
04/16 02:53:40.813: [amf] WARNING: [suci-0-208-93-0000-0-0-0000000031] Registration reject [90] (../src/amf/nas-path.c:219)
Also I don't why it is falling back to port 80, there is no reference to port 80 in the configuration.
04/16 02:53:30.809: [sbi] WARNING: NF EndPoint updated [10.96.18.36:80] (../lib/sbi/context.c:1618)
04/16 02:53:30.809: [sbi] WARNING: NF EndPoint updated [10.96.18.36:80] (../lib/sbi/context.c:1527)
Also NRF is complaining that it can't connect to UDM on port 443
N.B - I confirmed that all the NFs are listening on port 443
AUSF Config:
NRF Config:
AMF Config:
Logs
NRF Logs:
AMF Logs:
AUSF Logs:
Expected behaviour
AMF and AUSF should be able to communicate without any issues
Observed Behaviour
AMF is having issues communicating with AUSF
NRF seems to be having issues communicating with UDM (This might be a temporary connectivity issue)
eNodeB/gNodeB
ueransim
UE Models and versions
ueransim
The text was updated successfully, but these errors were encountered: