Hi, Fully supporting that forcing DHCPv4 or static IPv4 is no longer the optimal config. IMHO we should have options:
- no address give => just use inet6 auto (maybe even default to DHCPv4 in parallel too - OPTIONALLY!) That will be using full autoconfig with privacy extensions by default and "just get some connectivity" online - The --ip should understand both IPv6 and IPv4. If multiple arguments are given, the secondaries should be auto added (i.e. allowing to describe dual-stack) - The --netmask should default to 64 for IPv6 addresses and be optional if --ip is IPv6 - The --broadcast isn't really required anyway. Might be ditched - The --nameservers should be accepting both IPv4 and IPv6 - A new --dhcpv6 should allow for both stateless and stateful address assignment. For stateful a --duid should be added similar to the --mac to allow "predicing" the DHCP lease. - Additionally to using RA+SLAAC+privacy it would be cool to have an option to use a known prefix (e.g. the local prefix) and just dynamically generate a "random" IPv6 that is then used statically (like the dynamically generated root password) using a generator just like http://www.infracaninophile.co.uk/articles/hotchpotch/rand-aaaa.pl Maybe the prefix of the local interface on the Xen host should be default if no other option is configured. Thanks! Kilian
