Consider supporting IPv6 autoconf in configure_networking

[LaMont Jones]

Because DHCPv6 only does addresses, and not routes, configure_networking needs to wait for the kernel to process a router-advertisement before returning claiming an IPv6 config (since all it will have is a /128 and no routes, making for a pretty useless network stack.) See Bug #1609898 for context.

(The syntax for ip= should probably also be extended to allow SLAAC configuration. If the user said "dhcp", then we should insist on getting our answer from DHCP.)

On the bright side, iscsi retries, so after 1 or more failures to connect, the router-advertisement comes in and the connect succeeds.

[Scott Moser (smoser)]

https://code.launchpad.net/~smoser/ubuntu/+source/initramfs-tools/+git/initramfs-tools/+ref/lp-1631010

there i added 'ip6=only' and 'ip6=only-S' (we can change the syntax), but '-S' means to pass '-S' to 'dhclient -6'.

[Mathieu Trudel-Lapierre (cyphermox)]

If we want to do this, let's use ip6=stateless or ip6=dhcp rather than only/only-S.

[LaMont Jones (lamont)]

Converting this to be the bug for ip6=stateless (or ip6=autoconf?), as the rest of it was solved with 1621507.

[LaMont Jones (lamont)]

And leaving it triaged for MAAS, since once initramfs-tools supports it, MAAS will need to propagate that to the UI.

[LaMont Jones (lamont)]

I am also not aware of anyone in the MAAS space who _wants_ autoconf for ipv6 networks. I am aware of at least one who wants it OFF for their networks.

[Newell Jensen (newell-jensen)]

Triaging script set to "Confirmed" but setting back to "Triaged" per Lamont's #4 comment.

[Adam Collard (adam-collard)]

This bug has not seen any activity in the last 6 months, so it is being automatically closed.

If you are still experiencing this issue, please feel free to re-open.

MAAS Team

[Dimitri John Ledkov (xnox)]

What about static ipv6? does that make sense? Because i think at least IBM has asked to support this before.

[A Shah (ashphx)]

Is there any status updates on this ?