You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When i run the ./test.sh TestRegistration i got the error "this upf do not associate with smf", with upf ip : 10.200.200.101. And the test finish on a panic: test timed out after 10min.
To Reproduce
Steps to reproduce the behavior:
Install the free5gc package
Follow the step and being at the testing one
./test.sh TestRegistration
Expected behavior
Expect SUCCESS at the end of the test.
Screenshots
Environment (please complete the following information):
free5GC Version v3.0.5
OS Ubuntu 20.04.1
Kernel version 5.8.0-43-generic
go version: 1.16 linux/amd64
gcc version 9.3.0
mongo 3.6.8
I'm working on Windows with VmWare.
Trace File
Configuration File
The configuration file for the SMF is the classic one given in the package free5gc. I didn't modify anything.
But the TestRegistration add a new UE ID, like we can saw on this screen (the second one, the first was made with the webconsole).
The text was updated successfully, but these errors were encountered:
You need to execute make upf under free5gc folder to build upf binary first, and then run ./test.sh TestRegistration
If no more issue, please close this issue.
Thanks.
Describe the bug
When i run the ./test.sh TestRegistration i got the error "this upf do not associate with smf", with upf ip : 10.200.200.101. And the test finish on a panic: test timed out after 10min.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Expect SUCCESS at the end of the test.
Screenshots
Environment (please complete the following information):
I'm working on Windows with VmWare.
Trace File
Configuration File
The configuration file for the SMF is the classic one given in the package free5gc. I didn't modify anything.
But the TestRegistration add a new UE ID, like we can saw on this screen (the second one, the first was made with the webconsole).
The text was updated successfully, but these errors were encountered: