-
Notifications
You must be signed in to change notification settings - Fork 28
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hi, why the tail call always can't run successfully, thanks #70
Comments
And I am wondering where is SessionProgram::setup() called? I haven't found it been called anywhere, thanks. |
Hi Bradley, I seem that you have been able to run this project and really gone far in running this. However, I was proceeding as per documentation, and is stuck currently. When using command "make install" inside the docker, I am getting issue in compilation of Configuration.cpp file. Thanks |
@bradley-code-again, @hrkgarg, Sorry for the late reply. I appreciate that you have been trying to run. I am without band right now to help you guys. This definitely could have some issue. @bradley-code-again, did you create the PFCP Session? Check here: https://github.com/navarrothiago/upf-bpf/tree/master/tests/api/requests_body. You can import inside Postman. Usually, three steps are done:
|
@hrkgarg, hi, I didn't change anything in env.sh. There is a problem of a cpp file, I changed somewhere manually. I don't remember exactly what I have changes, but it is somewhere auto generated. Read the error carefully, then you may find it. |
Hi, thanks for your wonderful project and sharing. I am trying to run your code but without TRex. I send some dummy GTP packets of N3 and UDP packets of N6 to the running program. The packets can be caught at the entry_point of SEC("xdp_entry_point"), but these packets never can come to SEC("xdp_uplink_entry_point") or SEC("xdp_downlink_entry_point"), and the tail call is always failed.
I am wondering why, and when will you call getUplinkFileDescriptor(). It looks like you don't need to call that to trigger tail call? many thanks for your ideas.
The text was updated successfully, but these errors were encountered: