Replies: 6 comments
-
|
Hi @dilallkx,
Please find the attached scenario where as the UL, DL throughput for wifi1 is set to 1Mbps. lab2@lab2:~$ kubectl get pod --all-namespaces -o wide lab2@lab2:~$ kubectl logs vlc1-56dd69f659-lzrjc --namespace create
Thank you in advance, I look forward to hearing from you. BR, |
Beta Was this translation helpful? Give feedback.
-
|
Hi @itnor4, Thank you for using the platform & for reaching out! It seems your traffic is not going through the platform as expected. I would like to have a closer look at your scenario to verify the ingress and egress rules for the external apps. Could you please export and attach your scenario to this discussion? Could you also clarify where your external apps are running? Also, what are the expected traffic flows that you want to pass through AdvantEDGE? For example, the VLC client may send a request to the VLC server on port 31000 via AdvantEDGE, however the subsequent data flow may not use the same session & ports, and may require a different set of rules to pass through AdvantEDGE. With this additional information we should be able to get this working for you! |
Beta Was this translation helpful? Give feedback.
-
|
Hi @dilallkx, Thank you for your response and please find the attach scenario. Could you also clarify where your external apps are running? The mec-app is deployed at the same machine where AdvantEDGE is running, I am using VLC docker container in a pod that plays the video on loop. I have created service for that pod mapping the external IP as 131.114.55.221 with port 8080 (This IP address is same as AdvantEDGE). For ex. during different practical trials I have also used VLC application to stream the video with TCP instead of container in K8s pod, the issue remains the same. If the packet loss is too high at PoA where the UE is connected then I see effect of the network characteristics being applied such as (packet loss effect), when the packet loss is lower than 40% around 20-30% there is no effect the video still runs with good quality and the UE app pod log always has this issue (time="2023-06-06T11:57:04.2Z" level=info msg="Pinger error: 10.32.0.16 i/o timeout" meep.component=meep-tc-sidecar) running in the backend. The throughput is calculated wrong. However, the UDP did not had any such problems it works well as expected. Thank you, I look forward to hearing from you. BR, |
Beta Was this translation helpful? Give feedback.
-
|
Hi @itnor4, Thank you for the scenario. If I understand correctly, you have a VLC app running in a k8s pod on the same machine as AdvantEDGE that sends a TCP video stream to the VLC player running on a different Ubuntu machine. The VLC app is configured to send the video stream to AdvantEDGE at 131.114.55.221:31000 using the mec-app ingress rule, and you would then expect it to be sent to the external VLC player at 131.114.55.150:8080 using the vlc1 egress rule. This seems correct to me. Do you confirm that VLC protocol used with TCP creates a single TCP session between your external applications? Is it possible that multiple TCP sessions are established by the applications when using TCP? This could lead to some flows passing through AdvantEDGE and other flows that bypass AdvantEDGE. Please confirm (with traces on the external player) that there is a single TCP connection on port 8080, and that the video stream data flow uses this port. Also, please verify that the TCP SYN packet for the TCP session originates from the container and is sent to port 31000. Regards! |
Beta Was this translation helpful? Give feedback.
-
|
Hi @dilallkx, Thank you for your response. Just to confirm, does the configuration of 131.114.55.150:8080 needs to be done at UE app within AdvantEDGE using Egress rule, currently the setting is at 131.114.55.221:8080 which is the AdvantEDGE and mec-app IP. Egress mapping for ue-app my-service::131.114.55.221:8080:TCP |
Beta Was this translation helpful? Give feedback.
-
|
Hi @itnor4, I seem to have mixed up the IP addresses in my previous reply. The ingress rule is the AdvantEDGE entry point where traffic (i.e. video stream) should be sent; in your case this is mec-app 131.114.55.221:31000. With this configuration, the only traffic that will pass through AdvantEDGE is TCP traffic for the TCP session established from an external app towards 131.114.55.221:31000. If your external VLC app establishes a TCP connection with 131.114.55.221:31000 and sends the video stream over this same TCP connection, then it will go through AdvantEDGE and reach the VLC player at 131.114.55.221:8080. If a new TCP session is established for the video stream on a different port or with a different protocol then it may bypass AdvantEDGE. This is where the trace is useful to identify the data flows. I hope this clarifies the platform behavior! |
Beta Was this translation helpful? Give feedback.
-
Hi,
I have question regarding the setup and configuration of an external mec-app and ue-app in AdvantEDGE, as instructed here at https://interdigitalinc.github.io/AdvantEDGE/docs/overview/features/ext-nodes/ I have followed these configurations:
Egress mapping for mec-app my-service::131.114.55.221:8080:TCP
Ingress mapping for ue-app 31000:my-service:8080:TCP
Where as the mec-app is a VLC application running in docker container managed by K8s and exposed at 131.114.55.221:8080
While, the ue-app is VLC application running on Ubuntu OS.
Thank you, I look forward to hearing from you.
BR,
Prachi
Beta Was this translation helpful? Give feedback.
All reactions