Routed network is checking IP address available on parent network

Hi,

I configured a routed network, it looks very promising.
Nevertheless, there are annoying messages in lxd.log msg="Failed checking IP address available on parent network"

time="2022-09-06T09:41:38+03:00" level=warning msg="Failed checking IP address available on parent network" IP=x.x.x.125 device=eth0 driver=nic err="iface: 'bond0.220' can't reach ip: 'x.x.x.125'" instance=c3 parent=bond0.220 project=default
time="2022-09-06T09:41:38+03:00" level=warning msg="Failed checking IP address available on parent network" IP=x.x.x.126 device=eth0 driver=nic err="iface: 'bond0.220' can't reach ip: 'x.x.x.126'" instance=c3 parent=bond0.220 project=default
time="2022-09-06T09:41:38+03:00" level=warning msg="Failed checking IP address available on parent network" IP=x.x.x.7 device=eth0 driver=nic err="iface: 'bond0.220' can't reach ip: 'x.x.x.7'" instance=c3 parent=bond0.220 project=default
time="2022-09-06T09:42:08+03:00" level=warning msg="Failed checking IP address available on parent network" IP=x.x.x.125 device=eth0 driver=nic err="iface: 'bond0.220' can't reach ip: 'x.x.x.125'" instance=c3 parent=bond0.220 project=default
time="2022-09-06T09:42:08+03:00" level=warning msg="Failed checking IP address available on parent network" IP=x.x.x.7 device=eth0 driver=nic err="iface: 'bond0.220' can't reach ip: 'x.x.x.7'" instance=c3 parent=bond0.220 project=default
time="2022-09-06T09:42:08+03:00" level=warning msg="Failed checking IP address available on parent network" IP=x.x.x.126 device=eth0 driver=nic err="iface: 'bond0.220' can't reach ip: 'x.x.x.126'" instance=c3 parent=bond0.220 project=default

I understand why but is there any option to disable such warnings, or it should be simply ignored?

“Issue” found.
To remove this check container shouldn’t be attached to a parent interface.
In case it was added earlier, simply remove it from container config
lxc config device unset c2 eth0 parent
This also makes true L3 connection to all containers.

1 Like

I got that too, restarted the container and it has worked without removing the parent.
So gradually just ignored that message.