Comment 3 for bug 1635716
Revision history for this message
| Mathieu Trudel-Lapierre (cyphermox) wrote | #3 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
net-eth0.conf:
DEVICE=eth0
HOSTNAME=mysystem
IPV4ADDRESS=
[...]
net6-eth0.conf:
DEVICE=eth0
HOSTNAME=mysystem
IPV6ADDRESS=
[...]
The concept of DEVICE, HOSTNAME, and DNSDOMAIN are universal; DHCP may provide a hostname and domain name as a response when assigning an IP address, and the device used can be useful to have in both the IPv4 and IPv6 case -- we should assume that anything that is relevant to IPv4 that isn't specific to IPv4 will still be relevant in the world of IPv6 for any software that expects to bring up a remote rootfs.
If cloud-init is making an assumption that a specific key such as DEVICE is specific to IPv4, that is an incorrect assumption and needs to be fixed to properly support IPv6 in a separate file than IPv4 settings in the initramfs.