Ryan, Thank you so much for taking the time to go over the constraints and competing goals. It's always helpful to know what constituencies are involved.
> That said, I do think that cloud-init can make it easier to enable ipv6 where > it's desired (but without having to write your own network config). We're > looking into supporting a kernel parameter or cloud-config option to enable > the default config to block on ipv6 (note, we cannot use user-data to indicate > this preference as user-data is processed after networking is up as user-data > can be fetched via network URL). I think this would be a good compromise to get things moving. In my case of downloading the cloud image and specifying NoCloudNet via the SMBIOS serial number option, another key might be the simplest path. Something like: n=4 : configure IPv4 only (default now) n=6 : configure IPv6 only n=64 : configure both stacks I might then pass in: ds=nocloud-net;n=6;h=cloudtest;i=iid-local01;s=http://gemini.home.nivex.net/cidata/ Of course it's easy for me to throw out such a suggestion since I don't know how much is involved in the codebase. Is this something that might be doable in the near future? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1878682 Title: IPv6 not enabled by default To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1878682/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
