You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have deployed 5G openverso/open5gs network on kubernetes cluster.
In 5G network, UPF component provides end user UE navigation. It is responsible for decapsulating GTP traffic received from UE and routing traffic to destination.
When istio is enabled, seems like Istio envoy in UPF doesn't route UE traffic outside the pod. This is a network trace taken in UPF:
When excluding ports 80/443 in Istio, everything works fine meaning UE can browse Internet. But we would like to avoid it in order to gain Istio observability on those ports
I know this is very specific to 5G technology and maybe GTP protocol. In any case, I would appreciate if somebody could give a hint.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hello,
We have deployed 5G openverso/open5gs network on kubernetes cluster.
In 5G network, UPF component provides end user UE navigation. It is responsible for decapsulating GTP traffic received from UE and routing traffic to destination.
When istio is enabled, seems like Istio envoy in UPF doesn't route UE traffic outside the pod. This is a network trace taken in UPF:
When excluding ports 80/443 in Istio, everything works fine meaning UE can browse Internet. But we would like to avoid it in order to gain Istio observability on those ports
I know this is very specific to 5G technology and maybe GTP protocol. In any case, I would appreciate if somebody could give a hint.
Thanks in advance,
Best Regards,
José Miguel
Beta Was this translation helpful? Give feedback.
All reactions