search

Orange-OpenSource / towards5gs-helm

Helm charts for deploying 5G network services on Kubernetes
Other
167 stars 130 forks source link

TUN interface created but No Connection #47

Closed akram09 closed 1 year ago

akram09 commented 2 years ago

Hello everyone, I wanted first to thank all the team that is maintaining such a project, it's indeed a very interesting contribution.

I'm actually trying to deploy the free5gc on a kubernetes cluster composed of 2 worker nodes and one master, And following are the steps that I have came across in my setup:

  1. I have verified the installation of the kernel module gtp5g on all the workers' nodes.
  2. I currently have only one physical interface called eth0 that I use as the master Interface for the network attachments.
  3. I'm currently using kube-ovn as the CNI plugin joined with Multus.
  4. In my use case I'm trying to connect a simple server with the upf :
    • The server is a simple pod that uses the same network-attachement-definition as the upf and is connected to the same network:

image

Here are the values.yml used for the deployment of free5gc charts:

global:
  n6network:
    name: n6network
    masterIf: eth0

  1. The ue and gnb were both deployed successfully and the interface uesimtun0 is up and working: image

  2. I have also activated the promicsuous mode and verified that the ipv4 forwarding is enabled on the upf pod.

Problem

When trying to ping from the user equipment pod to the upf everything works perfectly ( the ip address of the server is 10.100.10.10 and upf is 10.100.100.12) image But the problem occur when trying to access the server pod from the user equipment pod: image

I have checked the connection between upf and the server and it is indeed working fine: image

Is there anything I'm actually missing out on in my configuration?

raoufkh commented 2 years ago

Hi @akram09

Thanks first for the kind words.

Did you try to reach internet from the UE? You can try it by pinging or curling www.google.com

Bests Raouf

akram09 commented 2 years ago

Hello @raoufkh , Thank you for your answer

Yes indeed I have tried to curl www.google.com but still didn't work, I have been looking at some configurations and I guess pinging or accessing www.google.com won't work because the n6 interface is not configured to access the physical network.

But on the other hand I wonder why I can't access the server pod from the UE even if they are on the same subnet, is it a problem with Kube-Ovn ?

raoufkh commented 2 years ago

I've never tried a such scenario. Since the server N6 insterface and UPF N6 interface are in the same subnet, they should be able to ping each other. Can you check iptables rules on the UPF Pod (especially NAT rules that allow to mask the ip address of UEs)?

raoufkh commented 1 year ago

Don't hesitate to re-open if you have extra information on networking rules