> If you are not providing any network config to cloud-init, current the
default fallback is to DHCP (ipv4) only
This is precisely the bug I am reporting.
> And for ipv6 config, I suspect you'll want to provide an netplan
config with:
In the year 2020, IPv6 should be a first class citizen and I should not
need to provide additional config for it to work right. The issue here
is not that I can't find a workaround to make my scenarios work. The
issue here is that I should not need any such workarounds on a modern
network.
** Changed in: cloud-init (Ubuntu)
Status: Incomplete => New
--
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
