Closed ianchen0119 closed 3 months ago
Hi @gab-arrobo & @thakurajayL
Could you please help to review the PR? Thanks.
Hi @gab-arrobo
Do I need to do any enhancements for this PR? If yes, please let me know when you feel free.
Many thanks.
Hi @gab-arrobo
Do I need to do any enhancements for this PR? If yes, please let me know when you feel free.
Many thanks.
Hi @ianchen0119, I will try to review your PR in the coming days and will get back to you
@ianchen0119, I just enabled some additional linters. Please rebase your PR. Thank you!
@ianchen0119, how did you test the changes/PR?
Hi @gab-arrobo
After the UPF gets started, the fuzzing can be enabled. It will connect to the UPF and try to send the malformed PFCP message to explore the potential security issue.
We can use the command below to trigger the fuzzing, for example:
go test -fuzz=Fuzz -p 1 -parallel 1 -fuzztime 15m ./fuzz/...
Furthermore, go-upf PR #33 is to fix the bug, reported by a community user, and it can be reproduced by the fuzzing.
Hello,
I push a commit to let PFCP accept the loopback interface. Also, this PR was functional in my environment.
I run the UPF in host (10.10.0169), and run PFCPSIM on the same machine. It can create sessions, delete sessions, and also receive reports from UPF.
Hi @gab-arrobo Could you please help to approve the CI workflow?
Thank you.
Hello,
I push a commit to let PFCP accept the loopback interface. Also, this PR was functional in my environment.
I run the UPF in host (10.10.0169), and run PFCPSIM on the same machine. It can create sessions, delete sessions, and also receive reports from UPF.
Thanks for your input/update. I am going to try it.
Hello,
Thanks for the suggestion! @gab-arrobo
These were what I did in the latest commit:
go test
.