<div dir="ltr"><div>Hello,<br><br></div>I have an LXC container with static IPv6 address configured like this:<br><div><div><br>lxc.network.type = veth<br>lxc.network.hwaddr = 00:16:3e:76:13:c6<br>lxc.network.flags = up<br>
lxc.network.link = br0<br>lxc.network.ipv6 = 2001:XXXX::XXXX:XXXX/64<br><br></div><div>For some reason, when I start the container, this static IPv6 address doesn't work. However the same interface (seen as eth0 within the container) picks another IPv6 address for itself from the MAC address, and that address works correctly. If I add any other addresses while the container is running, they work perfectly. When I delete the static address from the interface and then add it again, it works. But it doesn't work right after the container boots.<br>
<br></div><div>With tcpdump within the container, I determined that ICMP6 echo requests arrive to the container, but the container doesn't reply on that address. Any other addresses added after container bootup are properly pingable. This is really strange, as I experience this on the very same interface.<br>
<br><br></div><div>$ ip -6 addr show<br></div><div><br>31: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qlen 1000<br> inet6 2001:XXXX::16:3eff:fe76:13c6/64 scope global dynamic <br> valid_lft 85692sec preferred_lft 13692sec<br>
inet6 2001:XXXX::XXXX:XXXX/64 scope global <br> valid_lft forever preferred_lft forever<br> inet6 fe80::216:3eff:fe76:13c6/64 scope link <br> valid_lft forever preferred_lft forever<br><br><br></div><div>
$ ip -6 route<br><br></div><div>2001:XXXX::/64 dev eth0 proto kernel metric 256 <br>fe80::/64 dev eth0 proto kernel metric 256 <br>default via fe80::XXXX:XXff:feXX:XXXX dev eth0 proto ra metric 1024 expires 423sec<br>
<br><br></div><div>/etc/network/interfaces - hopefully auto-generated, as I don't remember modifying it... however it's possible that I did:<br></div><div><br>auto eth0<br>iface eth0 inet dhcp<br><br>iface eth0 inet6 static<br>
address 2001:XXXX::XXXX:XXXX<br> netmask 64<br><br><br></div><div>Other containers those don't have a static IPv6 set up work correctly with SLAAC + privacy extensions.<br><br></div><div>I have no idea what might cause the container to not work with the statically set IPv6 address. Actually, I want it to only use this address, I don't even want it to pick the MAC-based address with SLAAC. I already disabled IPv6 privacy extensions within the container.<br>
<br></div><div>Is it an LXC bug or am I overlooking something?<br><br></div><div>Ask away if you'd like to see more data.<br><br><br></div><div>Regards,<br></div><div>MegaBrutal<br></div></div></div>