Orange-OpenSource / towards5gs-helm

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

Update README.md #10

Closed hkerma closed 2 years ago

hkerma commented 2 years ago

I believe the N9 network should be on eth0, only the N6 network should be on eth1. I might be wrong. In any case, they are some inconsistencies between the README and the values.yaml file associated to the free5gc chart.

raoufkh commented 2 years ago

Hello @hkerma

For the default value of the global.n6network.masterIf parameter you are right. It is eth1. Please update the network configuration section and I will merge the commit.

Regards, Raouf

hkerma commented 2 years ago

Hello I think the changes I made are already about the Network configuration section.

I am just confused about that sentences

In addition, please make sure global.n6network.subnetIP, global.n6network.gatewayIP and upf.n6if.IpAddress parameters will match the IP address of the toto interface in order to make the UPF able to reach the Data Network via its N6 interface.

Is toto supposed to be eth0 in the example? Then what is eth1? Sorry if I am saying nonsense, I am trying to understand.

Best, Hugo

raoufkh commented 2 years ago

By default, the helm charts suppose 2 network interfaces exist, respectively named eth0 and eth1. If only one interface is present and its name is toto, then you should check Network configuration section. If the name of the interface is eth0, then toto must be replaced by eth0. In this case, the UPF N6 will use eth0 as a master interface.

hkerma commented 2 years ago

Ok, thank you for that clarification. So the updates I made are actually correct?

raoufkh commented 2 years ago

I've made a review for the commit. It is true for N9 (default master interface is eth0). For N6, its master interface should also be set to totoif there is only one interface named toto.

hkerma commented 2 years ago

That is right, I will correct and update the PR. Thanks for your help