I did a fair amount of debug information including recreation with a
cloud image at lp:~smoser/+junk/lp-1377005 . I'll copy the final comment
here.
ok. so, i now know what happens, and why adding anything before the ipv6
address "fixes" the problem.
boot happens like this:
* system boot
* net-device-added fires network-interface.conf
* net-device-added runs ifup --allow auto
* ifup --allow auto reads /etc/network/interfaces *in order*
* after the *first* stanza is brought up, /etc/network/if-up.d/upstart is
invoked
* /etc/network/if-up.d/upstart finds all interfaces to be up and emits
static-network-up
* /etc/init/failsafe.conf is stopped, freeing procps.conf to start
* procps.conf runs sysctl on files in /etc/sysctl.d/*.conf
which includes /etc/sysctl.d/10-ipv6-privacy.conf
ipv6-privacy.conf ends up killing the existing addresses.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1352255
Title:
Impossible to configure network interface with only IPv6 address
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1352255/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
