Ok, so just had a pretty good chat with Martin, conclusion is that we will: - Make use of the debconf "seen" flag to check whether we are running interactively or not - If running interactively and no configuration was previously set, set both IPv4 and IPv6 to "yes" - Show a warning message to the user in both the IPv4 and IPv6 case telling them that a random subnet was picked for them and that if it's used somewhere on their network, they will need to change it to something else. - Show the user the pre-filled values.
The intent is that a user can just keep pressing enter in dpkg- reconfigure and they'll be getting working IPv4 and IPv6 connectivity. However a non-interactive clean package install WILL NOT pick any subnet and so will not risk breaking connectivity for the user. When saying "random" above, we will make a best effort to pick something that's not already in use but make no promises at succeeding, so that's why we will keep referring to it as "random". -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1567440 Title: debconf for bridge configuration is confusing and too complicated To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1567440/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
