ok. so some updates.
Ben fixed this in the cloud image build process via [1] (commit [2]), and limited the change to utopic+.
The fix was done by adding a file /etc/sysctl.d/99-cloudimg-ipv6.conf
The problem with this change is described in bug 1352255 and bug 994931. If ipv6 addresses are already configured, then setting the 'net.ipv6.conf.all.use_tempaddr' will remove the configured addresses.
So to actually fix this right, I suggest that the build proces:
* dpkg-divert /etc/sysctl.d/10-ipv6-privacy.conf to /etc/sysctl.d/10-ipv6-privacy.conf.disabled
* add a file /etc/sysctl.d/10-ipv6-privacy.conf.README that explains that and how the user could re-enable it (un-dpkg-divert it).
ok. so some updates. d/99-cloudimg- ipv6.conf
Ben fixed this in the cloud image build process via [1] (commit [2]), and limited the change to utopic+.
The fix was done by adding a file /etc/sysctl.
The problem with this change is described in bug 1352255 and bug 994931. If ipv6 addresses are already configured, then setting the 'net.ipv6. conf.all. use_tempaddr' will remove the configured addresses.
So to actually fix this right, I suggest that the build proces: d/10-ipv6- privacy. conf to /etc/sysctl. d/10-ipv6- privacy. conf.disabled d/10-ipv6- privacy. conf.README that explains that and how the user could re-enable it (un-dpkg-divert it).
* dpkg-divert /etc/sysctl.
* add a file /etc/sysctl.
-- bazaar. launchpad. net/~ubuntu- on-ec2/ vmbuilder/ automated- ec2-builds/ view/head: /live-config/ common/ hooks/060- ipv6.chroot bazaar. launchpad. net/~ubuntu- on-ec2/ vmbuilder/ automated- ec2-builds/ revision/ 646
[1] http://
[2] http://