Skip to content
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

Unable to access video in MEC #60

Closed
xiaobinggan-zmh opened this issue Aug 11, 2022 · 5 comments
Closed

Unable to access video in MEC #60

xiaobinggan-zmh opened this issue Aug 11, 2022 · 5 comments

Comments

@xiaobinggan-zmh
Copy link

I used K8S + Docker to deploy Free5GC. I tried to use the network provided by Free5GC to access the Internet, which could normally connect to the Internet. Then I deployed the Nginx server in the LAN where the core network was located, but the problem was that my UE could access the HTML in the Nginx server. However, I cannot download or access the MP4 video in the Nginx server. After a long time of checking, I still cannot find the problem. Do I need any special configuration to access the video in the MEC server?

I tried to use 5GC provided by OAI open source platform, which can access the video.

@abousselmi
Copy link
Collaborator

Hi @xiaobinggan-zmh

Can you be more precise about the errors you had ?

This project doesn't support k8s, it leverages docker-compose to run free5gc. But if you provide more info about your setup I can try to guide you to some possible fixes.

Regards,

@xiaobinggan-zmh
Copy link
Author

xiaobinggan-zmh commented Aug 14, 2022

Hi @abousselmi
I deploy the core network on the server (192.168.10.7). I access the video server (192.168.10.15) on MEC from my mobile phone (10.60.0.3). I deploy the Nginx server on MEC, and the mobile phone can access the HTML on the nginx server. But I can't access photos or videos, so I captured packets both on the MEC server and on my mobile phone. Capturing packets on the MEC server would lead to errors such as TCP Previous segment not captured and TCP Retransmission. Capturing the packet on my phone shows errors such as TCP Previous Segment Not captured and TCP Dup ACK. It must have been lost in the process, but I don't understand why.

Maybe I should add routing and forwarding to solve it.

@xiaobinggan-zmh
Copy link
Author

I have successfully solved the problem.

@abousselmi
Copy link
Collaborator

Hi @xiaobinggan-zmh

Can you explain how you solved the problem ?

Thanks,

@xiaobinggan-zmh
Copy link
Author

Since I am deployed with K8S, I added SVC for each NF and changed the mirror of UPF. Docker-compose should not encounter my problem if you use Docker-compose, which is caused by K8S.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants