Ideally it would be great to have full support for IPv6 IP assignment by DHCP. @marcos-mendez had a go at it in turnkeylinux/common#339 - using dhcpcd. But as I noted in turnkeylinux/common#339 (comment) unfortunately:
dhcpcd is not compatible with ifupdown & use of the /etc/network/interfaces file.
It also notes that static IPs need to be configured in /etc/dhcpcd.conf which changes our network config completely. And may not be compatible with setting static IPs with Proxmox LXC containers (when you set a static IP in PVE the PVE hosts modifies the LXC guest's /etc/network/interfaces).
My research suggests that our current stack should "just work" with SLAAC (Stateless Address Autoconfiguration) if we add this line to the interfaces file:
Also apparently ifupdown should already support IPv6 DHCP, but it still needs a DHCP client (and udhcpd only provides IPv4 DHCP). FWIW the interfaces file line is:
Possible alternate options:
dhcpcd-base (a dependency of dhcpcd) is apparently compatible with ifupdown//etc/network/interfaces file.
wide-dhcpv6-client - a DHCPv6 client that also apparently works alongside ifupdown for IPv6.
I'm not completely against moving to another DHCP client that uses a completely different config, but moving away from using ifupdown//etc/network/interfaces file will require a bit of work elsewhere to make it work with our existing tools - work that I'm not keep to embark on at this late stage of the v19.x dev cycle (& v19.0 is already WAY overdue...). And my above note re Proxmox also needs investigation and consideration.
Options that don't use ifupdown//etc/network/interfaces file:
dhcpcd - as proposed by @marcos-mendez - static interface conf goes in /etc/dhcpcd.conf`.
- [
systemd-networkd] - my feelings re systemd are mixed but AFAIK use of networkd would not require any additional packages. It uses .network files, which natively handle both IPv4 and IPv6.
I'd be particularly interested in your thoughts @marcos-mendez.
I'm also not sure what we should do with the changes we made to support IPv6 in Confconsole?! Perhaps we should roll that back for now? I imagine that the changes to IPv6 support in Webmin should be fine as-is?
Replaces: #1459
Ideally it would be great to have full support for IPv6 IP assignment by DHCP. @marcos-mendez had a go at it in turnkeylinux/common#339 - using
dhcpcd. But as I noted in turnkeylinux/common#339 (comment) unfortunately:It also notes that static IPs need to be configured in
/etc/dhcpcd.confwhich changes our network config completely. And may not be compatible with setting static IPs with Proxmox LXC containers (when you set a static IP in PVE the PVE hosts modifies the LXC guest's/etc/network/interfaces).My research suggests that our current stack should "just work" with SLAAC (Stateless Address Autoconfiguration) if we add this line to the interfaces file:
Also apparently
ifupdownshould already support IPv6 DHCP, but it still needs a DHCP client (andudhcpdonly provides IPv4 DHCP). FWIW the interfaces file line is:Possible alternate options:
dhcpcd-base(a dependency ofdhcpcd) is apparently compatible withifupdown//etc/network/interfacesfile.wide-dhcpv6-client- a DHCPv6 client that also apparently works alongsideifupdownfor IPv6.I'm not completely against moving to another DHCP client that uses a completely different config, but moving away from using
ifupdown//etc/network/interfacesfile will require a bit of work elsewhere to make it work with our existing tools - work that I'm not keep to embark on at this late stage of the v19.x dev cycle (& v19.0 is already WAY overdue...). And my above note re Proxmox also needs investigation and consideration.Options that don't use
ifupdown//etc/network/interfacesfile:dhcpcd- as proposed by @marcos-mendez - static interface conf goes in/etc/dhcpcd.conf`.systemd-networkd] - my feelings re systemd are mixed but AFAIK use of networkd would not require any additional packages. It uses.networkfiles, which natively handle both IPv4 and IPv6.I'd be particularly interested in your thoughts @marcos-mendez.
I'm also not sure what we should do with the changes we made to support IPv6 in Confconsole?! Perhaps we should roll that back for now? I imagine that the changes to IPv6 support in Webmin should be fine as-is?
Replaces: #1459