The free5GC helm install succeeds but cannot connect to the external NW. it appears that it is not tied to the Multus Master Interface. How to reslove this problems?
$ ip a
2: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
link/ether 4c:52:62:65:bb:fd brd ff:ff:ff:ff:ff:ff
inet 172.31.16.37/24 brd 172.31.16.255 scope global eno1
valid_lft forever preferred_lft forever
inet6 fe80::4e52:62ff:fe65:bbfd/64 scope link
valid_lft forever preferred_lft forever
7: ens1f0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 9000 qdisc mq state UP group default qlen 1000
link/ether b8:ce:f6:72:b0:d4 brd ff:ff:ff:ff:ff:ff
inet 172.31.1.30/24 brd 172.31.1.255 scope global ens1f0
valid_lft forever preferred_lft forever
inet6 fe80::bace:f6ff:fe72:b0d4/64 scope link
valid_lft forever preferred_lft forever
$ helm install free5gc-v1 ./free5gc/ --set free5gc-upf.upf.securityContext.privileged=true --set free5gc-upf.upf.securityContext.capabilities=null --set global.n6network.subnetIP=172.31.1.0 --set global.n6network.gatewayIP=172.31.1.1 --set global.n6network.excludeIP=172.31.1.254 --set free5gc-upf.upf.n6if.ipAddress=172.31.1.11 --set global.n2network.masterIf=eno1 --set global.n3network.masterIf=eno1 --set global.n4network.masterIf=eno1 --set global.n6network.masterIf=ens1f0 --set global.n9network.masterIf=eno1
$ kubectl get po
NAME READY STATUS RESTARTS AGE
free5gc-v1-free5gc-amf-amf-69c476d9cb-k47kz 1/1 Running 0 52s
free5gc-v1-free5gc-ausf-ausf-7675996f67-ch2bt 1/1 Running 0 51s
free5gc-v1-free5gc-dbpython-dbpython-7d4c7fd7f8-zc254 1/1 Running 0 52s
free5gc-v1-free5gc-nrf-nrf-55cffd6c79-ft4w2 1/1 Running 0 51s
free5gc-v1-free5gc-nssf-nssf-795f9f5577-79rdz 1/1 Running 0 51s
free5gc-v1-free5gc-pcf-pcf-797f677cfc-kzwk4 1/1 Running 0 51s
free5gc-v1-free5gc-smf-smf-766cddcd99-skk95 1/1 Running 0 51s
free5gc-v1-free5gc-udm-udm-684f7b8688-p4drb 1/1 Running 0 52s
free5gc-v1-free5gc-udr-udr-65cdb74d7d-tv7ch 1/1 Running 0 50s
free5gc-v1-free5gc-upf-upf-57c6c59d8b-9qw8f 1/1 Running 0 51s
free5gc-v1-free5gc-webui-webui-5b9b94bb95-x2q4n 1/1 Running 0 52s
mongodb-0 1/1 Running 0 51s
If the Multus Master Interface is connected to the Multus Master Interface, it is recognized that XXX>@if<YYY is displayed, but it appears to be displayed incorrectly.
$ kubectl exec -it free5gc-v1-free5gc-upf-upf-57c6c59d8b-9qw8f -- ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: tunl0@NONE: <NOARP> mtu 1480 qdisc noop state DOWN group default qlen 1000
link/ipip 0.0.0.0 brd 0.0.0.0
4: eth0@if51: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1480 qdisc noqueue state UP group default
link/ether fe:2b:34:2a:32:a5 brd ff:ff:ff:ff:ff:ff link-netnsid 0
inet 182.16.184.168/32 scope global eth0
valid_lft forever preferred_lft forever
inet6 fe80::fc2b:34ff:fe2a:32a5/64 scope link
valid_lft forever preferred_lft forever
5: n3@tunl0: <BROADCAST,MULTICAST,UP,LOWER_UP,M-DOWN> mtu 1500 qdisc noqueue state UNKNOWN group default
link/ether 4c:52:62:65:c5:d4 brd ff:ff:ff:ff:ff:ff
inet 10.100.50.233/29 brd 10.100.50.239 scope global n3
valid_lft forever preferred_lft forever
inet6 fe80::4c52:6200:165:c5d4/64 scope link
valid_lft forever preferred_lft forever
6: n6@n4: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 9000 qdisc noqueue state UNKNOWN group default
link/ether b8:ce:f6:7c:6b:58 brd ff:ff:ff:ff:ff:ff
inet 172.31.1.11/24 brd 172.31.1.255 scope global n6
valid_lft forever preferred_lft forever
inet6 fe80::b8ce:f600:17c:6b58/64 scope link
valid_lft forever preferred_lft forever
7: n4@tunl0: <BROADCAST,MULTICAST,UP,LOWER_UP,M-DOWN> mtu 1500 qdisc noqueue state UNKNOWN group default
link/ether 4c:52:62:65:c5:d4 brd ff:ff:ff:ff:ff:ff
inet 10.100.50.241/29 brd 10.100.50.247 scope global n4
valid_lft forever preferred_lft forever
inet6 fe80::4c52:6200:265:c5d4/64 scope link
valid_lft forever preferred_lft forever
8: upfgtp: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1464 qdisc noqueue state UNKNOWN group default qlen 1000
link/none
inet6 fe80::c9a2:a8e0:6916:9641/64 scope link stable-privacy
valid_lft forever preferred_lft forever
The free5GC helm install succeeds but cannot connect to the external NW. it appears that it is not tied to the Multus Master Interface. How to reslove this problems?
enviroment
bash output
If the Multus Master Interface is connected to the Multus Master Interface, it is recognized that XXX>@if<YYY is displayed, but it appears to be displayed incorrectly.
Also pod cannot connect to open network.