n6 connecticity when nagp is NodePort

[hackeryounow]

nr-ue and nr-gnb are not run in pod, and then ping -I uesimtun0 google.com failed.

I wonder know whether this could be solved by changing the helm charts files.

[hackeryounow]

After analzing some protocol packets in a kubenetes cluster, I found the N3 network cann't be connected by gnb. I haven't solved it. Maybe, changing network way by Service, not NetworkAttachmentDefinition for N3 is a good choice. It is not the best method.

[raoufkh]

Hello @hackeryounow! If you deploy gNB outside the cluster, you can use an N3 interface that in the same network as UPF N3 interface. If you don't have one, you can create an ipvlan or macvlan interface and use it.

For example:

sudo ip link add link eth0 name n3 type ipvlan mode l2 && \
    sudo ip addr add 10.100.50.236/29 dev n3 && \
    sudo ip link set n3 up

Knowing that eth0 is within the same network as the master interface of UPF N3 interface.

Additional N3 interface is attached using Multus for network isolation and providing the possibility for network accelaration (later, we could add the possibility of using SRIOV).

[github-actions[bot]]

This issue is stale because it has been open for 30 days with no activity.

[github-actions[bot]]

This issue was closed because it has been inactive for 14 days since being marked as stale.