I am trying to make some initial configuration through RESTful plugin. My vpp version is 22.10 and it has 2 DPDK interfaces TGE1 and TGE2. I'm using the linux-cp plugin of VPP. I hope to create a loopback interface, but the ligato seems not support linux-cp plugin configuration, so I write the lcp create command in the bootstrap.vpp file, and in my vpp.conf, I use exec bootstrap.vpp to execute the commands when vpp starting.
However, I found that the ip addresses of TGE1 and TGE2 were configured correctly, but loop0 wasn't configured. Actually, when I use vppctl show int addr, I found a new loopback loop1 was created and configured with the ip addresses of loop0. The loop0 and the host-interface loop0 created by linux-cp stayed down and unconfigured.
I tried to solve the problem. I dumped the interfaces with the RESTful api, and found that the name of loop0 is actually UNTAGGED-loop0. I modified the YAML configuration above but it didn't work. The behavior was almost same: a new loopback interface was created and configured, but the original loop0 wasn't.
Is this a BUG of ligato or my YAML configuration is wrong? How can I configure a existed loopback interface rather than create a new one?
I am trying to make some initial configuration through RESTful plugin. My vpp version is 22.10 and it has 2 DPDK interfaces
TGE1
andTGE2
. I'm using the linux-cp plugin of VPP. I hope to create a loopback interface, but the ligato seems not support linux-cp plugin configuration, so I write thelcp create
command in thebootstrap.vpp
file, and in myvpp.conf
, I useexec bootstrap.vpp
to execute the commands when vpp starting.My
bootstrap.vpp
is:Then I write a
init.yaml
and PUT it to the ligato RESTful plugin to configure the IP addresses and the states of the interfaces.However, I found that the ip addresses of TGE1 and TGE2 were configured correctly, but loop0 wasn't configured. Actually, when I use
vppctl show int addr
, I found a new loopbackloop1
was created and configured with the ip addresses of loop0. The loop0 and the host-interface loop0 created by linux-cp stayed down and unconfigured. I tried to solve the problem. I dumped the interfaces with the RESTful api, and found that the name ofloop0
is actuallyUNTAGGED-loop0
. I modified the YAML configuration above but it didn't work. The behavior was almost same: a new loopback interface was created and configured, but the originalloop0
wasn't.Is this a BUG of ligato or my YAML configuration is wrong? How can I configure a existed loopback interface rather than create a new one?