issue_owner_repo
listlengths 2
2
| issue_body
stringlengths 0
261k
⌀ | issue_title
stringlengths 1
925
| issue_comments_url
stringlengths 56
81
| issue_comments_count
int64 0
2.5k
| issue_created_at
stringlengths 20
20
| issue_updated_at
stringlengths 20
20
| issue_html_url
stringlengths 37
62
| issue_github_id
int64 387k
2.46B
| issue_number
int64 1
127k
|
|---|---|---|---|---|---|---|---|---|---|
[
"free5gc",
"free5gc"
] |
Using free5gc v3.0.6 and UERANSIM.
Registration is happening with DefaultNonGBR5QI . Here how can we add multiple 5QI (like 6, 7, 8) during registration...
|
How can we add multiple 5QI during registration
|
https://api.github.com/repos/free5gc/free5gc/issues/316/comments
| 1 |
2022-03-03T13:52:10Z
|
2023-07-05T06:44:09Z
|
https://github.com/free5gc/free5gc/issues/316
| 1,158,435,544 | 316 |
[
"free5gc",
"free5gc"
] |
## Describe the bug
When a PDU session release request is received, a PDU session release command is sent, but the 5GSM cause is set to unknown (0).
This is not the value specified in 3GPP TS 24.501 9.11.4.2 5GSM cause.
## To Reproduce
1. Run test.sh -o TestPDUSessionReleaseRequest
2. Check the pcap after the test is finished.
## Expected behavior
Sets 5GSM cause value according to 6.3.3.2 Network-requested PDU session release procedure initiation in TS24.501.
## Environment (please complete the following information):
- free5GC Version: v3.0.6
- OS: Ubuntu 18.04
- Kernel version: 5.0.0-23-generic
- go version go1.14.4 linux/amd64
## Pull Request
[Pull Request](https://github.com/free5gc/smf/pull/42) for the fix.
|
[Bugs] "5GSM Cause" IE of "PDU Session Release Command" NAS Message is incorrect.
|
https://api.github.com/repos/free5gc/free5gc/issues/315/comments
| 1 |
2022-03-01T07:42:04Z
|
2022-03-01T09:46:19Z
|
https://github.com/free5gc/free5gc/issues/315
| 1,154,982,828 | 315 |
[
"free5gc",
"free5gc"
] |
## Describe the bug
When a Mobility registration updating is received, it returns a Registration Accept, but may incorrectly set the PDU session status IE.
AMF responds with INACTIVE in a RegistratonAccept even if the PDU Session status of AMF is in ACTIVE state.
## To Reproduce
1. RegistrationRequest ~ establish PDUSession
2. UE Context Release Request ~ UE Context Release Complete
3. UE/gNB -> 5GC InitialUEMessage, Registration request, Registration request(mobility registration updating)
4. UE/gNB <- 5GC InitialContextSetupRequest, Registration accept
Incorrect PDU session status IE settings.
## Expected behavior
PDU session status IE set to Registration Accept correctly.
## Environment (please complete the following information):
- free5GC Version: v3.0.6
- OS: Ubuntu 18.04
- Kernel version: 5.0.0-23-generic
- go version go1.14.4 linux/amd64
## Pull Request
[Pull Request](https://github.com/free5gc/amf/pull/62) for the fix.
|
[Bugs] Wrong parameters set for PDU session status IE in Registration Accept for Mobility Registration Updating.
|
https://api.github.com/repos/free5gc/free5gc/issues/314/comments
| 1 |
2022-02-22T05:17:46Z
|
2022-03-01T07:26:59Z
|
https://github.com/free5gc/free5gc/issues/314
| 1,146,466,761 | 314 |
[
"free5gc",
"free5gc"
] |
## Documentation request
Is this content [here](https://github.com/free5gc/free5gc/wiki/Environment#hardware-tested) still valid?
> In the market today, there are neither hardware gNB nor hardware UEs that interface directly with a standalone 5GC, so no hardware testing has yet been performed against free5gc.
`open5gs` seems to have some [hardware](https://open5gs.org/open5gs/docs/hardware/01-genodebs) listed.
## Suggestion
Maybe, add tests with a `gNodeB` or even [UERANSIM](https://github.com/aligungr/UERANSIM) ?
## Additional context
None.
|
[Docs] Has any tests been conducted with hardware?
|
https://api.github.com/repos/free5gc/free5gc/issues/313/comments
| 3 |
2022-02-20T06:07:17Z
|
2022-03-30T16:35:13Z
|
https://github.com/free5gc/free5gc/issues/313
| 1,144,931,402 | 313 |
[
"free5gc",
"free5gc"
] |
I was following the passes described in the official site (https://www.free5gc.org/installations/stage-3-free5gc-install/) but I can't pass any test.
When I run any test, for example TestRegistration, I get the following outputs:
./bin/free5gc-upfd: invalid option -- 'f'
NAME:
upf - 5G User Plane Function (UPF)
USAGE:
main [global options] command [command options] [arguments...]
COMMANDS:
help, h Shows a list of commands or help for one command
GLOBAL OPTIONS:
-c FILE Load configuration from FILE
-l FILE Output NF log to FILE
-g FILE Output free5gc log to FILE
-h show help
2022-02-18T18:13:06Z [ERRO][UPF][Util] Illigal option: f
2022-02-18T18:13:06Z [ERRO][UPF][Util] Error parsing args
...
And then the test stay stuck on Remove Request Transaction [1]
Others error I can retrieve, before the Remove Request Transaction [1] are:
2022-02-18T18:13:58Z [ERRO][SMF][CTX] In ActivateUpLinkTunnel UPF IP: 10.200.200.101
2022-02-18T18:13:58Z [ERRO][SMF][CTX] Allocate PDR Error: this upf do not associate with smf
To Reproduce it, just follow the steps as described on official site (https://www.free5gc.org/installations/stage-3-free5gc-install/)
I know Stage 3 is not the actual, but the steps seems to be coherent with documentation here on github.
## Environment (please complete the following information):
- free5GC Version: v3.0.6
- OS: Ubuntu 20.0.04
- Kernel version: 5.4.0-100-generic
- go version: go version go1.15.8 linux/amd64
- gtp:
gtp5g 118784 0
udp_tunnel 16384 1 gtp5g
|
[Bugs] Can't pass any test, upf error, illigal option: f
|
https://api.github.com/repos/free5gc/free5gc/issues/312/comments
| 7 |
2022-02-18T18:24:14Z
|
2022-04-01T00:51:18Z
|
https://github.com/free5gc/free5gc/issues/312
| 1,143,542,073 | 312 |
[
"free5gc",
"free5gc"
] |
## Describe the bug
The UPDKGtpHandler() reads the G-PDU packet from the UDP socket and analyzes the GTP header, but since the wrong offset value (third argument) is passed to FindPDRByTEID(), GTPUHeaderLen() tries to obtain the total length of the GTP header including the extension header, but analyzes from a position that is not the GTP header, and the correct result is not returned.
## To Reproduce
I think it's obvious from the source code.
## Expected behavior
The GTP header is parsed correctly when UL data is received.
## Environment (please complete the following information):
- free5GC Version: v3.0.6
- OS: Ubuntu 18.04
- Kernel version: 5.0.0-23-generic
- go version go1.14.4 linux/amd64
## Pull Request
[Pull Request](https://github.com/free5gc/upf/pull/53) for the fix.
|
[Bugs] There is an error in the processing to analyze the GTP header when receiving UL data.
|
https://api.github.com/repos/free5gc/free5gc/issues/311/comments
| 1 |
2022-02-16T04:52:01Z
|
2022-03-02T14:13:40Z
|
https://github.com/free5gc/free5gc/issues/311
| 1,139,533,521 | 311 |
[
"free5gc",
"free5gc"
] |
## Describe the bug
My setup consists of all the free5gc network functions and I'm using gnbsim for emulating the procedures. The registration process is smooth and I didn't find any discrepancy in the flows. However, for the PDU session establishment, with reference to **3gpp.TS.23.502(section 4.3.2.2.1)**, there is a flow from **SMF -> PCF for PCF selection (step 7a)**. During this flow, there is a request from **PCF to mongoDB** for flowrule selection from the collection **policyData.ues.flowRule**. During subscription or registration, I didn't find any steps for inserting any flowrules. (Please correct me here, if Im wrong). Kindly let me know or point me to the documentation related to this, if I'm missing something.
## To Reproduce
Steps to reproduce the behavior:
1. Insert subscriber information and register the UE. Run the comm PDU session establishment procedure.
2. And analyse the packets using wireshark destined to mongoDB instance.
## Expected behavior
Expecting a flowrule in the mongoDB query **()** from PCF-> mongoDB query.
## Screenshots
The following screenshot (packet no:129) is the request from PCF to mongo instance requesting policyData.ues.flowRule for a particular ueId.
In the wireshark screenshot, we can see the return of **empty document** from mongoDB instance.
## Environment (please complete the following information):
- K8s/Docker container deployment (4 node cluster with single master)
- OS: [e.g. Ubuntu 18.04 Server]
- Kernel version: [e.g. 5.200.0-0-generic]
## Trace File
### Configuration File
The associated source file calling this request can be seen in line:177
https://github.com/free5gc/pcf/blob/72c023f88ab53d899e46edfb883b9c6055de27b7/producer/smpolicy.go
### Log File
|
No flowrule is returned from MongoDB while establishing PDU session.
|
https://api.github.com/repos/free5gc/free5gc/issues/310/comments
| 2 |
2022-02-13T10:14:50Z
|
2023-07-05T06:41:32Z
|
https://github.com/free5gc/free5gc/issues/310
| 1,135,599,651 | 310 |
[
"free5gc",
"free5gc"
] | null |
Solved
|
https://api.github.com/repos/free5gc/free5gc/issues/309/comments
| 0 |
2022-02-12T17:02:47Z
|
2022-03-31T16:07:52Z
|
https://github.com/free5gc/free5gc/issues/309
| 1,134,298,842 | 309 |
[
"free5gc",
"free5gc"
] |
## Describe the bug
EpollWait() internally calls the system call epoll_wait.
If epoll_wait receives any signal during execution, it sets errno to EINTR (Interrupted system call) and returns -1.
UpdkPacketReceiverThread exits the loop and terminates the thread if EpollWait() returns a negative value.
When the thread UpdkPacketReceiverThread is terminated, the handler associated with the socket receiving the packet data is not called, so the buffering of the DL packet is not performed even in the buffering mode, the timing of the PFCP Session Report Request is not generated, and Paging cannot be performed.
## To Reproduce
- Run ./test.sh TestPaging
- Execute "sudo strace -f -p $(pgrep -n upfd) -tt -e 'trace=epoll_wait'" at the CM-IDLE timing. Review the following logs:.
```
2022-02-02T16:12:55+09:00 [INFO][AMF][NGAP][127.0.0.1:9487][AMF_UE_NGAP_ID:1] Send UE Context Release Command
2022-02-02T16:12:55+09:00 [INFO][AMF][NGAP][127.0.0.1:9487] Handle UE Context Release Complete
2022-02-02T16:12:55+09:00 [INFO][AMF][NGAP][127.0.0.1:9487][AMF_UE_NGAP_ID:1] Rel Ue Context in GMM-Registered
2022-02-02T16:12:55+09:00 [INFO][AMF][NGAP][127.0.0.1:9487] Release UE[imsi-2089300007487] Context : N2 Connection Release
2022-02-02T16:12:58+09:00 [ERRO][UPF][Util] Epoll Wait Error : Interrupted system call
2022-02-02T16:12:58+09:00 [ERRO][UPF][Util] Epoll Wait error : Interrupted system call
2022-02-02T16:12:58+09:00 [ERRO][UPF][Util] Epoll Wait Error : Interrupted system call
2022-02-02T16:12:58+09:00 [ERRO][UPF][Util] Epoll Wait error : Interrupted system call
2022-02-02T16:12:59+09:00 [ERRO][UPF][Util] Epoll Wait Error : Interrupted system call
2022-02-02T16:12:59+09:00 [ERRO][UPF][Util] Epoll Wait error : Interrupted system call
panic: test timed out after 10m0s
:
```
If the scenario continues, the Paging does not occur and the scenario does not finish.
## Expected behavior
When epoll_wait returns EINTR, the packet receiving thread does not exits unexpectedly.
## Environment (please complete the following information):
- free5GC Version: v3.0.6
- OS: Ubuntu 18.04
- Kernel version: 5.0.0-23-generic
- go version go1.14.4 linux/amd64
## Pull Request
[Pull Request](https://github.com/free5gc/upf/pull/52) for the fix.
|
[Bugs] When epoll_wait returned EINTR, the packet receiving thread exits unexpectedly.
|
https://api.github.com/repos/free5gc/free5gc/issues/308/comments
| 1 |
2022-02-04T08:05:23Z
|
2022-02-05T15:35:18Z
|
https://github.com/free5gc/free5gc/issues/308
| 1,123,919,328 | 308 |
[
"free5gc",
"free5gc"
] |
The binary free5gc-upfd is not produced in the right directory
I use ubuntu 20.04, up to date (apt upgrade) and cmake -GNinja ..
My patch:
>
```
> > diff --git a/CMakeLists.txt b/CMakeLists.txt
> > index 6522fe2..91aa49c 100644
> > --- a/CMakeLists.txt
> > +++ b/CMakeLists.txt
> > @@ -37,7 +37,7 @@ add_compile_options(-Wall -Werror -Wno-address-of-packed-member)
> > set(CMAKE_C_FLAGS_DEBUG "${CMAKE_C_FLAGS_DEBUG} -g3 -O0")
> >
> > # Submodules
> > -add_subdirectory(src)
> > +add_subdirectory(src ${BUILD_BIN_DIR})
> > add_subdirectory(updk)
> > add_subdirectory(lib/pfcp)
> > add_subdirectory(lib/pfcp/test)
> > diff --git a/src/CMakeLists.txt b/src/CMakeLists.txt
> > index 6dfbcf2..0414aa5 100644
> > --- a/src/CMakeLists.txt
> > +++ b/src/CMakeLists.txt
> > @@ -9,12 +9,14 @@ file(GLOB SRC_FILES
> > "*.c"
> > "n4/*.c"
> > "up/*.c"
> > -)
> > + )
> > +
> > add_executable(${PROJECT_NAME} ${SRC_FILES})
> > +message( "${BUILD_BIN_DIR}/free5gc-upfd")
> > set_target_properties(
> > ${PROJECT_NAME}
> > PROPERTIES
> > - OUTPUT_NAME "${BUILD_BIN_DIR}/free5gc-upfd"
> > + RUNTIME_OUTPUT_NAME "free5gc-upfd"
> > SUFFIX ""
> > )
```
**We will advise people to follow the issue template set, otherwise the issue might be disregarded.**
**free5GC mainly uses GitHub for issue tracking. Information regarding to general questions or technical support. It will be highly considered if forward to the [forum](https://forum.free5gc.org).**
**free5GC will appreciate it, if people can refer to [TS](https://github.com/free5gc/free5gc/wiki/Trouble_Shooting) and [forum](https://forum.free5gc.org) prior to bug reporting**
<!-- Remove warning (above 3 lines) while reporting the issue -->
## Describe the bug
A clear and concise description of what the bug is.
## To Reproduce
Steps to reproduce the behavior:
1. Change config '...'
2. Code patch '...' (You can fork the project and give us the patch diff you have modified)
3. Run command '...'
4. Dump packet '...'
## Expected behavior
A clear and concise description of what you expected to happen.
## Screenshots
If applicable, add screenshots to help explain the problem.
## Environment (please complete the following information):
- free5GC Version: [e.g. v3.0.100]
- OS: [e.g. Ubuntu 200.04 Server]
- Kernel version: [e.g. 5.200.0-0-generic]
- go version: [e.g. 1.10.0 linux/amd64]
- c compiler version (Option): [e.g. gcc version 1.1.0]
## Trace File
### Configuration File
Provide the configuration file here.
If not clear of what to do, the `config` folder can be zip and upload it here.
### PCAP File
Dump the packet and provide the pcap file here.
If not clear of what to do, this command can be used `sudo tcpdump -i any -w free5gc.pcap` prior to running bug reproduce. Then upload the pcap file `free5gc.pcap`.
### Log File
Provide the program log file here.
If not clear of what to do, copy the printed log on the screen and upload it here.
## System architecture (Option)
Please provide the draft architecture, including the scenario, use cases, installation environment(bare metal, vm, container, or k8s), etc.
## Walkthrough (Option)
free5GC will be interested on the research or finding in brief.
## Additional context
It will be appreciated if other context can be added here.
|
[Bugs]
|
https://api.github.com/repos/free5gc/free5gc/issues/307/comments
| 1 |
2022-02-03T23:41:27Z
|
2023-06-24T15:14:29Z
|
https://github.com/free5gc/free5gc/issues/307
| 1,123,664,513 | 307 |
[
"free5gc",
"free5gc"
] |
Hi,
I want to test the upf and know the gtp traffic generation.
Iam in a search of GTP traffic generator to send gtp packets to upf.
Please suggest me that how can i generate the gtp traffic or a tool that generate the gtp traffic.
|
GTP Traffic Generation
|
https://api.github.com/repos/free5gc/free5gc/issues/306/comments
| 6 |
2022-02-02T13:25:14Z
|
2023-07-29T06:13:38Z
|
https://github.com/free5gc/free5gc/issues/306
| 1,121,924,142 | 306 |
[
"free5gc",
"free5gc"
] |
Hello
I am working on the 5G core and it is connected to the UE and RAN.
ping for me I want to use iperf to send TCP and UDP packets.
>> the UPF in VM1
>> 5G core in VM2
>> UERANSIM in VM3
ping -I uesimtun0 google.com -c3 >>> work but with IP address for google, NAT does not work for me.
ping -I uesimtun0 UPF -c3 >> instead of UPF i but the IP address of the UPF .. its work for me.
Know, I want to use UPF as a server and uesimtun0 as a client and send UDP packets using iperf3 or iperf.
I check when the firewall is on and oof and I have the same issues.
If there is another tool that I could use to generate traffic from uesimtun0 to UPF.
I use iperf as the flowing but i get broken pips.
<img width="637" alt="Screenshot 2022-02-01 at 4 55 07 pm" src="https://user-images.githubusercontent.com/34620715/152014815-c186825f-9a3e-493c-a117-2e0f62816982.png">
<img width="646" alt="Screenshot 2022-02-01 at 4 56 01 pm" src="https://user-images.githubusercontent.com/34620715/152014827-f81f5ca9-8a8b-405f-800e-fa4531d3a0d0.png">
If you have an idea, please let me know
Regards,
Noor
|
How can i Test the Bandwidth between the UE (ueransim0) interface and the 5G Core
|
https://api.github.com/repos/free5gc/free5gc/issues/305/comments
| 1 |
2022-02-01T22:05:38Z
|
2023-07-12T13:54:22Z
|
https://github.com/free5gc/free5gc/issues/305
| 1,121,247,908 | 305 |
[
"free5gc",
"free5gc"
] |
## Describe the bug
Multiple data races are occurred in the TestPaging.
## To Reproduce
Apply this patch and exec `./test.sh TestPaging`
```
diff --git a/test.sh b/test.sh
index e5f9168..6ebe7d0 100755
--- a/test.sh
+++ b/test.sh
@@ -193,7 +193,7 @@ then
else
cd test
- $GOROOT/bin/go test -v -vet=off -run $1
+ $GOROOT/bin/go test -race -v -vet=off -run $1
fi
terminate $1
```
## Expected behavior
No data races are shown.
## Environment (please complete the following information):
- free5GC Version: commit id bef19d5b957
- OS: Ubuntu 20.04
- Kernel version: 5.4.0-96-generic
- go version: go version go1.14.4 linux/amd64
- c compiler version (Option): 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)
### Log File
```
nishi@GTP-U:~/free5gc-deb/free5gc$ ./test.sh TestPaging
2022-01-31T14:51:06+09:00 [INFO][UPF][Util] Config: /home/nishi/free5gc-deb/free5gc/NFs/upf/build/config/upfcfg.test.yaml
2022-01-31T14:51:06+09:00 [INFO][UPF][Util] UPF config version [1.0.0]
2022-01-31T14:51:06+09:00 [INFO][UPF][Util] Set log level: info
2022-01-31T14:51:06+09:00 [INFO][UPF][Util] DNN routes added, main routing table:
2022-01-31T14:51:06+09:00 [INFO][UPF][Util] DstIp Gateway Iface Priority RtProto Type
2022-01-31T14:51:06+09:00 [INFO][UPF][Util] 60.60.0.0 /24 0.0.0.0 upfgtp 0 static unicast
2022-01-31T14:51:06+09:00 [INFO][UPF][Util] 10.200.200.0 /24 0.0.0.0 veth1 0 kernel unicast
2022-01-31T14:51:14+09:00 [INFO][NRF][Init] NRF Log level is set to [info] level
2022-01-31T14:51:14+09:00 [INFO][LIB][Path] set log level : info
2022-01-31T14:51:14+09:00 [INFO][LIB][Path] set report call : false
2022-01-31T14:51:14+09:00 [INFO][LIB][OAPI] set log level : info
2022-01-31T14:51:14+09:00 [INFO][LIB][OAPI] set report call : false
2022-01-31T14:51:14+09:00 [INFO][LIB][MonDB] set log level : info
2022-01-31T14:51:14+09:00 [INFO][LIB][MonDB] set report call : false
2022-01-31T14:51:14+09:00 [INFO][NRF][CFG] config version [1.0.0]
2022-01-31T14:51:14+09:00 [INFO][NRF][Init] Server started
2022-01-31T14:51:14+09:00 [INFO][NRF][Init] nrfconfig Info: Version[1.0.0] Description[NRF initial local configuration]
2022-01-31T14:51:14+09:00 [INFO][NRF][Init] Binding addr: [127.0.0.10:8000]
2022-01-31T14:51:14+09:00 [INFO][AMF][Init] AMF Log level is set to [info] level
2022-01-31T14:51:14+09:00 [INFO][LIB][NAS] set log level : info
2022-01-31T14:51:14+09:00 [INFO][LIB][NAS] set report call : false
2022-01-31T14:51:14+09:00 [INFO][LIB][NGAP] set log level : info
2022-01-31T14:51:14+09:00 [INFO][LIB][NGAP] set report call : false
2022-01-31T14:51:14+09:00 [INFO][LIB][FSM] set log level : info
2022-01-31T14:51:14+09:00 [INFO][LIB][FSM] set report call : false
2022-01-31T14:51:14+09:00 [INFO][LIB][Aper] set log level : info
2022-01-31T14:51:14+09:00 [INFO][LIB][Aper] set report call : false
2022-01-31T14:51:14+09:00 [INFO][LIB][Path] set log level : info
2022-01-31T14:51:14+09:00 [INFO][LIB][Path] set report call : false
2022-01-31T14:51:14+09:00 [INFO][LIB][OAPI] set log level : info
2022-01-31T14:51:14+09:00 [INFO][LIB][OAPI] set report call : false
2022-01-31T14:51:14+09:00 [INFO][AMF][CFG] config version [1.0.2]
2022-01-31T14:51:14+09:00 [INFO][AMF][Init] Server started
2022-01-31T14:51:14+09:00 [INFO][AMF][Util] amfconfig Info: Version[1.0.2] Description[AMF initial local configuration]
2022-01-31T14:51:14+09:00 [INFO][AMF][NGAP] Listen on 127.0.0.1:38412
2022-01-31T14:51:14+09:00 [INFO][NRF][MGMT] Handle NFRegisterRequest
2022-01-31T14:51:14+09:00 [INFO][NRF][MGMT] urilist update
2022-01-31T14:51:14+09:00 [INFO][NRF][MGMT] Create NF Profile
2022-01-31T14:51:14+09:00 [INFO][NRF][MGMT] Location header: http://127.0.0.10:8000/nnrf-nfm/v1/nf-instances/139f22d5-1de7-4b3b-b6d1-f1bb94b504bd
2022-01-31T14:51:14+09:00 [INFO][NRF][GIN] | 201 | 127.0.0.1 | PUT | /nnrf-nfm/v1/nf-instances/139f22d5-1de7-4b3b-b6d1-f1bb94b504bd |
2022-01-31T14:51:14+09:00 [INFO][SMF][Init] SMF Log level is set to [info] level
2022-01-31T14:51:14+09:00 [INFO][LIB][NAS] set log level : info
2022-01-31T14:51:14+09:00 [INFO][LIB][NAS] set report call : false
2022-01-31T14:51:14+09:00 [INFO][LIB][NGAP] set log level : info
2022-01-31T14:51:14+09:00 [INFO][LIB][NGAP] set report call : false
2022-01-31T14:51:14+09:00 [INFO][LIB][Aper] set log level : info
2022-01-31T14:51:14+09:00 [INFO][LIB][Aper] set report call : false
2022-01-31T14:51:14+09:00 [INFO][LIB][Path] set log level : info
2022-01-31T14:51:14+09:00 [INFO][LIB][Path] set report call : false
2022-01-31T14:51:14+09:00 [INFO][LIB][OAPI] set log level : info
2022-01-31T14:51:14+09:00 [INFO][LIB][OAPI] set report call : false
2022-01-31T14:51:14+09:00 [INFO][LIB][PFCP] set log level : info
2022-01-31T14:51:14+09:00 [INFO][LIB][PFCP] set report call : false
2022-01-31T14:51:14+09:00 [INFO][SMF][CFG] SMF config version [1.0.2]
2022-01-31T14:51:14+09:00 [INFO][SMF][CFG] UE-Routing config version [1.0.1]
2022-01-31T14:51:14+09:00 [INFO][SMF][CTX] smfconfig Info: Version[1.0.2] Description[SMF initial local configuration]
2022-01-31T14:51:14+09:00 [INFO][SMF][CTX] Endpoints: [10.200.200.102]
2022-01-31T14:51:14+09:00 [INFO][SMF][Init] Server started
2022-01-31T14:51:14+09:00 [INFO][NRF][MGMT] Handle NFRegisterRequest
2022-01-31T14:51:14+09:00 [INFO][NRF][MGMT] urilist update
2022-01-31T14:51:14+09:00 [INFO][NRF][MGMT] Create NF Profile
2022-01-31T14:51:14+09:00 [INFO][NRF][MGMT] Location header: http://127.0.0.10:8000/nnrf-nfm/v1/nf-instances/702790f0-0795-48f3-84cf-a73777518f9d
2022-01-31T14:51:14+09:00 [INFO][NRF][GIN] | 201 | 127.0.0.1 | PUT | /nnrf-nfm/v1/nf-instances/702790f0-0795-48f3-84cf-a73777518f9d |
2022-01-31T14:51:14+09:00 [INFO][SMF][Init] SMF Registration to NRF {702790f0-0795-48f3-84cf-a73777518f9d SMF REGISTERED 0 0xc000650740 0xc000650780 [] [] [127.0.0.2] [] <nil> [] [] <nil> 0 0 0 area1 <nil> <nil> <nil> <nil> 0xc000099480 <nil> <nil> <nil> <nil> <nil> map[] <nil> false 0xc0006505c0 false false []}
2022-01-31T14:51:14+09:00 [INFO][SMF][PFCP] Listen on 10.200.200.1:8805
2022-01-31T14:51:14+09:00 [INFO][SMF][App] Send PFCP Association Request to UPF[10.200.200.101]
2022-01-31T14:51:14+09:00 [INFO][UPF][Util] [PFCP] Handle PFCP association setup request
2022-01-31T14:51:14+09:00 [INFO][UPF][Util] [PFCP] Association Setup Response
2022-01-31T14:51:14+09:00 [INFO][LIB][PFCP] Remove Request Transaction [1]
2022-01-31T14:51:14+09:00 [INFO][SMF][PFCP] In HandlePfcpAssociationSetupResponse
2022-01-31T14:51:14+09:00 [INFO][SMF][PFCP] Handle PFCP Association Setup Response with NodeID[10.200.200.101]
2022-01-31T14:51:14+09:00 [INFO][SMF][PFCP] UPF(10.200.200.101)[internet] setup association
2022-01-31T14:51:14+09:00 [INFO][UDR][Init] UDR Log level is set to [info] level
2022-01-31T14:51:14+09:00 [INFO][LIB][Path] set log level : info
2022-01-31T14:51:14+09:00 [INFO][LIB][Path] set report call : false
2022-01-31T14:51:14+09:00 [INFO][LIB][OAPI] set log level : info
2022-01-31T14:51:14+09:00 [INFO][LIB][OAPI] set report call : false
2022-01-31T14:51:14+09:00 [INFO][LIB][MonDB] set log level : info
2022-01-31T14:51:14+09:00 [INFO][LIB][MonDB] set report call : false
2022-01-31T14:51:14+09:00 [INFO][UDR][CFG] config version [1.0.0]
2022-01-31T14:51:14+09:00 [INFO][UDR][Init] UDR Config Info: Version[1.0.0] Description[UDR initial local configuration]
2022-01-31T14:51:14+09:00 [INFO][UDR][Init] Server started
2022-01-31T14:51:14+09:00 [INFO][UDR][Util] udrconfig Info: Version[1.0.0] Description[UDR initial local configuration]
2022-01-31T14:51:14+09:00 [INFO][NRF][MGMT] Handle NFRegisterRequest
2022-01-31T14:51:14+09:00 [INFO][NRF][MGMT] urilist update
2022-01-31T14:51:14+09:00 [INFO][NRF][MGMT] Create NF Profile
2022-01-31T14:51:15+09:00 [INFO][NRF][MGMT] Location header: http://127.0.0.10:8000/nnrf-nfm/v1/nf-instances/a9c17b81-6a55-4fe5-9441-23f69510656d
2022-01-31T14:51:15+09:00 [INFO][NRF][GIN] | 201 | 127.0.0.1 | PUT | /nnrf-nfm/v1/nf-instances/a9c17b81-6a55-4fe5-9441-23f69510656d |
2022-01-31T14:51:15+09:00 [INFO][PCF][Init] PCF Log level is set to [info] level
2022-01-31T14:51:15+09:00 [INFO][LIB][Path] set log level : info
2022-01-31T14:51:15+09:00 [INFO][LIB][Path] set report call : false
2022-01-31T14:51:15+09:00 [INFO][LIB][OAPI] set log level : info
2022-01-31T14:51:15+09:00 [INFO][LIB][OAPI] set report call : false
2022-01-31T14:51:15+09:00 [INFO][PCF][CFG] config version [1.0.0]
2022-01-31T14:51:15+09:00 [INFO][PCF][Init] Server started
2022-01-31T14:51:15+09:00 [INFO][PCF][Util] pcfconfig Info: Version[1.0.0] Description[PCF initial local configuration]
2022-01-31T14:51:15+09:00 [INFO][NRF][MGMT] Handle NFRegisterRequest
2022-01-31T14:51:15+09:00 [INFO][NRF][MGMT] urilist update
2022-01-31T14:51:15+09:00 [INFO][NRF][MGMT] Create NF Profile
2022-01-31T14:51:15+09:00 [INFO][NRF][MGMT] Location header: http://127.0.0.10:8000/nnrf-nfm/v1/nf-instances/741d3f3c-9d62-4f5d-9b49-b50a5d03e327
2022-01-31T14:51:15+09:00 [INFO][NRF][GIN] | 201 | 127.0.0.1 | PUT | /nnrf-nfm/v1/nf-instances/741d3f3c-9d62-4f5d-9b49-b50a5d03e327 |
2022-01-31T14:51:15+09:00 [INFO][NRF][DSCV] Handle NFDiscoveryRequest
2022-01-31T14:51:15+09:00 [INFO][NRF][GIN] | 200 | 127.0.0.1 | GET | /nnrf-disc/v1/nf-instances?requester-nf-type=PCF&service-names=nudr-dr&target-nf-type=UDR |
2022-01-31T14:51:15+09:00 [INFO][UDM][Init] UDM Log level is set to [info] level
2022-01-31T14:51:15+09:00 [INFO][LIB][Path] set log level : info
2022-01-31T14:51:15+09:00 [INFO][LIB][Path] set report call : false
2022-01-31T14:51:15+09:00 [INFO][LIB][OAPI] set log level : info
2022-01-31T14:51:15+09:00 [INFO][LIB][OAPI] set report call : false
2022-01-31T14:51:15+09:00 [INFO][UDM][CFG] config version [1.0.1]
2022-01-31T14:51:15+09:00 [INFO][UDM][Init] UDM Config Info: Version[1.0.1] Description[UDM initial local configuration]
2022-01-31T14:51:15+09:00 [INFO][UDM][Init] Server started
2022-01-31T14:51:15+09:00 [INFO][UDM][Util] udmconfig Info: Version[1.0.1] Description[UDM initial local configuration]
2022-01-31T14:51:15+09:00 [INFO][NRF][MGMT] Handle NFRegisterRequest
2022-01-31T14:51:15+09:00 [INFO][NRF][MGMT] urilist update
2022-01-31T14:51:15+09:00 [INFO][NRF][MGMT] Create NF Profile
2022-01-31T14:51:15+09:00 [INFO][NRF][MGMT] Location header: http://127.0.0.10:8000/nnrf-nfm/v1/nf-instances/142931ac-5317-4292-8fbf-8d7c6596345d
2022-01-31T14:51:15+09:00 [INFO][NRF][GIN] | 201 | 127.0.0.1 | PUT | /nnrf-nfm/v1/nf-instances/142931ac-5317-4292-8fbf-8d7c6596345d |
2022-01-31T14:51:15+09:00 [INFO][NSSF][Init] NSSF Log level is set to [info] level
2022-01-31T14:51:15+09:00 [INFO][LIB][Path] set log level : info
2022-01-31T14:51:15+09:00 [INFO][LIB][Path] set report call : false
2022-01-31T14:51:15+09:00 [INFO][LIB][OAPI] set log level : info
2022-01-31T14:51:15+09:00 [INFO][LIB][OAPI] set report call : false
2022-01-31T14:51:15+09:00 [INFO][NSSF][CFG] config version [1.0.0]
2022-01-31T14:51:15+09:00 [INFO][NSSF][Init] Server started
2022-01-31T14:51:15+09:00 [INFO][NRF][MGMT] Handle NFRegisterRequest
2022-01-31T14:51:15+09:00 [INFO][NRF][MGMT] urilist update
2022-01-31T14:51:15+09:00 [INFO][NRF][MGMT] Create NF Profile
2022-01-31T14:51:15+09:00 [INFO][NRF][MGMT] Location header: http://127.0.0.10:8000/nnrf-nfm/v1/nf-instances/8345539f-8db7-45f9-a605-8440634dcafd
2022-01-31T14:51:15+09:00 [INFO][NRF][GIN] | 201 | 127.0.0.1 | PUT | /nnrf-nfm/v1/nf-instances/8345539f-8db7-45f9-a605-8440634dcafd |
2022-01-31T14:51:15+09:00 [INFO][AUSF][Init] AUSF Log level is set to [info] level
2022-01-31T14:51:15+09:00 [INFO][LIB][Path] set log level : info
2022-01-31T14:51:15+09:00 [INFO][LIB][Path] set report call : false
2022-01-31T14:51:15+09:00 [INFO][LIB][OAPI] set log level : info
2022-01-31T14:51:15+09:00 [INFO][LIB][OAPI] set report call : false
2022-01-31T14:51:15+09:00 [INFO][AUSF][CFG] config version [1.0.0]
2022-01-31T14:51:15+09:00 [INFO][AUSF][Init] Server started
2022-01-31T14:51:15+09:00 [INFO][AUSF][Init] ausfconfig Info: Version[1.0.0] Description[AUSF initial local configuration]
ausf context = &{{{0 0} {<nil>} map[] 0} {{0 0} {<nil>} map[] 0} 92296baa-87f2-46a9-bd32-337dbd186605 ausfGroup001 8000 127.0.0.9 127.0.0.9 http://127.0.0.9:8000 http http://127.0.0.10:8000 map[nausf-auth:{92296baa-87f2-46a9-bd32-337dbd186605 nausf-auth 0xc0006502c0 http REGISTERED 0xc0006502a0 [] <nil> [] [] <nil> 0 0 0 <nil> <nil> }] [{208 93} {123 45}] 0xc000320280 false}
2022-01-31T14:51:15+09:00 [INFO][NRF][MGMT] Handle NFRegisterRequest
2022-01-31T14:51:15+09:00 [INFO][NRF][MGMT] urilist update
2022-01-31T14:51:15+09:00 [INFO][NRF][MGMT] Create NF Profile
2022-01-31T14:51:15+09:00 [INFO][NRF][MGMT] Location header: http://127.0.0.10:8000/nnrf-nfm/v1/nf-instances/92296baa-87f2-46a9-bd32-337dbd186605
2022-01-31T14:51:15+09:00 [INFO][NRF][GIN] | 201 | 127.0.0.1 | PUT | /nnrf-nfm/v1/nf-instances/92296baa-87f2-46a9-bd32-337dbd186605 |
=== RUN TestPaging
2022-01-31T14:51:16+09:00 [INFO][AMF][NGAP] [AMF] SCTP Accept from: 127.0.0.1:9487
2022-01-31T14:51:16+09:00 [INFO][AMF][NGAP] Create a new NG connection for: 127.0.0.1:9487
2022-01-31T14:51:16+09:00 [INFO][AMF][NGAP][127.0.0.1:9487] Handle NG Setup request
2022-01-31T14:51:16+09:00 [INFO][AMF][NGAP][127.0.0.1:9487] Send NG-Setup response
2022-01-31T14:51:16+09:00 [INFO][AMF][NGAP][127.0.0.1:9487] Handle Initial UE Message
2022-01-31T14:51:16+09:00 [INFO][AMF][GMM][AMF_UE_NGAP_ID:1] Handle Registration Request
2022-01-31T14:51:16+09:00 [INFO][AMF][GMM][AMF_UE_NGAP_ID:1] Authentication procedure
2022-01-31T14:51:16+09:00 [INFO][NRF][DSCV] Handle NFDiscoveryRequest
2022-01-31T14:51:16+09:00 [INFO][NRF][GIN] | 200 | 127.0.0.1 | GET | /nnrf-disc/v1/nf-instances?requester-nf-type=AMF&target-nf-type=AUSF |
2022-01-31T14:51:16+09:00 [INFO][AUSF][UeAuthPost] HandleUeAuthPostRequest
2022-01-31T14:51:16+09:00 [INFO][AUSF][UeAuthPost] Serving network authorized
2022-01-31T14:51:16+09:00 [INFO][NRF][DSCV] Handle NFDiscoveryRequest
2022-01-31T14:51:16+09:00 [INFO][NRF][GIN] | 200 | 127.0.0.1 | GET | /nnrf-disc/v1/nf-instances?requester-nf-type=AUSF&service-names=nudm-ueau&target-nf-type=UDM |
2022-01-31T14:51:16+09:00 [INFO][UDM][UEAU] Handle GenerateAuthDataRequest
2022-01-31T14:51:16+09:00 [INFO][LIB][3GPP] suciPart: [suci 0 208 93 0 0 0 00007487]
2022-01-31T14:51:16+09:00 [INFO][LIB][3GPP] scheme 0
2022-01-31T14:51:16+09:00 [INFO][LIB][3GPP] SUPI type is IMSI
http://127.0.0.10:8000
2022-01-31T14:51:16+09:00 [INFO][NRF][DSCV] Handle NFDiscoveryRequest
2022-01-31T14:51:16+09:00 [INFO][NRF][GIN] | 200 | 127.0.0.1 | GET | /nnrf-disc/v1/nf-instances?requester-nf-type=UDM&target-nf-type=UDR |
2022-01-31T14:51:16+09:00 [INFO][UDR][DRepo] Handle QueryAuthSubsData
2022-01-31T14:51:16+09:00 [INFO][UDR][GIN] | 200 | 127.0.0.1 | GET | /nudr-dr/v1/subscription-data/imsi-2089300007487/authentication-data/authentication-subscription |
2022/01/31 14:51:16 http2: server connection error from 127.0.0.1:53540: connection error: PROTOCOL_ERROR
2022-01-31T14:51:16+09:00 [INFO][UDR][DRepo] Handle ModifyAuthentication
2022-01-31T14:51:16+09:00 [INFO][UDR][GIN] | 204 | 127.0.0.1 | PATCH | /nudr-dr/v1/subscription-data/imsi-2089300007487/authentication-data/authentication-subscription |
AUTN = 1d01a8611e188000beb08deb451899fe
2022-01-31T14:51:16+09:00 [INFO][UDM][GIN] | 200 | 127.0.0.1 | POST | /nudm-ueau/v1/suci-0-208-93-0-0-0-00007487/security-information/generate-auth-data |
2022-01-31T14:51:16+09:00 [INFO][AUSF][UeAuthPost] Add SuciSupiPair (suci-0-208-93-0-0-0-00007487, imsi-2089300007487) to map.
2022-01-31T14:51:16+09:00 [INFO][AUSF][UeAuthPost] Use 5G AKA auth method
2022-01-31T14:51:16+09:00 [INFO][AUSF][5gAkaAuth] XresStar = 3063323031363366366238613139623133313865636561376332333366393534
2022-01-31T14:51:16+09:00 [INFO][AUSF][GIN] | 201 | 127.0.0.1 | POST | /nausf-auth/v1/ue-authentications |
2022-01-31T14:51:16+09:00 [INFO][AMF][GMM][AMF_UE_NGAP_ID:1] Send Authentication Request
2022-01-31T14:51:16+09:00 [INFO][AMF][NGAP][127.0.0.1:9487][AMF_UE_NGAP_ID:1] Send Downlink Nas Transport
2022-01-31T14:51:16+09:00 [INFO][AMF][NGAP][127.0.0.1:9487] Handle Uplink Nas Transport
2022-01-31T14:51:16+09:00 [INFO][AMF][NGAP][127.0.0.1:9487][AMF_UE_NGAP_ID:1] Uplink NAS Transport (RAN UE NGAP ID: 1)
2022-01-31T14:51:16+09:00 [INFO][AMF][GMM][AMF_UE_NGAP_ID:1] Handle Authentication Response
==================
WARNING: DATA RACE
Write at 0x000003672360 by goroutine 36:
github.com/free5gc/openapi/Nausf_UEAuthentication.NewAPIClient()
/home/nishi/go/pkg/mod/github.com/free5gc/[email protected]/Nausf_UEAuthentication/client.go:40 +0xdd2
github.com/free5gc/amf/consumer.SendAuth5gAkaConfirmRequest()
/home/nishi/free5gc-deb/free5gc/NFs/amf/consumer/ue_authentication.go:66 +0x41c
github.com/free5gc/amf/gmm.HandleAuthenticationResponse()
/home/nishi/free5gc-deb/free5gc/NFs/amf/gmm/handler.go:1944 +0xb83
github.com/free5gc/amf/gmm.Authentication()
/home/nishi/free5gc-deb/free5gc/NFs/amf/gmm/sm.go:181 +0x80b
github.com/free5gc/fsm.(*FSM).SendEvent()
/home/nishi/go/pkg/mod/github.com/free5gc/[email protected]/fsm.go:95 +0x2e1
github.com/free5gc/amf/nas.Dispatch()
/home/nishi/free5gc-deb/free5gc/NFs/amf/nas/dispatch.go:27 +0x474
github.com/free5gc/amf/nas.HandleNAS()
/home/nishi/free5gc-deb/free5gc/NFs/amf/nas/handler.go:33 +0x2ec
github.com/free5gc/amf/ngap.HandleUplinkNasTransport()
/home/nishi/free5gc-deb/free5gc/NFs/amf/ngap/handler.go:234 +0x8bd
github.com/free5gc/amf/ngap.Dispatch()
/home/nishi/free5gc-deb/free5gc/NFs/amf/ngap/dispatcher.go:49 +0xcaf
github.com/free5gc/amf/ngap/service.handleConnection()
/home/nishi/free5gc-deb/free5gc/NFs/amf/ngap/service/service.go:204 +0x45a
Previous write at 0x000003672360 by goroutine 45:
github.com/free5gc/openapi/Nudr_DataRepository.NewAPIClient()
/home/nishi/go/pkg/mod/github.com/free5gc/[email protected]/Nudr_DataRepository/client.go:79 +0x102e
github.com/free5gc/udr/producer/callback.SendOnDataChangeNotify()
/home/nishi/free5gc-deb/free5gc/NFs/udr/producer/callback/callback.go:15 +0x1a3
Goroutine 36 (running) created at:
github.com/free5gc/amf/ngap/service.listenAndServe()
/home/nishi/free5gc-deb/free5gc/NFs/amf/ngap/service/service.go:136 +0x12a4
Goroutine 45 (finished) created at:
github.com/free5gc/udr/producer.PreHandleOnDataChangeNotify()
/home/nishi/free5gc-deb/free5gc/NFs/udr/producer/callback.go:31 +0x3fa
github.com/free5gc/udr/producer.ModifyAuthenticationProcedure()
/home/nishi/free5gc-deb/free5gc/NFs/udr/producer/data_repository.go:281 +0x44d
github.com/free5gc/udr/producer.HandleModifyAuthentication()
/home/nishi/free5gc-deb/free5gc/NFs/udr/producer/data_repository.go:260 +0x199
github.com/free5gc/udr/datarepository.HTTPModifyAuthentication()
/home/nishi/free5gc-deb/free5gc/NFs/udr/datarepository/api_authentication_data_document.go:57 +0x4a1
github.com/gin-gonic/gin.(*Context).Next()
/home/nishi/go/pkg/mod/github.com/gin-gonic/[email protected]/context.go:161 +0xa6
github.com/gin-gonic/gin.RecoveryWithWriter.func1()
/home/nishi/go/pkg/mod/github.com/gin-gonic/[email protected]/recovery.go:83 +0x85
github.com/gin-gonic/gin.(*Context).Next()
/home/nishi/go/pkg/mod/github.com/gin-gonic/[email protected]/context.go:161 +0xa6
github.com/free5gc/logger_util.ginToLogrus.func1()
/home/nishi/go/pkg/mod/github.com/free5gc/[email protected]/logger_util.go:65 +0x162
github.com/gin-gonic/gin.(*Context).Next()
/home/nishi/go/pkg/mod/github.com/gin-gonic/[email protected]/context.go:161 +0xa6
github.com/gin-gonic/gin.(*Engine).handleHTTPRequest()
/home/nishi/go/pkg/mod/github.com/gin-gonic/[email protected]/gin.go:409 +0xa5d
github.com/gin-gonic/gin.(*Engine).ServeHTTP()
/home/nishi/go/pkg/mod/github.com/gin-gonic/[email protected]/gin.go:367 +0x2f4
net/http.Handler.ServeHTTP-fm()
/usr/local/go/src/net/http/server.go:87 +0x64
golang.org/x/net/http2.(*serverConn).runHandler()
/home/nishi/go/pkg/mod/golang.org/x/[email protected]/http2/server.go:2176 +0xc0
==================
2022-01-31T14:51:16+09:00 [INFO][AUSF][5gAkaAuth] Auth5gAkaComfirmRequest
2022-01-31T14:51:16+09:00 [INFO][AUSF][5gAkaAuth] res*: 3063323031363366366238613139623133313865636561376332333366393534
Xres*: 3063323031363366366238613139623133313865636561376332333366393534
2022-01-31T14:51:16+09:00 [INFO][AUSF][5gAkaAuth] 5G AKA confirmation succeeded
2022-01-31T14:51:16+09:00 [INFO][UDM][UEAU] Handle ConfirmAuthDataRequest
2022-01-31T14:51:16+09:00 [INFO][UDR][DRepo] Handle CreateAuthenticationStatus
2022-01-31T14:51:16+09:00 [INFO][UDR][GIN] | 204 | 127.0.0.1 | PUT | /nudr-dr/v1/subscription-data/imsi-2089300007487/authentication-data/authentication-status |
2022-01-31T14:51:16+09:00 [INFO][UDM][GIN] | 201 | 127.0.0.1 | POST | /nudm-ueau/v1/imsi-2089300007487/auth-events |
2022-01-31T14:51:16+09:00 [INFO][AUSF][GIN] | 200 | 127.0.0.1 | PUT | /nausf-auth/v1/ue-authentications/suci-0-208-93-0-0-0-00007487/5g-aka-confirmation |
2022-01-31T14:51:16+09:00 [INFO][AMF][GMM][AMF_UE_NGAP_ID:1][SUPI:imsi-2089300007487] Send Security Mode Command
2022-01-31T14:51:16+09:00 [INFO][AMF][NGAP][127.0.0.1:9487][AMF_UE_NGAP_ID:1] Send Downlink Nas Transport
Security Header Type Integrity Protected With New 5g Nas Security Context
cmac value: 0x3a06f515
err <nil>
2022-01-31T14:51:16+09:00 [INFO][AMF][NGAP][127.0.0.1:9487] Handle Uplink Nas Transport
2022-01-31T14:51:16+09:00 [INFO][AMF][NGAP][127.0.0.1:9487][AMF_UE_NGAP_ID:1] Uplink NAS Transport (RAN UE NGAP ID: 1)
2022-01-31T14:51:16+09:00 [INFO][AMF][GMM][AMF_UE_NGAP_ID:1][SUPI:imsi-2089300007487] Handle Security Mode Complete
2022-01-31T14:51:16+09:00 [INFO][AMF][GMM][AMF_UE_NGAP_ID:1][SUPI:imsi-2089300007487] Handle InitialRegistration
2022-01-31T14:51:16+09:00 [INFO][NRF][DSCV] Handle NFDiscoveryRequest
2022-01-31T14:51:16+09:00 [INFO][NRF][GIN] | 200 | 127.0.0.1 | GET | /nnrf-disc/v1/nf-instances?requester-nf-type=AMF&supi=imsi-2089300007487&target-nf-type=UDM |
2022-01-31T14:51:16+09:00 [INFO][UDM][SDM] Handle GetNssai
2022-01-31T14:51:16+09:00 [INFO][UDR][DRepo] Handle QueryAmData
2022-01-31T14:51:16+09:00 [INFO][UDR][GIN] | 200 | 127.0.0.1 | GET | /nudr-dr/v1/subscription-data/imsi-2089300007487/20893/provisioned-data/am-data?supported-features= |
2022-01-31T14:51:16+09:00 [INFO][UDM][GIN] | 200 | 127.0.0.1 | GET | /nudm-sdm/v1/imsi-2089300007487/nssai?plmn-id=%7B%22mcc%22%3A%22208%22%2C%22mnc%22%3A%2293%22%7D |
2022-01-31T14:51:16+09:00 [INFO][NRF][DSCV] Handle NFDiscoveryRequest
2022-01-31T14:51:16+09:00 [INFO][NRF][GIN] | 200 | 127.0.0.1 | GET | /nnrf-disc/v1/nf-instances?requester-nf-type=AMF&supi=imsi-2089300007487&target-nf-type=UDM |
2022-01-31T14:51:16+09:00 [INFO][UDM][UECM] Handle RegistrationAmf3gppAccess
2022-01-31T14:51:16+09:00 [INFO][UDM][UECM] UEID: imsi-2089300007487
2022-01-31T14:51:16+09:00 [INFO][UDR][DRepo] Handle CreateAmfContext3gpp
2022-01-31T14:51:16+09:00 [INFO][UDR][GIN] | 204 | 127.0.0.1 | PUT | /nudr-dr/v1/subscription-data/imsi-2089300007487/context-data/amf-3gpp-access |
2022-01-31T14:51:16+09:00 [INFO][UDM][GIN] | 201 | 127.0.0.1 | PUT | /nudm-uecm/v1/imsi-2089300007487/registrations/amf-3gpp-access |
2022/01/31 14:51:16 http2: server connection error from 127.0.0.1:52006: connection error: PROTOCOL_ERROR
2022-01-31T14:51:16+09:00 [INFO][UDM][SDM] Handle GetAmData
2022-01-31T14:51:16+09:00 [INFO][UDR][DRepo] Handle QueryAmData
2022-01-31T14:51:16+09:00 [INFO][UDR][GIN] | 200 | 127.0.0.1 | GET | /nudr-dr/v1/subscription-data/imsi-2089300007487/20893/provisioned-data/am-data?supported-features=%7B%22mcc%22%3A%22208%22%2C%22mnc%22%3A%2293%22%7D |
2022-01-31T14:51:16+09:00 [INFO][UDM][GIN] | 200 | 127.0.0.1 | GET | /nudm-sdm/v1/imsi-2089300007487/am-data?plmn-id=%7B%22mcc%22%3A%22208%22%2C%22mnc%22%3A%2293%22%7D |
2022/01/31 14:51:16 http2: server connection error from 127.0.0.1:52010: connection error: PROTOCOL_ERROR
2022-01-31T14:51:16+09:00 [INFO][UDM][SDM] Handle GetSmfSelectData
2022-01-31T14:51:16+09:00 [INFO][UDR][DRepo] Handle QuerySmfSelectData
2022-01-31T14:51:16+09:00 [INFO][UDR][GIN] | 200 | 127.0.0.1 | GET | /nudr-dr/v1/subscription-data/imsi-2089300007487/20893/provisioned-data/smf-selection-subscription-data?supported-features= |
2022-01-31T14:51:16+09:00 [INFO][UDM][GIN] | 200 | 127.0.0.1 | GET | /nudm-sdm/v1/imsi-2089300007487/smf-select-data?plmn-id=%7B%22mcc%22%3A%22208%22%2C%22mnc%22%3A%2293%22%7D |
2022/01/31 14:51:16 http2: server connection error from 127.0.0.1:52014: connection error: PROTOCOL_ERROR
2022-01-31T14:51:16+09:00 [INFO][UDM][SDM] Handle GetUeContextInSmfData
2022-01-31T14:51:16+09:00 [INFO][UDR][DRepo] Handle QuerySmfRegList
2022-01-31T14:51:16+09:00 [INFO][UDR][GIN] | 200 | 127.0.0.1 | GET | /nudr-dr/v1/subscription-data/imsi-2089300007487/context-data/smf-registrations?supported-features= |
2022-01-31T14:51:16+09:00 [INFO][UDM][GIN] | 200 | 127.0.0.1 | GET | /nudm-sdm/v1/imsi-2089300007487/ue-context-in-smf-data |
2022/01/31 14:51:16 http2: server connection error from 127.0.0.1:52018: connection error: PROTOCOL_ERROR
2022-01-31T14:51:16+09:00 [INFO][UDM][SDM] Handle Subscribe
2022-01-31T14:51:16+09:00 [INFO][UDR][DRepo] Handle CreateSdmSubscriptions
2022-01-31T14:51:16+09:00 [INFO][UDR][GIN] | 201 | 127.0.0.1 | POST | /nudr-dr/v1/subscription-data/imsi-2089300007487/context-data/sdm-subscriptions |
2022-01-31T14:51:16+09:00 [INFO][UDM][GIN] | 201 | 127.0.0.1 | POST | /nudm-sdm/v1/imsi-2089300007487/sdm-subscriptions |
2022-01-31T14:51:16+09:00 [INFO][NRF][DSCV] Handle NFDiscoveryRequest
2022-01-31T14:51:16+09:00 [INFO][NRF][GIN] | 200 | 127.0.0.1 | GET | /nnrf-disc/v1/nf-instances?preferred-locality=area1&requester-nf-type=AMF&supi=imsi-2089300007487&target-nf-type=PCF |
2022-01-31T14:51:16+09:00 [INFO][PCF][Ampolicy] Handle AM Policy Create Request
2022-01-31T14:51:16+09:00 [INFO][NRF][DSCV] Handle NFDiscoveryRequest
2022-01-31T14:51:16+09:00 [INFO][NRF][GIN] | 200 | 127.0.0.1 | GET | /nnrf-disc/v1/nf-instances?requester-nf-type=PCF&target-nf-type=UDR |
2022-01-31T14:51:16+09:00 [INFO][UDR][DRepo] Handle PolicyDataUesUeIdAmDataGet
2022-01-31T14:51:16+09:00 [INFO][UDR][GIN] | 200 | 127.0.0.1 | GET | /nudr-dr/v1/policy-data/ues/imsi-2089300007487/am-data |
2022-01-31T14:51:16+09:00 [INFO][NRF][DSCV] Handle NFDiscoveryRequest
2022-01-31T14:51:16+09:00 [INFO][NRF][GIN] | 200 | 127.0.0.1 | GET | /nnrf-disc/v1/nf-instances?guami=%7B%22plmnId%22%3A%7B%22mcc%22%3A%22208%22%2C%22mnc%22%3A%2293%22%7D%2C%22amfId%22%3A%22cafe00%22%7D&requester-nf-type=PCF&target-nf-type=AMF |
2022-01-31T14:51:16+09:00 [INFO][AMF][Comm] Handle AMF Status Change Subscribe Request
2022-01-31T14:51:16+09:00 [INFO][AMF][Comm] new AMF Status Subscription[1]
2022-01-31T14:51:16+09:00 [INFO][AMF][GIN] | 201 | 127.0.0.1 | POST | /namf-comm/v1/subscriptions |
2022-01-31T14:51:16+09:00 [INFO][PCF][GIN] | 201 | 127.0.0.1 | POST | /npcf-am-policy-control/v1/policies |
2022-01-31T14:51:16+09:00 [INFO][AMF][GMM][AMF_UE_NGAP_ID:1][SUPI:imsi-2089300007487] Send Registration Accept
2022-01-31T14:51:16+09:00 [INFO][AMF][NGAP][127.0.0.1:9487][AMF_UE_NGAP_ID:1] Send Initial Context Setup Request
2022-01-31T14:51:16+09:00 [INFO][AMF][NGAP][127.0.0.1:9487] Handle Initial Context Setup Response
2022-01-31T14:51:16+09:00 [INFO][NAS][Message] Encode ExtendedProtocolConfigurationOptions in EncodePDUSessionEstablishmentRequest
2022-01-31T14:51:16+09:00 [INFO][AMF][NGAP][127.0.0.1:9487] Handle Uplink Nas Transport
2022-01-31T14:51:16+09:00 [INFO][AMF][NGAP][127.0.0.1:9487][AMF_UE_NGAP_ID:1] Uplink NAS Transport (RAN UE NGAP ID: 1)
2022-01-31T14:51:16+09:00 [INFO][AMF][GMM][AMF_UE_NGAP_ID:1][SUPI:imsi-2089300007487] Handle Registration Complete
2022-01-31T14:51:16+09:00 [INFO][AMF][NGAP][127.0.0.1:9487] Handle Uplink Nas Transport
2022-01-31T14:51:16+09:00 [INFO][AMF][NGAP][127.0.0.1:9487][AMF_UE_NGAP_ID:1] Uplink NAS Transport (RAN UE NGAP ID: 1)
2022-01-31T14:51:16+09:00 [INFO][AMF][GMM][AMF_UE_NGAP_ID:1][SUPI:imsi-2089300007487] Handle UL NAS Transport
2022-01-31T14:51:16+09:00 [INFO][AMF][GMM][AMF_UE_NGAP_ID:1][SUPI:imsi-2089300007487] Transport 5GSM Message to SMF
2022-01-31T14:51:16+09:00 [INFO][AMF][GMM][AMF_UE_NGAP_ID:1][SUPI:imsi-2089300007487] Select SMF [snssai: {Sst:1 Sd:010203}, dnn: internet]
2022-01-31T14:51:16+09:00 [INFO][NRF][DSCV] Handle NFDiscoveryRequest
2022-01-31T14:51:16+09:00 [INFO][NRF][GIN] | 200 | 127.0.0.1 | GET | /nnrf-disc/v1/nf-instances?requester-nf-type=AMF&target-nf-type=NSSF |
2022-01-31T14:51:16+09:00 [INFO][NSSF][NsSelect] Handle NSSelectionGet
2022-01-31T14:51:16+09:00 [INFO][NSSF][GIN] | 200 | 127.0.0.1 | GET | /nnssf-nsselection/v1/network-slice-information?nf-id=139f22d5-1de7-4b3b-b6d1-f1bb94b504bd&nf-type=AMF&slice-info-request-for-pdu-session=%7B%22sNssai%22%3A%7B%22sst%22%3A1%2C%22sd%22%3A%22010203%22%7D%2C%22roamingIndication%22%3A%22NON_ROAMING%22%7D |
2022-01-31T14:51:16+09:00 [INFO][NRF][DSCV] Handle NFDiscoveryRequest
2022-01-31T14:51:16+09:00 [INFO][NRF][GIN] | 200 | 127.0.0.1 | GET | /nnrf-disc/v1/nf-instances?dnn=internet&preferred-locality=area1&requester-nf-type=AMF&service-names=nsmf-pdusession&snssais=%7B%22sst%22%3A1%2C%22sd%22%3A%22010203%22%7D&target-nf-type=SMF&target-plmn-list=%7B%22mcc%22%3A%22208%22%2C%22mnc%22%3A%2293%22%7D |
2022-01-31T14:51:16+09:00 [INFO][SMF][PduSess] Receive Create SM Context Request
2022-01-31T14:51:16+09:00 [INFO][SMF][PduSess] In HandlePDUSessionSMContextCreate
2022/01/31 14:51:16 http2: server connection error from 127.0.0.1:42658: connection error: PROTOCOL_ERROR
2022-01-31T14:51:16+09:00 [INFO][NRF][DSCV] Handle NFDiscoveryRequest
2022-01-31T14:51:16+09:00 [INFO][NRF][GIN] | 200 | 127.0.0.1 | GET | /nnrf-disc/v1/nf-instances?requester-nf-type=SMF&target-nf-type=UDM |
2022-01-31T14:51:16+09:00 [INFO][SMF][PduSess] Send NF Discovery Serving UDM Successfully
2022-01-31T14:51:16+09:00 [INFO][SMF][CTX] Allocated UE IP address: 60.60.0.1
2022-01-31T14:51:16+09:00 [INFO][SMF][CTX] Selected UPF: UPF
2022-01-31T14:51:16+09:00 [INFO][SMF][PduSess] UE[imsi-2089300007487] PDUSessionID[10] IP[60.60.0.1]
2022-01-31T14:51:16+09:00 [INFO][UDM][SDM] Handle GetSmData
2022-01-31T14:51:16+09:00 [INFO][UDM][SDM] getSmDataProcedure: SUPI[imsi-2089300007487] PLMNID[20893] DNN[internet] SNssai[{"sst":1,"sd":"010203"}]
2022/01/31 14:51:16 http2: server connection error from 127.0.0.1:53604: connection error: PROTOCOL_ERROR
2022-01-31T14:51:16+09:00 [INFO][UDR][DRepo] Handle QuerySmData
2022-01-31T14:51:16+09:00 [INFO][UDR][GIN] | 200 | 127.0.0.1 | GET | /nudr-dr/v1/subscription-data/imsi-2089300007487/20893/provisioned-data/sm-data?single-nssai=%7B%22sst%22%3A1%2C%22sd%22%3A%22010203%22%7D |
2022-01-31T14:51:16+09:00 [INFO][UDM][GIN] | 200 | 127.0.0.1 | GET | /nudm-sdm/v1/imsi-2089300007487/sm-data?dnn=internet&plmn-id=%7B%22mcc%22%3A%22208%22%2C%22mnc%22%3A%2293%22%7D&single-nssai=%7B%22sst%22%3A1%2C%22sd%22%3A%22010203%22%7D |
2022-01-31T14:51:16+09:00 [INFO][SMF][GSM] In HandlePDUSessionEstablishmentRequest
2022-01-31T14:51:16+09:00 [INFO][NAS][Convert] ProtocolOrContainerList: [0xc0007c82a0 0xc0007c82e0 0xc0007c8320]
2022-01-31T14:51:16+09:00 [INFO][SMF][GSM] Protocol Configuration Options
2022-01-31T14:51:16+09:00 [INFO][SMF][GSM] &{[0xc0007c82a0 0xc0007c82e0 0xc0007c8320]}
2022-01-31T14:51:16+09:00 [INFO][SMF][GSM] Didn't Implement container type IPAddressAllocationViaNASSignallingUL
2022-01-31T14:51:16+09:00 [INFO][SMF][PduSess] PCF Selection for SMContext SUPI[imsi-2089300007487] PDUSessionID[10]
2022-01-31T14:51:16+09:00 [INFO][NRF][DSCV] Handle NFDiscoveryRequest
2022-01-31T14:51:16+09:00 [INFO][NRF][GIN] | 200 | 127.0.0.1 | GET | /nnrf-disc/v1/nf-instances?preferred-locality=area1&requester-nf-type=SMF&target-nf-type=PCF |
2022-01-31T14:51:16+09:00 [INFO][PCF][SMpolicy] Handle CreateSmPolicy
2022-01-31T14:51:16+09:00 [INFO][UDR][DRepo] Handle PolicyDataUesUeIdSmDataGet
2022-01-31T14:51:16+09:00 [INFO][UDR][GIN] | 200 | 127.0.0.1 | GET | /nudr-dr/v1/policy-data/ues/imsi-2089300007487/sm-data?dnn=internet&snssai=%7B%22sst%22%3A1%2C%22sd%22%3A%22010203%22%7D |
2022-01-31T14:51:17+09:00 [INFO][PCF][GIN] | 201 | 127.0.0.1 | POST | /npcf-smpolicycontrol/v1/sm-policies |
2022-01-31T14:51:17+09:00 [INFO][SMF][PduSess] SUPI[imsi-2089300007487] has no pre-config route
2022-01-31T14:51:17+09:00 [INFO][NRF][DSCV] Handle NFDiscoveryRequest
2022-01-31T14:51:17+09:00 [INFO][NRF][GIN] | 200 | 127.0.0.1 | GET | /nnrf-disc/v1/nf-instances?requester-nf-type=SMF&target-nf-instance-id=139f22d5-1de7-4b3b-b6d1-f1bb94b504bd&target-nf-type=AMF |
2022-01-31T14:51:17+09:00 [INFO][SMF][Consumer] SendNFDiscoveryServingAMF ok
2022-01-31T14:51:17+09:00 [INFO][UPF][Util] [PFCP] Handle PFCP session establishment request
2022-01-31T14:51:17+09:00 [INFO][SMF][GIN] | 201 | 127.0.0.1 | POST | /nsmf-pdusession/v1/sm-contexts |
2022-01-31T14:51:17+09:00 [INFO][UPF][Util] [PFCP] Session Establishment Response
2022-01-31T14:51:17+09:00 [INFO][SMF][PFCP] In HandlePfcpSessionEstablishmentResponse
2022-01-31T14:51:17+09:00 [INFO][LIB][PFCP] Remove Request Transaction [2]
&{1000 Kbps 1000 Kbps}
2022-01-31T14:51:17+09:00 [INFO][AMF][GMM][AMF_UE_NGAP_ID:1][SUPI:imsi-2089300007487] create smContext[pduSessionID: 10] Success
2022-01-31T14:51:17+09:00 [INFO][AMF][Producer] Handle N1N2 Message Transfer Request
2022-01-31T14:51:17+09:00 [INFO][AMF][NGAP][127.0.0.1:9487][AMF_UE_NGAP_ID:1] Send PDU Session Resource Setup Request
2022-01-31T14:51:17+09:00 [INFO][AMF][GIN] | 200 | 127.0.0.1 | POST | /namf-comm/v1/ue-contexts/imsi-2089300007487/n1-n2-messages |
2022-01-31T14:51:17+09:00 [INFO][AMF][NGAP][127.0.0.1:9487] Handle PDU Session Resource Setup Response
2022-01-31T14:51:17+09:00 [INFO][SMF][PduSess] Receive Update SM Context Request
2022-01-31T14:51:17+09:00 [INFO][SMF][PduSess] In HandlePDUSessionSMContextUpdate
==================
WARNING: DATA RACE
Read at 0x00c00099c558 by goroutine 235:
github.com/free5gc/smf/producer.HandlePDUSessionSMContextUpdate()
/home/nishi/free5gc-deb/free5gc/NFs/smf/producer/pdu_session.go:427 +0x5ecb
github.com/free5gc/smf/pdusession.HTTPUpdateSmContext()
/home/nishi/free5gc-deb/free5gc/NFs/smf/pdusession/api_individual_sm_context.go:83 +0x67b
github.com/gin-gonic/gin.(*Context).Next()
/home/nishi/go/pkg/mod/github.com/gin-gonic/[email protected]/context.go:161 +0xa6
github.com/gin-gonic/gin.RecoveryWithWriter.func1()
/home/nishi/go/pkg/mod/github.com/gin-gonic/[email protected]/recovery.go:83 +0x85
github.com/gin-gonic/gin.(*Context).Next()
/home/nishi/go/pkg/mod/github.com/gin-gonic/[email protected]/context.go:161 +0xa6
github.com/free5gc/logger_util.ginToLogrus.func1()
/home/nishi/go/pkg/mod/github.com/free5gc/[email protected]/logger_util.go:65 +0x162
github.com/gin-gonic/gin.(*Context).Next()
/home/nishi/go/pkg/mod/github.com/gin-gonic/[email protected]/context.go:161 +0xa6
github.com/gin-gonic/gin.(*Engine).handleHTTPRequest()
/home/nishi/go/pkg/mod/github.com/gin-gonic/[email protected]/gin.go:409 +0xa5d
github.com/gin-gonic/gin.(*Engine).ServeHTTP()
/home/nishi/go/pkg/mod/github.com/gin-gonic/[email protected]/gin.go:367 +0x2f4
net/http.Handler.ServeHTTP-fm()
/usr/local/go/src/net/http/server.go:87 +0x64
golang.org/x/net/http2.(*serverConn).runHandler()
/home/nishi/go/pkg/mod/golang.org/x/[email protected]/http2/server.go:2176 +0xc0
Previous write at 0x00c00099c558 by goroutine 102:
github.com/free5gc/smf/pfcp/handler.HandlePfcpSessionEstablishmentResponse()
/home/nishi/free5gc-deb/free5gc/NFs/smf/pfcp/handler/handler.go:196 +0xcbf
github.com/free5gc/smf/pfcp.Dispatch()
/home/nishi/free5gc-deb/free5gc/NFs/smf/pfcp/dispatcher.go:43 +0x6f5
Goroutine 235 (running) created at:
golang.org/x/net/http2.(*serverConn).processHeaders()
/home/nishi/go/pkg/mod/golang.org/x/[email protected]/http2/server.go:1906 +0x9a9
golang.org/x/net/http2.(*serverConn).processFrame()
/home/nishi/go/pkg/mod/golang.org/x/[email protected]/http2/server.go:1420 +0x43e
golang.org/x/net/http2.(*serverConn).processFrameFromReader()
/home/nishi/go/pkg/mod/golang.org/x/[email protected]/http2/server.go:1378 +0x7ab
golang.org/x/net/http2.(*serverConn).serve()
/home/nishi/go/pkg/mod/golang.org/x/[email protected]/http2/server.go:877 +0x14c0
golang.org/x/net/http2.(*Server).ServeConn()
/home/nishi/go/pkg/mod/golang.org/x/[email protected]/http2/server.go:471 +0xdcb
golang.org/x/net/http2/h2c.h2cHandler.ServeHTTP()
/home/nishi/go/pkg/mod/golang.org/x/[email protected]/http2/h2c/h2c.go:87 +0x2f7
golang.org/x/net/http2/h2c.(*h2cHandler).ServeHTTP()
<autogenerated>:1 +0x9d
net/http.serverHandler.ServeHTTP()
/usr/local/go/src/net/http/server.go:2807 +0xce
net/http.(*conn).serve()
/usr/local/go/src/net/http/server.go:1895 +0x837
Goroutine 102 (finished) created at:
github.com/free5gc/smf/pfcp/udp.Run.func1()
/home/nishi/free5gc-deb/free5gc/NFs/smf/pfcp/udp/udp.go:44 +0x2a9
==================
2022-01-31T14:51:17+09:00 [INFO][UPF][Util] [PFCP] Handle PFCP session modification request
2022-01-31T14:51:17+09:00 [INFO][UPF][Util] [PFCP] Session Modification Response
2022-01-31T14:51:17+09:00 [INFO][LIB][PFCP] Remove Request Transaction [3]
2022-01-31T14:51:17+09:00 [INFO][SMF][PFCP] In HandlePfcpSessionModificationResponse
2022-01-31T14:51:17+09:00 [INFO][SMF][PduSess] [SMF] PFCP Modification Resonse Accept
2022-01-31T14:51:17+09:00 [INFO][SMF][PFCP] PFCP Session Modification Success[1]
2022-01-31T14:51:17+09:00 [INFO][SMF][GIN] | 200 | 127.0.0.1 | POST | /nsmf-pdusession/v1/sm-contexts/urn:uuid:d0fa772e-1127-4cd1-b4ad-6556e3c08f63/modify |
2022-01-31T14:51:17+09:00 [INFO][AMF][NGAP][127.0.0.1:9487] UE Context Release Request
2022-01-31T14:51:17+09:00 [WARN][AMF][NGAP][127.0.0.1:9487] Cause RadioNetwork[1]
2022-01-31T14:51:17+09:00 [INFO][AMF][NGAP][127.0.0.1:9487][AMF_UE_NGAP_ID:1] Ue Context in GMM-Registered
2022-01-31T14:51:17+09:00 [INFO][SMF][PduSess] Receive Update SM Context Request
2022-01-31T14:51:17+09:00 [INFO][SMF][PduSess] In HandlePDUSessionSMContextUpdate
2022-01-31T14:51:17+09:00 [INFO][UPF][Util] [PFCP] Handle PFCP session modification request
2022-01-31T14:51:17+09:00 [INFO][UPF][Util] [PFCP] Session Modification Response
2022-01-31T14:51:17+09:00 [INFO][LIB][PFCP] Remove Request Transaction [4]
2022-01-31T14:51:17+09:00 [INFO][SMF][PFCP] In HandlePfcpSessionModificationResponse
2022-01-31T14:51:17+09:00 [INFO][SMF][PduSess] [SMF] PFCP Modification Resonse Accept
2022-01-31T14:51:17+09:00 [INFO][SMF][PFCP] PFCP Session Modification Success[1]
2022-01-31T14:51:17+09:00 [INFO][SMF][GIN] | 200 | 127.0.0.1 | POST | /nsmf-pdusession/v1/sm-contexts/urn:uuid:d0fa772e-1127-4cd1-b4ad-6556e3c08f63/modify |
2022-01-31T14:51:17+09:00 [INFO][AMF][NGAP][127.0.0.1:9487][AMF_UE_NGAP_ID:1] Send UE Context Release Command
2022-01-31T14:51:17+09:00 [INFO][AMF][NGAP][127.0.0.1:9487] Handle UE Context Release Complete
2022-01-31T14:51:17+09:00 [INFO][AMF][NGAP][127.0.0.1:9487][AMF_UE_NGAP_ID:1] Rel Ue Context in GMM-Registered
2022-01-31T14:51:17+09:00 [INFO][AMF][NGAP][127.0.0.1:9487] Release UE[imsi-2089300007487] Context : N2 Connection Release
2022-01-31T14:51:18+09:00 [INFO][AMF][Producer] Handle N1N2 Message Transfer Request
==================
WARNING: DATA RACE
Read at 0x00c0005b79b0 by goroutine 222:
runtime.mapaccess2_faststr()
/usr/local/go/src/runtime/map_faststr.go:107 +0x0
github.com/free5gc/amf/context.(*AmfUe).CmConnect()
/home/nishi/free5gc-deb/free5gc/NFs/amf/context/amf_ue.go:271 +0x345
github.com/free5gc/amf/producer.N1N2MessageTransferProcedure()
/home/nishi/free5gc-deb/free5gc/NFs/amf/producer/n1n2message.go:173 +0x3edf
github.com/free5gc/amf/producer.HandleN1N2MessageTransferRequest()
/home/nishi/free5gc-deb/free5gc/NFs/amf/producer/n1n2message.go:27 +0x31b
github.com/free5gc/amf/communication.HTTPN1N2MessageTransfer()
/home/nishi/free5gc-deb/free5gc/NFs/amf/communication/api_n1_n2_message_collection_document.go:71 +0x535
github.com/gin-gonic/gin.(*Context).Next()
/home/nishi/go/pkg/mod/github.com/gin-gonic/[email protected]/context.go:161 +0xa6
github.com/gin-gonic/gin.RecoveryWithWriter.func1()
/home/nishi/go/pkg/mod/github.com/gin-gonic/[email protected]/recovery.go:83 +0x85
github.com/gin-gonic/gin.(*Context).Next()
/home/nishi/go/pkg/mod/github.com/gin-gonic/[email protected]/context.go:161 +0xa6
github.com/free5gc/logger_util.ginToLogrus.func1()
/home/nishi/go/pkg/mod/github.com/free5gc/[email protected]/logger_util.go:65 +0x162
github.com/gin-gonic/gin.(*Context).Next()
/home/nishi/go/pkg/mod/github.com/gin-gonic/[email protected]/context.go:161 +0xa6
github.com/gin-gonic/gin.(*Engine).handleHTTPRequest()
/home/nishi/go/pkg/mod/github.com/gin-gonic/[email protected]/gin.go:409 +0xa5d
github.com/gin-gonic/gin.(*Engine).ServeHTTP()
/home/nishi/go/pkg/mod/github.com/gin-gonic/[email protected]/gin.go:367 +0x2f4
net/http.Handler.ServeHTTP-fm()
/usr/local/go/src/net/http/server.go:87 +0x64
golang.org/x/net/http2.(*serverConn).runHandler()
/home/nishi/go/pkg/mod/golang.org/x/[email protected]/http2/server.go:2176 +0xc0
Previous write at 0x00c0005b79b0 by goroutine 36:
runtime.mapdelete_faststr()
/usr/local/go/src/runtime/map_faststr.go:297 +0x0
github.com/free5gc/amf/context.(*AmfUe).DetachRanUe()
/home/nishi/free5gc-deb/free5gc/NFs/amf/context/amf_ue.go:294 +0x47d
github.com/free5gc/amf/context.(*RanUe).Remove()
/home/nishi/free5gc-deb/free5gc/NFs/amf/context/ran_ue.go:81 +0x3d8
github.com/free5gc/amf/ngap.HandleUEContextReleaseComplete()
/home/nishi/free5gc-deb/free5gc/NFs/amf/ngap/handler.go:561 +0xda1
github.com/free5gc/amf/ngap.Dispatch()
/home/nishi/free5gc-deb/free5gc/NFs/amf/ngap/dispatcher.go:103 +0x7d9
github.com/free5gc/amf/ngap/service.handleConnection()
/home/nishi/free5gc-deb/free5gc/NFs/amf/ngap/service/service.go:204 +0x45a
Goroutine 222 (running) created at:
golang.org/x/net/http2.(*serverConn).processHeaders()
/home/nishi/go/pkg/mod/golang.org/x/[email protected]/http2/server.go:1906 +0x9a9
golang.org/x/net/http2.(*serverConn).processFrame()
/home/nishi/go/pkg/mod/golang.org/x/[email protected]/http2/server.go:1420 +0x43e
golang.org/x/net/http2.(*serverConn).processFrameFromReader()
/home/nishi/go/pkg/mod/golang.org/x/[email protected]/http2/server.go:1378 +0x7ab
golang.org/x/net/http2.(*serverConn).serve()
/home/nishi/go/pkg/mod/golang.org/x/[email protected]/http2/server.go:877 +0x14c0
golang.org/x/net/http2.(*Server).ServeConn()
/home/nishi/go/pkg/mod/golang.org/x/[email protected]/http2/server.go:471 +0xdcb
golang.org/x/net/http2/h2c.h2cHandler.ServeHTTP()
/home/nishi/go/pkg/mod/golang.org/x/[email protected]/http2/h2c/h2c.go:87 +0x2f7
golang.org/x/net/http2/h2c.(*h2cHandler).ServeHTTP()
<autogenerated>:1 +0x9d
net/http.serverHandler.ServeHTTP()
/usr/local/go/src/net/http/server.go:2807 +0xce
net/http.(*conn).serve()
/usr/local/go/src/net/http/server.go:1895 +0x837
Goroutine 36 (running) created at:
github.com/free5gc/amf/ngap/service.listenAndServe()
/home/nishi/free5gc-deb/free5gc/NFs/amf/ngap/service/service.go:136 +0x12a4
==================
2022-01-31T14:51:18+09:00 [INFO][AMF][GMM][AMF_UE_NGAP_ID:1][SUPI:imsi-2089300007487] Send Paging to TAI(&{Mcc:208 Mnc:93}, Tac:000001)
2022-01-31T14:51:18+09:00 [INFO][AMF][GIN] | 202 | 127.0.0.1 | POST | /namf-comm/v1/ue-contexts/imsi-2089300007487/n1-n2-messages |
2022-01-31T14:51:18+09:00 [INFO][SMF][PFCP] Receive ATTEMPTING_TO_REACH_UE, AMF is able to page the UE
2022-01-31T14:51:18+09:00 [INFO][UPF][Util] [PFCP] Handle PFCP session report response
2022-01-31T14:51:18+09:00 [INFO][UPF][Util] [PFCP] Session Report Response
2022-01-31T14:51:20+09:00 [INFO][AMF][NGAP][127.0.0.1:9487] Handle Initial UE Message
2022-01-31T14:51:20+09:00 [INFO][AMF][GMM][AMF_UE_NGAP_ID:2] Handle Service Request
2022-01-31T14:51:20+09:00 [INFO][AMF][NGAP][127.0.0.1:9487][AMF_UE_NGAP_ID:2] Send Initial Context Setup Request
2022-01-31T14:51:20+09:00 [INFO][AMF][NGAP][127.0.0.1:9487] Handle Initial Context Setup Response
2022-01-31T14:51:20+09:00 [INFO][SMF][PduSess] Receive Update SM Context Request
2022-01-31T14:51:20+09:00 [INFO][SMF][PduSess] In HandlePDUSessionSMContextUpdate
2022-01-31T14:51:20+09:00 [INFO][UPF][Util] [PFCP] Handle PFCP session modification request
2022-01-31T14:51:20+09:00 [INFO][UPF][Util] [PFCP] Session Modification Response
==================
WARNING: DATA RACE
Write at 0x00c000630000 by goroutine 218:
internal/race.WriteRange()
/usr/local/go/src/internal/race/race.go:49 +0x9a
syscall.Read()
/usr/local/go/src/syscall/syscall_unix.go:192 +0x7e
internal/poll.(*FD).Read()
/usr/local/go/src/internal/poll/fd_unix.go:165 +0x1c7
net.(*netFD).Read()
/usr/local/go/src/net/fd_unix.go:202 +0x65
net.(*conn).Read()
/usr/local/go/src/net/net.go:184 +0xa0
test_test.TestPaging.func1()
/home/nishi/free5gc-deb/free5gc/test/registration_test.go:1663 +0xf0
Previous read at 0x00c000630006 by goroutine 34:
[failed to restore the stack]
Goroutine 218 (running) created at:
test_test.TestPaging()
/home/nishi/free5gc-deb/free5gc/test/registration_test.go:1659 +0x33fb
testing.tRunner()
/usr/local/go/src/testing/testing.go:991 +0x1eb
Goroutine 34 (running) created at:
testing.(*T).Run()
/usr/local/go/src/testing/testing.go:1042 +0x660
testing.runTests.func1()
/usr/local/go/src/testing/testing.go:1284 +0xa6
testing.tRunner()
/usr/local/go/src/testing/testing.go:991 +0x1eb
testing.runTests()
/usr/local/go/src/testing/testing.go:1282 +0x527
testing.(*M).Run()
/usr/local/go/src/testing/testing.go:1199 +0x2ff
main.main()
_testmain.go:78 +0x223
==================
2022-01-31T14:51:20+09:00 [INFO][LIB][PFCP] Remove Request Transaction [5]
2022-01-31T14:51:20+09:00 [INFO][SMF][PFCP] In HandlePfcpSessionModificationResponse
2022-01-31T14:51:20+09:00 [INFO][SMF][PduSess] [SMF] PFCP Modification Resonse Accept
2022-01-31T14:51:20+09:00 [INFO][SMF][GIN] | 200 | 127.0.0.1 | POST | /nsmf-pdusession/v1/sm-contexts/urn:uuid:d0fa772e-1127-4cd1-b4ad-6556e3c08f63/modify |
2022-01-31T14:51:20+09:00 [INFO][SMF][PFCP] PFCP Session Modification Success[1]
2022-01-31T14:51:21+09:00 [INFO][AMF][NGAP] Handle SCTP Notification[addr: <nil>]
2022-01-31T14:51:21+09:00 [INFO][NRF][Init] Terminating NRF...
2022-01-31T14:51:21+09:00 [INFO][NRF][Init] NRF terminated
2022-01-31T14:51:21+09:00 [INFO][AMF][NGAP][127.0.0.1:9487] SCTP_SHUTDOWN_EVENT notification, close the connection
2022-01-31T14:51:21+09:00 [INFO][AMF][NGAP][127.0.0.1:9487] Remove RAN Context[ID: <PlmnID: {Mcc:208 Mnc:93}, GNbID: 000102>]
2022-01-31T14:51:21+09:00 [INFO][AMF][Init] Terminating AMF...
2022-01-31T14:51:21+09:00 [INFO][AMF][NGAP] Handle SCTP Notification[addr: <nil>]
2022-01-31T14:51:21+09:00 [INFO][AMF][Consumer] [AMF] Send Deregister NFInstance
2022-01-31T14:51:21+09:00 [WARN][AMF][NGAP] RAN context has been removed[addr: <nil>]
2022-01-31T14:51:21+09:00 [INFO][NRF][MGMT] Handle NFDeregisterRequest
2022-01-31T14:51:22+09:00 [INFO][NRF][GIN] | 204 | 127.0.0.1 | DELETE | /nnrf-nfm/v1/nf-instances/139f22d5-1de7-4b3b-b6d1-f1bb94b504bd |
2022-01-31T14:51:22+09:00 [INFO][AMF][Init] [AMF] Deregister from NRF successfully
2022-01-31T14:51:22+09:00 [INFO][AMF][Init] Send AMF Status Indication to Notify RANs due to AMF terminating
2022-01-31T14:51:22+09:00 [INFO][AMF][NGAP] Close SCTP server...
2022-01-31T14:51:22+09:00 [INFO][AMF][NGAP] SCTP server closed
2022-01-31T14:51:22+09:00 [INFO][AMF][Producer] [AMF] Send Amf Status Change Notify to http://127.0.0.7:8000/npcf-callback/v1/amfstatus
2022-01-31T14:51:22+09:00 [WARN][PCF][Callback] [PCF] Handle Amf Status Change Notify is not implemented.
2022-01-31T14:51:22+09:00 [INFO][PCF][GIN] | 204 | 127.0.0.1 | POST | /npcf-callback/v1/amfstatus |
2022-01-31T14:51:22+09:00 [INFO][AMF][Init] AMF terminated
2022-01-31T14:51:22+09:00 [INFO][SMF][Init] Terminating SMF...
2022-01-31T14:51:22+09:00 [INFO][SMF][Consumer] Send Deregister NFInstance
2022-01-31T14:51:22+09:00 [INFO][NRF][MGMT] Handle NFDeregisterRequest
2022-01-31T14:51:23+09:00 [INFO][NRF][GIN] | 204 | 127.0.0.1 | DELETE | /nnrf-nfm/v1/nf-instances/702790f0-0795-48f3-84cf-a73777518f9d |
2022-01-31T14:51:23+09:00 [INFO][SMF][Init] Deregister from NRF successfully
2022-01-31T14:51:23+09:00 [INFO][UDR][Init] Terminating UDR...
2022-01-31T14:51:23+09:00 [INFO][UDR][Consumer] Send Deregister NFInstance
2022-01-31T14:51:23+09:00 [INFO][NRF][MGMT] Handle NFDeregisterRequest
2022-01-31T14:51:24+09:00 [INFO][NRF][GIN] | 204 | 127.0.0.1 | DELETE | /nnrf-nfm/v1/nf-instances/a9c17b81-6a55-4fe5-9441-23f69510656d |
2022-01-31T14:51:24+09:00 [INFO][UDR][Init] Deregister from NRF successfully
2022-01-31T14:51:24+09:00 [INFO][UDR][Init] UDR terminated
2022-01-31T14:51:24+09:00 [INFO][PCF][Init] Terminating PCF...
2022-01-31T14:51:24+09:00 [INFO][PCF][Consumer] Send Deregister NFInstance
2022-01-31T14:51:24+09:00 [INFO][NRF][MGMT] Handle NFDeregisterRequest
2022-01-31T14:51:25+09:00 [INFO][NRF][GIN] | 204 | 127.0.0.1 | DELETE | /nnrf-nfm/v1/nf-instances/741d3f3c-9d62-4f5d-9b49-b50a5d03e327 |
2022-01-31T14:51:25+09:00 [INFO][PCF][Init] Deregister from NRF successfully
2022-01-31T14:51:25+09:00 [INFO][PCF][Init] PCF terminated
2022-01-31T14:51:25+09:00 [INFO][UDM][Init] Terminating UDM...
2022-01-31T14:51:25+09:00 [INFO][UDM][Consumer] Send Deregister NFInstance
2022-01-31T14:51:25+09:00 [INFO][NRF][MGMT] Handle NFDeregisterRequest
2022-01-31T14:51:26+09:00 [INFO][NRF][GIN] | 204 | 127.0.0.1 | DELETE | /nnrf-nfm/v1/nf-instances/142931ac-5317-4292-8fbf-8d7c6596345d |
2022-01-31T14:51:26+09:00 [INFO][UDM][Init] Deregister from NRF successfully
2022-01-31T14:51:26+09:00 [INFO][UDM][Init] UDM terminated
2022-01-31T14:51:26+09:00 [INFO][NSSF][Init] Terminating NSSF...
2022-01-31T14:51:26+09:00 [INFO][NSSF][App] Send Deregister NFInstance
2022-01-31T14:51:26+09:00 [INFO][NRF][MGMT] Handle NFDeregisterRequest
2022-01-31T14:51:27+09:00 [INFO][NRF][GIN] | 204 | 127.0.0.1 | DELETE | /nnrf-nfm/v1/nf-instances/8345539f-8db7-45f9-a605-8440634dcafd |
2022-01-31T14:51:27+09:00 [INFO][NSSF][Init] Deregister from NRF successfully
2022-01-31T14:51:27+09:00 [INFO][NSSF][Init] NSSF terminated
2022-01-31T14:51:27+09:00 [INFO][AUSF][Init] Terminating AUSF...
2022-01-31T14:51:27+09:00 [INFO][AUSF][App] Send Deregister NFInstance
2022-01-31T14:51:27+09:00 [INFO][NRF][MGMT] Handle NFDeregisterRequest
2022-01-31T14:51:28+09:00 [INFO][NRF][GIN] | 204 | 127.0.0.1 | DELETE | /nnrf-nfm/v1/nf-instances/92296baa-87f2-46a9-bd32-337dbd186605 |
2022-01-31T14:51:28+09:00 [INFO][AUSF][Init] Deregister from NRF successfully
2022-01-31T14:51:28+09:00 [INFO][AUSF][Init] AUSF terminated
TestPaging: testing.go:906: race detected during execution of test
--- FAIL: TestPaging (12.45s)
: testing.go:906: race detected during execution of test
FAIL
exit status 1
FAIL test 14.348s
2022-01-31T14:51:31+09:00 [INFO][UPF][Util] Removing DNN routes
nishi@GTP-U:~/free5gc-deb/free5gc$
```
|
[Bugs] Datarace in TestPaging
|
https://api.github.com/repos/free5gc/free5gc/issues/304/comments
| 2 |
2022-01-31T05:54:36Z
|
2022-06-22T00:46:01Z
|
https://github.com/free5gc/free5gc/issues/304
| 1,119,006,181 | 304 |
[
"free5gc",
"free5gc"
] |
## Describe the bug
When Ran information is switched by SwitchToRan(), the log information is not updated.
## To Reproduce
Use TestXnHandover
## Expected behavior
The log information is updated.
## Environment (please complete the following information):
- free5GC Version: v3.0.6
- OS: Ubuntu 18.04
- Kernel version: 5.0.0-23-generic
- go version go1.14.4 linux/amd64
## Trace File
### Log File
```
2022-01-28T08:14:00Z [INFO][AMF][NGAP][127.0.0.1:9488] Handle Path Switch Request
2022-01-28T08:14:00Z [INFO][SMF][PduSess] Receive Update SM Context Request
2022-01-28T08:14:00Z [INFO][SMF][PduSess] In HandlePDUSessionSMContextUpdate
2022-01-28T08:14:00Z [INFO][UPF][Util] [PFCP] Handle PFCP session modification request
2022-01-28T08:14:00Z [INFO][UPF][Util] [PFCP] Session Modification Response
2022-01-28T08:14:00Z [INFO][SMF][PFCP] In HandlePfcpSessionModificationResponse
2022-01-28T08:14:00Z [INFO][SMF][PduSess] [SMF] PFCP Modification Resonse Accept
2022-01-28T08:14:00Z [INFO][SMF][PFCP] PFCP Session Modification Success[1]
2022-01-28T08:14:00Z [INFO][SMF][GIN] | 200 | 127.0.0.1 | POST | /nsmf-pdusession/v1/sm-contexts/urn:uuid:e7b85c36-0e68-4980-9a30-d1e88fd6ee2d/modify |
2022-01-28T08:14:00Z [INFO][LIB][PFCP] Remove Request Transaction [4]
2022-01-28T08:14:00Z [INFO][AMF][Context] RanUe[RanUeNgapID: 1] Switch to new Ran[Name: nctu]
2022-01-28T08:14:00Z [INFO][AMF][NGAP][127.0.0.1:9487][AMF_UE_NGAP_ID:1] Send Path Switch Request Acknowledge
```
[127.0.0.1:9487] at Send Path Switch Request Acknowledge is source ran address, it should be target ran address[127.0.0.1:9488].
## Additional context
I have sent a [PR](https://github.com/free5gc/amf/pull/61).
|
[Bugs] Log information is not updated
|
https://api.github.com/repos/free5gc/free5gc/issues/303/comments
| 1 |
2022-01-28T08:31:38Z
|
2022-02-06T02:35:59Z
|
https://github.com/free5gc/free5gc/issues/303
| 1,117,129,592 | 303 |
[
"free5gc",
"free5gc"
] |
## Describe the bug
The current AmfUe is deleted when UEcontextRelease for the previous session occurs after re-establishing Registration~PduSession in a new session while the previous session has not completed the Registration procedure.
## To Reproduce
1. RegistrationRequest~SecuritymodeCommand(Previous session has not completed the Registration procedure)
2. RegistartionRequest~PDU session established(New Session)
3. UEContextReleaseRequest~UEContextReleaseComplete(to Previous session)
4. ServiceRequest(to New Session)
AmfUe is deleted at 3.UEContextrelease, so it cannot recognize the UE.
## Expected behavior
AmfUe is not deleted
## Environment (please complete the following information):
- free5GC Version: v3.0.6
- OS: Ubuntu 18.04
- Kernel version: 5.0.0-23-generic
- go version go1.14.4 linux/amd64
## Trace File
### PCAP File
[Bug_DeletedAmfUe.zip](https://github.com/free5gc/free5gc/files/7956477/Bug_DeletedAmfUe.zip)
### Log File
```
2022-01-28T02:54:17Z [INFO][AMF][NGAP][127.0.1.1:9784] Release UE[imsi-2089300007487] Context : Release Ue Context (/home/fujitsu/devel305/free5gc/NFs/amf/ngap/handler.go:566 github.com/free5gc/amf/ngap.HandleUEContextReleaseComplete)
2022-01-28T02:54:17Z [INFO][AMF][NGAP][127.0.1.1:9784] Handle Initial UE Message (/home/fujitsu/devel305/free5gc/NFs/amf/ngap/handler.go:855 github.com/free5gc/amf/ngap.HandleInitialUEMessage)
2022-01-28T02:54:17Z [WARN][AMF][NGAP][127.0.1.1:9784][AMF_UE_NGAP_ID:3] Unknown UE [GUTI: 20893cafe0000000002] (/home/fujitsu/devel305/free5gc/NFs/amf/ngap/handler.go:949 github.com/free5gc/amf/ngap.HandleInitialUEMessage)
2022-01-28T02:54:17Z [WARN][NAS][Security] Integrity NIA0 is emergency. (/home/fujitsu/devel305/free5gc/lib/nas/security/security.go:71 github.com/free5gc/nas/security.NASMacCalculate)
2022-01-28T02:54:17Z [WARN][AMF][NAS][AMF_UE_NGAP_ID:3] NAS MAC verification failed(received: 0x074baea8, expected: 0x00000000) (/home/fujitsu/devel305/free5gc/NFs/amf/nas/nas_security/security.go:179 github.com/free5gc/amf/nas/nas_security.Decode)
2022-01-28T02:54:17Z [INFO][AMF][GMM][AMF_UE_NGAP_ID:3] Handle Service Request (/home/fujitsu/devel305/free5gc/NFs/amf/gmm/handler.go:1547 github.com/free5gc/amf/gmm.HandleServiceRequest)
2022-01-28T02:54:17Z [WARN][AMF][GMM][AMF_UE_NGAP_ID:3] No Security Context : SUPI[] (/home/fujitsu/devel305/free5gc/NFs/amf/gmm/handler.go:1569 github.com/free5gc/amf/gmm.HandleServiceRequest)
2022-01-28T02:54:17Z [INFO][AMF][GMM][AMF_UE_NGAP_ID:3] Send Service Reject (/home/fujitsu/devel305/free5gc/NFs/amf/gmm/message/send.go:233 github.com/free5gc/amf/gmm/message.SendServiceReject)
```
## Additional context
I have sent a [PR](https://github.com/free5gc/amf/pull/60).
|
[Bugs] Current AmfUe is deleted when AMF receives UEContextRelease of previous session
|
https://api.github.com/repos/free5gc/free5gc/issues/302/comments
| 1 |
2022-01-28T07:01:45Z
|
2022-02-06T02:20:52Z
|
https://github.com/free5gc/free5gc/issues/302
| 1,117,067,052 | 302 |
[
"free5gc",
"free5gc"
] |
## Describe the bug
AMF accepts registration request with wrong PLMN value which does not match subscriber database.
## To Reproduce
Use TestRegistration
1. Change mobileIdentity5GS (change PLMN from 20893 to 208930, not change SUPI)
From:
```
Buffer: []uint8{0x01, 0x02, 0xf8, 0x39, 0xf0, 0xff, 0x00, 0x00, 0x00, 0x00, 0x47, 0x78},
```
To:
```
Buffer: []uint8{0x01, 0x02, 0x08, 0x39, 0xf0, 0xff, 0x00, 0x00, 0x00, 0x70, 0x84, 0xf7},
```
2. Run TestRegistration
## Expected behavior
AMF sends Registration Reject to UE.
## Environment
- free5GC Version: v3.0.6
- OS: Ubuntu 18.04
- Kernel version: 5.0.0-23-generic
- go version go1.14.4 linux/amd64
## Trace File
### Log File
```
2022-01-26T04:09:22Z [INFO][AMF][GMM][AMF_UE_NGAP_ID:1][SUPI:imsi-2089300007487] Handle InitialRegistration
2022-01-26T04:09:22Z [INFO][NRF][DSCV] Handle NFDiscoveryRequest
2022-01-26T04:09:22Z [INFO][NRF][GIN] | 200 | 127.0.0.1 | GET | /nnrf-disc/v1/nf-instances?requester-nf-type=AMF&supi=imsi-2089300007487&target-nf-type=UDM |
2022-01-26T04:09:22Z [INFO][UDM][SDM] Handle GetNssai
2022-01-26T04:09:22Z [INFO][UDR][DRepo] Handle QueryAmData
2022-01-26T04:09:22Z [INFO][UDR][GIN] | 404 | 127.0.0.1 | GET | /nudr-dr/v1/subscription-data/imsi-2089300007487/208930/provisioned-data/am-data?supported-features= |
2022-01-26T04:09:22Z [WARN][UDM][SDM] 404 Not Found
2022-01-26T04:09:22Z [INFO][UDM][GIN] | 404 | 127.0.0.1 | GET | /nudm-sdm/v1/imsi-2089300007487/nssai?plmn-id=%7B%22mcc%22%3A%22208%22%2C%22mnc%22%3A%22930%22%7D |
2022-01-26T04:09:22Z [ERRO][AMF][GMM][AMF_UE_NGAP_ID:1][SUPI:imsi-2089300007487] SDM_Get Slice Selection Subscription Data Failed Problem[&{Type: Title: Status:404 Detail:404 Not Found Instance: Cause:USER_NOT_FOUND InvalidParams:[]}]
2022-01-26T04:09:22Z [INFO][NRF][DSCV] Handle NFDiscoveryRequest
2022-01-26T04:09:22Z [INFO][NRF][GIN] | 200 | 127.0.0.1 | GET | /nnrf-disc/v1/nf-instances?requester-nf-type=AMF&supi=imsi-2089300007487&target-nf-type=UDM |
2022-01-26T04:09:22Z [INFO][UDM][UECM] Handle RegistrationAmf3gppAccess
2022-01-26T04:09:22Z [INFO][UDM][UECM] UEID: imsi-2089300007487
2022-01-26T04:09:22Z [INFO][UDR][DRepo] Handle CreateAmfContext3gpp
2022-01-26T04:09:22Z [INFO][UDR][GIN] | 204 | 127.0.0.1 | PUT | /nudr-dr/v1/subscription-data/imsi-2089300007487/context-data/amf-3gpp-access |
2022-01-26T04:09:22Z [INFO][UDM][GIN] | 201 | 127.0.0.1 | PUT | /nudm-uecm/v1/imsi-2089300007487/registrations/amf-3gpp-access |
2022-01-26T04:09:22Z [INFO][UDM][SDM] Handle GetAmData
2022-01-26T04:09:22Z [INFO][UDR][DRepo] Handle QueryAmData
2022-01-26T04:09:22Z [INFO][UDR][GIN] | 404 | 127.0.0.1 | GET | /nudr-dr/v1/subscription-data/imsi-2089300007487/208930/provisioned-data/am-data?supported-features=%7B%22mcc%22%3A%22208%22%2C%22mnc%22%3A%22930%22%7D |
2022-01-26T04:09:22Z [INFO][UDM][GIN] | 404 | 127.0.0.1 | GET | /nudm-sdm/v1/imsi-2089300007487/am-data?plmn-id=%7B%22mcc%22%3A%22208%22%2C%22mnc%22%3A%22930%22%7D |
2022-01-26T04:09:22Z [ERRO][AMF][GMM][AMF_UE_NGAP_ID:1][SUPI:imsi-2089300007487] SDM_Get AmData Failed Problem[&{Type: Title: Status:404 Detail:404 Not Found Instance: Cause:USER_NOT_FOUND InvalidParams:[]}]
...
2022-01-26T04:09:22Z [INFO][AMF][GMM][AMF_UE_NGAP_ID:1][SUPI:imsi-2089300007487] Send Registration Accept
2022-01-26T04:09:22Z [INFO][AMF][NGAP][127.0.0.1:9487][AMF_UE_NGAP_ID:1] Send Initial Context Setup Request
2022-01-26T04:09:22Z [ERRO][AMF][NGAP][127.0.0.1:9487][AMF_UE_NGAP_ID:1] Build InitialContextSetupRequest failed : SEQUENCE OF Size is lower than lowerbound
2022-01-26T04:09:28Z [WARN][AMF][GMM][AMF_UE_NGAP_ID:1][SUPI:imsi-2089300007487] T3550 expires, retransmit Registration Accept (retry: 1)
2022-01-26T04:09:28Z [INFO][AMF][NGAP][127.0.0.1:9487][AMF_UE_NGAP_ID:1] Send Downlink Nas Transport
```
## Additional context
[Pull Request](https://github.com/free5gc/amf/pull/59) for the fix.
|
[Bugs] AMF accepts registration request with wrong PLMN
|
https://api.github.com/repos/free5gc/free5gc/issues/301/comments
| 1 |
2022-01-27T05:53:07Z
|
2022-02-06T02:19:29Z
|
https://github.com/free5gc/free5gc/issues/301
| 1,115,803,497 | 301 |
[
"free5gc",
"free5gc"
] |
## Issue Description
NAS package in your repository has supported NIA3 and NEA3, which version is v1.0.4, but the free5gc uses v1.0.0, when will update it?
### What's the version are you using
Version 3.0.6
### Is your feature request related to a problem? Please describe.
NAS Security:
### Describe the solution you'd like
Just change the NAS package version in "free5gc/NFs/amf/go.mod", and rebuild amf, will it cause error?
|
[Feat] NAS Security with NIA3 and NEA3
|
https://api.github.com/repos/free5gc/free5gc/issues/299/comments
| 1 |
2022-01-11T03:49:00Z
|
2022-03-31T16:16:17Z
|
https://github.com/free5gc/free5gc/issues/299
| 1,098,618,865 | 299 |
[
"free5gc",
"free5gc"
] | null |
Does free5c support IPv6 address assignment？If so, how do I configure the IP pool in smfcfg.yaml?
|
https://api.github.com/repos/free5gc/free5gc/issues/298/comments
| 1 |
2022-01-09T11:39:59Z
|
2022-01-13T14:11:47Z
|
https://github.com/free5gc/free5gc/issues/298
| 1,097,173,210 | 298 |
[
"free5gc",
"free5gc"
] |
Thanks for your great work!
I want to attach as many users as possible. How can I insert a large number of users with scripts (not web console)?
Moreover, does free5gc have a limit on the number of access users? If so, where is the bottleneck? Number of ports? Or only depends on hardware performance?
|
How can I insert subscribers without webconsole?
|
https://api.github.com/repos/free5gc/free5gc/issues/297/comments
| 2 |
2021-12-30T14:36:26Z
|
2023-07-05T09:01:55Z
|
https://github.com/free5gc/free5gc/issues/297
| 1,091,142,687 | 297 |
[
"free5gc",
"free5gc"
] |
**We will advise people to follow the issue template set, otherwise the issue might be disregarded.**
**free5GC mainly uses GitHub for issue tracking. Information regarding to general questions or technical support. It will be highly considered if forward to the [forum](https://forum.free5gc.org).**
**free5GC will appreciate it, if people can refer to [TS](https://github.com/free5gc/free5gc/wiki/Trouble_Shooting) and [forum](https://forum.free5gc.org) prior to bug reporting**
<!-- Remove warning (above 3 lines) while reporting the issue -->
## Describe the bug
How can I test 5QI parameters in free5gc
|
[Question] How do I test 5QI parameters in free5gc, thanks
|
https://api.github.com/repos/free5gc/free5gc/issues/295/comments
| 5 |
2021-12-22T05:00:19Z
|
2023-11-09T17:34:28Z
|
https://github.com/free5gc/free5gc/issues/295
| 1,086,451,626 | 295 |
[
"free5gc",
"free5gc"
] |
## Describe the bug
When receiving the Mobility and Periodic Registration Update in the CM-CONNECTED state, AMF returns DownlinkNASTransport but may return InitialContextSetupRequest.
## To Reproduce
1. RegistrationRequest ~ establish PDUSession
2. AN Release(UE Context Release Request ~ UE Context Release Complete)
3. UE/gNB -> 5GC InitialUEmessage/ServiceRequest
4. UE/gNB <- 5GC InitialContextSetupRequest/ServiceAccept
5. gNB -> 5GC InitialContextSetupResponse
6. gNB -> 5GC PDUSessionReleaseRequest
7. gNB <- 5GC PDUSessionResourceReleaseCommand
8. UE/gNB -> 5GC UplinkNASTransport/RegistrationRequest(Mobility Registration Update)
## Expected behavior
AMF returns DownlinkNASTransport.
## Environment (please complete the following information):
- free5GC Version: 3.0.6
- OS: Ubuntu 18.04
- Kernel version: 5.0.0-23-generic
- go version go1.14.4 linux/amd64
## Trace File
### PCAP File
[RegistrationAccept_in_CM-CONNECTED.zip](https://github.com/free5gc/free5gc/files/7743307/RegistrationAccept_in_CM-CONNECTED.zip)
### Log File
```
2021-12-20T14:45:22+09:00 [INFO][AMF][NGAP][127.0.1.1:9784] Handle Uplink Nas Transport (/home/fujitsu/free5gc/NFs/amf/ngap/handler.go:176 github.com/free5gc/amf/ngap.HandleUplinkNasTransport)
2021-12-20T14:45:22+09:00 [INFO][AMF][NGAP][127.0.1.1:9784][AMF_UE_NGAP_ID:2] Uplink NAS Transport (RAN UE NGAP ID: 2) (/home/fujitsu/free5gc/NFs/amf/ngap/handler.go:228 github.com/free5gc/amf/ngap.HandleUplinkNasTransport)
2021-12-20T14:45:22+09:00 [INFO][AMF][GMM][AMF_UE_NGAP_ID:2] Handle Registration Request (/home/fujitsu/free5gc/NFs/amf/gmm/handler.go:365 github.com/free5gc/amf/gmm.HandleRegistrationRequest)
2021-12-20T14:45:22+09:00 [INFO][AMF][GMM][AMF_UE_NGAP_ID:2] Authentication procedure (/home/fujitsu/free5gc/NFs/amf/gmm/handler.go:1468 github.com/free5gc/amf/gmm.AuthenticationProcedure)
2021-12-20T14:45:22+09:00 [INFO][AMF][GMM][AMF_UE_NGAP_ID:2][SUPI:imsi-2089300007487] Handle MobilityAndPeriodicRegistrationUpdating (/home/fujitsu/free5gc/NFs/amf/gmm/handler.go:710 github.com/free5gc/amf/gmm.HandleMobilityAndPeriodicRegistrationUpdating)
2021-12-20T14:45:22+09:00 [INFO][AMF][GMM][AMF_UE_NGAP_ID:2][SUPI:imsi-2089300007487] Send Registration Accept (/home/fujitsu/free5gc/NFs/amf/gmm/message/send.go:362 github.com/free5gc/amf/gmm/message.SendRegistrationAccept)
2021-12-20T14:45:22+09:00 [INFO][AMF][NGAP][127.0.1.1:9784][AMF_UE_NGAP_ID:2] Send Initial Context Setup Request (/home/fujitsu/free5gc/NFs/amf/ngap/message/send.go:356 github.com/free5gc/amf/ngap/message.SendInitialContextSetupRequest)
```
## Additional context
I have sent a [PR](https://github.com/free5gc/amf/pull/54).
|
[Bugs] RegistrationAccept in CM-CONNECTED state may be sent by not DownlinkNASTransport but InitialContextSetupRequest
|
https://api.github.com/repos/free5gc/free5gc/issues/294/comments
| 1 |
2021-12-20T07:40:21Z
|
2022-01-04T15:31:51Z
|
https://github.com/free5gc/free5gc/issues/294
| 1,084,459,614 | 294 |
[
"free5gc",
"free5gc"
] |
## Describe the bug
If AMF is repeatedly received Registration Request from same UE, the number of Allowed NSSAI in Initial Context Setup Request increases. Finally AMF fails to build Initial Context Setup Request.
## To Reproduce
1. RegistrationRequest ~ PDUsessionResourceSetupResponse
2. gNB -> 5GC UEContextReleaseRequest
3. gNB <- 5GC UEContextReleaseCommand
4. UE/gNB -> 5GC InitialUEmessage/RegistrationRequest(mobility registration updating with requested NSSAI)
5. UE/gNB <- 5GC InitialContextSetupRequest/RegistrationAccept
6. gNB -> 5GC InitialContextSetupResponse
7. Repeat 4 ~ 6 (over 8 times)
## Expected behavior
Not increase the number of Allowed NSSAI, and AMF succeeds to build Initial Context Setup Request.
## Environment
- free5GC Version: 3.0.6
- OS: Ubuntu 18.04
- Kernel version: 5.0.0-23-generic
- go version go1.14.4 linux/amd64
## Trace File
### PCAP File
[increase-allowednssai.zip](https://github.com/free5gc/free5gc/files/7733679/increase-allowednssai.zip)
### Log File
```
2021-12-17T07:05:42Z [INFO][AMF][GMM][AMF_UE_NGAP_ID:1][SUPI:imsi-2089300007487] Handle MobilityAndPeriodicRegistrationUpdating
2021-12-17T07:05:42Z [INFO][AMF][GMM][AMF_UE_NGAP_ID:1][SUPI:imsi-2089300007487] RequestedNssai - ServingSnssai: &{Sst:1 Sd:010203}, HomeSnssai: <nil>
2021-12-17T07:05:42Z [INFO][AMF][GMM][AMF_UE_NGAP_ID:1][SUPI:imsi-2089300007487] Send Registration Accept
2021-12-17T07:05:42Z [INFO][AMF][NGAP][127.0.0.1:9487][AMF_UE_NGAP_ID:1] Send Initial Context Setup Request
2021-12-17T07:05:42Z [ERRO][AMF][NGAP][127.0.0.1:9487][AMF_UE_NGAP_ID:1] Build InitialContextSetupRequest failed : SEQUENCE OF Size is larger than upperbound
```
## Additional context
[Pull Request](https://github.com/free5gc/amf/pull/53) for the fix.
|
[Bugs] Increase the number of Allowed NSSAI in Initial Context Setup Request
|
https://api.github.com/repos/free5gc/free5gc/issues/293/comments
| 2 |
2021-12-17T08:38:08Z
|
2022-01-04T15:24:29Z
|
https://github.com/free5gc/free5gc/issues/293
| 1,083,014,137 | 293 |
[
"free5gc",
"free5gc"
] |
In 3.0.5 release note, there is a bug fix about mobility and periodicUpdate Registration, so i wonder if free5gc supports different registration mode?
If supported, how do i test them?
Thank You!
|
Does Free5gc support Different Registration Mode?
|
https://api.github.com/repos/free5gc/free5gc/issues/292/comments
| 1 |
2021-12-13T04:34:39Z
|
2023-06-29T06:14:18Z
|
https://github.com/free5gc/free5gc/issues/292
| 1,078,077,665 | 292 |
[
"free5gc",
"free5gc"
] |
## Describe the bug
If UPF receives PFCP request with SEID same as deleted PFCP session by PFCP Session Deletion Request, the deleted session is found when searching for session with UpfSessionFindBySeid().
## To Reproduce
If gNB sends PDU Session Resource SetupResponse late during PDU Session Release procedure as shown below, this issue is happened.
1. UE/gNB->5GC UplinkNASTransport, UL NAS transport, PDU session establishment request
2. UE/gNB<-5GC PDUSessionResourceSetupRequest, DL NAS transport, PDU session establishment accept
3. UE/gNB->5GC UplinkNASTransport, UL NAS transport, PDU session release request
4. SMF->UPF PFCP Session Deletion Request
5. SMF<-UPF PFCP Session Deletion Response
6. UE/gNB<-5GC PDUSessionResourceReleaseCommand, DL NAS transport, PDU session release command
7. gNB->5GC PDUSessionResourceSetupResponse(response to 2.PDUSessionResourceSetupRequest)
8. SMF->UPF PFCP Session Modification Request(SEID is same as 4.PFCP Session)
9. SMF<-UPF PFCP Session Modification Response
## Expected behavior
Deleted session is not found by UpfSessionFindBySeid() at 8. and PFCP Session Modification Response is not sent.
## Environment (please complete the following information):
- free5GC Version: 3.0.6
- OS: Ubuntu 18.04
- Kernel version: 5.0.0-23-generic
- go version go1.14.4 linux/amd64
## Trace File
### PCAP File
[Bugs_UpfSessionFindBySeid.zip](https://github.com/free5gc/free5gc/files/7638939/Bugs_UpfSessionFindBySeid.zip)
## Additional context
I have sent a [PR](https://github.com/free5gc/upf/pull/47)
|
[Bugs] Deleted PFCP session is found by UpfSessionFindBySeid().
|
https://api.github.com/repos/free5gc/free5gc/issues/291/comments
| 3 |
2021-12-02T04:11:04Z
|
2022-01-04T08:16:59Z
|
https://github.com/free5gc/free5gc/issues/291
| 1,069,108,754 | 291 |
[
"free5gc",
"free5gc"
] |
## Issue Description
One PFCP Session Report Request message is sent to the SMF per one downlink packet to be buffered.
It is too much.
### What's the version are you using
v3.0.6
### Is your feature request related to a problem? Please describe.
No.
### Describe the solution you'd like
- Put the timestamp field to the head of the packetBuffer
- Send PFCP Session Report Request message only when the packetBuffer is empty or when the timestamp stored at the head of the packetBuffer has been expired
- Update the timestamp in the packetBuffer when PFCP Session Report Request is sent
- Clear the packetBuffer if the timestamp has been expired when a new packet is going to be buffered
### Describe alternatives/workarounds you've considered
Nothing.
### Additional context
Nothing.
## Issue Template Checklist
<!-- Please answer the questions below. If not the issue might be disregarded. -->
### If willing to resolve an issue by submitting Pull request, please consider the points below.
<!-- free5GC will be happy to welcome first contributor’s, in order to broaden the community. -->
- [x] Yes, I have the time and I know how to start.
- [ ] Yes, I have the time but I don't know how to start, I would need guidance.
- [ ] No, I don't have the time, although I believe I could do it if I had the time...
- [ ] No, I don't have the time and I wouldn't even know how to start.
|
[Feat] Suppress the frequency of sending PFCP Session Report Request messages
|
https://api.github.com/repos/free5gc/free5gc/issues/290/comments
| 1 |
2021-12-01T10:32:15Z
|
2021-12-26T08:10:05Z
|
https://github.com/free5gc/free5gc/issues/290
| 1,068,234,296 | 290 |
[
"free5gc",
"free5gc"
] |
## Describe the bug
UPF leaks PfcpXact if PFCP Session Report Response is not processed.
An allocated PfcpXact about PFCP Session Report procedure is freed only when received the `UPF_EVENT_N4_MESSAGE` event about `PFCP_SESSION_REPORT_RESPONSE` message by the event consumer thread.
Therefore the PfcpXact will be leaked if such `UPF_EVENT_N4_MESSAGE` event is not received by the event consumer thread for whatever reasons. This will eventually empty `pfcpXactPool` and prevent to create a new PFCP transaction anymore.
## To Reproduce
Steps to reproduce the behavior:
1. Apply the following patch to prevent for SMF to respond PFCP Session Report Requests and to make `pfcpXactPool` empty
```patch
--- a/test/registration_test.go
+++ b/test/registration_test.go
@@ -677,9 +677,17 @@ func TestServiceRequest(t *testing.T) {
assert.Nil(t, err)
// UE is CM-IDLE now
-
+ err = exec.Command("sudo", "iptables", "-A", "INPUT", "-i", "veth0", "-p", "udp", "--dport", "8805", "-j", "DROP").Run()
+ assert.NoError(t, err)
+ defer exec.Command("sudo", "iptables", "-D", "INPUT", "-i", "veth0", "-p", "udp", "--dport", "8805", "-j", "DROP").Run()
time.Sleep(1 * time.Second)
+ exec.Command("sudo", "ip", "netns", "exec", "UPFns", "ping", "-s", "0", "-c", "70", "-i", "0.1", "60.60.0.1").Run()
+ err = exec.Command("sudo", "iptables", "-D", "INPUT", "-i", "veth0", "-p", "udp", "--dport", "8805", "-j", "DROP").Run()
+ assert.NoError(t, err)
+
+ exec.Command("sudo", "ip", "netns", "exec", "UPFns", "ping", "-s", "0", "-c", "1", "60.60.0.1").Run()
+
// send NAS Service Request
pdu = nasTestpacket.GetServiceRequest(nasMessage.ServiceTypeData)
```
2. Run `./test.sh -o TestServiceRequest`
You can see the following messages in logs/nf/upf.log:
```
time="2021-11-30T15:42:15+09:00" level=warning msg="Index Pool is empty" category=Util component=UPF
time="2021-11-30T15:42:15+09:00" level=error msg="Transaction allocation failed" category=Util component=UPF
time="2021-11-30T15:42:15+09:00" level=error msg="new Xact error" category=Util component=UPF
time="2021-11-30T15:42:15+09:00" level=error category=Util component=UPF
time="2021-11-30T15:42:18+09:00" level=warning msg="Index Pool is empty" category=Util component=UPF
time="2021-11-30T15:42:18+09:00" level=error msg="Transaction allocation failed" category=Util component=UPF
time="2021-11-30T15:42:18+09:00" level=error msg="new Xact error" category=Util component=UPF
time="2021-11-30T15:42:18+09:00" level=error category=Util component=UPF
time="2021-11-30T15:42:21+09:00" level=warning msg="Index Pool is empty" category=Util component=UPF
time="2021-11-30T15:42:21+09:00" level=error msg="Transaction allocation failed" category=Util component=UPF
time="2021-11-30T15:42:21+09:00" level=error msg="new Xact error" category=Util component=UPF
time="2021-11-30T15:42:21+09:00" level=error category=Util component=UPF
```
These mean that no new PfcpXact about PFCP Session Modification procedure triggered by Service Request procedure was allocated.
You can also see the following message just before upf was terminated.
```
time="2021-11-30T15:42:26+09:00" level=warning msg="64 not freed in pfcpXactPool[0] of PFCP Transaction" category=Util component=UPF
```
This shows that 64 PfcpXacts had been leaked.
## Expected behavior
Leaked PfcpXacts will be freed after specific timeouts respectively so that they will be able to be allocated to new PFCP procedures.
## Environment (please complete the following information):
- free5GC Version: v3.0.6
- OS: Ubuntu 18.04 LTS
- Kernel version: 5.0.0-23-generic
- go version: 1.14.4 linux/amd64
- c compiler version (Option): gcc 7.5.0
|
[Bugs] UPF leaks PfcpXact if PFCP Session Report Response is not processed
|
https://api.github.com/repos/free5gc/free5gc/issues/289/comments
| 1 |
2021-11-30T08:24:37Z
|
2021-12-10T15:16:55Z
|
https://github.com/free5gc/free5gc/issues/289
| 1,066,933,733 | 289 |
[
"free5gc",
"free5gc"
] |
## Describe the bug
when i want to Subscribers a new UE in the webUI, i find this problem
## To Reproduce
## Expected behavior
It can susscessfuly subcribe a UE information
## Screenshots
## Environment (please complete the following information):
- free5GC Version: [e.g. v3.0.6]
- OS: [e.g. Ubuntu 18.04 Server]
- Kernel version: [e.g. 5.0.0-23-generic]
- go version: [e.g. 1.17.3 linux/amd64]
- c compiler version (Option): [e.g. gcc version 7.5.0]
## Trace File
### Configuration File
Provide the configuration file here.
If not clear of what to do, the `config` folder can be zip and upload it here.
### PCAP File
Dump the packet and provide the pcap file here.
If not clear of what to do, this command can be used `sudo tcpdump -i any -w free5gc.pcap` prior to running bug reproduce. Then upload the pcap file `free5gc.pcap`.
### Log File
Provide the program log file here.
If not clear of what to do, copy the printed log on the screen and upload it here.
## System architecture (Option)
Please provide the draft architecture, including the scenario, use cases, installation environment(bare metal, vm, container, or k8s), etc.
## Walkthrough (Option)
free5GC will be interested on the research or finding in brief.
## Additional context
It will be appreciated if other context can be added here.
|
webUI always show loading
|
https://api.github.com/repos/free5gc/free5gc/issues/288/comments
| 1 |
2021-11-29T03:09:23Z
|
2022-01-10T05:27:42Z
|
https://github.com/free5gc/free5gc/issues/288
| 1,065,557,043 | 288 |
[
"free5gc",
"free5gc"
] |
## Describe the bug
SMF panics if it receives UecontextreleaseRequest after receiving PDUSessionReleaseRequest.
## To Reproduce
1. RegistrationRequest ~ establish PDUSession
2. UE/gNB -> 5GC UpLinkNASTransport/PDUSessionReleaseRequest
3. gNB <- 5GC PDUSessionResourceReleaseCommand
4. gNB -> 5GC UEContextReleaseRequest
## Expected behavior
No panic.
## Environment (please complete the following information):
free5GC Version: 3.0.6
OS: Ubuntu 18.04
Kernel version: 5.0.0-23-generic
go version go1.14.4 linux/amd64
## Trace File
### Console log
```
2021-11-24T09:29:50Z [INFO][AMF][NGAP][127.0.1.1:9784] UE Context Release Request (/home/fujitsu/devel305/free5gc/NFs/amf/ngap/handler.go:1854 github.com/free5gc/amf/ngap.HandleUEContextReleaseRequest)
2021-11-24T09:29:50Z [WARN][AMF][NGAP][127.0.1.1:9784] Cause RadioNetwork[1] (/home/fujitsu/devel305/free5gc/NFs/amf/ngap/handler.go:3985 github.com/free5gc/amf/ngap.printAndGetCause)
2021-11-24T09:29:50Z [INFO][AMF][NGAP][127.0.1.1:9784][AMF_UE_NGAP_ID:1] Ue Context in GMM-Registered (/home/fujitsu/devel305/free5gc/NFs/amf/ngap/handler.go:1914 github.com/free5gc/amf/ngap.HandleUEContextReleaseRequest)
2021-11-24T09:29:50Z [INFO][SMF][PduSess] Recieve Update SM Context Request (/home/fujitsu/devel305/free5gc/NFs/smf/pdusession/api_individual_sm_context.go:62 github.com/free5gc/smf/pdusession.HTTPUpdateSmContext)
2021-11-24T09:29:50Z [INFO][SMF][PduSess] In HandlePDUSessionSMContextUpdate (/home/fujitsu/devel305/free5gc/NFs/smf/producer/pdu_session.go:245 github.com/free5gc/smf/producer.HandlePDUSessionSMContextUpdate)
2021-11-24T09:29:50Z [INFO][SMF][PduSess] The SMContext State should be Active State (/home/fujitsu/devel305/free5gc/NFs/smf/producer/pdu_session.go:392 github.com/free5gc/smf/producer.HandlePDUSessionSMContextUpdate)
2021-11-24T09:29:50Z [INFO][SMF][PduSess] SMContext state: InActivePending (/home/fujitsu/devel305/free5gc/NFs/smf/producer/pdu_session.go:393 github.com/free5gc/smf/producer.HandlePDUSessionSMContextUpdate)
2021-11-24T09:29:50Z [ERRO][SMF][PduSess] AN Release Error (/home/fujitsu/devel305/free5gc/NFs/smf/producer/pdu_session.go:408 github.com/free5gc/smf/producer.HandlePDUSessionSMContextUpdate)
2021/11/24 09:29:50 [Recovery] 2021/11/24 - 09:29:50 panic recovered:
runtime error: invalid memory address or nil pointer dereference
/usr/local/go/src/runtime/panic.go:212 (0x44d919)
panicmem: panic(memoryError)
/usr/local/go/src/runtime/signal_unix.go:695 (0x44d768)
sigpanic: panicmem()
/home/fujitsu/devel305/free5gc/NFs/smf/producer/pdu_session.go:416 (0x118a919)
HandlePDUSessionSMContextUpdate: farList = append(farList, DLPDR.FAR)
/home/fujitsu/devel305/free5gc/NFs/smf/pdusession/api_individual_sm_context.go:83 (0x11959df)
HTTPUpdateSmContext: HTTPResponse := producer.HandlePDUSessionSMContextUpdate(
/home/fujitsu/go/pkg/mod/github.com/gin-gonic/[email protected]/context.go:161 (0xc98b5a)
(*Context).Next: c.handlers[c.index](c)
```
## Additional context
I have sent a [PR](https://github.com/free5gc/smf/pull/37)
|
[Bugs] SMF panics when receiving UEContextReleaseRequest
|
https://api.github.com/repos/free5gc/free5gc/issues/287/comments
| 1 |
2021-11-24T10:04:31Z
|
2022-01-13T14:11:06Z
|
https://github.com/free5gc/free5gc/issues/287
| 1,062,226,022 | 287 |
[
"free5gc",
"free5gc"
] |
## Describe the bug
If AMF receives UContextReleaseRequest during waiting for SecurityModeComplete, it retransmits SecurityModeCommand because the Timer(T3560) is not stopped.
## To Reproduce
1. UE/gNB -> 5GC InitialUEMessage/RegistrationRequest
2. UE/gNB <- 5GC DownLinkNASTransport/AuthenticationRequest
3. UE/gNB -> 5GC UpLinkNASTransport/AuthenticationResponse
4. UE/gNB <- 5GC DownLinkNASTransport/SecurityModeCommand
5. gNB -> 5GC UContextReleaseRequest
6. UE/gNB <- 5GC DownLinkNASTransport/SecurityModeCommand(retry 4.ScurityModeCommand)
## Expected behavior
Not retransmit SecurityModeCommand Message.
## Environment (please complete the following information):
free5GC Version: 3.0.6
OS: Ubuntu 18.04
Kernel version: 5.0.0-23-generic
go version go1.14.4 linux/amd64
## Trace File
### PCAP File
[Bugs_Retransmit.zip](https://github.com/free5gc/free5gc/files/7593457/Bugs_Retransmit.zip)
## Additional context
I have sent a [PR](https://github.com/free5gc/amf/pull/52).
|
[Bugs] AMF retransmits SecurityModeCommand even though it receives UEContextReleaseRequest.
|
https://api.github.com/repos/free5gc/free5gc/issues/286/comments
| 1 |
2021-11-24T07:18:23Z
|
2022-01-04T14:13:03Z
|
https://github.com/free5gc/free5gc/issues/286
| 1,062,082,004 | 286 |
[
"free5gc",
"free5gc"
] |
**We will advise people to follow the issue template set, otherwise the issue might be disregarded.**
**free5GC mainly uses GitHub for issue tracking. Information regarding to general questions or technical support. It will be highly considered if forward to the [forum](https://forum.free5gc.org).**
**free5GC will appreciate it, if people can refer to [TS](https://github.com/free5gc/free5gc/wiki/Trouble_Shooting) and [forum](https://forum.free5gc.org) prior to bug reporting**
<!-- Remove warning (above 3 lines) while reporting the issue -->
## Describe the bug
When I insert a new UE from the Webconsole, all the QoS parameters are not updated at the UPF. That is, I will expect that in case of different parameters (AMBR, 5QI, MBR, GBR, ...) a new QER must be created at UPF. This does not happen, in fact I check with gtp5g-tunnel command the list of QER and the only one is the first I inserted at the beginning.
## To Reproduce
Steps to reproduce the behavior:
0. Set up a running free5gc CN
1. Configure at least 2 UE with different IMSI
2. Open Webconsole and insert two different DNN configuration and Flow Rules
3. Verify at UPF with gtp5-tunnel commands you can find at "~/free5gc/NFs/upf/updk/src/third_party/libgtp5gnl/tools"; for instance "sudo ./gtp5g-tunnel list qer"
You will get this list with different values (very far from the ones set in the Webconsole)
***************************************************************
[QER ID: 1]
Gate Status: 0
MBR Parameter Info
UL High: 3
UL Low: 232
DL High: 3
DL Low: 232
GBR Parameter Info
UL High: 0
UL Low: 0
DL High: 0
DL Low: 0
Correlation ID: 0
RQI: 0
QFI: 0
PPI: 0
RCSR: 0
Related PDR ID: 4, 3, 2, 1 (Not a real IE)
***************************************************************
## Expected behavior
I will expect more QER with values similar to the ones inserted in the Webcosole
*******************************************************************
[QER ID: 1]
Gate Status: 0
MBR Parameter Info
UL High: X1
UL Low: X2
DL High: X3
DL Low: X4
GBR Parameter Info
UL High: X5
UL Low: X6
DL High: X7
DL Low: X8
Correlation ID: 0
RQI: 0
QFI: 0
PPI: 0
RCSR: 0
Related PDR ID: 4, 3, 2, 1 (Not a real IE)
[QER ID: 2]
Gate Status: 0
MBR Parameter Info
UL High: Y1
UL Low: Y2
DL High: Y3
DL Low: Y4
GBR Parameter Info
UL High: Y5
UL Low: Y6
DL High: Y7
DL Low: Y8
Correlation ID: 0
RQI: 0
QFI: 0
PPI: 0
RCSR: 0
Related PDR ID: 4, 3, 2, 1 (Not a real IE)
*****************************************************************
By the way I was unable to decode the unit of measure of the parameters (Mbps, Kbps, ?)
## Screenshots
If applicable, add screenshots to help explain the problem.
## Environment (please complete the following information):
- free5GC Version: v3.0.6
- OS: Ubuntu 20.04
- Kernel version: 5.4.0-89-generic
- go version: go version go1.15.8 linux/amd64
- c compiler version (Option): gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)
## Trace File
### Configuration File
EXAMPLE FREE5GC DEFAULT
### PCAP File
NOT REQUIRED
### Log File
NOT REQUIRED
## System architecture (Option)
N/A
## Walkthrough (Option)
N/A
## Additional context
N/A
|
[Bugs] Multiple QER load
|
https://api.github.com/repos/free5gc/free5gc/issues/285/comments
| 3 |
2021-11-22T15:27:51Z
|
2023-09-11T01:52:12Z
|
https://github.com/free5gc/free5gc/issues/285
| 1,060,290,740 | 285 |
[
"free5gc",
"free5gc"
] |
## Issue Description
### What's the version are you using
v3.0.6
### Is your feature request related to a problem? Please describe.
No.
This feature is related to [issue/226](https://github.com/free5gc/free5gc/issues/226).
### Describe the solution you'd like
#### Preparation
1. Locate AMF, SMF, PCF and UPF in each area.
2. Set same "locality" to amfcfg.yaml, smfcfg.yaml and pcfcfg.yaml in each area.
#### Execution
1. PCF registers NF Profile with the locality
2. AMF and SMF select PCF by Nnrf_NFDiscovery_Request including preferred-locality
### Pull Request
Pull Request for the feature.
- [free5gc](https://github.com/free5gc/free5gc/pull/283)
- [amf](https://github.com/free5gc/amf/pull/51)
- [smf](https://github.com/free5gc/smf/pull/35)
- [pcf](https://github.com/free5gc/pcf/pull/3)
### Describe alternatives/workarounds you've considered
None
### Additional context
None
## Issue Template Checklist
<!-- Please answer the questions below. If not the issue might be disregarded. -->
### If willing to resolve an issue by submitting Pull request, please consider the points below.
<!-- free5GC will be happy to welcome first contributor’s, in order to broaden the community. -->
- [x] Yes, I have the time and I know how to start.
- [ ] Yes, I have the time but I don't know how to start, I would need guidance.
- [ ] No, I don't have the time, although I believe I could do it if I had the time...
- [ ] No, I don't have the time and I wouldn't even know how to start.
|
[Feat] PCF selection according to locality
|
https://api.github.com/repos/free5gc/free5gc/issues/284/comments
| 1 |
2021-11-18T08:05:54Z
|
2022-01-10T05:26:18Z
|
https://github.com/free5gc/free5gc/issues/284
| 1,057,054,072 | 284 |
[
"free5gc",
"free5gc"
] |
## Describe the bug
If PDU Session is established without releasing previous PFCP session, PDUSessionResourceSetupRequest message is sent when sending DL data with the IP address of the previously allocated UE.
## To Reproduce
1. Initial Registration ~ establish PDUSession
2. AN Release(UE Context Release Request ~ UE Context Release Complete)
3. Initial Registration ~ establish PDUSession(same UE as 1.)
4. Sending DL data with the IP address of the previously(1.) allocated UE
## Expected behavior
Release old PFCP Session and not sending PDUSessionResourceSetupRequest message.
## Environment (please complete the following information):
- free5GC Version: 3.0.6
- OS: Ubuntu 18.04
- Kernel version: 5.0.0-23-generic
- go version go1.14.4 linux/amd64
### PCAP File
[Bugs_OldPFCPSessionLeft.zip](https://github.com/free5gc/free5gc/files/7544948/Bugs_OldPFCPSessionLeft.zip)
## Additional context
I have sent a [PR](https://github.com/free5gc/smf/pull/33).
|
[Bugs] Old PFCP Session left in SMF and UPF
|
https://api.github.com/repos/free5gc/free5gc/issues/281/comments
| 1 |
2021-11-16T09:19:15Z
|
2022-01-10T14:17:11Z
|
https://github.com/free5gc/free5gc/issues/281
| 1,054,637,745 | 281 |
[
"free5gc",
"free5gc"
] |
## Describe the bug
The logging function of UPF, `UTLT_LogPrint()` is not thread-safe.
The log message buffer is possible to be overwritten by another thread during a thread is running it.
As a result, unexpected log message may be shown.
## To Reproduce
It is not easy to explain the way to reproduce it intentionally.
So many PDU session establishment / release messages will cause it.
## Expected behavior
`UTLT_LogPrint()` is thread-safe, and each log message is not overwritten by other threads.
## Environment (please complete the following information):
- free5GC Version: 3.0.5
- OS: Ubuntu 18.04
- Kernel version: 5.0.0-23-generic
- go version go1.14.4 linux/amd64
## Additional context
I have sent a [PR](https://github.com/free5gc/upf/pull/43).
|
[Bugs] The UPF logging function is not thread-safe, so the contents of another log may be overwritten during logging
|
https://api.github.com/repos/free5gc/free5gc/issues/280/comments
| 1 |
2021-11-16T06:16:29Z
|
2021-11-30T04:00:55Z
|
https://github.com/free5gc/free5gc/issues/280
| 1,054,489,892 | 280 |
[
"free5gc",
"free5gc"
] |
Hi i am having some trouble ,
the UE and gnb are configured with sst 01 and SSD 010203 which can be seen in the ng setup request and response
But when it come ti registration request/response or pdu seestion establishment it uses a different SD
can someone help and confirm if it is in fact a problem on the software, or I am missing something ?
|
[Bugs] NSSAI (SD) in the NG setup doesnt match the one used in the Registration request
|
https://api.github.com/repos/free5gc/free5gc/issues/278/comments
| 4 |
2021-11-10T11:06:20Z
|
2021-11-15T00:56:52Z
|
https://github.com/free5gc/free5gc/issues/278
| 1,049,687,712 | 278 |
[
"free5gc",
"free5gc"
] |
## Describe the bug
I deploy the free5gc:v3.0.6 with k8s 1.22.3, and my ueransim-user can have ip address(which is 60.60.0.1), but when I ping www.baidu.com -I uesimtun0, I find the ue can't access to the internet. I use docker-compose to deploy the free5gc:v3.0.6 the ue can access to the internet. I do this in the upf:
**iptables -I FORWARD 1 -j ACCEPT
iptables -t nat -A POSTROUTING -s 60.60.0.0/16 ! -o upfgtp -j MASQUERADE
iptables -t nat -A POSTROUTING -s 60.61.0.0/16 ! -o upfgtp -j MASQUERADE
iptables -t nat -A POSTROUTING -s 60.62.0.0/16 ! -o upfgtp -j MASQUERADE**
and i compare with the docker-compose deploy free5gc with k8s deploy free5gc,the UPF's iptables rules are different:
docker-compose:UPF's iptbales rules:
****Chain PREROUTING (policy ACCEPT)
target prot opt source destination**
**Chain INPUT (policy ACCEPT)
target prot opt source destination**
**Chain OUTPUT (policy ACCEPT)
target prot opt source destination
DOCKER_OUTPUT all -- anywhere 127.0.0.11**
**Chain POSTROUTING (policy ACCEPT)
target prot opt source destination
DOCKER_POSTROUTING all -- anywhere 127.0.0.11
MASQUERADE all -- 60-60-0-0.rev.home.ne.jp/16 anywhere
MASQUERADE all -- 60-61-0-0.rev.home.ne.jp/16 anywhere
MASQUERADE all -- 60.62.0.0/16 anywhere**
**Chain DOCKER_OUTPUT (1 references)
target prot opt source destination
DNAT tcp -- anywhere 127.0.0.11 tcp dpt:53 to:127.0.0.11:43101
DNAT udp -- anywhere 127.0.0.11 udp dpt:53 to:127.0.0.11:46333**
**Chain DOCKER_POSTROUTING (1 references)
target prot opt source destination
SNAT tcp -- 127.0.0.11 anywhere tcp spt:43101 to::53
SNAT udp -- 127.0.0.11 anywhere udp spt:46333 to::53****
k8s:UPF's iptables rules:
**Chain PREROUTING (policy ACCEPT)
target prot opt source destination**
**Chain INPUT (policy ACCEPT)
target prot opt source destination**
**Chain OUTPUT (policy ACCEPT)
target prot opt source destination
DOCKER_OUTPUT all -- anywhere 127.0.0.11**
**Chain POSTROUTING (policy ACCEPT)
target prot opt source destination
DOCKER_POSTROUTING all -- anywhere 127.0.0.11
MASQUERADE all -- 60-60-0-0.rev.home.ne.jp/16 anywhere
MASQUERADE all -- 60-61-0-0.rev.home.ne.jp/16 anywhere
MASQUERADE all -- 60.62.0.0/16 anywhere**
**Chain DOCKER_OUTPUT (1 references)
target prot opt source destination
DNAT tcp -- anywhere 127.0.0.11 tcp dpt:53 to:127.0.0.11:43101
DNAT udp -- anywhere 127.0.0.11 udp dpt:53 to:127.0.0.11:46333**
**Chain DOCKER_POSTROUTING (1 references)
target prot opt source destination
SNAT tcp -- 127.0.0.11 anywhere tcp spt:43101 to::53
SNAT udp -- 127.0.0.11 anywhere udp spt:46333 to::53**
## Expected behavior
I want my ue can access to the internet
## Environment (please complete the following information):
- free5GC Version: [e.g. v3.0.6]
- OS: [e.g. Ubuntu 18.04 Server]
- Kernel version: [e.g. 5.200.0-0-generic]
- go version: [e.g. 1.10.0 linux/amd64]
- c compiler version (Option): [e.g. gcc version 1.1.0]
|
free5gc with k8s, ueransim-user can't access to the internet
|
https://api.github.com/repos/free5gc/free5gc/issues/276/comments
| 2 |
2021-11-05T09:35:03Z
|
2023-09-04T06:06:52Z
|
https://github.com/free5gc/free5gc/issues/276
| 1,045,628,575 | 276 |
[
"free5gc",
"free5gc"
] |
The network topology is as follows:
links: # the topology graph of userplane, A and B represent the two nodes of each link
- A: gNB1
B: BranchingUPF
- A: gNB2
B: BranchingUPF
- A: BranchingUPF
B: AnchorUPF1
- A: BranchingUPF
B: AnchorUPF2
- A: BranchingUPF
B: AnchorUPF3
- A: BranchingUPF
B: AnchorUPF4
/smf - 10.100.200.15
2021-11-04T21:19:11Z [INFO][UPF][Util] Config: /free5gc/config/upfcfg.yaml
2021-11-04T21:19:11Z [INFO][UPF][Util] UPF config version [1.0.0]
2021-11-04T21:19:11Z [INFO][UPF][Util] Set log level: info
2021-11-04T21:19:11Z [INFO][UPF][Util] DNN routes added, main routing table:
2021-11-04T21:19:11Z [INFO][UPF][Util] DstIp Gateway Iface Priority RtProto Type
2021-11-04T21:19:11Z [INFO][UPF][Util] 60.60.0.0 /24 0.0.0.0 upfgtp 0 static unicast
2021-11-04T21:19:11Z [INFO][UPF][Util] 10.100.200.0 /24 0.0.0.0 eth0 0 kernel unicast
2021-11-04T21:19:11Z [INFO][UPF][Util] 0.0.0.0 /0 10.100.200.1 eth0 0 boot unicast
2021-11-04T21:19:13Z [INFO][UPF][Util] [PFCP] Handle PFCP association setup request
2021-11-04T21:19:13Z [INFO][UPF][Util] [PFCP] Association Setup Response
2021-11-04T21:19:14Z [INFO][UPF][Util] [PFCP] Handle PFCP session establishment request
2021-11-04T21:19:14Z [INFO][UPF][Util] [PFCP] Session Establishment Response
2021-11-04T21:19:14Z [INFO][UPF][Util] [PFCP] Handle PFCP session modification request
2021-11-04T21:19:14Z [INFO][UPF][Util] [PFCP] Session Modification Response
2021-11-04T21:19:14Z [INFO][UPF][Util] [PFCP] Handle PFCP session modification request
2021-11-04T21:19:14Z [INFO][UPF][Util] [PFCP] Session Modification Response
2021-11-04T21:19:14Z [INFO][UPF][Util] [PFCP] Handle PFCP session establishment request
2021-11-04T21:19:14Z [INFO][UPF][Util] [PFCP] Session Establishment Response
2021-11-04T21:19:14Z [INFO][UPF][Util] [PFCP] Handle PFCP session modification request
2021-11-04T21:19:14Z [INFO][UPF][Util] [PFCP] Session Modification Response
2021-11-04T21:19:14Z [INFO][UPF][Util] [PFCP] Handle PFCP session modification request
2021-11-04T21:19:14Z [INFO][UPF][Util] [PFCP] Session Modification Response
2021-11-04T21:20:03Z [INFO][UPF][Util] [PFCP] Handle PFCP session establishment request
2021-11-04T21:20:03Z [INFO][UPF][Util] [PFCP] Session Establishment Response
2021-11-04T21:20:03Z [INFO][UPF][Util] [PFCP] Handle PFCP session modification request
2021-11-04T21:20:03Z [INFO][UPF][Util] [PFCP] Session Modification Response
2021-11-04T21:20:03Z [WARN][UPF][Util] [19] remote Request Duplicated. Retransmit! for step 2 type 52 peer [10.100.200.15]:8805
2021-11-04T21:20:03Z [WARN][UPF][Util] [19] remote Request Duplicated. Retransmit! for step 2 type 52 peer [10.100.200.15]:8805
2021-11-04T21:20:03Z [WARN][UPF][Util] [19] remote Request Duplicated. Retransmit! for step 2 type 52 peer [10.100.200.15]:8805
2021-11-04T21:20:03Z [ERRO][UPF][Util] Index Pool is full, it may not belong to this pool
2021-11-04T21:20:03Z [WARN][UPF][Util] [19] remote Request Duplicated. Retransmit! for step 2 type 52 peer [10.100.200.15]:8805
2021-11-04T21:20:03Z [ERRO][UPF][Util] Index Pool is full, it may not belong to this pool
2021-11-04T21:20:03Z [WARN][UPF][Util] [19] remote Request Duplicated. Retransmit! for step 2 type 52 peer [10.100.200.15]:8805
2021-11-04T21:20:03Z [ERRO][UPF][Util] Index Pool is full, it may not belong to this pool
2021-11-04T21:20:03Z [WARN][UPF][Util] [19] remote Request Duplicated. Retransmit! for step 2 type 52 peer [10.100.200.15]:8805
2021-11-04T21:20:03Z [ERRO][UPF][Util] Index Pool is full, it may not belong to this pool
2021-11-04T21:20:03Z [WARN][UPF][Util] [19] remote Request Duplicated. Retransmit! for step 2 type 52 peer [10.100.200.15]:8805
2021-11-04T21:20:03Z [ERRO][UPF][Util] Index Pool is full, it may not belong to this pool
2021-11-04T21:20:03Z [WARN][UPF][Util] [19] remote Request Duplicated. Retransmit! for step 2 type 52 peer [10.100.200.15]:8805
2021-11-04T21:20:03Z [ERRO][UPF][Util] Index Pool is full, it may not belong to this pool
2021-11-04T21:20:03Z [WARN][UPF][Util] [19] remote Request Duplicated. Retransmit! for step 2 type 52 peer [10.100.200.15]:8805
2021-11-04T21:20:03Z [ERRO][UPF][Util] Index Pool is full, it may not belong to this pool
2021-11-04T21:20:03Z [WARN][UPF][Util] [19] remote Request Duplicated. Retransmit! for step 2 type 52 peer [10.100.200.15]:8805
2021-11-04T21:20:03Z [ERRO][UPF][Util] Index Pool is full, it may not belong to this pool
2021-11-04T21:20:03Z [WARN][UPF][Util] [19] remote Request Duplicated. Retransmit! for step 2 type 52 peer [10.100.200.15]:8805
|
[Bugs]remote Request Duplicated. Retransmit | UPF Index Pool is full
|
https://api.github.com/repos/free5gc/free5gc/issues/275/comments
| 1 |
2021-11-04T21:37:35Z
|
2023-08-14T05:38:39Z
|
https://github.com/free5gc/free5gc/issues/275
| 1,045,232,900 | 275 |
[
"free5gc",
"free5gc"
] |
**We will advise people to follow the issue template set, otherwise the issue might be disregarded.**
**free5GC mainly uses GitHub for issue tracking. Information regarding to general questions or technical support. It will be highly considered if forward to the [forum](https://forum.free5gc.org).**
**free5GC will appreciate it, if people can refer to [TS](https://github.com/free5gc/free5gc/wiki/Trouble_Shooting) and [forum](https://forum.free5gc.org) prior to bug reporting**
<!-- Remove warning (above 3 lines) while reporting the issue -->
## Describe the bug
AUSF does not handle when res* is received in uppercase format
## To Reproduce
Need an AMF that will send res* in uppercase format
## Expected behavior
From 3gpp (TS 29.509) res* is in format '[A-Fa-f0-9]{32}' so uppercase should be accepted
##Correction
In function Auth5gAkaComfirmRequestProcedure of the file ue_authentication.go
changing the condition if strings.Compare(updateConfirmationData.ResStar, ausfCurrentContext.XresStar) == 0
to
if strings.Compare(strings.ToLower(updateConfirmationData.ResStar), strings.ToLower(ausfCurrentContext.XresStar)) == 0
Solves this issue
|
[Bugs] AUSF does not handle when res* is received in uppercase format
|
https://api.github.com/repos/free5gc/free5gc/issues/274/comments
| 1 |
2021-11-02T10:58:26Z
|
2023-08-08T16:17:34Z
|
https://github.com/free5gc/free5gc/issues/274
| 1,042,179,177 | 274 |
[
"free5gc",
"free5gc"
] |
## Describe the bug
When I fuzz the URL of the request. I found the code doesn't handle illegal target-nf-type input.
## To Reproduce
Run the nrf and send HTTP2 package like url is
/nnrf-disc/v1/nf-instances?requester-nf-type=AMF&supi=imsi-208930000000014&target-nf-type=0
I changed target-nf-type as "0".
You can see the code detail in "nrf/producer/nf_discovery.go L518".
Besides the supi is also not have legal check.
## Expected behavior
A better way is to tell the wrong input.
## Screenshots
Here is log.
## Environment (please complete the following information):
doesn't matter.
- free5GC Version: [e.g. v3.0.100]
- OS: [e.g. Ubuntu 200.04 Server]
- Kernel version: [e.g. 5.200.0-0-generic]
- go version: [e.g. 1.10.0 linux/amd64]
- c compiler version (Option): [e.g. gcc version 1.1.0]
### Log File
Thanks.
|
[Bugs]NRF crashed when NRF Discovery params target-nf-type is illegal input.
|
https://api.github.com/repos/free5gc/free5gc/issues/273/comments
| 0 |
2021-11-02T07:17:12Z
|
2023-07-20T05:08:05Z
|
https://github.com/free5gc/free5gc/issues/273
| 1,041,955,946 | 273 |
[
"free5gc",
"free5gc"
] |
Hi,
Is there any way can help to update the uerouting rules after the SMF is up?
Thanks in advance.
Best regards,
Ziran
|
[Feat] Update uerouting rules after the SMF is up
|
https://api.github.com/repos/free5gc/free5gc/issues/272/comments
| 1 |
2021-10-31T05:29:29Z
|
2023-06-21T05:29:16Z
|
https://github.com/free5gc/free5gc/issues/272
| 1,040,380,653 | 272 |
[
"free5gc",
"free5gc"
] |
Hello Sir,
How can I clear the log files without having an issue or error?
I have VM with 5Gcore with 10 GB and after one week of work and testing the free5gc, I get no space available in my VM.
I tried to clear the log file or create the file again but i still have the same issue.
<img width="797" alt="Screenshot 2021-10-25 at 10 43 53 pm" src="https://user-images.githubusercontent.com/34620715/138775798-0d23b77b-3bdb-4879-9d3a-beb2d456a6b0.png">
Thanks,
Noor
|
Log files: clear the log file
|
https://api.github.com/repos/free5gc/free5gc/issues/271/comments
| 2 |
2021-10-25T21:47:06Z
|
2023-07-21T08:53:20Z
|
https://github.com/free5gc/free5gc/issues/271
| 1,035,602,838 | 271 |
[
"free5gc",
"free5gc"
] |
hello erveryone:
can we use multiple upf with the version of v3.0.5 free5gc?
|
can wu use mutliple upf with the verison of v3.0.5 free5gc
|
https://api.github.com/repos/free5gc/free5gc/issues/270/comments
| 6 |
2021-10-22T08:58:29Z
|
2021-10-26T14:16:30Z
|
https://github.com/free5gc/free5gc/issues/270
| 1,033,344,824 | 270 |
[
"free5gc",
"free5gc"
] |
<!-- Remove warning (above 3 lines) while reporting the issue -->
## Describe the bug
When attaching and registering a UE and sending a PDU session establishment request, the network
responds with a PDU session establishment accept. The allocated PDU address is set to 60.60.0.1 and looks correct.
But the transportLayerAddress for the gtpTunnel in the UPTransportLayerInformation is always set to localhost 127.0.0.8, thus unreachable for my UE. My goal would be getting through a ping.
I included a zip containing a PCAP, the logfiles and the config files.
[free5gc_resources.tar.gz](https://github.com/free5gc/free5gc/files/7390977/free5gc_resources.tar.gz)
I appreciate any assistance.
## Expected behavior
I expect to receive a reachable ip adress within the PDU Session Establishment Accept.
## Screenshots
If applicable, add screenshots to help explain the problem.
## Environment (please complete the following information):
- free5GC Version: v3.0.6
- OS: Ubuntu 18.04
- Kernel version: 5.4.0-87-generic
- go version: go1.14.4 linux/amd64
- c compiler version (Option): gcc version 7.5.0 (Ubuntu 7.5.0-3ubuntu1~18.04)
## System architecture
I am using a custom UE+gNB implementation to connect to the core.
UE and gNB are running on my local setup, and free5GC is running in a virtual machine
.
|
[Bugs] PDU Session Establishment Accept sets localhost (127.0.0.8) as TransportLayerAddress
|
https://api.github.com/repos/free5gc/free5gc/issues/269/comments
| 1 |
2021-10-21T15:32:55Z
|
2021-10-21T16:45:30Z
|
https://github.com/free5gc/free5gc/issues/269
| 1,032,641,239 | 269 |
[
"free5gc",
"free5gc"
] |
## Describe the bug
When PfcpXact timerexpire, EventSend() sends an event to the event queue with TimerExpireCheck() taking mutexlock.
When a large number of PfcpXacts are timerexpired at approximately the same time, the event queue can overflow because a large number of events are sent to the event queue at approximately the same time.
If you attempt to send an event when the event queue is full, EventSend() will block holding the mutexlock until the queue becomes empty.
The PfcpXact timerexpire event sent to the event queue is pruned by EventRecv() in eventConsumer() and passed through UpfDispatcher() to PfcpXactTimeout().
When releasing PfcpXact, use TimerDelete() to release the timer, but try to acquire mutexlock.
At this time, if the event queue overflows and EventSend() of TimerExpireCheck() is blocked, mutexlock cannot be taken and deadlock occurs. As a result, transmission and reception of PFCP become impossible.
## To Reproduce
No reliable reproduction method has been found.
If you send a Pdu Session Establishment Request from dozens of UEs at the same time, it will be reproduced someday.
## Expected behavior
No deadlock occurs.
PFCP transmission and reception are not inhibited.
## Environment (please complete the following information):
- free5GC Version: 3.0.5
- OS: Ubuntu 18.04
- Kernel version: 5.0.0-23-generic
- go version go1.14.4 linux/amd64
## Pull Request
[Pull Request](https://github.com/free5gc/upf/pull/40) for the fix.
|
[Bugs]When a large number of PfcpXacts are timerexpire at approximately the same time, TimerExpireCheck deadlocks and cannot transmit or receive PFCPs.
|
https://api.github.com/repos/free5gc/free5gc/issues/268/comments
| 4 |
2021-10-21T10:15:40Z
|
2021-11-30T04:07:14Z
|
https://github.com/free5gc/free5gc/issues/268
| 1,032,312,224 | 268 |
[
"free5gc",
"free5gc"
] |
## Describe the bug
DNNs are stored into MongoDB as keys of documents in some collections, for example,
"db.subscriptionData.provisionedData.smData" and "db.policyData.ues.smData".
MongoDB query API treats a period(.) in the query key as a delimiter of nested documents.
So that, NFs cannot get data from MongoDB if DNN as a query key contains a period.
As a result, PDU session cannot be established with such DNN.
## To Reproduce
1. Set DNN which contains a period like "example.net" into smfcfg.yaml, upfcfg.yaml, UE and MongoDB.
2. Register the UE to free5GC and try to establish a PDU session with the DNN.
You can see the following log output indicating that the SmPolicy cannot be obtained:.
```
2021-10-20T16:21:30+09:00 [INFO][PCF][SMpolicy] Handle CreateSmPolicy
2021-10-20T16:21:30+09:00 [INFO][UDR][DRepo] Handle PolicyDataUesUeIdSmDataGet
2021-10-20T16:21:30+09:00 [INFO][UDR][GIN] | 404 | 127.0.0.1 | GET | /nudr-dr/v1/policy-data/ues/imsi-2089300007487/sm-data?dnn=example.net&snssai=%7B%22sst%22%3A1%2C%22sd%22%3A%22010203%22%7D |
2021-10-20T16:21:30+09:00 [WARN][PCF][SMpolicy] Can't find UE[imsi-2089300007487] SM Policy Data in UDR
2021-10-20T16:21:30+09:00 [INFO][PCF][GIN] | 400 | 127.0.0.1 | POST | /npcf-smpolicycontrol/v1/sm-policies |
2021-10-20T16:21:30+09:00 [ERRO][SMF][PduSess] setup sm policy association failed: 400 Bad Request { 400 Can't find UE SM Policy Data in UDR USER_UNKNOWN []}
2021-10-20T16:21:30+09:00 [INFO][SMF][GIN] | 403 | 127.0.0.1 | POST | /nsmf-pdusession/v1/sm-contexts |
2021-10-20T16:21:30+09:00 [WARN][AMF][GMM][AMF_UE_NGAP_ID:1][SUPI:imsi-2089300007487] PDU Session Establishment Request is rejected by SMF[pduSessionId:10]
```
## Expected behavior
NFs can get data from MongoDB even if DNN contains a period, and a PDU session with the DNN can be established.
## Environment (please complete the following information):
- free5GC Version: 3.0.5
- OS: Ubuntu 18.04
- Kernel version: 5.0.0-23-generic
- go version go1.14.4 linux/amd64
## System architecture (Option)
- To replace all periods(.) in DNN to underscores(_) which is not available to be used in DNN
before storing it into MongoDB.
- To replace all periods(.) in DNN to underscores(_) before calling MongoDB query API.
- To replace all underscores(_) of DNNs in the gotten data, from MongoDB by the query API, to periods(.).
## Pull Request
- [udr](https://github.com/free5gc/udr/pull/4)
### If willing to resolve an issue by submitting Pull request, please consider the points below.
Webconsole also needs to be fixed but I don't know how to fix it.
|
[Bugs] PDU session cannot be established if DNN contains a period(.)
|
https://api.github.com/repos/free5gc/free5gc/issues/267/comments
| 1 |
2021-10-20T09:09:32Z
|
2021-11-30T08:24:14Z
|
https://github.com/free5gc/free5gc/issues/267
| 1,031,163,813 | 267 |
[
"free5gc",
"free5gc"
] |
Hello Sir,
How could I connect 3 upf (different VM upf1, upf2 and upf3 ) with different SMF (smf1, smf2 and smf3) on VM for the core?
When I try to add new upf (upf4 with IP: 172.16.4.105 ) with (smf4), I get an error as in the image below.
" Failed to listen: listen udp 172.16.4.105:8805: bind: cannot assign requested address
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0xb43884]
"
<img width="1309" alt="Screenshot 2021-10-17 at 7 34 35 pm" src="https://user-images.githubusercontent.com/34620715/137644792-64e782cd-d41a-440f-bd0a-7979437a80e2.png">
I checked the configurations files all fine but i don't know why i get this error.
Could you please help?
Regards,
Noor
|
Failed to listen: listen udp, panic: runtime error: invalid memory address or nil pointer dereference
|
https://api.github.com/repos/free5gc/free5gc/issues/266/comments
| 3 |
2021-10-17T21:02:30Z
|
2023-08-29T04:53:44Z
|
https://github.com/free5gc/free5gc/issues/266
| 1,028,436,788 | 266 |
[
"free5gc",
"free5gc"
] |
**If the design issue template is not followed, the issue might be closed.**
<!-- Remove above warning line while reporting the issue -->
## Documentation request
The tag v3.0.6 does not include the latest hash for the amf, smf and udm which leads to PDU session establishment errors (tested with UERANSIM v3.2.4, specific error on the UDM unmarshalling the PLMNID).
## Suggestion
Replace the current v3.0.6 tag to include the latest commit.
To avoid this error in the current version, users must not follow the wiki and remove the tag when cloning the repo
```bash
cd ~
git clone --recursive -j `nproc` https://github.com/free5gc/free5gc.git
cd free5gc
```
## Additional context
Nope 👍
|
[Docs] Update tag for v3.0.6 - Errors in AMF, UDM and SMF if not
|
https://api.github.com/repos/free5gc/free5gc/issues/265/comments
| 3 |
2021-10-15T15:59:03Z
|
2021-10-26T14:22:36Z
|
https://github.com/free5gc/free5gc/issues/265
| 1,027,581,627 | 265 |
[
"free5gc",
"free5gc"
] |
## Describe the bug
I find when my ue connect to gnb, the gnb has an error:
[2021-10-09 07:06:10.936] [app] [error] TUN allocation failure [Open failure /dev/net/tun]
does anyone know how to solve this problem?
Thanks very much
|
UERANSIM ue can't access to the internet
|
https://api.github.com/repos/free5gc/free5gc/issues/263/comments
| 2 |
2021-10-09T07:34:37Z
|
2021-10-26T14:21:48Z
|
https://github.com/free5gc/free5gc/issues/263
| 1,021,634,333 | 263 |
[
"free5gc",
"free5gc"
] |
now i want to relay NAGP packages, how can i do this? are there some tools or commands
thx~
|
[Feat]relay some pcap packages
|
https://api.github.com/repos/free5gc/free5gc/issues/262/comments
| 1 |
2021-10-09T07:19:11Z
|
2023-06-26T05:41:26Z
|
https://github.com/free5gc/free5gc/issues/262
| 1,021,630,769 | 262 |
[
"free5gc",
"free5gc"
] |
## Describe the bug
We connect free5gc to the real NG and UEs, the access initiated by the unauthenticated UE is rejected. After 128 times, AMF will crash. The repeated access of the rejected UE causes the panic.
## Expected behavior
Expected to solve the service crash.
## Environment (please complete the following information):
- free5GC Version: [v3.0.5]
- OS: [e.g. Ubuntu 18.04 Server]
- Kernel version: [5.2.0-0-generic]
- go version: [go1.14.4 linux/amd64]
## Trace File
### Log File
2021-09-26T18:24:04+08:00 [ERRO][AMF][GMM][AMF_UE_NGAP_ID:303] Nausf_UEAU Authenticate Request Failed: &{Type: Title: Status:500 Detail: Instance: Cause:AV_GENERATION_PROBLEM InvalidParams:[]}
2021-09-26T18:31:27+08:00 [INFO][AMF][NGAP][12.12.12.101:65453] Handle Initial UE Message
2021-09-26T18:31:27+08:00 [WARN][NAS][Security] Integrity NIA0 is emergency.
2021-09-26T18:31:27+08:00 [WARN][AMF][NAS][AMF_UE_NGAP_ID:304] NAS MAC verification failed(received: 0x52636310, expected: 0x00000000)
2021-09-26T18:31:27+08:00 [INFO][AMF][GMM][AMF_UE_NGAP_ID:304] Handle Registration Request
2021-09-26T18:31:27+08:00 [ERRO][AMF][GMM] NAS decode Fail: MsgType[35] doesn't exist in GMM Message
2021-09-26T18:31:52+08:00 [INFO][AMF][NGAP][12.12.12.101:65453] Handle Initial UE Message
2021-09-26T18:31:52+08:00 [WARN][NAS][Security] Integrity NIA0 is emergency.
2021-09-26T18:31:52+08:00 [WARN][AMF][NAS][AMF_UE_NGAP_ID:305] NAS MAC verification failed(received: 0x61f2591c, expected: 0x00000000)
2021-09-26T18:31:52+08:00 [INFO][AMF][GMM][AMF_UE_NGAP_ID:305] Handle Registration Request
2021-09-26T18:31:52+08:00 [ERRO][AMF][GMM] NAS decode Fail: MsgType[111] doesn't exist in GMM Message
2021-09-26T18:32:17+08:00 [INFO][AMF][NGAP][12.12.12.101:65453] Handle Initial UE Message
2021-09-26T18:32:17+08:00 [WARN][NAS][Security] Integrity NIA0 is emergency.
2021-09-26T18:32:17+08:00 [WARN][AMF][NAS][AMF_UE_NGAP_ID:306] NAS MAC verification failed(received: 0xa329edea, expected: 0x00000000)
2021-09-26T18:32:17+08:00 [INFO][AMF][GMM][AMF_UE_NGAP_ID:306] Handle Registration Request
2021-09-26T18:32:17+08:00 [ERRO][AMF][GMM] The payload of NAS Message Container is not Registration Request
2021-09-26T18:32:42+08:00 [INFO][AMF][NGAP][12.12.12.101:65453] Handle Initial UE Message
2021-09-26T18:32:42+08:00 [WARN][NAS][Security] Integrity NIA0 is emergency.
2021-09-26T18:32:42+08:00 [WARN][AMF][NAS][AMF_UE_NGAP_ID:307] NAS MAC verification failed(received: 0x99224524, expected: 0x00000000)
2021-09-26T18:32:42+08:00 [INFO][AMF][GMM][AMF_UE_NGAP_ID:307] Handle Registration Request
2021-09-26T18:32:42+08:00 [INFO][AMF][NGAP] [AMF] SCTP Accept from: 12.12.12.101:65528
panic: runtime error: slice bounds out of range [:60] with length 16
|
[Bugs]free5gc service crashes after the unauthenticated UE access is rejected about 128 times
|
https://api.github.com/repos/free5gc/free5gc/issues/261/comments
| 3 |
2021-10-09T03:05:24Z
|
2023-07-03T09:40:04Z
|
https://github.com/free5gc/free5gc/issues/261
| 1,021,581,637 | 261 |
[
"free5gc",
"free5gc"
] |
Hello sir,
I followed your instructions based on the video "https://www.youtube.com/watch?v=AEMrjKRWarw".
<img width="976" alt="Screenshot 2021-10-06 at 2 15 26 pm" src="https://user-images.githubusercontent.com/34620715/136373655-96c0309e-5396-490d-973e-46908e925c19.png">
Ping successful with 8.8.8.8 as in the image. Also, I can ping google with his IP address (142.250.187.206), but it failed when I try to ping the real-word internet with (google.com) or download a document for example.
Could you please help me with this?
I have a problem with the NAT
sudo sysctl -w net.ipv4.ip_forward=1
sudo iptables -t nat -A POSTROUTING -o enp0s3 -j MASQUERADE
sudo systemctl stop ufw
sudo iptables -I FORWARD 1 -j ACCEPT
I used NAT this command as well >> " iptables -t nat -A POSTROUTING -s 60.61.0.0/24 ! -o upfgtp -j MASQUERADE " the UPF but the ping still not working.
<img width="705" alt="Screenshot 2021-10-13 at 2 38 56 pm" src="https://user-images.githubusercontent.com/34620715/137144317-fe6d036c-3aa6-4e8e-830e-c82977916a1d.png">
<img width="547" alt="Screenshot 2021-10-13 at 2 40 31 pm" src="https://user-images.githubusercontent.com/34620715/137144354-1e2d0156-aa0e-40cc-abfd-f684f236d2a0.png">
Thanks
Noor
|
Connect to the interent (UERANSIM can't access to the internet)
|
https://api.github.com/repos/free5gc/free5gc/issues/260/comments
| 1 |
2021-10-07T11:15:31Z
|
2023-07-21T08:47:19Z
|
https://github.com/free5gc/free5gc/issues/260
| 1,019,921,256 | 260 |
[
"free5gc",
"free5gc"
] |
## Describe the bug
Because you are not checking the return value of BufblkAlloc() or BufblkBytes(), segmentation faults can occur if BufAlloc() internally fails.
## To Reproduce
It is difficult to reproduce the event intentionally, but I think it is clear from the source code that you will access the invalid address when you continue processing without confirming these abnormal return values.
## Expected behavior
- Do not cause a Segmentation fault if BufblkAlloc() or BufblkBytes() returns an abnormal return value.
- BufblkAlloc() and BufblkBytes() that do not determine the return value are guaranteed to respond normally.
## Environment (please complete the following information):
- free5GC Version: 3.0.5
- OS: Ubuntu 18.04
- Kernel version: 5.0.0-23-generic
- go version go1.14.4 linux/amd64
## Pull Request
[Pull Request](https://github.com/free5gc/upf/pull/39) for the fix.
|
[Bugs] SegFault may result when an error occurs during BufBlkAlloc or BufblkBytes.
|
https://api.github.com/repos/free5gc/free5gc/issues/259/comments
| 1 |
2021-10-07T06:21:51Z
|
2021-10-25T04:16:56Z
|
https://github.com/free5gc/free5gc/issues/259
| 1,019,661,360 | 259 |
[
"free5gc",
"free5gc"
] |
Hi,
Please I am having issues running ueransim with Free5gc. Any ideas what could be the issue?
when trying service request
./nr-cli UERANSIM-gnb-208-93-1 -e "ue-release 1"
nr_ue | [2021-10-03 19:13:02.995] [rrc] [debug] Sending RRC Setup Request
nr_ue | [2021-10-03 19:13:02.995] [nas] [info] UE switches to state [MM-SERVICE-REQUEST-INITIATED]
nr_ue | [2021-10-03 19:13:02.995] [rrc] [info] RRC connection established
nr_ue | [2021-10-03 19:13:02.995] [rrc] [info] UE switches to state [RRC-CONNECTED]
nr_ue | [2021-10-03 19:13:02.995] [nas] [info] UE switches to state [CM-CONNECTED]
nr_ue | [2021-10-03 19:13:03.008] [nas] [warning] Not protected Service Reject message received
nr_ue | [2021-10-03 19:13:03.008] [nas] [error] Service Reject received with cause [UE_IDENTITY_CANNOT_BE_DERIVED_FROM_NETWORK]
nr_ue | [2021-10-03 19:13:03.009] [nas] [info] UE switches to state [5U2-NOT-UPDATED]
nr_ue | [2021-10-03 19:13:03.009] [nas] [info] UE switches to state [MM-DEREGISTERED/PS]
nr_ue | [2021-10-03 19:13:03.009] [nas] [debug] Initial registration required due to [DUE-TO-SERVICE_REJECT]
nr_ue | [2021-10-03 19:13:03.009] [nas] [info] UE switches to state [MM-DEREGISTERED/NORMAL-SERVICE]
nr_ue | [2021-10-03 19:13:03.009] [nas] [debug] Sending Initial Registration
nr_ue | [2021-10-03 19:13:03.009] [nas] [info] UE switches to state [MM-REGISTER-INITIATED]
nr_ue | [2021-10-03 19:13:03.013] [rrc] [debug] RRC Release received
gnb
nr_gnb | [2021-10-03 19:13:15.078] [ngap] [warning] Sending an error indication with cause: radio-network/unknown-local-UE-NGAP-ID
nr_gnb | [2021-10-03 19:13:21.077] [ngap] [warning] Sending an error indication with cause: radio-network/unknown-local-UE-NGAP-ID
nr_gnb | [2021-10-03 19:13:27.077] [ngap] [warning] Sending an error indication with cause: radio-network/unknown-local-UE-NGAP-ID
@namssob pointed out that
According to 38.413 8.6.1.2
When the NG-RAN node has received from the radio interface the 5G-S-TMSI IE, it shall include it in the INITIAL UE MESSAGE messagev
the pcap file
expected:
|
[Service Reject received with cause [UE_IDENTITY_CANNOT_BE_DERIVED_FROM_NETWORK]
|
https://api.github.com/repos/free5gc/free5gc/issues/258/comments
| 4 |
2021-10-05T11:49:15Z
|
2021-10-10T13:22:27Z
|
https://github.com/free5gc/free5gc/issues/258
| 1,016,228,509 | 258 |
[
"free5gc",
"free5gc"
] |
Hello Sir,
I tried the new free5gc version.
I did as in the video and I have issues with the SMF in the demo the UE does not connect to the server as in the images below.
For the first UE, the server did not respond and the second UE was not subscribed.
I added both of them through the web counsel.
Could you please help me to solve the problem?
<img width="976" alt="Screenshot 2021-10-03 at 3 26 42 pm" src="https://user-images.githubusercontent.com/34620715/135772463-a20c82da-0a3f-4c8e-9134-038abada287f.png">
<img width="995" alt="Screenshot 2021-10-03 at 3 26 59 pm" src="https://user-images.githubusercontent.com/34620715/135772465-bab737dd-5eea-4c15-877d-6c568bdefd9c.png">
<img width="954" alt="Screenshot 2021-10-03 at 3 27 17 pm" src="https://user-images.githubusercontent.com/34620715/135772466-09776499-b35a-4a60-a4e7-cb2b2833e065.png">
<img width="962" alt="Screenshot 2021-10-03 at 3 33 16 pm" src="https://user-images.githubusercontent.com/34620715/135772467-9726ba32-0880-41c6-abc6-647ec3116bf1.png">
<img width="990" alt="Screenshot 2021-10-03 at 3 33 27 pm" src="https://user-images.githubusercontent.com/34620715/135772469-7fb484cb-649a-4ed0-a3f7-4911df83dec7.png">
Thanks,
Noor Mohammedali.
|
Issue with DNN if the number of the DNN more than 9
|
https://api.github.com/repos/free5gc/free5gc/issues/256/comments
| 7 |
2021-10-03T21:47:20Z
|
2023-08-14T05:37:53Z
|
https://github.com/free5gc/free5gc/issues/256
| 1,014,550,580 | 256 |
[
"free5gc",
"free5gc"
] |
Hello,
I have installed latest version of free5gc on ubuntu system and trying to create BDT Policy but fails.
--------terminal output-----
root@zs22:~# curl -X 'POST' -H 'Accept: application/json' -H 'Content-Type: application/json' -i 'http://127.0.0.7:8000/npcf-bdtpolicycontrol/v1/bdtpolicies' --data '{"aspId": "123456","desTimeInt": {"startTime": "2021-08-12 16:09:25","stopTime": "2021-08-12 16:10:27"},"numOfUes": 5,"volPerUe": {"duration": 60,"totalVolume": 50,"downlinkVolume": 30,"uplinkVolume": 20},"suppFeat": "123456"}'
HTTP/1.1 500 Internal Server Error
Date: Mon, 20 Sep 2021 20:22:11 GMT
Content-Length: 0
root@zs22:~#
root@zs22:~#
root@zs22:~# curl -X 'POST' -H 'Accept: application/json' -H 'Content-Type: application/json' -i 'http://127.0.0.7:8000/npcf-bdtpolicycontrol/v1/bdtpolicies' --data '{"bdtReqData": [{"aspId": "123456","desTimeInt": {"startTime": "2021-08-12 16:09:25","stopTime": "2021-08-12 16:10:27"},"numOfUes": 5,"volPerUe": {"duration": 60,"totalVolume": 50,"downlinkVolume": 30,"uplinkVolume": 20},"suppFeat": "123456"}]}'
HTTP/1.1 500 Internal Server Error
Date: Mon, 20 Sep 2021 20:22:21 GMT
Content-Length: 0
root@zs22:~#
root@zs22:~# curl -X 'POST' -H 'Accept: application/json' -H 'Content-Type: application/json' -i 'http://127.0.0.7:8000/npcf-bdtpolicycontrol/v1/bdtpolicies' --data '{"bdtReqData": {"aspId": "123456","desTimeInt": {"startTime": "2021-08-12 16:09:25","stopTime": "2021-08-12 16:10:27"},"numOfUes": 5,"volPerUe": {"duration": 60,"totalVolume": 50,"downlinkVolume": 30,"uplinkVolume": 20},"suppFeat": "123456"}}'
HTTP/1.1 500 Internal Server Error
Date: Mon, 20 Sep 2021 20:22:29 GMT
Content-Length: 0
root@zs22:~#
----------------------------LOGS----------------------------------------
2021-09-20T14:22:29-06:00 [INFO][PCF][Bdtpolicy] Handle CreateBDTPolicyContext
2021-09-20T14:22:29-06:00 [INFO][UDR][DRepo] Handle PolicyDataBdtDataGet
2021-09-20T14:22:29-06:00 [INFO][UDR][GIN] | 200 | 127.0.0.1 | GET | /nudr-dr/v1/policy-data/bdt-data |
2021/09/20 14:22:29 [Recovery] 2021/09/20 - 14:22:29 panic recovered:
interface conversion: interface {} is **models.BdtReqData, not *models.BdtReqData
/usr/local/go/src/runtime/iface.go:260 (0x409b71)
panicdottypeE: panic(&TypeAssertionError{iface, have, want, ""})
/root/free5gc/NFs/pcf/producer/bdtpolicy.go:200 (0xe02059)
createBDTPolicyContextProcedure: response.BdtReqData = deepcopy.Copy(&request).(*models.BdtReqData)
/root/free5gc/NFs/pcf/producer/bdtpolicy.go:151 (0xe00e66)
HandleCreateBDTPolicyContextRequest: header, response, problemDetails := createBDTPolicyContextProcedure(&requestMsg)
/root/free5gc/NFs/pcf/bdtpolicy/api_bdt_policies_collection_routers.go:56 (0xe2404e)
HTTPCreateBDTPolicy: rsp := producer.HandleCreateBDTPolicyContextRequest(req)
/root/go/pkg/mod/github.com/gin-gonic/[email protected]/context.go:161 (0x99faaa)
(*Context).Next: c.handlers[c.index](c)
/root/go/pkg/mod/github.com/gin-gonic/[email protected]/recovery.go:83 (0x9b1e7f)
RecoveryWithWriter.func1: c.Next()
/root/go/pkg/mod/github.com/gin-gonic/[email protected]/context.go:161 (0x99faaa)
(*Context).Next: c.handlers[c.index](c)
/root/go/pkg/mod/github.com/free5gc/[email protected]/logger_util.go:65 (0x9b3a2d)
ginToLogrus.func1: c.Next()
/root/go/pkg/mod/github.com/gin-gonic/[email protected]/context.go:161 (0x99faaa)
(*Context).Next: c.handlers[c.index](c)
/root/go/pkg/mod/github.com/gin-gonic/[email protected]/gin.go:409 (0x9a9555)
(*Engine).handleHTTPRequest: c.Next()
/root/go/pkg/mod/github.com/gin-gonic/[email protected]/gin.go:367 (0x9a8c6c)
(*Engine).ServeHTTP: engine.handleHTTPRequest(c)
/root/go/pkg/mod/golang.org/x/[email protected]/http2/h2c/h2c.go:98 (0xa0f049)
h2cHandler.ServeHTTP: s.Handler.ServeHTTP(w, r)
/usr/local/go/src/net/http/server.go:2807 (0x789e52)
serverHandler.ServeHTTP: handler.ServeHTTP(rw, req)
/usr/local/go/src/net/http/server.go:1895 (0x7857cb)
(*conn).serve: serverHandler{c.server}.ServeHTTP(w, w.req)
/usr/local/go/src/runtime/asm_amd64.s:1373 (0x463420)
goexit: BYTE $0x90 // NOP
2021-09-20T14:22:29-06:00 [INFO][PCF][GIN] | 500 | 127.0.0.1 | POST | /npcf-bdtpolicycontrol/v1/bdtpolicies |
-------------------------------------------------------------------------
kindly help me here.
|
Error while create BDTPolicy
|
https://api.github.com/repos/free5gc/free5gc/issues/255/comments
| 3 |
2021-09-20T20:24:24Z
|
2021-12-28T12:58:33Z
|
https://github.com/free5gc/free5gc/issues/255
| 1,001,370,354 | 255 |
[
"free5gc",
"free5gc"
] |
Please update the wiki installation section. On the official web-site (https://www.free5gc.org/installations/stage-3-free5gc-install/) there is the procedure for installation using kernel 5.4.x instead of 5.0.23.
Thnks
|
[Docs] Update Wiki - Installation
|
https://api.github.com/repos/free5gc/free5gc/issues/254/comments
| 1 |
2021-09-20T07:41:23Z
|
2021-09-23T01:03:18Z
|
https://github.com/free5gc/free5gc/issues/254
| 1,000,663,256 | 254 |
[
"free5gc",
"free5gc"
] |
## Description
When the UE requests a PDU session, the SMF crashes with an error "runtime error: invalid memory address or nil pointer dereference"
## To Reproduce
Steps to reproduce the behavior:
1. Use Free5GC v3.0.5
2. Change config of the amf, smf, upf and ue to change the dnn "internet" to "default". Example configs working and another version with the minimal changes to make it fail is attached in the zip below.
3. Populate the database with an entry for the UE, specifying the dnn default
3. Using UERANSIM, with the provided configurations, try to connect
## Expected behavior
The UE establishes a PDU session, or the core networks returns an understandable error
## Screenshots
UE provisioned in DB:
## Environment:
- free5GC Version: v3.0.5
- Kernel in control plane: 4.15.0-154-generic
- Kernel in user plane: 5.4.0-84-generic
- OS in control plane: Ubuntu 18.04.5 LTS
- OS in user plane: Ubuntu 20.04.1 LTS
- C compiler: gcc (Ubuntu 9.3.0-17ubuntu1~20.04) 9.3.0
- Go version: go version go1.14.4 linux/amd64
## Trace File
### Configuration Files
[config.zip](https://github.com/free5gc/free5gc/files/7155799/config.zip)
### Log File
SMF logs:
[smf.txt](https://github.com/free5gc/free5gc/files/7155873/smf.txt)
|
[Bugs] SMF crashes when connecting a UE using a different DNN from "internet"
|
https://api.github.com/repos/free5gc/free5gc/issues/253/comments
| 3 |
2021-09-13T16:32:37Z
|
2023-08-14T05:37:27Z
|
https://github.com/free5gc/free5gc/issues/253
| 995,095,047 | 253 |
[
"free5gc",
"free5gc"
] |
I met the following errors while running free5gc-docker-compose:
containers running order is like :
`Attaching to upfb, upf2, upf1, mongodb, nrf, webui, ausf, pcf, nssf, udr, smf, amf, udm, n3iwf
nrf | 2021/09/12 23:18:05 http2: server connection error from 10.100.200.9:46048: connection error: PROTOCOL_ERROR
`
|
[Bugs] http2: server connection error from .....: connection error: PROTOCOL_ERROR
|
https://api.github.com/repos/free5gc/free5gc/issues/252/comments
| 5 |
2021-09-12T23:19:58Z
|
2023-07-07T01:11:38Z
|
https://github.com/free5gc/free5gc/issues/252
| 994,310,854 | 252 |
[
"free5gc",
"free5gc"
] |
I try to integrate Free5GC with Katana-slice Manager. I don't know if there any interfaces I can use to combine theses two things.
Thank you in advance!
|
[Feat] Interface for Katana-slice Manager
|
https://api.github.com/repos/free5gc/free5gc/issues/251/comments
| 1 |
2021-09-08T14:41:08Z
|
2023-06-21T05:29:11Z
|
https://github.com/free5gc/free5gc/issues/251
| 991,217,086 | 251 |
[
"free5gc",
"free5gc"
] |
## Describe the bug
SMF panics during the construction of PDU Session Establishment Accept message
if DNN of provisioned data in mongodb is different from any of SMF, UPF or UE.
## To Reproduce
1. Set same DNN to smfcfg.conf, upfcfg.yaml and UE.
2. Provision different DNN for the UE to mongodb.
3. Make the UE register to free5GC and try to establish a PDU session.
You can see the following log output which represents SMF paniced.
```
2021-09-06T19:45:15+09:00 [ERRO][SMF][PduSess] (/home/l5gc/free5gc/NFs/smf/producer/pdu_session.go:180 github.com/free5gc/smf/producer.HandlePDUSessionSMContextCreate)
2021/09/06 19:45:15 [Recovery] 2021/09/06 - 19:45:15 panic recovered:
runtime error: invalid memory address or nil pointer dereference
/usr/local/go/src/runtime/panic.go:212 (0x44d5a9)
panicmem: panic(memoryError)
/usr/local/go/src/runtime/signal_unix.go:695 (0x44d3f8)
sigpanic: panicmem()
/home/l5gc/free5gc/NFs/smf/producer/callback.go:71 (0x12b015d)
ApplySmPolicyFromDecision: for id, sessRuleModel := range decision.SessRules {
/home/l5gc/free5gc/NFs/smf/producer/pdu_session.go:187 (0x12b1fb4)
HandlePDUSessionSMContextCreate: if err := ApplySmPolicyFromDecision(smContext, smPolicyDecision); err != nil {
```
## Expected behavior
SMF does not panic, and send PDU Session Reject message back.
## Environment (please complete the following information):
- free5GC Version: 3.0.5
- OS: Ubuntu 18.04
- Kernel version: 5.0.0-23-generic
- go version go1.14.4 linux/amd64
## Pull Request
[Pull Request](https://github.com/free5gc/smf/pull/28) for the fix.
Note:To compile this PR, you need to merge [Pull Request in the nas library](https://github.com/free5gc/nas/pull/8) and [Pull Request in the openapi library](https://github.com/free5gc/openapi/pull/2).
|
[Bugs] PDU Session Establishment panic without DNN for subscription
|
https://api.github.com/repos/free5gc/free5gc/issues/246/comments
| 1 |
2021-09-07T08:11:36Z
|
2021-09-13T04:24:42Z
|
https://github.com/free5gc/free5gc/issues/246
| 989,714,345 | 246 |
[
"free5gc",
"free5gc"
] |
## Describe the bug
AMF does not send a modify sm-context request to SMF when a Service Request (mo-data) is received.
## To Reproduce
1. Make a UE in CM-IDLE state.
2. Send a Initial UE Message, Service Request (mo-data) from the UE
```go
func TestPaging(t *testing.T) {
:
// send NAS Service Request
pdu = nasTestpacket.GetServiceRequest(nasMessage.ServiceTypeData) ★
pdu, err = test.EncodeNasPduWithSecurity(ue, pdu, nas.SecurityHeaderTypeIntegrityProtectedAndCiphered, true, false)
```
3. Check the pcap. You can't see the following packet;
`POST /nsmf-pdusession/v1/sm-contexts/urn:uuid:.../modify`
## Expected behavior
AMF send a modify sm-context request to SMF when a Service Request (mo-data) is received, and the UE becomes to be able to send uplink data traffic afterwards.
## Environment (please complete the following information):
- free5GC Version: 3.0.5
- OS: Ubuntu 18.04
- Kernel version: 5.0.0-23-generic
- go version go1.14.4 linux/amd64
## Pull Request
[Pull Request](https://github.com/free5gc/amf/pull/38) for the fix.
|
[Bugs] The sm-context is not modified when a service request (mo-data) is received
|
https://api.github.com/repos/free5gc/free5gc/issues/238/comments
| 1 |
2021-08-31T11:36:50Z
|
2021-09-01T09:01:28Z
|
https://github.com/free5gc/free5gc/issues/238
| 983,760,507 | 238 |
[
"free5gc",
"free5gc"
] |
## Describe the bug
Multiple packets bufferd during the UE is in CM-IDLE state are packed in GTP-U and sent as one packet to the UE after the UE goes in CM-CONNECTED state.
## To Reproduce
1. Add a sleep to `TestPaging()` in `registration_test.go` in order to wait UPF buffers downlink packets to the UE.
```go
// Registration -> Pdu Session Establishment -> AN Release due to UE Idle -> Send downlink data
func TestPaging(t *testing.T) {
:
// UE is CM-IDLE now
time.Sleep(60 * time.Second) ★Add
```
2. Run `test.sh -o TestPaging` and wait the following log is output.
```
[INFO][AMF][NGAP][127.0.0.1:9487] Release UE[imsi-2089300007487] Context : N2 Connection Release
```
3. Ping to the UE from UPFns.
```
# ip netns exec UPFns ping -c 5 60.60.0.1
```
4. Check the pcap after the test is finished.
## Expected behavior
Each packet in the buffer is sent to the UE as one GTP-U packet separately.
## Environment (please complete the following information):
- free5GC Version: 3.0.5
- OS: Ubuntu 18.04
- Kernel version: 5.0.0-23-generic
- go version go1.14.4 linux/amd64
## Pull Request
[Pull Request](https://github.com/free5gc/upf/pull/37) for the fix.
|
[Bugs] UPF send multiple buffered packet by 1 GTP packet when paging
|
https://api.github.com/repos/free5gc/free5gc/issues/237/comments
| 1 |
2021-08-31T11:14:32Z
|
2021-09-08T08:27:53Z
|
https://github.com/free5gc/free5gc/issues/237
| 983,740,517 | 237 |
[
"free5gc",
"free5gc"
] |
**If the design issue template is not followed, the issue might be closed.**
<!-- Remove above warning line while reporting the issue -->
## Issue Description
### What's the version are you using
Please describe the free5GC version using. If possible, the package, device or emulator description will be very supportive.
v3.0.5
### Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem might be. For instance, I'm always frustrated when [...]
Not a problem, but a new funtion request which will be more useful in 5g industry
### Describe the solution you'd like
A clear and concise description of what is expected. How can the requested feature be used to approach the problem it's supposed to solve?
I would like to support UE can have multiple QoS follows in same or different PDU session for QoS differentiation purpose.
### Describe alternatives/workarounds you've considered
A clear and concise description of any alternative solutions or features considering. It will be highly appreciated, if existing workaround knowledge can be shared.
Not found other solution from mobile network view.
### Additional context
Please include additional context or screenshots on feature request.
## Issue Template Checklist
<!-- Please answer the questions below. If not the issue might be disregarded. -->
### If willing to resolve an issue by submitting Pull request, please consider the points below.
<!-- free5GC will be happy to welcome first contributor’s, in order to broaden the community. -->
- [ ] Yes, I have the time and I know how to start.
- [ x] Yes, I have the time but I don't know how to start, I would need guidance.
- [ ] No, I don't have the time, although I believe I could do it if I had the time...
- [ ] No, I don't have the time and I wouldn't even know how to start.
|
[Feat] Support multipe QoS Flows in default PDU or multiple PDU sessions per UE
|
https://api.github.com/repos/free5gc/free5gc/issues/235/comments
| 2 |
2021-08-25T06:09:57Z
|
2023-07-21T08:46:48Z
|
https://github.com/free5gc/free5gc/issues/235
| 978,757,098 | 235 |
[
"free5gc",
"free5gc"
] |
## Describe the bug
when start ausf, nrf show :
2021/08/23 06:49:46 http2: server connection error from 10.42.0.138:55432: connection error: PROTOCOL_ERROR
2021-08-23T06:49:46Z [INFO][NRF][MGMT] Handle NFRegisterRequest
2021-08-23T06:49:46Z [INFO][NRF][MGMT] urilist create
2021-08-23T06:49:46Z [INFO][NRF][MGMT] Create NF Profile
2021-08-23T06:49:46Z [INFO][NRF][MGMT] Location header: http://0.0.0.0:30001/nnrf-nfm/v1/nf-instances/478249b1-aff9-46eb-b886-074ae5babda4
2021-08-23T06:49:46Z [INFO][NRF][GIN] | 201 | 10.42.0.138 | PUT | /nnrf-nfm/v1/nf-instances/478249b1-aff9-46eb-b886-074ae5babda4 |
## To Reproduce
Steps to reproduce the behavior:
1. Change config '...'
nrfcfg.yaml:
configuration:
MongoDBName: free5gc # database name in MongoDB
MongoDBUrl: mongodb://mongodb-svc:27017 # a valid URL of the mongodb
sbi: # Service-based interface information
scheme: http # the protocol for sbi (http or https)
registerIPv4: 0.0.0.0 #127.0.0.10 # IP used to serve NFs or register to another NRF
bindingIPv4: 0.0.0.0 #127.0.0.10 # IP used to bind the service
port: 30001 # port used to bind the service
ausfcfg.yaml:
configuration:
sbi: # Service-based interface information
scheme: http # the protocol for sbi (http or https)
registerIPv4: 0.0.0.0 #127.0.0.9 # IP used to register to NRF
bindingIPv4: 0.0.0.0 #127.0.0.9 # IP used to bind the service
port: 30005 # Port used to bind the service
serviceNameList: # the SBI services provided by this AUSF, refer to TS 29.509
- nausf-auth # Nausf_UEAuthentication service
nrfUri: http://free5gc-nrf-svc:30001 # a valid URI of NRF
3. Run command './nrf ./ausf'
## Expected behavior
nrf log:
2021-08-23T07:42:55Z [INFO][NRF][DSCV] Handle NFDiscoveryRequest
2021-08-23T07:42:55Z [INFO][NRF][GIN] | 200 | 10.42.0.137 | GET | /nnrf-disc/v1/nf-instances?requester-nf-type=AMF&target-nf-type=AUSF |
amf log:
2021-08-23T07:42:55Z [ERRO][AMF][GMM][AMF_UE_NGAP_ID:6] Nausf_UEAU Authenticate Request Error: server no response
2021-08-23T07:42:55Z [INFO][AMF][GMM][AMF_UE_NGAP_ID:6] Handle Authentication Error
2021-08-23T07:42:55Z [INFO][AMF][GMM][AMF_UE_NGAP_ID:6] Send Registration Reject
2021-08-23T07:42:55Z [INFO][AMF][NGAP][10.42.0.1:57798][AMF_UE_NGAP_ID:6] Send Downlink Nas Transport
## Environment (please complete the following information):
- free5GC Version: [e.g. v3.0.5]
- OS: [ Ubuntu 18.04 Server]
- Kernel version: [e.g. 5.0.0.23-generic]
- go version: [1.14.4 linux/amd64]
- k3s version: [v1.19.7+k3s1]
|
connection error: PROTOCOL_ERROR
|
https://api.github.com/repos/free5gc/free5gc/issues/234/comments
| 1 |
2021-08-23T08:07:34Z
|
2021-09-10T19:43:12Z
|
https://github.com/free5gc/free5gc/issues/234
| 976,750,722 | 234 |
[
"free5gc",
"free5gc"
] |
Hi @free5gc-org @mariakagi @aligungr and everyone
I wrote a very simple configuration that uses free5GC and UERANSIM to select the nearby UPF according to the connected gNodeB.
https://github.com/s5uishida/free5gc_ueransim_nearby_upf_sample_config
This feature was added to free5GC last month, so this time I compared the configurations for Open5GS and free5GC simply.
Best regards,
--Shigeru
|
FYI: Sample configuration - Select nearby UPF according to the connected gNodeB
|
https://api.github.com/repos/free5gc/free5gc/issues/231/comments
| 2 |
2021-08-17T14:08:55Z
|
2021-10-01T09:16:14Z
|
https://github.com/free5gc/free5gc/issues/231
| 972,731,868 | 231 |
[
"free5gc",
"free5gc"
] |
I added the iptables command mentioned in https://githubmemory.com/repo/free5gc/free5gc-compose/issues/26?page=1
The ping still failed.
Thank you for your time and help!
|
[Bugs]UERAN container ping failed
|
https://api.github.com/repos/free5gc/free5gc/issues/230/comments
| 4 |
2021-08-16T19:34:03Z
|
2021-09-02T18:12:27Z
|
https://github.com/free5gc/free5gc/issues/230
| 972,039,964 | 230 |
[
"free5gc",
"free5gc"
] |
## Issue Description
Some UPF uses APN instead DNN as such PDR session request will not be possible.
### What's the version are you using
https://github.com/travelping/upg-vpp/issues/118#issuecomment-834344277 - This issue can shed more light on this, it is not specific to a free5gc version rather it is about having the feature
### Is your feature request related to a problem? Please describe.
This will make it easier to use other UPF with Free5gc control plane components.
### Describe the solution you'd like
Place a conditional flag in the UPF section of SMF configuration to use APN instead of DNN format for that particular UPF.
Maybe something like the snapshot below:
### Describe alternatives/workarounds you've considered
I don't think there is an existing workaround yet on Free5gc side
### Additional context
None
## Issue Template Checklist
<!-- Please answer the questions below. If not the issue might be disregarded. -->
### If willing to resolve an issue by submitting Pull request, please consider the points below.
<!-- free5GC will be happy to welcome first contributor’s, in order to broaden the community. -->
- [ ] Yes, I have the time and I know how to start.
- [x] Yes, I have the time but I don't know how to start, I would need guidance. _**- I don't have much programming background but I am open to suggestions on where this can be changed in the code**_
- [ ] No, I don't have the time, although I believe I could do it if I had the time...
- [ ] No, I don't have the time and I wouldn't even know how to start.
|
[Feat] Add Network Instance IE encoding Option In SMF
|
https://api.github.com/repos/free5gc/free5gc/issues/228/comments
| 2 |
2021-08-03T06:47:01Z
|
2021-09-07T08:39:12Z
|
https://github.com/free5gc/free5gc/issues/228
| 958,786,155 | 228 |
[
"free5gc",
"free5gc"
] |
Bigger buffers don’t fix the issue. They prevent UPF from crashing, but UEs are still not registering after some time.
_Originally posted by @srac0 in https://github.com/free5gc/free5gc/issues/218#issuecomment-891006152_
|
[Bugs] PFCP Session Establishment Request not handled by UPF
|
https://api.github.com/repos/free5gc/free5gc/issues/227/comments
| 1 |
2021-08-02T13:02:29Z
|
2021-09-13T13:08:24Z
|
https://github.com/free5gc/free5gc/issues/227
| 958,120,421 | 227 |
[
"free5gc",
"free5gc"
] |
## Issue Description
### What's the version are you using
v3.0.5
### Is your feature request related to a problem? Please describe.
SMF selects UPF by DNN and S-NSSAI, without considering the location of gNB.
IF UE connects to gNB in Area1, SMF should select UPF in Area1.
### Describe the solution you'd like
#### Preparation
1. Locate AMF, SMF and UPF in each area.
2. Set same "locality" to amfcfg.yaml and smfcfg.yaml in each area.
#### Execution
1. SMF registers NF Profile with the locality
2. AMF selects SMF by Nnrf_NFDiscovery_Request including preferred-locality
### Pull Request
Pull Request for the feature.
- [free5gc](https://github.com/free5gc/free5gc/pull/225)
- [amf](https://github.com/free5gc/amf/pull/37)
- [smf](https://github.com/free5gc/smf/pull/25)
### Describe alternatives/workarounds you've considered
None
### Additional context
None
|
[Feat] UPF selection according to connected gNB
|
https://api.github.com/repos/free5gc/free5gc/issues/226/comments
| 4 |
2021-07-27T02:20:02Z
|
2021-07-28T03:23:59Z
|
https://github.com/free5gc/free5gc/issues/226
| 953,437,319 | 226 |
[
"free5gc",
"free5gc"
] |
**Describe the bug**
AMF is not implemented with NIA3 and NEA3 Integrity and ciphering algorithms
I installed the free5GC Stage 3 Installation Guide from this link " https://www.free5gc.org/installations/stage-3/" by following the link "https://www.free5gc.org/stage-3-videos/create-ubuntu-machine/" and the UERANSIM from " https://github.com/aligungr/UERANSIM/wiki/Installation".
I am trying to test all Ciphering and integrity algorithms but found its not implemented yet.
Is there anything i am missing to configure or support is not really present
i can see the below prints on 5GCore console
In 5GCore NEA3 Ciphering algorithm not supported
2021-07-09T03:21:30Z [INFO][AMF][NGAP][10.22.109.75:36574][AMF_UE_NGAP_ID:1] Uplink NAS Transport (RAN UE NGAP ID: 1)
2021-07-09T03:21:30Z [ERRO][AMF][NAS][AMF_UE_NGAP_ID:1][SUPI:imsi-208930000000001] Encrypt error: NEA3 not implement yet.
2021-07-09T03:21:36Z [WARN][AMF][GMM][AMF_UE_NGAP_ID:1][SUPI:imsi-208930000000001] T3560 expires, retransmit Security Mode Command (retry: 3)
In 5GCore NIA3 integrity not supported.
2021-07-09T03:28:18Z [INFO][AMF][GMM][AMF_UE_NGAP_ID:1][SUPI:imsi-208930000000001] Send Security Mode Command
2021-07-09T03:28:18Z [ERRO][AMF][GMM][AMF_UE_NGAP_ID:1][SUPI:imsi-208930000000001] MAC calcuate error: NIA3 not implement yet.
please let me know if logs required.
UERANSIM free5gc-ue.yaml config :
integrity:
IA1: true
IA2: true
IA3: true
ciphering:
EA0: true
EA1: true
EA2: true
EA3: true
5GCore AMF config :
security: # NAS security parameters
integrityOrder: # the priority of integrity algorithms
- NIA3
# - NIA0
cipheringOrder: # the priority of ciphering algorithms
- NEA3
# - NEA2
**To Reproduce**
Configure NIA3 or NEA3 algo in amfcfg.yaml config file
Attach UE
**Expected behavior**
Core should support NIA3 or NEA3 Integrity and ciphering algorithsm
**Environment (please complete the following information):**
free5GC Version: 3.0.5
OS: Ubuntu 20.04
Kernel version: 5.4.0-77-generic
go version go1.14.4 linux/amd64
|
[Bugs]Support of NIA3 and NEA3 Integrity and Ciphering algorithms
|
https://api.github.com/repos/free5gc/free5gc/issues/224/comments
| 1 |
2021-07-26T07:46:53Z
|
2023-07-21T08:45:53Z
|
https://github.com/free5gc/free5gc/issues/224
| 952,607,983 | 224 |
[
"free5gc",
"free5gc"
] |
Hello,
I installed the free5GC Stage 3 Installation Guide from this link " https://www.free5gc.org/installations/stage-3/" by fallow this link "https://www.free5gc.org/stage-3-videos/create-ubuntu-machine/" and the UERANSIM from " https://github.com/aligungr/UERANSIM/wiki/Installation".
At the beginning, everything went fine, I installed the 5G core and UERANSIM as well in different VMs.
For the 5G VM when i run the test some time fail and some time pass. Dose anyone have an idea why that's happened.
In the UERANSIM VM, the UE connect to the RAN and RAN connect the free5GC VM.
but the UE lost acconection, as i see i had a connection failure.
<img width="1440" alt="Screenshot 2021-07-22 at 8 23 30 pm" src="https://user-images.githubusercontent.com/34620715/126722679-f4ccb0d0-c19e-4d2c-8ca3-c637789f5893.png">
<img width="1440" alt="Screenshot 2021-07-22 at 8 23 49 pm" src="https://user-images.githubusercontent.com/34620715/126722690-1925c9e0-e983-49a3-b0bf-afd2f3efbda9.png">
And when i try to run the RAN and the UE again i get this issues..
<img width="1440" alt="Screenshot 2021-07-23 at 12 55 07 am" src="https://user-images.githubusercontent.com/34620715/126723031-2a19d0c7-f852-46d1-ac44-8164d013f039.png">
[free5gc .:run.sh log file.zip](https://github.com/free5gc/free5gc/files/6865981/free5gc.run.sh.log.file.zip)
I new to 5G and Go lang.
I have another question, now in my AMF, SMF and NSSF, I have S-NSSAIs information, How can I attach the UE information including the S-NSSAIs in the test file to do the registration and authentication and send PDU session.
For example, we have a user connect to a 5G network, I want to make this user connect to slice 1 and slice 2 and if the user chooses to connect to another slice or service, My system will accept the connection. and I will know the slice id, slice number, slice service for each user in my 5G network.
Do i need to add these information to the registration_test.go file. In the registration_test.go, I can see the imsi information and servingPlmnId and the S-NSSAIs in PDU section.
In this case, I could avoid any error happened in UERANSIM VM. I tried to use the Webconsole but with it just sent the registration part.
Thanks,
Noor
|
UE Register to 5G core
|
https://api.github.com/repos/free5gc/free5gc/issues/223/comments
| 3 |
2021-07-23T00:24:21Z
|
2021-10-02T18:51:35Z
|
https://github.com/free5gc/free5gc/issues/223
| 951,154,656 | 223 |
[
"free5gc",
"free5gc"
] |
## Describe the bug
Regarding the "plmn-id" parameter in Nudm or so on SBI messages, it is specified explicitly as json format.
However, your AMF encodes it as plain string format. (ex. plmn-id=00101; here, MCC is "001" and "MNC is "01".)
## To Reproduce
Steps to reproduce the behavior:
1. Start NRF, NSSF, AUSF, PCF and UDM Simulators over my own Tester 1.
2. Start AMF, SMF and UPF NFs of your free5GC S/W.
3. Start UE/gNB Simulator over my own Tester 2.
4. From the UE/gNB Simulator, start "Initial Registration" Test Case.
5. Monitor and check the N1/N2 and SBI messages through WireShark
## Expected behavior
The "plmn-id" parameter should be encoded as like as plmn-id={"mcc"="001", "mnc"="01"}.
## Environment (please complete the following information):
- free5GC Version: v.3.0.5
- OS: Ubuntu 18.04.5 LTS
- Kernel version: 5.0.0-23
- go version: go1.14.4
### PCAP File
[1-1_20210625144656_SBI-TestCase-Ph1.1.zip](https://github.com/free5gc/free5gc/files/6845049/1-1_20210625144656_SBI-TestCase-Ph1.1.zip)
- Log No 1265 : Nsdm-GetData (NSSAI) Header
- Log No 1300 : Nsdm-GetData (AM) Header
- Log No 1310 : Nsdm-GetData (SmfSelectData) Header
- Log No 1320 : Nsdm-GetData (UeContextInSmfData) Header
## System architecture (Option)
## Additional context
------TS29503_Nudm_SDM.yaml; Line#49---------------------------------
- name: plmn-id
in: query
description: serving PLMN ID
content:
application/json:
schema:
$ref: 'TS29571_CommonData.yaml#/components/schemas/PlmnId'
------TS29571_CommonData.yaml; Line#975---------------------------------
PlmnId:
type: object
properties:
mcc:
$ref: '#/components/schemas/Mcc'
mnc:
$ref: '#/components/schemas/Mnc'
required:
- mcc
- mnc
|
[Bugs] "plmn-id" parameter in Nudm or so on SBI messages
|
https://api.github.com/repos/free5gc/free5gc/issues/221/comments
| 3 |
2021-07-20T02:55:43Z
|
2021-10-27T06:49:29Z
|
https://github.com/free5gc/free5gc/issues/221
| 948,199,919 | 221 |
[
"free5gc",
"free5gc"
] |
## Describe the bug
Regarding the "supiORsuci" (IMSI-based SUPI) parameter in Nausf or so on SBI messages, its MSIN field should be encoded with BCD format. (For more details, please refer Section C.4 in TS33.501.) However, AMF encodes it as plain string format.
## To Reproduce
Steps to reproduce the behavior:
1. Start NRF, NSSF, AUSF, PCF and UDM Simulators over my own Tester 1.
2. Start AMF, SMF and UPF NFs of free5GC S/W.
3. Start UE/gNB Simulator over my own Tester 2.
4. From the UE/gNB Simulator, start "Initial Registration" Test Case.
5. Monitor and check the N1/N2 and SBI messages through WireShark
## Expected behavior
MSIN field should be encoded with BCD format, not plain string format.
## Environment (please complete the following information):
- free5GC Version: [e.g. v3.0.100]
- OS: [e.g. Ubuntu 200.04 Server]
- Kernel version: [e.g. 5.200.0-0-generic]
- go version: [e.g. 1.10.0 linux/amd64]
- c compiler version (Option): [e.g. gcc version 1.1.0]
### PCAP File
[1-1_20210625144656_SBI-TestCase-Ph1.1.zip](https://github.com/free5gc/free5gc/files/6845049/1-1_20210625144656_SBI-TestCase-Ph1.1.zip)
- Log No 1138 : 5GMM-RegistrationRequest Message
- Log No 1163 : Nausf-UEAU-AuthenticateRequest Contents
## System architecture (Option)
|
[Bugs] MSIN format in the "supiORsuci" (IMSI-based SUPI) parameter
|
https://api.github.com/repos/free5gc/free5gc/issues/220/comments
| 15 |
2021-07-20T02:45:47Z
|
2023-07-17T09:00:01Z
|
https://github.com/free5gc/free5gc/issues/220
| 948,196,237 | 220 |
[
"free5gc",
"free5gc"
] |
## Describe the bug
The problem occurrs in authentication synchronization. The UE sends its SQN value as part of resynchronization process. But the UDM does not use these values in authentication request and results in authentication reject
## To Reproduce
Steps to reproduce the behavior:
1. Start all NFs + gNB
2. Start UE with SQN stored as 0b604a81eca8, f1e8a523a36d and 16f3b3f70fc2. See the 3GPP TS 35.208 version 15.0.0 Release 15 for more test data
3. Run registration
4. Get authentication reject after receive two authentication request request and authentication failure(synch failure)
## Expected behavior
In resynchronization process UDM should get valid SQN(48bits) from UE and update it to UDM.
## Root cause
In udm/producer/generate_auth_data.go. The variable SqnMAx limit the range of SQN accepted by UDM.
```
const (
SqnMAx int64 = 0x7FFFFFFFFFF
)
```
## Environment :
- free5GC Version: 3.0.5
- OS: Ubuntu 18.04
- Kernel version: 5.0.0-23-generic
- go version: go version go1.14.4 linux/amd64
## Trace File
### PCAP File
[free5gc_synch_failure.zip](https://github.com/free5gc/free5gc/files/6825706/free5gc_synch_failure.zip)
## Pull request
https://github.com/free5gc/udm/pull/5 for the fix.
|
[Bugs] Synch Failure with some SQNs
|
https://api.github.com/repos/free5gc/free5gc/issues/219/comments
| 7 |
2021-07-15T19:26:39Z
|
2021-08-18T15:04:21Z
|
https://github.com/free5gc/free5gc/issues/219
| 945,687,283 | 219 |
[
"free5gc",
"free5gc"
] |
## Describe the bug
When registering many UE’s (with UERANSIM), some are not registered. This is not systematic, but this always happens after some UE’s rebooting. Unregistered UEs are due to unhandled PFCP Session Establishment Request. These requests can be seen in PCAP traces but not UPF’s log.
## To Reproduce
Steps to reproduce the behavior:
1. Start all NFs + gNB.
2. Start many UEs (e.g. 30).
3. Restart some UEs.
## Expected behavior
All UEs should be registered, and UPF should handle all PFCP Session Establishment Requests.
## Environment (please complete the following information):
- free5GC Version: last version (b1172c3)
- OS: Ubuntu server 20.04
- Kernel version: 5.4.0-77-generic
- go version: 1.14.4
- UERANSIM version: v3.2.2
## Trace File
### PCAP File
[pcap.zip](https://github.com/free5gc/free5gc/files/6800188/pcap.zip)
### Log File
```log
UERANSIM v3.2.2
[info] UE switches to state [MM-DEREGISTERED/PLMN-SEARCH]
[debug] New signal detected for cell[1], total [1] cells in coverage
[info] Selected cell plmn[208/93] tac[1] category[SUITABLE]
[info] UE switches to state [MM-DEREGISTERED/PS]
[info] UE switches to state [MM-DEREGISTERED/NORMAL-SERVICE]
[debug] Initial registration required due to [MM-DEREG-NORMAL-SERVICE]
[debug] UAC access attempt is allowed for identity[0], category[MO_sig]
[debug] Sending Initial Registration
[info] UE switches to state [MM-REGISTER-INITIATED]
[debug] Sending RRC Setup Request
[info] RRC connection established
[info] UE switches to state [RRC-CONNECTED]
[info] UE switches to state [CM-CONNECTED]
[debug] Authentication Request received
[debug] Sending Authentication Failure due to SQN out of range
[debug] Authentication Request received
[debug] Security Mode Command received
[debug] Selected integrity[2] ciphering[0]
[debug] Registration accept received
[info] UE switches to state [MM-REGISTERED/NORMAL-SERVICE]
[debug] Sending Registration Complete
[info] Initial Registration is successful
[debug] Sending PDU Session Establishment Request
[debug] UAC access attempt is allowed for identity[0], category[MO_sig]
[warning] Retransmitting PDU Session Establishment Request due to T3580 expiry
[debug] UAC access attempt is allowed for identity[0], category[MO_sig]
[warning] Retransmitting PDU Session Establishment Request due to T3580 expiry
[debug] UAC access attempt is allowed for identity[0], category[MO_sig]
```
[log.zip](https://github.com/free5gc/free5gc/files/6800190/log.zip)
|
[Bugs] PFCP Session Establishment Request not handled by UPF
|
https://api.github.com/repos/free5gc/free5gc/issues/218/comments
| 2 |
2021-07-12T09:48:50Z
|
2023-07-03T09:39:31Z
|
https://github.com/free5gc/free5gc/issues/218
| 941,873,526 | 218 |
[
"free5gc",
"free5gc"
] |
## Describe the bug
There is a defect in handling Bufblk in PFCP message processing, causing segmentation fault due to NULL pointer access and memory leak due to insufficient post-processing on error.
## To Reproduce
A NULL pointer access is performed by continuing the processing without determining the result of Bufblk alloc.
1. Reduce `MAX_NUM_OF_BUFBLK_POOL` in `lib/utlt/src/utlt_buff.c` as follows:
```diff
- #define MAX_NUM_OF_BUFBLK_POOL 256
+ #define MAX_NUM_OF_BUFBLK_POOL 5
```
2. Build UPF
3. run `test.sh TestRegistration`
```
console.log
:
2021-07-02T19:21:46+09:00 [INFO][UPF][Util] [PFCP] Handle PFCP session modification request
2021-07-02T19:21:46+09:00 [WARN][UPF][Util] Pool is empty
2021-07-02T19:21:46+09:00 [ERRO][UPF][Util] The pool of Buffer is empty
./test.sh: line 79: 7157 Segmentation fault ${EXEC_UPFNS} ./bin/free5gc-upfd -f config/upfcfg.test.yaml
2021-07-02T19:21:48+09:00 [INFO][NRF][Init] Terminating NRF...
```
In addition, if `PfcpXactUpdateTX()` returns STATUS_ERROR when `BufblkAlloc()` or `BufblkBuf()` failed by bufBlkPool depletion,
bufBlk already allocated before calling `PfcpXactUpdateTX()` doesn't free. This causes memory leak.
## Expected behavior
- Don't cause segmentation fault when `BufblkAlloc()` failed.
- Don't cause segmentation fault when `BufblkBuf()` failed.
- Free already allocated bufBlk when `PfcpXactUpdateTx()` returns STATUS_ERROR caused by failure of `BufblkAlloc()` or `BufblkBuf()`.
## Environment (please complete the following information):
- free5GC Version: 3.0.5
- OS: Ubuntu 18.04
- Kernel version: 5.0.0-23-generic
- go version go1.14.4 linux/amd64
## Pull Request
[Pull Request](https://github.com/free5gc/upf/pull/29) for the fix.
|
[Bugs] An abend may result in a bufBlk leak or NULL access.
|
https://api.github.com/repos/free5gc/free5gc/issues/217/comments
| 1 |
2021-07-06T07:25:58Z
|
2021-07-06T15:47:36Z
|
https://github.com/free5gc/free5gc/issues/217
| 937,597,941 | 217 |
[
"free5gc",
"free5gc"
] |
## Describe the bug
UE never be able to reconnect to AMF after the AMF reboots in trouble without sending Deregistration to the UE.
Status of all UEs are initialized if AMF reboots, but UEs don't know it.
AMF will drop Service Request message from UEs that consider themselves to be registered with the AMF because the AMF has already forgotten the UEs.
UEs will keep trying to send Service Request since AMF doesn't respond anything.
## To Reproduce
The registered UE will use TestRegistration to simulate an image reconnected by ServiceRequest after an AMF (5GC) reboot.
1. Change `TestRegistration` in `test/registration_test.go` as follows:
In order to reproduce such situation, insert "NAS Service Request" procedure before "NAS Registration Request" in `TestRegistration()` in `test/registration_test.go`.
```diff
--- a/test/registration_test.go
+++ b/test/registration_test.go
@@ -109,6 +109,34 @@ func TestRegistration(t *testing.T) {
assert.NotNil(t, getData)
}
+ // send NAS Service Request
+ pdu := nasTestpacket.GetServiceRequest(nasMessage.ServiceTypeData)
+ pdu, err = test.EncodeNasPduWithSecurity(ue, pdu, nas.SecurityHeaderTypeIntegrityProtectedAndCiphered, true, false)
+ assert.Nil(t, err)
+ sendMsg, err = test.GetInitialUEMessage(ue.RanUeNgapId, pdu, "fe0000000001")
+ assert.Nil(t, err)
+ _, err = conn.Write(sendMsg)
+ assert.Nil(t, err)
+
+ // receive NAS Service Request
+ n, err = conn.Read(recvMsg)
+ assert.Nil(t, err)
+ _, err = ngap.Decoder(recvMsg[:n])
+ assert.Nil(t, err)
+ // receive UE Context Release Command
+ n, err = conn.Read(recvMsg)
+ assert.Nil(t, err)
+ _, err = ngap.Decoder(recvMsg[:n])
+ assert.Nil(t, err)
+
+ // send ngap UE Context Release Complete
+ sendMsg, err = test.GetUEContextReleaseComplete(ue.AmfUeNgapId, ue.RanUeNgapId, nil)
+ assert.Nil(t, err)
+ _, err = conn.Write(sendMsg)
+ assert.Nil(t, err)
+ ue.AmfUeNgapId = 2
+ time.Sleep(1 * time.Second)
+
// send InitialUeMessage(Registration Request)(imsi-2089300007487)
mobileIdentity5GS := nasType.MobileIdentity5GS{
Len: 12, // suci
@@ -140,7 +168,7 @@ func TestRegistration(t *testing.T) {
resStat := ue.DeriveRESstarAndSetKey(ue.AuthenticationSubs, rand[:], "5G:mnc093.mcc208.3gppnetwork.org")
// send NAS Authentication Response
- pdu := nasTestpacket.GetAuthenticationResponse(resStat, "")
+ pdu = nasTestpacket.GetAuthenticationResponse(resStat, "")
sendMsg, err = test.GetUplinkNASTransport(ue.AmfUeNgapId, ue.RanUeNgapId, pdu)
assert.Nil(t, err)
_, err = conn.Write(sendMsg)
```
2. Run `test.sh TestRegistration`.
```
2021-07-05T13:47:36+09:00 [INFO][AMF][NGAP][127.0.0.1:9487] Handle NG Setup request
2021-07-05T13:47:36+09:00 [INFO][AMF][NGAP][127.0.0.1:9487] Send NG-Setup response
2021-07-05T13:47:36+09:00 [INFO][AMF][NGAP][127.0.0.1:9487] Handle Initial UE Message
2021-07-05T13:47:36+09:00 [WARN][AMF][NGAP][127.0.0.1:9487][AMF_UE_NGAP_ID:1] Unknown UE [GUTI: 20893cafe0000000001]
2021-07-05T13:47:36+09:00 [WARN][NAS][Security] Integrity NIA0 is emergency.
2021-07-05T13:47:36+09:00 [WARN][AMF][NAS][AMF_UE_NGAP_ID:1] NAS MAC verification failed(received: 0x7e11b57e, expected: 0x00000000)
2021-07-05T13:47:36+09:00 [ERRO][AMF][GMM][AMF_UE_NGAP_ID:1] state mismatch: receieve gmm message[message type 0x4c] at Deregistered state
```
## Expected behavior
AMF returns NAS Service Reject (cause #9) if receiving NAS Service Request from a UE which is expected RM-REGISTERED and CM-IDLE by the AMF.
```
1. UE/gNB -> 5GC InitialUEMessage, Service request
2. UE/gNB <- 5GC DownlinkNASTransport, Service reject (UE identity cannot be derived by the network)
3. gNB <- 5GC UEContextReleaseCommand
4. gNB -> 5GC UEContextReleaseComplete
5. UE/gNB -> 5GC InitialUEMessage, Registration request
6. UE/gNB <- 5GC DownlinkNASTransport, Authentication request
:
```
## Environment (please complete the following information):
- free5GC Version: 3.0.5
- OS: Ubuntu 18.04
- Kernel version: 5.0.0-23-generic
- go version go1.14.4 linux/amd64
## Pull Request
[Pull Request](https://github.com/free5gc/amf/pull/32) for the fix.
|
[Bugs] The UE will not reconnect if the AMF reboots without sending a deregistration to the UE.
|
https://api.github.com/repos/free5gc/free5gc/issues/216/comments
| 1 |
2021-07-06T02:41:26Z
|
2021-07-06T15:48:14Z
|
https://github.com/free5gc/free5gc/issues/216
| 937,468,913 | 216 |
[
"free5gc",
"free5gc"
] |
## Describe the bug
If AMF restarts after establishment of 5G NAS security context with ue, AMF fails to decode Registration Request in NAS message container IE of Registration Request(GUTI) and stops Registration Procecure.
## To Reproduce
### Preparation
1. Change AMF config
see [Configuration File](#Configuration-File)
2. Change `TestGUTIRegistrationRequest` in `test/registration_test.go` as follows:
```go
// New UE
// ue := test.NewRanUeContext("imsi-2089300007487", 1, security.AlgCiphering128NEA0, security.AlgIntegrity128NIA2)
ue := test.NewRanUeContext("imsi-2089300007487", 1, security.AlgCiphering128NEA2, security.AlgIntegrity128NIA2)
```
After sending ngap UE Context Release Complete, set sleep to restart AMF and connect AMF
```go
// restart AMF (kill and restart AMF process from another window)
fmt.Println("###")
time.Sleep(30 * time.Second)
// close Connection
// RAN connect to AMF
// send NGSetupRequest Msg
// receive NGSetupResponse Msg
```
Change Registration Request in Second Registration (Register with GUTI)
according to TS 24.501 v15.06 4.4.6 Protection of initial NAS signalling messages b) 1)
``` go
innerRegistrationRequest := nasTestpacket.GetRegistrationRequest(nasMessage.RegistrationType5GSInitialRegistration,
GUTI5GS, nil, ue.GetUESecurityCapability(), ue.Get5GMMCapability(), nil, nil)
// encrypt inner Registration Request
m := nas.NewMessage()
err = m.PlainNasDecode(&innerRegistrationRequest)
require.Nil(t, err)
payload, err := m.PlainNasEncode()
require.Nil(t, err)
err = security.NASEncrypt(ue.CipheringAlg, ue.KnasEnc, ue.ULCount.Get(), security.Bearer3GPP,
security.DirectionUplink, payload)
require.Nil(t, err)
// add security header to outer Registration Request
registrationRequest = nasTestpacket.GetRegistrationRequest(nasMessage.RegistrationType5GSInitialRegistration,
GUTI5GS, nil, ueSecurityCapability, nil, payload, nil)
// change ue.CipheringAlg to set security header, not to encrypt outer Registration Request
ue.CipheringAlg = security.AlgCiphering128NEA0
pdu, err = test.EncodeNasPduWithSecurity(ue, registrationRequest, nas.SecurityHeaderTypeIntegrityProtected, true, false)
// restore ue.CipheringAlg
ue.CipheringAlg = security.AlgCiphering128NEA2
require.Nil(t, err)
sendMsg, err = test.GetInitialUEMessage(ue.RanUeNgapId, pdu, "")
require.Nil(t, err)
_, err = conn.Write(sendMsg)
require.Nil(t, err)
```
### Execution
1. Start NFs as separeted process and start test with "-args noinit" option.
2. Restart AMF after establishment of 5G NAS security context.
3. Send Registration Request with GUTI from UE.
## Expected behavior
Authenticate subscriber before processing the registration request.
(TS 24.501 v15.06 4.4.4.3 Integrity checking of NAS signalling messages in the AMF)
## Environment (please complete the following information):
- free5GC Version: v3.0.5
- OS: Ubuntu 18.04.4 LTS
- Kernel version: 5.0.0-23-generic
- go version: 1.14.4
## Trace File
### Configuration File
amfcfg.yaml
```yaml
security: # NAS security parameters
cipheringOrder: # the priority of ciphering algorithms
- NEA2
```
### PCAP File
[free5gc_fails-to-decode-reg.pcap.gz](https://github.com/free5gc/free5gc/files/6753114/free5gc_fails-to-decode-reg.pcap.gz)
### Log File
```
2021-07-02T02:27:50Z [INFO][AMF][NGAP][127.0.0.1:9487] Handle Initial UE Message
2021-07-02T02:27:50Z [WARN][NAS][Security] Integrity NIA0 is emergency.
2021-07-02T02:27:50Z [WARN][AMF][NAS][AMF_UE_NGAP_ID:1] NAS MAC verification failed(received: 0x6f572c2e, expected: 0x00000000)
2021-07-02T02:27:50Z [INFO][AMF][GMM][AMF_UE_NGAP_ID:1] Handle Registration Request
2021-07-02T02:27:50Z [ERRO][AMF][GMM] NAS decode Fail: MsgType[31] doesn't exist in GMM Message
```
## Pull Request
[Pull Request](https://github.com/free5gc/amf/pull/35) for the fix.
|
[Bugs] AMF fails to decode Registration Request(GUTI) after restart
|
https://api.github.com/repos/free5gc/free5gc/issues/215/comments
| 3 |
2021-07-02T08:15:28Z
|
2021-07-14T04:45:27Z
|
https://github.com/free5gc/free5gc/issues/215
| 935,532,817 | 215 |
[
"free5gc",
"free5gc"
] |
## Describe the bug
AMF panics when it receives a UE Context Release Complete NGAP message while it has already received a UE Context Release Complete NGAP message related to the same UE.
Some gNBs don't send UEContextReleaseComplete to UEContextReleaseCommand immediately and they might send InitialUEMessage before sending UEContextReleaseComplete.
## To Reproduce
1. RegistrationRequest ~ PDUsessionResourceSetupResponse
2. gNB -> 5GC UEContextReleaseRequest
3. gNB <- 5GC UEContextReleaseCommand
4. UE/gNB -> 5GC InitialUEmessage/ServiceRequest
5. UE/gNB <- 5GC InitialContextSetupRequest/ServiceAccept
6. gNB -> 5GC InitialContextSetupResponse
7. gNB -> 5GC UEContextReleaseRequest
8. gNB <- 5GC UEContextReleaseCommand
9. gNB -> 5GC UEContextReleaseComplete(Response to 3.UEContextReleaseCommand)
10. gNB -> 5GC UEContextReleaseComplete(Response to 8.UEContextReleaseCommand)
#### AMF panic log
```
2021-06-30T19:54:51+09:00 [INFO][AMF][NGAP][127.0.0.1:9487] Handle UE Context Release Complete (/home/ubuntu/devel305/free5gc/NFs/amf/ngap/handler.go:413 github.com/free5gc/amf/ngap.HandleUEContextReleaseComplete)
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x10 pc=0x10658bc]
goroutine 307 [running]:
github.com/free5gc/amf/ngap.HandleUEContextReleaseComplete(0xc00063a000, 0xc000d605c0)
/home/ubuntu/devel305/free5gc/NFs/amf/ngap/handler.go:532 +0x32c
github.com/free5gc/amf/ngap.Dispatch(0x1c058a0, 0xc00057dd40, 0xc000d64000, 0x26, 0x2000)
/home/ubuntu/devel305/free5gc/NFs/amf/ngap/dispatcher.go:103 +0x841
github.com/free5gc/amf/ngap/service.handleConnection(0xc00057dd40, 0x2000, 0x179e548, 0x179e550)
/home/ubuntu/devel305/free5gc/NFs/amf/ngap/service/service.go:204 +0x700
created by github.com/free5gc/amf/ngap/service.listenAndServe
/home/ubuntu/devel305/free5gc/NFs/amf/ngap/service/service.go:136 +0xc43
```
## Expected behavior
No panic.
## Root cause
`amfUe.ReleaseCause[ran.AnType]` is set to nil when AMF receives UEContextReleaseComplete.
Therefore, AMF panics by nil pointer dereference of `amfUe.ReleaseCause[ran.AnType]` when receiving next UEContextReleaseComplete.
## Environment (please complete the following information):
- free5GC Version: 3.0.5
- OS: Ubuntu 18.04
- Kernel version: 5.0.0-23-generic
- go version: go version go1.14.4 linux/amd64
## Pull Request
[Pull Request](https://github.com/free5gc/amf/pull/34) for the fix.
|
[Bugs]AMF panics when receiving UeContextReleaseComplete continuously
|
https://api.github.com/repos/free5gc/free5gc/issues/214/comments
| 6 |
2021-07-02T07:36:49Z
|
2021-07-08T04:49:23Z
|
https://github.com/free5gc/free5gc/issues/214
| 935,504,272 | 214 |
[
"free5gc",
"free5gc"
] |
## Describe the bug
AMF panics when it receives a Deregistration Request NAS message while it has already received a UE Context Release Complete NGAP message related to the same UE.
Some gNBs don't send UEContextReleaseComplete to UEContextReleaseCommand immediately and they might send InitialUEMessage before sending UEContextReleaseComplete.
## To Reproduce
1. RegistrationRequest ~ PDUsessionResourceSetupResponse
2. gNB -> 5GC UEContextReleaseRequest
3. gNB <- 5GC UEContextReleaseCommand
4. UE/gNB -> 5GC InitialUEmessage/ServiceRequest
5. UE/gNB <- 5GC InitialContextSetupRequest/ServiceAccept
6. gNB -> 5GC InitialContextSetupResponse
7. gNB -> 5GC UEContextReleaseComplete(Response to 3.UEContextReleaseCommand)
8. UE/gNB -> 5GC UplinkNAS/DeregistrationRequest
#### AMF panic log
```
2021-06-30T19:23:34+09:00 [INFO][AMF][GMM][AMF_UE_NGAP_ID:1][SUPI:imsi-2089300007487] Handle Deregistration Request(UE Originating) (/home/ubuntu/devel305/free5gc/NFs/amf/gmm/handler.go:2155 github.com/free5gc/amf/gmm.HandleDeregistrationRequest)
2021-06-30T19:23:34+09:00 [INFO][SMF][PduSess] Recieve Release SM Context Request (/home/ubuntu/devel305/free5gc/NFs/smf/pdusession/api_individual_sm_context.go:28 github.com/free5gc/smf/pdusession.HTTPReleaseSmContext)
2021-06-30T19:23:34+09:00 [INFO][SMF][PduSess] In HandlePDUSessionSMContextRelease (/home/ubuntu/devel305/free5gc/NFs/smf/producer/pdu_session.go:913 github.com/free5gc/smf/producer.HandlePDUSessionSMContextRelease)
2021-06-30T19:23:34+09:00 [TRAC][SMF][CTX] SMContextState Change State: PFCPModification (/home/ubuntu/devel305/free5gc/NFs/smf/producer/pdu_session.go:1031 github.com/free5gc/smf/producer.releaseTunnel)
2021-06-30T19:23:34+09:00 [INFO][UPF][Util] [PFCP] Handle PFCP session deletion request
2021-06-30T19:23:34+09:00 [INFO][UPF][Util] [PFCP] Session Deletion Response
2021-06-30T19:23:34+09:00 [INFO][LIB][PFCP] Remove Request Transaction [6] (/home/ubuntu/go/pkg/mod/github.com/free5gc/[email protected]/pfcpUdp/udp.go:160 github.com/free5gc/pfcp/pfcpUdp.(*PfcpServer).RemoveTransaction)
2021-06-30T19:23:34+09:00 [INFO][SMF][PFCP] Handle PFCP Session Deletion Response (/home/ubuntu/devel305/free5gc/NFs/smf/pfcp/handler/handler.go:275 github.com/free5gc/smf/pfcp/handler.HandlePfcpSessionDeletionResponse)
2021-06-30T19:23:34+09:00 [TRAC][SMF][PduSess] Delete pending pfcp response: UPF IP [10.200.200.101] (/home/ubuntu/devel305/free5gc/NFs/smf/pfcp/handler/handler.go:296 github.com/free5gc/smf/pfcp/handler.HandlePfcpSessionDeletionResponse)
2021-06-30T19:23:34+09:00 [INFO][SMF][PFCP] PFCP Session Deletion Success[1] (/home/ubuntu/devel305/free5gc/NFs/smf/pfcp/handler/handler.go:302 github.com/free5gc/smf/pfcp/handler.HandlePfcpSessionDeletionResponse)
2021-06-30T19:23:34+09:00 [TRAC][SMF][CTX] In case SessionReleaseSuccess (/home/ubuntu/devel305/free5gc/NFs/smf/producer/pdu_session.go:963 github.com/free5gc/smf/producer.HandlePDUSessionSMContextRelease)
2021-06-30T19:23:34+09:00 [TRAC][SMF][CTX] SMContextState Change State: InActivePending (/home/ubuntu/devel305/free5gc/NFs/smf/producer/pdu_session.go:965 github.com/free5gc/smf/producer.HandlePDUSessionSMContextRelease)
2021-06-30T19:23:34+09:00 [INFO][SMF][PduSess] UE[imsi-2089300007487] PDUSessionID[10] Release IP[60.60.0.1] (/home/ubuntu/devel305/free5gc/NFs/smf/context/sm_context.go:189 github.com/free5gc/smf/context.RemoveSMContext)
2021-06-30T19:23:34+09:00 [DEBU][SMF][CTX] [{60.60.0.2 - 60.60.255.254}->{60.60.0.1 - 60.60.0.1}] (/home/ubuntu/devel305/free5gc/NFs/smf/context/user_plane_information.go:647 github.com/free5gc/smf/context.(*UeIPPool).release)
2021-06-30T19:23:34+09:00 [INFO][SMF][GIN] | 204 | 127.0.0.1 | POST | /nsmf-pdusession/v1/sm-contexts/urn:uuid:bb95b73b-0b49-4512-bc32-6944428eb262/release | (/home/ubuntu/devel305/free5gc/lib/logger_util/logger_util.go:157 github.com/free5gc/logger_util.ginToLogrus.func1)
2021-06-30T19:23:34+09:00 [INFO][PCF][Ampolicy] Handle AM Policy Association Delete
2021-06-30T19:23:34+09:00 [INFO][PCF][GIN] | 204 | 127.0.0.1 | DELETE | /npcf-am-policy-control/v1/policies/imsi-2089300007487-1 |
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x90 pc=0x10250c6]
goroutine 309 [running]:
github.com/free5gc/amf/gmm/message.SendDeregistrationAccept(0x0)
/home/ubuntu/devel305/free5gc/NFs/amf/gmm/message/send.go:240 +0x26
github.com/free5gc/amf/gmm.HandleDeregistrationRequest(0xc0000dd600, 0x173171b, 0xb, 0xc00051d290, 0x1, 0xc00047b0e0)
/home/ubuntu/devel305/free5gc/NFs/amf/gmm/handler.go:2194 +0xb86
github.com/free5gc/amf/gmm.DeregisteredInitiated(0xc000623d10, 0x1731999, 0xb, 0xc00051da70)
/home/ubuntu/devel305/free5gc/NFs/amf/gmm/sm.go:364 +0x68d
github.com/free5gc/fsm.(*FSM).SendEvent(0xc000438280, 0xc000623d10, 0x174f4cf, 0x19, 0xc00051da70, 0x11, 0x19)
/home/ubuntu/go/pkg/mod/github.com/free5gc/[email protected]/fsm.go:100 +0x2f4
github.com/free5gc/amf/gmm.Registered(0xc000623d10, 0x1731a5f, 0xb, 0xc00051d7a0)
/home/ubuntu/devel305/free5gc/NFs/amf/gmm/sm.go:99 +0x6e6
github.com/free5gc/fsm.(*FSM).SendEvent(0xc000438280, 0xc000623d10, 0x1731a5f, 0xb, 0xc00051d7a0, 0x1bac9f0, 0x14894e0)
/home/ubuntu/go/pkg/mod/github.com/free5gc/[email protected]/fsm.go:95 +0x22d
github.com/free5gc/amf/nas.Dispatch(0xc0000dd600, 0x173171b, 0xb, 0x2e, 0xc00098b1c0, 0x19, 0xc00098b1c0)
/home/ubuntu/devel305/free5gc/NFs/amf/nas/dispatch.go:27 +0x29e
github.com/free5gc/amf/nas.HandleNAS(0xc0005c9680, 0x2e, 0xc0001a5c20, 0x18, 0x20)
/home/ubuntu/devel305/free5gc/NFs/amf/nas/handler.go:39 +0x178
github.com/free5gc/amf/ngap.HandleUplinkNasTransport(0xc00056be00, 0xc00098a0a0)
/home/ubuntu/devel305/free5gc/NFs/amf/ngap/handler.go:234 +0x701
github.com/free5gc/amf/ngap.Dispatch(0x1c01ea0, 0xc000523490, 0xc0008f0000, 0x43, 0x2000)
/home/ubuntu/devel305/free5gc/NFs/amf/ngap/dispatcher.go:49 +0x527
github.com/free5gc/amf/ngap/service.handleConnection(0xc000523490, 0x2000, 0x179b538, 0x179b540)
/home/ubuntu/devel305/free5gc/NFs/amf/ngap/service/service.go:204 +0x700
created by github.com/free5gc/amf/ngap/service.listenAndServe
/home/ubuntu/devel305/free5gc/NFs/amf/ngap/service/service.go:136 +0xc43
```
## Expected behavior
No panic.
## Root cause
AMF panics caused by nil pointer dereference in SendDeregistrationAccept() since ue.AmfUe is made nil at receiving UecontextReleaseComplete.
```go
func SendDeregistrationAccept(ue *context.RanUe) {
ue.AmfUe.GmmLog.Info("Send Deregistration Accept") ★
}
```
So, We have fixed AMF not to send DeregistrationAccept if UE State is CM-IDLE.
AMF should not call SendDeregistrationAccept() when the UE is in CM-IDLE.
The issue [#199](https://github.com/free5gc/free5gc/issues/199) is similar problem.
## Environment (please complete the following information):
- free5GC Version: 3.0.5
- OS: Ubuntu 18.04
- Kernel version: 5.0.0-23-generic
- go version: go version go1.14.4 linux/amd64
## Pull Request
[Pull Request](https://github.com/free5gc/amf/pull/33) for the fix.
This fixes the issue [#199](https://github.com/free5gc/free5gc/issues/199), too.
|
[Bugs]AMF panics on receiving Deregistration Request after receiving UEContextReleaseComplete
|
https://api.github.com/repos/free5gc/free5gc/issues/213/comments
| 1 |
2021-07-02T07:33:24Z
|
2021-08-18T15:12:57Z
|
https://github.com/free5gc/free5gc/issues/213
| 935,502,025 | 213 |
[
"free5gc",
"free5gc"
] |
## Issue Description
free5GC v3.0.5 discards NGAP messages that contain extended value of ENUMERATED type in it.
Some gNBs send such messages.
### What's the version are you using
free5GC v3.0.5
### Is your feature request related to a problem? Please describe.
It's a problem. UE cannot access via such gNBs.
### Describe the solution you'd like
I've sent PR's:
- https://github.com/free5gc/aper/pull/1
- https://github.com/free5gc/ngap/pull/4
### Describe alternatives/workarounds you've considered
Nothing
### Additional context
Nothing
## Issue Template Checklist
### If willing to resolve an issue by submitting Pull request, please consider the points below.
- [x] Yes, I have the time and I know how to start.
- [ ] Yes, I have the time but I don't know how to start, I would need guidance.
- [ ] No, I don't have the time, although I believe I could do it if I had the time...
- [ ] No, I don't have the time and I wouldn't even know how to start.
|
[Feat] Handle extended value of ENUMERATED type in NGAP messages
|
https://api.github.com/repos/free5gc/free5gc/issues/212/comments
| 1 |
2021-06-30T11:32:45Z
|
2021-07-06T15:48:40Z
|
https://github.com/free5gc/free5gc/issues/212
| 933,601,805 | 212 |
[
"free5gc",
"free5gc"
] |
## Documentation request
How to differentiate UE traffic outside the UPF, since the UPF NATs all the traffic being generated by the UEs.
Hi,
I need to differentiate the network traffic being generated by multiple UEs but when I capture the traffic through tcpdump, going to the DN, I can see that it's all natted, therefore unable to understand who-generated-what. Do you have any kind of suggestion on how to solve my issue?
My final goal is to map the generated traffic by the UEs to the emulated SIM card present within the HSS database; this way I can perform whitelist policing.
|
[Docs] Differentiate/Identify traffic flows from UEs
|
https://api.github.com/repos/free5gc/free5gc/issues/211/comments
| 6 |
2021-06-22T06:38:06Z
|
2021-08-27T06:41:58Z
|
https://github.com/free5gc/free5gc/issues/211
| 926,884,410 | 211 |
[
"free5gc",
"free5gc"
] |
Hi,
I'm creating a NWu tool (similar to my SWu tool (https://github.com/fasferraz/SWu-IKEv2) but for 5G), and i'm doing tests with your free5GC core.
I notice that the AMF is creating the integrity and ciphering keys for NAS with bearerId/NAS connection identifier 0x01 when sending the NAS to the N3IWF. According to 33.501, for non3GPP accesses the NAS connection identifier should by 0x02 Check 33.501 7.2.1 for example.
NAS connection identifier 0x01 should be used for 3GPP accesses.
I didn't reach the point of calculating N3IWF key, but 33.501 also states the same:
"The AMF upon reception of the NAS SMC Complete from the UE or upon success of integrity protection
verification, initiates the NGAP procedure to set up the AN context. AMF shall compute the N3IWF key,
KN3IWF, using the uplink NAS COUNT associated with NAS connection identifier "0x02" as defined in Annex
A.9 for the establishment of the IPsec SA between the UE and the N3IWF and shall include it in the NGAP
Initial Context Setup Request sent to the N3IWF."
I've also another question about AN Parameters, mainly the NSSAI, where you are coding each S-NSSAI with 6 bytes. I think this should be coded with 5 bytes (when you don't have any mapped HPLMN SST/SD).
24.502 states that "When the AN-parameter type field indicates the requested NSSAI, the AN-parameter value field is coded according to value part of NSSAI information element as specified in subclause 9.11.3.37 of 3GPP TS 24.501 [4]."
Subclause 9.11.3.37 of 24.501 states that inside NSSAI IEI the "S-NSSAI value is coded as the length and value part of S-NSSAI information element as specified in subclause 9.11.2.8 starting with the second octet."
So if you are starting in second octet, you should exclude the S-NSSAI IEI:
S-NSSAI octet 2 is the length (1 bytes), and then you have SST (1 byte) and SD (3 bytes). So a total of 1+1+3=5 bytes.
if you check a normal 5G registration trace (Registration Accept message you will notice that the NAS have each S-NSSAI inside the allowed NSSAI IEI coded with 5 bytes.
|
[Bugs] For Non3GPP accesses N3IWF/AMF is not creating integrity and ciphering keys with NAS connection identifier "0x02"
|
https://api.github.com/repos/free5gc/free5gc/issues/210/comments
| 9 |
2021-06-21T10:42:37Z
|
2021-10-29T13:59:49Z
|
https://github.com/free5gc/free5gc/issues/210
| 926,082,345 | 210 |
[
"free5gc",
"free5gc"
] |
## Describe the bug
got a working free5gc docker-compose setup that I've adapted to K8s
used aligungr's UERANSIM
- invoking the gNB - OK
- when invoking the UE - errors appear on the gNB console and connection to AMF fails
I've opened a UERANSIM issue (https://github.com/aligungr/UERANSIM/issues/346) and aligungr stated that it's an AMF failure.
attached
CONSOLE output from: UERANSIM (gNB, UE)
CONSOLE output of all free5gc components
SNIFFER capture on UERANSIM site (showing the SCTP and RLS communication)
CONFIG files of all free5gc components
[RLS.SCTP.zip](https://github.com/free5gc/free5gc/files/6653784/RLS.SCTP.zip)
[UERANSIM console.zip](https://github.com/free5gc/free5gc/files/6653785/UERANSIM.console.zip)
[free5gc console.zip](https://github.com/free5gc/free5gc/files/6653786/free5gc.console.zip)
## To Reproduce
Steps to reproduce the behavior:
1. set free5gc config as attached
2. run gNB
3. run UE
## Environment (please complete the following information):
- free5GC Version: don't know how to check this. I think the info appears in the console logs attached.
- OS & Kernel:
$ cat /etc/redhat-release
CentOS Linux release 8.3.2011
$ uname -a
Linux d50d-sa-app28 4.18.0-240.22.1.el8_3.x86_64 #1 SMP Thu Apr 8 19:01:30 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
|
AMF Fails after activation of UE
|
https://api.github.com/repos/free5gc/free5gc/issues/209/comments
| 5 |
2021-06-15T07:52:07Z
|
2021-07-21T09:01:46Z
|
https://github.com/free5gc/free5gc/issues/209
| 921,110,917 | 209 |
[
"free5gc",
"free5gc"
] |
The NAS layer of NGAP packet is encrypted. How not to encrypt it
|
[Bugs] The NAS layer of NGAP packet is encrypted. How not to encrypt it
|
https://api.github.com/repos/free5gc/free5gc/issues/208/comments
| 2 |
2021-05-26T10:01:52Z
|
2021-08-09T11:27:53Z
|
https://github.com/free5gc/free5gc/issues/208
| 902,133,717 | 208 |
[
"free5gc",
"free5gc"
] |
When testing, the following error appears?
cannot access '*sslkey.log': No such file or directory, and
in the testkeylog directory, all log files have a size of 0
|
[Bugs]How do I decrypt TLS
|
https://api.github.com/repos/free5gc/free5gc/issues/207/comments
| 2 |
2021-05-26T10:00:10Z
|
2021-08-27T06:38:18Z
|
https://github.com/free5gc/free5gc/issues/207
| 902,131,490 | 207 |
[
"free5gc",
"free5gc"
] |
## Issue Description
I want a UE which can connect to free5gc through n3iwf
### What's the version are you using
v3.0.5
### Is your feature request related to a problem? Please describe.
I tried using a UE from the other git repo but it has issues connecting to free5gc core.
### Describe the solution you'd like
I want a UE which can connect to free5gc
### Describe alternatives/workarounds you've considered
None
### Additional context
## Issue Template Checklist
### If willing to resolve an issue by submitting Pull request, please consider the points below.
<!-- free5GC will be happy to welcome first contributor’s, in order to broaden the community. -->
- [ ] Yes, I have the time and I know how to start.
- [X] Yes, I have the time but I don't know how to start, I would need guidance.
- [ ] No, I don't have the time, although I believe I could do it if I had the time...
- [ ] No, I don't have the time and I wouldn't even know how to start.
|
[Feat] UE to connect to n3iwf
|
https://api.github.com/repos/free5gc/free5gc/issues/206/comments
| 1 |
2021-05-26T01:13:05Z
|
2023-07-17T10:41:55Z
|
https://github.com/free5gc/free5gc/issues/206
| 901,590,004 | 206 |
[
"free5gc",
"free5gc"
] |
## Describe the bug
Unable to connect to n3iwf using a UE
## To Reproduce
Steps to reproduce the behavior:
1. I used the following UE "https://github.com/my5G/my5G-non3GPP-access", to connect to free5gc n3iwf
## Expected behavior
I expected the UE to connect to the free5gc but the connection hangs during marshalling.
## Screenshots
None
## Environment (please complete the following information):
- free5GC Version: [e.g. v3.0.5]
- OS: [e.g. Ubuntu 20.04]
Is there any UE free5gc suggests other than the Test script?
|
[Bugs] Unable to connect to n3iwf using a UE
|
https://api.github.com/repos/free5gc/free5gc/issues/205/comments
| 15 |
2021-05-26T01:10:03Z
|
2021-12-13T04:44:00Z
|
https://github.com/free5gc/free5gc/issues/205
| 901,587,716 | 205 |
[
"free5gc",
"free5gc"
] |
pcap: [NetWorkInstanceValue_Empty.gz](https://github.com/free5gc/free5gc/files/6524343/NetWorkInstanceValue_Empty.gz)
I noticed that during the sessionablishmentRequest the network instance field of the first create PDR is empty. Is it possible to initialize it? Thanks in advance
free5gc version: v3.0.5
|
[Bugs] Empty Network instance value during SessionEstablishment request
|
https://api.github.com/repos/free5gc/free5gc/issues/204/comments
| 3 |
2021-05-21T18:11:05Z
|
2021-07-30T07:30:01Z
|
https://github.com/free5gc/free5gc/issues/204
| 898,295,956 | 204 |
[
"free5gc",
"free5gc"
] |
## Describe the bug
The webconsole has UI for modification of an existing subscriber. But the functionality is not working. It doesn't fetch data from the mongoDB, but just uses default data (or previously filled data on same browser session).
## To Reproduce
Update existing subscriber's data.
## Expected behavior
Properly update subscriber's data
## Environment (please complete the following information):
- free5GC Version: 3.0.5
- OS: Ubuntu 18.04
- Kernel version: 5.0.0-23-generic
- go version: 1.15.8 linux/amd64
## Pull Request
[Pull Request](https://github.com/free5gc/webconsole/pull/9) for the fix.
|
[Bugs] Unable to modify a subscriber entry from webconsole
|
https://api.github.com/repos/free5gc/free5gc/issues/203/comments
| 0 |
2021-05-19T16:18:14Z
|
2023-07-21T07:44:45Z
|
https://github.com/free5gc/free5gc/issues/203
| 895,639,540 | 203 |
[
"free5gc",
"free5gc"
] |
## Describe the bug
The setting of ike exchange type in n3iwf/ike/message/types.go is inconsistent with the formal setting of ike protocol.
## To Reproduce
I tried to connected my phone with n3iwf through wi-fi. After setting the network config, n3iwf received the ike request from my phone. But n3iwf returned the warning "Unimplemented IKE message type, exchange type: 2". However, the setting of ike exchange type of n3iwf is 34-37, which is shown in screenshot 1. The standard setting of ike exchanged type from offical website is shown in screenshot 2. The ike exchange type of an ipsec request should be in 0-5.
## Screenshots
screenshot 1
screenshot 2
## Environment (please complete the following information):
- free5GC Version: v3.0.5
- OS: Ubuntu 18.04
- Kernel version: 5.0.0-23-generic
- go version: 1.14.4 linux/amd64
- wireless route: TL-WVR1200G
### PCAP File
Here are some pcap files. Src.ip is my phone. Det.ip is ikeBindAddress of n3iwf.
[pcaps.zip](https://github.com/free5gc/free5gc/files/6440769/pcaps.zip)
|
[Bugs] n3iwf ike exchange types are inconsistent with standard values
|
https://api.github.com/repos/free5gc/free5gc/issues/202/comments
| 5 |
2021-05-07T10:11:13Z
|
2021-05-27T02:20:03Z
|
https://github.com/free5gc/free5gc/issues/202
| 878,719,295 | 202 |
[
"free5gc",
"free5gc"
] |
## Describe the bug
UDM HTTP GET TS29503_Nudm_SDM.yaml:/{supi} method's parameter plmn-id is prone to injection
The following message
`GET','/nudm-sdm/v1/imsi-2089300007487?plmn-id=authentication-data/authentication-subscription?`
results into sending later HTTP GET /authentication-data/authentication-subscription/ message from UDR towards UDM.
This means that plmn-id parameter is injectable and not properly sanitized after receiving by UDM.
## To Reproduce
Steps to reproduce the behavior:
1. Run free5gc locally
2. Sent HTTP `GET','/nudm-sdm/v1/imsi-2089300007487?plmn-id=authentication-data/authentication-subscription?` to UDM 127.0.0.3:8000
## Expected behavior
plmn-id parameter should be sanitized by UDM.
## Screenshots
## Environment (please complete the following information):
- free5GC Version: [e.g. v3.0.5]
- OS: [e.g. Ubuntu 20.04.2 LTS]
- Kernel version: [e.g. 5.4.0-72-generic]
- go version: [e.g. 1.14.4 linux/amd64]
- c compiler version (Option): [e.g. gcc version 9.3.0]
## Trace File
_(can be provided if needed)_
### Configuration File
_(can be provided if needed)_
### PCAP File
_(can be provided if needed)_
### Log File
_(can be provided if needed)_
## System architecture (Option)
free5gc installed locally. All nodes running in single VM.
## Walkthrough (Option)
## Additional context
|
[Bugs] UDM HTTP GET TS29503_Nudm_SDM.yaml:/{supi} method's parameter plmn-id is prone to injection
|
https://api.github.com/repos/free5gc/free5gc/issues/201/comments
| 3 |
2021-05-05T10:25:12Z
|
2023-08-14T05:36:58Z
|
https://github.com/free5gc/free5gc/issues/201
| 876,302,913 | 201 |
[
"free5gc",
"free5gc"
] |
## Describe the bug
dataSetNames variable is not used in getSupiProcedure in the following code: https://github.com/free5gc/udm/blob/master/producer/subscriber_data_management.go#L183
This results in failure of the following operation GET operation from UDM:
`GET','/nudm-sdm/v1/imsi-2089300007487?plmn-id=20893&dataset-names=AM'`
Operation would fail, because the UDM tries to query all the data from UDR despite the dataset-names parameter specifies AM data only.
The UDM would return 404 DATA NOT FOUND, because it has not successfully retrieved trace data from UDR. And exited the whole procedure. Additionally this behavior is maybe not robust and it should return at least partial data.
## To Reproduce
Steps to reproduce the behavior:
1. Run free5gc locally
2. Sent HTTP `GET','/nudm-sdm/v1/imsi-2089300007487?plmn-id=20893&dataset-names=AM'` to UDM 127.0.0.3:8000
## Expected behavior
dataset-names parameter should be used and returned corresponding data.
## Screenshots
## Environment (please complete the following information):
- free5GC Version: [e.g. v3.0.5]
- OS: [e.g. Ubuntu 20.04.2 LTS]
- Kernel version: [e.g. 5.4.0-72-generic]
- go version: [e.g. 1.14.4 linux/amd64]
- c compiler version (Option): [e.g. gcc version 9.3.0]
## Trace File
### Configuration File
### PCAP File
### Log File
## System architecture (Option)
free5gc installed locally. All nodes running in single VM.
## Walkthrough (Option)
## Additional context
|
[Bugs] dataset-names parameter is not used in GetDataSets operation in UDM
|
https://api.github.com/repos/free5gc/free5gc/issues/200/comments
| 1 |
2021-04-28T09:06:01Z
|
2021-10-19T05:00:10Z
|
https://github.com/free5gc/free5gc/issues/200
| 869,716,143 | 200 |
[
"free5gc",
"free5gc"
] |
## Describe the bug
free5gc AMF panics and crashes when a UE context is released at the NGAP level by the gNodeB before the end of a NAS Registration, when NAS retransmissions with timer T3550 are ongoing. This is a standard situation that can happen in case of bad radio condition where a UE loses its radio connection while exchanging NAS signaling with the network.
Two different behavior are observed in case a UE context is released before the end of a NAS registration:
- when the UE context is released during the Authentication or Security Mode Control procedure, the AMF keeps sending NAS retransmission according to timer T3560. This is shown in the 1st pcap `free5gc_nas-reg-interrupt_crash.pcap.gz`.
- when the UE context is released after Security Mode Control but before completing the Registration, the AMF stops sending NAS retransmission according to timer T3550, but finally crashes. This is shown in the 2nd pcap `free5gc_nas-reg-interrupt_crash.pcap.gz` and the log extract below.
## To Reproduce
One way to reproduce is to modify a gNB / UE emulator, to release a UE context before the end of a NAS registration exchange. Another way is to use a real gNodeB and UE, and stops the radio radio connection or interface at the right timing before the NAS registration is completed.
## Expected behavior
free5gc AMF should not crash while processing a NGAP UE release procedure, whatever state and negotiation is ongoing at the NAS level, here with T3550 retransmission.
On another side, when a UE context is released, the AMF should stops sending NAS retransmission, as is it the case with T3560 retransmission.
## Environment (please complete the following information):
- free5GC Version: v3.0.5
- OS: Ubuntu 20.04
- Kernel version: 5.4.0-62-generic
- go version: go1.14.4 linux/amd64
## Trace File
### Configuration File
No specific configuration is required.
### PCAP File
When the UE context is released during T3560 retransmission, which keeps being sent:
[free5gc_nas-reg-interrupt_no-crash.pcap.gz](https://github.com/free5gc/free5gc/files/6382866/free5gc_nas-reg-interrupt_no-crash.pcap.gz)
When the UE context is released during T3550 retransmission, after which the AMF breaks:
[free5gc_nas-reg-interrupt_crash.pcap.gz](https://github.com/free5gc/free5gc/files/6382867/free5gc_nas-reg-interrupt_crash.pcap.gz)
### Log File
This is the AMF log extract when it crashes after releasing the UE context during T3550 retransmission:
```
2021-04-27T07:42:22Z [INFO][AMF][GMM][AMF_UE_NGAP_ID:14][SUPI:imsi-208690000000001] Send Registration Accept
2021-04-27T07:42:22Z [INFO][AMF][NGAP][172.27.128.253:38412][AMF_UE_NGAP_ID:14] Send Downlink Nas Transport
2021-04-27T07:42:28Z [WARN][AMF][GMM][AMF_UE_NGAP_ID:14][SUPI:imsi-208690000000001] T3550 expires, retransmit Registration Accept (retry: 1)
2021-04-27T07:42:28Z [INFO][AMF][NGAP][172.27.128.253:38412][AMF_UE_NGAP_ID:14] Send Downlink Nas Transport
2021-04-27T07:42:31Z [INFO][AMF][NGAP][172.27.128.253:38412] UE Context Release Request
2021-04-27T07:42:31Z [WARN][AMF][NGAP][172.27.128.253:38412] Cause RadioNetwork[21]
2021-04-27T07:42:31Z [INFO][AMF][NGAP][172.27.128.253:38412][AMF_UE_NGAP_ID:14] Ue Context in Non GMM-Registered
2021-04-27T07:42:31Z [INFO][AMF][NGAP][172.27.128.253:38412][AMF_UE_NGAP_ID:14] Send UE Context Release Command
2021-04-27T07:42:31Z [INFO][AMF][NGAP][172.27.128.253:38412] Handle UE Context Release Complete
2021-04-27T07:42:31Z [INFO][AMF][NGAP][172.27.128.253:38412] Release UE[imsi-208690000000001] Context : Release Ue Context
2021-04-27T07:42:34Z [WARN][AMF][GMM][AMF_UE_NGAP_ID:14][SUPI:imsi-208690000000001] [NAS] UE Context released, abort retransmission of Registration Accept
2021-04-27T07:42:40Z [WARN][AMF][GMM][AMF_UE_NGAP_ID:14][SUPI:imsi-208690000000001] [NAS] UE Context released, abort retransmission of Registration Accept
2021-04-27T07:42:46Z [WARN][AMF][GMM][AMF_UE_NGAP_ID:14][SUPI:imsi-208690000000001] [NAS] UE Context released, abort retransmission of Registration Accept
2021-04-27T07:42:52Z [WARN][AMF][GMM][AMF_UE_NGAP_ID:14][SUPI:imsi-208690000000001] T3550 Expires 4 times, abort retransmission of Registration Accept
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x100 pc=0xb9ee2d]
goroutine 247 [running]:
github.com/free5gc/amf/context.(*AmfUe).ClearRegistrationRequestData(...)
/home/p1sec/free5gc/NFs/amf/context/amf_ue.go:537
github.com/free5gc/amf/gmm/message.SendRegistrationAccept.func2()
/home/p1sec/free5gc/NFs/amf/gmm/message/send.go:285 +0x1ad
github.com/free5gc/amf/context.NewTimer.func1(0xc0000a9a00, 0xc00018f780, 0xc00018f740, 0xc0000c3450)
/home/p1sec/free5gc/NFs/amf/context/timer.go:39 +0x12d
created by github.com/free5gc/amf/context.NewTimer
/home/p1sec/free5gc/NFs/amf/context/timer.go:29 +0xd6
```
|
[Bugs] AMF breaks when a UE context is released before completing a NAS registration
|
https://api.github.com/repos/free5gc/free5gc/issues/199/comments
| 2 |
2021-04-27T07:58:23Z
|
2021-09-07T08:26:09Z
|
https://github.com/free5gc/free5gc/issues/199
| 868,574,780 | 199 |
[
"free5gc",
"free5gc"
] |
## Describe the bug
While testing the free5gc AMF for some NAS basic security features and fuzzing, I could trigger several crashes, while sending malformed NAS message. This means those issues are relatively exposed as they can be trigger by any 5G subscriber, in the principle.
Here, all memory issues due to mishandled NAS messages and IE structures are caught by the GO memory runtime, which protects the binary for potential exploitable cases.
## To Reproduce
No easy way to reproduce with available open-source tools. A modification of a gNB / UE emulator can be done to send malformed NAS messages.
## Expected behavior
An attacker could leverage this to cause excessive downtime and resource consumption against a pool of AMF. As much as possible, crashing the binary should be avoided when decoding subscriber's provided NAS signaling message. During the decoding process, verifications should be made to ensure the messages are valid ; in case of invalid or malformed messages, it should be dropped and the corresponding UE context should be deleted.
## Environment (please complete the following information):
- free5GC Version: v3.0.5
- OS: Ubuntu 20.04
- Kernel version: 5.4.0-62-generic
- go version: go1.14.4 linux/amd64
## Trace File
### Configuration File
No specific configuration is required.
### PCAP File
No specific pcap file is provided. If required, pcap corresponding some specific crashes can be provided.
### Log File
The following part lists some GOLANG stacktraces and corresponding malformed NAS and IE cases.
When a IE with TLV structure (type 4 or 6) is provided, but without the expected length, free5gc crashes, e.g. with an empty 5GSID:
```
2021-03-08T12:18:12Z [INFO][AMF][GMM][AMF_UE_NGAP_ID:31] Handle Registration Request
panic: runtime error: index out of range [0] with length 0
goroutine 7 [running]:
github.com/free5gc/amf/gmm.HandleRegistrationRequest(0xc00011b080, 0xe3727a, 0xb, 0xf, 0xc0002cd790, 0xc0004e3530, 0xb75bb2)
/home/p1sec/free5gc/NFs/amf/gmm/handler.go:425 +0x1969
github.com/free5gc/amf/gmm.DeRegistered(0xc0005a0600, 0xe373b9, 0xb, 0xc0005a0900)
/home/p1sec/free5gc/NFs/amf/gmm/sm.go:30 +0x3ef
github.com/free5gc/fsm.(*FSM).SendEvent(0xc00009ab20, 0xc0005a0600, 0xe373b9, 0xb, 0xc0005a0900, 0x0, 0xcb6ba0)
/home/p1sec/go/pkg/mod/github.com/free5gc/[email protected]/fsm.go:95 +0x22d
github.com/free5gc/amf/nas.Dispatch(0xc00011b080, 0xe3727a, 0xb, 0xf, 0xc00047f980, 0x20, 0xc00047f980)
/home/p1sec/free5gc/NFs/amf/nas/dispatch.go:22 +0x251
github.com/free5gc/amf/nas.HandleNAS(0xc0005d8a20, 0xf, 0xc000230f20, 0x11, 0x20)
/home/p1sec/free5gc/NFs/amf/nas/handler.go:39 +0x178
github.com/free5gc/amf/ngap.HandleInitialUEMessage(0xc0005a4080, 0xc000248ce0)
/home/p1sec/free5gc/NFs/amf/ngap/handler.go:1003 +0x4dc
github.com/free5gc/amf/ngap.Dispatch(0xfab8c0, 0xc00013fbe0, 0xc00029e000, 0x3c, 0x2000)
/home/p1sec/free5gc/NFs/amf/ngap/dispatcher.go:47 +0x3bb
github.com/free5gc/amf/ngap/service.handleConnection(0xc00013fbe0, 0x2000, 0xe6a348, 0xe6a350)
/home/p1sec/free5gc/NFs/amf/ngap/service/service.go:204 +0x700
created by github.com/free5gc/amf/ngap/service.listenAndServe
/home/p1sec/free5gc/NFs/amf/ngap/service/service.go:136 +0xc43
```
Or a UE Security Capabilities:
```
panic: runtime error: index out of range [1] with length 0
goroutine 49 [running]:
github.com/free5gc/nas/nasType.(*UESecurityCapability).GetIA2_128_5G(...)
/home/p1sec/go/pkg/mod/github.com/free5gc/[email protected]/nasType/NAS_UESecurityCapability.go:197
github.com/free5gc/amf/context.(*AmfUe).SelectSecurityAlg(0xc000118580, 0xc000385af8, 0x1, 0x8, 0xc000385b00, 0x1, 0x8)
/home/p1sec/free5gc/NFs/amf/context/amf_ue.go:501 +0x226
github.com/free5gc/amf/gmm.SecurityMode(0xc00006f710, 0xe37356, 0xb, 0xc0003e7200)
/home/p1sec/free5gc/NFs/amf/gmm/sm.go:221 +0xfb3
github.com/free5gc/fsm.(*FSM).SendEvent(0xc000386b50, 0xc00006f710, 0xe3efd6, 0x16, 0xc0003e7200, 0x0, 0x0)
/home/p1sec/go/pkg/mod/github.com/free5gc/[email protected]/fsm.go:100 +0x2f4
github.com/free5gc/amf/gmm.HandleAuthenticationResponse(0xc000118580, 0xe3727a, 0xb, 0xc0004e1b20, 0x1, 0x20)
/home/p1sec/free5gc/NFs/amf/gmm/handler.go:1900 +0xdd8
github.com/free5gc/amf/gmm.Authentication(0xc00006f710, 0xe373b9, 0xb, 0xc0003e6390)
/home/p1sec/free5gc/NFs/amf/gmm/sm.go:165 +0x5ce
github.com/free5gc/fsm.(*FSM).SendEvent(0xc000386b50, 0xc00006f710, 0xe373b9, 0xb, 0xc0003e6390, 0xc0004e1a60, 0xcb6ba0)
/home/p1sec/go/pkg/mod/github.com/free5gc/[email protected]/fsm.go:95 +0x22d
github.com/free5gc/amf/nas.Dispatch(0xc000118580, 0xe3727a, 0xb, 0x2e, 0xc0004e1b00, 0x20, 0xc0004e1b00)
/home/p1sec/free5gc/NFs/amf/nas/dispatch.go:22 +0x251
github.com/free5gc/amf/nas.HandleNAS(0xc0003d3e60, 0x2e, 0xc00026e3c0, 0x15, 0x20)
/home/p1sec/free5gc/NFs/amf/nas/handler.go:39 +0x178
github.com/free5gc/amf/ngap.HandleUplinkNasTransport(0xc000123e80, 0xc0004e09e0)
/home/p1sec/free5gc/NFs/amf/ngap/handler.go:233 +0x701
github.com/free5gc/amf/ngap.Dispatch(0xfab8c0, 0xc000402120, 0xc0000c8000, 0x41, 0x2000)
/home/p1sec/free5gc/NFs/amf/ngap/dispatcher.go:49 +0x527
github.com/free5gc/amf/ngap/service.handleConnection(0xc000402120, 0x2000, 0xe6a348, 0xe6a350)
/home/p1sec/free5gc/NFs/amf/ngap/service/service.go:204 +0x700
created by github.com/free5gc/amf/ngap/service.listenAndServe
/home/p1sec/free5gc/NFs/amf/ngap/service/service.go:136 +0xc43
```
This happens also with an oversized IE value, e.g. with 5G MM Capabilities:
```
2021-03-08T13:49:59Z [INFO][AMF][NGAP][172.27.128.253:38412] Handle Initial UE Message
panic: runtime error: slice bounds out of range [:32] with length 13
goroutine 7 [running]:
github.com/free5gc/nas/nasMessage.(*RegistrationRequest).DecodeRegistrationRequest(0xc000295e10, 0xc0001c1558)
/home/p1sec/go/pkg/mod/github.com/free5gc/[email protected]/nasMessage/NAS_RegistrationRequest.go:195 +0x1b57
github.com/free5gc/nas.(*Message).GmmMessageDecode(0xc00047c0a0, 0xc0001c1558, 0x10000000000000b, 0xc0001c12d0)
/home/p1sec/go/pkg/mod/github.com/free5gc/[email protected]/nas.go:201 +0x2de
github.com/free5gc/nas.(*Message).PlainNasDecode(0xc00047c0a0, 0xc0001c1558, 0xc0001c1510, 0x2)
/home/p1sec/go/pkg/mod/github.com/free5gc/[email protected]/nas.go:175 +0x58
github.com/free5gc/amf/nas/nas_security.Decode(0xc0004ed600, 0xe3727a, 0xb, 0xc0003926c0, 0x3b, 0x40, 0x11, 0xc0004d4500, 0xcad660)
/home/p1sec/free5gc/NFs/amf/nas/nas_security/security.go:136 +0x452
github.com/free5gc/amf/nas.HandleNAS(0xc000408240, 0xf, 0xc0003926c0, 0x3b, 0x40)
/home/p1sec/free5gc/NFs/amf/nas/handler.go:33 +0xaa
github.com/free5gc/amf/ngap.HandleInitialUEMessage(0xc00030e180, 0xc000312ea0)
/home/p1sec/free5gc/NFs/amf/ngap/handler.go:1003 +0x4dc
github.com/free5gc/amf/ngap.Dispatch(0xfab8c0, 0xc000277d70, 0xc0005f8000, 0x66, 0x2000)
/home/p1sec/free5gc/NFs/amf/ngap/dispatcher.go:47 +0x3bb
github.com/free5gc/amf/ngap/service.handleConnection(0xc000277d70, 0x2000, 0xe6a348, 0xe6a350)
/home/p1sec/free5gc/NFs/amf/ngap/service/service.go:204 +0x700
created by github.com/free5gc/amf/ngap/service.listenAndServe
/home/p1sec/free5gc/NFs/amf/ngap/service/service.go:136 +0xc43
```
<br/>
Providing malformed 5GSID can trigger several additional crashes in the `GutiToString` or `SuciToString` functions:
```
2021-03-08T12:22:45Z [INFO][AMF][GMM][AMF_UE_NGAP_ID:12] Handle Registration Request
panic: runtime error: slice bounds out of range [:4] with capacity 1
goroutine 7 [running]:
github.com/free5gc/nas/nasConvert.GutiToString(0xc000479530, 0x1, 0x1, 0xc000479530, 0x0, 0x0, 0x0, 0x0)
/home/p1sec/go/pkg/mod/github.com/free5gc/[email protected]/nasConvert/MobileIdentity5GS.go:98 +0x386
github.com/free5gc/amf/gmm.HandleRegistrationRequest(0xc0005bb080, 0xe3727a, 0xb, 0xf, 0xc000351110, 0xc000743530, 0xb75bb2)
/home/p1sec/free5gc/NFs/amf/gmm/handler.go:435 +0x111d
github.com/free5gc/amf/gmm.DeRegistered(0xc000452120, 0xe373b9, 0xb, 0xc0004526f0)
/home/p1sec/free5gc/NFs/amf/gmm/sm.go:30 +0x3ef
github.com/free5gc/fsm.(*FSM).SendEvent(0xc000386ab0, 0xc000452120, 0xe373b9, 0xb, 0xc0004526f0, 0x0, 0xcb6ba0)
/home/p1sec/go/pkg/mod/github.com/free5gc/[email protected]/fsm.go:95 +0x22d
github.com/free5gc/amf/nas.Dispatch(0xc0005bb080, 0xe3727a, 0xb, 0xf, 0xc00000cca0, 0x20, 0xc00000cca0)
/home/p1sec/free5gc/NFs/amf/nas/dispatch.go:22 +0x251
github.com/free5gc/amf/nas.HandleNAS(0xc0003d5e60, 0xf, 0xc0002e86c0, 0x12, 0x20)
/home/p1sec/free5gc/NFs/amf/nas/handler.go:39 +0x178
github.com/free5gc/amf/ngap.HandleInitialUEMessage(0xc0000ca180, 0xc000316180)
/home/p1sec/free5gc/NFs/amf/ngap/handler.go:1003 +0x4dc
github.com/free5gc/amf/ngap.Dispatch(0xfab8c0, 0xc00013fda0, 0xc0004d2000, 0x3d, 0x2000)
/home/p1sec/free5gc/NFs/amf/ngap/dispatcher.go:47 +0x3bb
github.com/free5gc/amf/ngap/service.handleConnection(0xc00013fda0, 0x2000, 0xe6a348, 0xe6a350)
/home/p1sec/free5gc/NFs/amf/ngap/service/service.go:204 +0x700
created by github.com/free5gc/amf/ngap/service.listenAndServe
/home/p1sec/free5gc/NFs/amf/ngap/service/service.go:136 +0xc43
```
or
```
2021-03-08T12:27:02Z [INFO][AMF][GMM][AMF_UE_NGAP_ID:53] Handle Registration Request
panic: runtime error: index out of range [2] with length 1
goroutine 49 [running]:
github.com/free5gc/nas/nasConvert.SuciToString(0xc0002dcb20, 0x1, 0x1, 0xc0002dcb20, 0x0, 0x0, 0x0)
/home/p1sec/go/pkg/mod/github.com/free5gc/[email protected]/nasConvert/MobileIdentity5GS.go:36 +0xaa9
github.com/free5gc/amf/gmm.HandleRegistrationRequest(0xc000113080, 0xe3727a, 0xb, 0xf, 0xc000281450, 0xc000075530, 0xb75bb2)
/home/p1sec/free5gc/NFs/amf/gmm/handler.go:431 +0xd9c
github.com/free5gc/amf/gmm.DeRegistered(0xc000069f20, 0xe373b9, 0xb, 0xc0003d2780)
/home/p1sec/free5gc/NFs/amf/gmm/sm.go:30 +0x3ef
github.com/free5gc/fsm.(*FSM).SendEvent(0xc000304b00, 0xc000069f20, 0xe373b9, 0xb, 0xc0003d2780, 0x0, 0xcb6ba0)
/home/p1sec/go/pkg/mod/github.com/free5gc/[email protected]/fsm.go:95 +0x22d
github.com/free5gc/amf/nas.Dispatch(0xc000113080, 0xe3727a, 0xb, 0xf, 0xc000628b60, 0x20, 0xc000628b60)
/home/p1sec/free5gc/NFs/amf/nas/dispatch.go:22 +0x251
github.com/free5gc/amf/nas.HandleNAS(0xc0003de000, 0xf, 0xc000480240, 0x12, 0x20)
/home/p1sec/free5gc/NFs/amf/nas/handler.go:39 +0x178
github.com/free5gc/amf/ngap.HandleInitialUEMessage(0xc0004c0180, 0xc0000981a0)
/home/p1sec/free5gc/NFs/amf/ngap/handler.go:1003 +0x4dc
github.com/free5gc/amf/ngap.Dispatch(0xfab8c0, 0xc00009a140, 0xc00054e000, 0x3d, 0x2000)
/home/p1sec/free5gc/NFs/amf/ngap/dispatcher.go:47 +0x3bb
github.com/free5gc/amf/ngap/service.handleConnection(0xc00009a140, 0x2000, 0xe6a348, 0xe6a350)
/home/p1sec/free5gc/NFs/amf/ngap/service/service.go:204 +0x700
created by github.com/free5gc/amf/ngap/service.listenAndServe
/home/p1sec/free5gc/NFs/amf/ngap/service/service.go:136 +0xc43
```
or
```
2021-03-08T13:29:29Z [INFO][AMF][GMM][AMF_UE_NGAP_ID:1] Handle Registration Request
panic: runtime error: index out of range [4] with length 4
goroutine 33 [running]:
github.com/free5gc/nas/nasConvert.SuciToString(0xc00054a588, 0x4, 0x4, 0xc00054a588, 0x0, 0x0, 0x0)
/home/p1sec/go/pkg/mod/github.com/free5gc/[email protected]/nasConvert/MobileIdentity5GS.go:53 +0xa81
github.com/free5gc/amf/gmm.HandleRegistrationRequest(0xc00054e000, 0xe3727a, 0xb, 0xf, 0xc0005540d0, 0xc0004e5530, 0xb75bb2)
/home/p1sec/free5gc/NFs/amf/gmm/handler.go:431 +0xd9c
github.com/free5gc/amf/gmm.DeRegistered(0xc00048cba0, 0xe373b9, 0xb, 0xc00048ced0)
/home/p1sec/free5gc/NFs/amf/gmm/sm.go:30 +0x3ef
github.com/free5gc/fsm.(*FSM).SendEvent(0xc0002d6670, 0xc00048cba0, 0xe373b9, 0xb, 0xc00048ced0, 0x0, 0xcb6ba0)
/home/p1sec/go/pkg/mod/github.com/free5gc/[email protected]/fsm.go:95 +0x22d
github.com/free5gc/amf/nas.Dispatch(0xc00054e000, 0xe3727a, 0xb, 0xf, 0xc00053afa0, 0x20, 0xc00053afa0)
/home/p1sec/free5gc/NFs/amf/nas/dispatch.go:22 +0x251
github.com/free5gc/amf/nas.HandleNAS(0xc0004c2240, 0xf, 0xc00049a940, 0x15, 0x20)
/home/p1sec/free5gc/NFs/amf/nas/handler.go:39 +0x178
github.com/free5gc/amf/ngap.HandleInitialUEMessage(0xc0004b2000, 0xc000508880)
/home/p1sec/free5gc/NFs/amf/ngap/handler.go:1003 +0x4dc
github.com/free5gc/amf/ngap.Dispatch(0xfab8c0, 0xc000304170, 0xc00051e000, 0x40, 0x2000)
/home/p1sec/free5gc/NFs/amf/ngap/dispatcher.go:47 +0x3bb
github.com/free5gc/amf/ngap/service.handleConnection(0xc000304170, 0x2000, 0xe6a348, 0xe6a350)
/home/p1sec/free5gc/NFs/amf/ngap/service/service.go:204 +0x700
created by github.com/free5gc/amf/ngap/service.listenAndServe
/home/p1sec/free5gc/NFs/amf/ngap/service/service.go:136 +0xc43
```
<br/>
Finally, it seems using any kind of LADN Indicator within the 5G Registration Request message leads to the AMF getting stuck, consuming CPU and memory forever, and not responding on the SCTP socket anymore. The process gets finally killed by the Linux kernel.
For instance sending a NAS Registration Request with the following LADN Indicator structure:
```
### LADNInd ###
<T : 116>
<L : 8>
<V : 0x0000000000000000>
```
Leads to this situation:
```
[4410188.716481] Out of memory: Killed process 1955374 (amf) total-vm:19664848kB, anon-rss:7375620kB, file-rss:0kB, shmem-rss:0kB, UID:1000 pgtables:22604kB oom_score_adj:0
[4410189.087583] oom_reaper: reaped process 1955374 (amf), now anon-rss:40kB, file-rss:0kB, shmem-rss:0kB
```
|
[Bugs] AMF breaks due to malformed NAS message
|
https://api.github.com/repos/free5gc/free5gc/issues/198/comments
| 4 |
2021-04-26T13:42:33Z
|
2023-12-04T08:48:27Z
|
https://github.com/free5gc/free5gc/issues/198
| 867,719,689 | 198 |
[
"free5gc",
"free5gc"
] |
## Describe the bug
free5gc fails to handle correctly when a UE connects with a security context not available anymore in the AMF.
When a UE re-establishes a NAS connection, reusing a NAS security context that has been setup in a past connection, it uses a NAS Container to put the complete initial NAS message security protected (encrypted and integrity protected), within the initial NAS message which has been stripped of all IEs that shall not be sent in clear-text. The free5gc's AMF fails however to decode and process the content of the NAS container, and does not respond to the UE in which the NAS connection timeouts. Therefore, free5gc is not able to handle NAS re-connection for standard UEs.
## To Reproduce
A complete gNB / UE emulator, or simply a recent 5G handset, should enable to test for such NAS re-connection and exhibit the issue.
## Expected behavior
The AMF should support security-protected NAS messages set in NAS container within initial NAS messages, as described in the 3GPP specification TS 24.501 section 4.4.6. In case the AMF has dropped or lost the security context used by the UE, it should then request the replay of the complete initial NAS message within the Security Mode Complete message.
## Environment (please complete the following information):
- free5GC Version: v3.0.5
- OS: Ubuntu 20.04
- Kernel version: 5.4.0-62-generic
- go version: go1.14.4 linux/amd64
## Trace File
### Configuration File
No specific configuration file is required.
### PCAP File
Attached is a pcap where a UE initially does a registration with the AMF and establishes a NAS security context while doing so. It then tries to reconnect while using the same security context to appropriately protect the initial NAS message, however the AMF fails to process the NAS Container and to respond to the UE.
[free5gc_nas_non-exist-sec-ctx_fail.pcap.gz](https://github.com/free5gc/free5gc/files/6377272/free5gc_nas_non-exist-sec-ctx_fail.pcap.gz)
### Log File
This is the log of the AMF corresponding to the pcap:
```
2021-02-12T09:46:18Z [INFO][AMF][NGAP][172.27.128.253:38412] Handle Initial UE Message
2021-02-12T09:46:18Z [INFO][AMF][GMM][AMF_UE_NGAP_ID:4] Handle Registration Request
2021-02-12T09:46:18Z [DEBU][NAS][Security] Use NEA0 (/home/p1sec/go/pkg/mod/github.com/free5gc/[email protected]/security/security.go:28 github.com/free5gc/nas/security.NASEncrypt)
2021-02-12T09:46:18Z [ERRO][AMF][GMM] The payload of NAS Message Container is not Registration Request
2021-02-12T09:46:26Z [INFO][AMF][NGAP][172.27.128.253:38412] Handle Uplink Nas Transport
2021-02-12T09:46:26Z [INFO][AMF][NGAP][172.27.128.253:38412][AMF_UE_NGAP_ID:4] Uplink NAS Transport (RAN UE NGAP ID: 3)
2021-02-12T09:46:26Z [INFO][AMF][GMM][AMF_UE_NGAP_ID:4] Handle Registration Request
2021-02-12T09:46:26Z [DEBU][NAS][Security] Use NEA0 (/home/p1sec/go/pkg/mod/github.com/free5gc/[email protected]/security/security.go:28 github.com/free5gc/nas/security.NASEncrypt)
2021-02-12T09:46:26Z [ERRO][AMF][GMM] The payload of NAS Message Container is not Registration Request
2021-02-12T09:46:32Z [INFO][AMF][NGAP][172.27.128.253:38412] Handle Uplink Nas Transport
2021-02-12T09:46:32Z [INFO][AMF][NGAP][172.27.128.253:38412][AMF_UE_NGAP_ID:4] Uplink NAS Transport (RAN UE NGAP ID: 3)
2021-02-12T09:46:32Z [INFO][AMF][GMM][AMF_UE_NGAP_ID:4] Handle Registration Request
2021-02-12T09:46:32Z [DEBU][NAS][Security] Use NEA0 (/home/p1sec/go/pkg/mod/github.com/free5gc/[email protected]/security/security.go:28 github.com/free5gc/nas/security.NASEncrypt)
2021-02-12T09:46:32Z [ERRO][AMF][GMM] NAS decode Fail: MsgType[225] doesn't exist in GMM Message
2021-02-12T09:46:38Z [INFO][AMF][NGAP][172.27.128.253:38412] Handle Uplink Nas Transport
2021-02-12T09:46:38Z [INFO][AMF][NGAP][172.27.128.253:38412][AMF_UE_NGAP_ID:4] Uplink NAS Transport (RAN UE NGAP ID: 3)
2021-02-12T09:46:38Z [INFO][AMF][GMM][AMF_UE_NGAP_ID:4] Handle Registration Request
2021-02-12T09:46:38Z [DEBU][NAS][Security] Use NEA0 (/home/p1sec/go/pkg/mod/github.com/free5gc/[email protected]/security/security.go:28 github.com/free5gc/nas/security.NASEncrypt)
2021-02-12T09:46:38Z [ERRO][AMF][GMM] NAS decode Fail: MsgType[163] doesn't exist in GMM Message
```
|
[Bugs] AMF fails to support NAS connection with an existing security context
|
https://api.github.com/repos/free5gc/free5gc/issues/197/comments
| 4 |
2021-04-26T13:12:39Z
|
2023-07-28T05:23:42Z
|
https://github.com/free5gc/free5gc/issues/197
| 867,689,888 | 197 |
[
"free5gc",
"free5gc"
] |
## Describe the bug
While testing the free5gc AMF for some NAS security features introduced in the 5G specifications, I found that the AMF processes any plaintext initial NAS message entirely (all IEs in the message are processed), without further check or warning. While the AMF still requests the replay of the initial NAS message in the Security Mode Complete, it does not care in case nothing is replayed, or a different message than the initial one, what seems contradictory to the "spirit" of the 5G security specification.
You can refer to 3GPP TS 33.501 section 6.4.6 for the global overview of the feature (while it is not saying anything specific to do in case the initial NAS message is not replayed or different), and TS 24.501 section 4.4.6 for the list of IEs that are to be processed in plaintext initial NAS message.
There are 2 main risks with this:
- The early processing of all IEs in the AMF, and missing check against the replayed message, could potentially enable some man-in-the-middle attack at the radio interface, where some cellular capabilities of a targeted subscriber are downgraded by the attacker.
- Processing all IEs, before subscriber's authentication has happened, may expose the AMF more than needed ; e.g. I could reach many assertions, and a memory corruption in the AMF demon, with malformed IEs in initial NAS messages.
## To Reproduce
No easy way to reproduce with available open-source tools. A modification of a gNB / UE emulator can be done to send the entire initial NAS message in clear-text, and not replaying it (or replaying with a different message) in the Security Mode Complete message.
## Expected behavior
I believe only "clear-text" IEs from the initial NAS message should be processed in the first place, then other IEs should be processed from the replayed message in the Security Mode Complete which is security protected. In case this replayed message is not provided, I believe the NAS connection should be dropped.
## Environment (please complete the following information):
- free5GC Version: v3.0.5
- OS: Ubuntu 20.04
- Kernel version: 5.4.0-62-generic
- go version: go1.14.4 linux/amd64
## Trace File
### Configuration File
No specific configuration required.
### PCAP File
A pcap is provided, where the complete initial NAS message is in clear text, and is not replayed in the Security Mode Complete message. The AMF does not issue any specific logging related to this issue, it processes all IEs from the initial NAS message.
[free5gc_nas-init-nosec.pcap.gz](https://github.com/free5gc/free5gc/files/6376764/free5gc_nas-init-nosec.pcap.gz)
### Log File
No specific log exists for this issue.
|
[Bugs] AMF processes entire plaintext initial NAS message
|
https://api.github.com/repos/free5gc/free5gc/issues/196/comments
| 1 |
2021-04-26T11:45:08Z
|
2023-08-09T03:32:37Z
|
https://github.com/free5gc/free5gc/issues/196
| 867,614,174 | 196 |
[
"free5gc",
"free5gc"
] |
## Describe the bug
During the NAS protocol exchange between the UE and the AMF, when the UE does not provide its IMEI directly in the Security Mode Complete, the AMF requests it in clear-text whereas the NAS security context has been established successfully. This contradicts the 3GPP specification on NAS TS 24.501, sections 4.4.4.1 and 4.4.4.2.
This issue may expose 5G subscribers' IMEI in clear-text over the radio interface, in case their handsets are failing to support properly the sending of the IMEI within the Security Mode Complete.
## To Reproduce
No easy way to reproduce with available open-source tools. A modification of a gNB / UE emulator can be done to answer Security Mode Control in a custom way, by not providing the IMEI in the message: this will trigger the AMF to then request IMEI in the clear.
## Expected behavior
IMEI shall never be requested in clear text NAS messages.
## Environment (please complete the following information):
- free5GC Version: v3.0.5
- OS: Ubuntu 20.04
- Kernel version: 5.4.0-62-generic
- go version: go1.14.4 linux/amd64
## Trace File
### Configuration File
No specific configuration required.
### PCAP File
A pcap is provided with 2 successive NAS registration, where this insecure behavior is exhibited during the 2nd registration.
[free5gc_nas-smc_imei-in-clear.pcap.gz](https://github.com/free5gc/free5gc/files/6376663/free5gc_nas-smc_imei-in-clear.pcap.gz)
### Log File
No specific log exists for this issue.
|
[Bugs] subscriber's IMEI requested in clear if not provided in NAS Security Mode Complete
|
https://api.github.com/repos/free5gc/free5gc/issues/195/comments
| 4 |
2021-04-26T11:28:46Z
|
2021-10-15T10:07:27Z
|
https://github.com/free5gc/free5gc/issues/195
| 867,600,755 | 195 |
[
"free5gc",
"free5gc"
] |
## Describe the bug
AMF Config file is given, there is a "version", when gives the verison 1.0.0, sometimes it says,
[ERRO][AMF][CFG] [0mconfig version is [1.0.0], but expected is [1.0.1].
but if changes to 1.0.1, it sometimes says:
[ERRO][AMF][CFG] [0mconfig version is [1.0.1], but expected is [1.0.0].
I am not sure if this is a bug, because maybe i miss something. this two version config file not compatible?
|
[Bugs] AMF config file 1.0.0 or 1.0.1
|
https://api.github.com/repos/free5gc/free5gc/issues/194/comments
| 2 |
2021-04-21T09:44:54Z
|
2021-04-28T03:47:26Z
|
https://github.com/free5gc/free5gc/issues/194
| 863,680,381 | 194 |
[
"free5gc",
"free5gc"
] |
## Describe the bug
Hi folks
Possible build config issue. Using the latest stable version. The build runs fine, but at testing time the following error occurs:
user@free5gc:~/free5gc$ ./test.sh TestRegistration
2021-04-19T13:48:17Z [INFO][UPF][Util] Config: /home/user/free5gc/NFs/upf/build/config/upfcfg.test.yaml
2021-04-19T13:48:17Z [INFO][UPF][Util] UPF config version [1.0.0]
2021-04-19T13:48:17Z [INFO][UPF][Util] Set log level: info
2021-04-19T13:48:17Z [INFO][UPF][Util] DNN routes added, main routing table:
2021-04-19T13:48:17Z [INFO][UPF][Util] DstIp Gateway Iface Priority RtProto Type
2021-04-19T13:48:17Z [INFO][UPF][Util] 60.60.0.0 /24 0.0.0.0 upfgtp 0 static unicast
2021-04-19T13:48:17Z [INFO][UPF][Util] 10.200.200.0 /24 0.0.0.0 veth1 0 kernel unicast
> go: github.com/free5gc/[email protected] requires
> github.com/free5gc/[email protected]: missing go.sum entry; to add it:
> go mod download github.com/free5gc/ngap
It seems the version of ngap that is downloaded is still v1.0.0, but the app dependancy demands v1.0.1.
Modifying go.mod for amf, smf and n3iwf back to v1.0.0 seems to fix the issue, but obviously now using v1.0.0
## To Reproduce
Steps to reproduce the behavior:
1. Clone stable as per instructions
2. make
3. Run registration test
## Environment:
- free5GC Version: [3.0.5]
- OS: [Ubuntu 20.04.2 server]
- Kernel version: [5.4.0-72-generic]
- go version: [go1.16.3 linux/amd64]
- c compiler version (Option): [Ubuntu 9.3.0-17ubuntu1~20.04]
|
[Bugs] Possible version miss match for ngap (wants v1.0.1, but can't find it)
|
https://api.github.com/repos/free5gc/free5gc/issues/193/comments
| 2 |
2021-04-19T14:12:06Z
|
2021-04-26T06:52:08Z
|
https://github.com/free5gc/free5gc/issues/193
| 861,353,922 | 193 |
[
"free5gc",
"free5gc"
] |
## Issue Description
### What's the version are you using
v3.0.5
### Is your feature request related to a problem? Please describe.
SMF always chooses the first UPF found in UPFs map.
It leads that the load is concentrated on the same UPF and adding UPF does not improve overall U-Plane performance.
### Describe the solution you'd like
If there are multiple UPFs matches conditions both DNN and S-NSSAI, select one UPF from them randomly to distribute the load and improve overall U-Plane performance.
#### Pull Request
Pull Requests for the feature:
* [free5gc](https://github.com/free5gc/free5gc/pull/191)
* [smf](https://github.com/free5gc/smf/pull/22)
### Describe alternatives/workarounds you've considered
None
### Additional context
None
## Issue Template Checklist
<!-- Please answer the questions below. If not the issue might be disregarded. -->
### If willing to resolve an issue by submitting Pull request, please consider the points below.
<!-- free5GC will be happy to welcome first contributor’s, in order to broaden the community. -->
- [x] Yes, I have the time and I know how to start.
- [ ] Yes, I have the time but I don't know how to start, I would need guidance.
- [ ] No, I don't have the time, although I believe I could do it if I had the time...
- [ ] No, I don't have the time and I wouldn't even know how to start.
|
[Feat]Multiple UPF and ULCL feature
|
https://api.github.com/repos/free5gc/free5gc/issues/192/comments
| 1 |
2021-03-25T06:41:19Z
|
2021-03-27T17:27:31Z
|
https://github.com/free5gc/free5gc/issues/192
| 840,614,663 | 192 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.