Consider supporting IPv6 autoconf in configure_networking

Bug #1632808 reported by LaMont Jones
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
MAAS
Invalid
Undecided
Unassigned
initramfs-tools (Ubuntu)
Triaged
Medium
Mathieu Trudel-Lapierre

Bug Description

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.

Tags: maas-ipv6
LaMont Jones (lamont)
tags: added: maas-ipv6
Revision history for this message
Scott Moser (smoser) wrote :

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'.

Revision history for this message
Mathieu Trudel-Lapierre (cyphermox) wrote :

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

Changed in initramfs-tools (Ubuntu):
status: New → Triaged
importance: Undecided → Medium
assignee: nobody → Mathieu Trudel-Lapierre (cyphermox)
Revision history for this message
LaMont Jones (lamont) wrote :

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

Changed in maas:
status: New → Fix Released
summary: - configure_networking exits without any ipv6 routes
+ Consider supporting IPv6 autoconf in configure_networking
Changed in maas:
status: Fix Released → Triaged
Revision history for this message
LaMont Jones (lamont) wrote :

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

Revision history for this message
LaMont Jones (lamont) wrote :

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.

Revision history for this message
Newell Jensen (newell-jensen) wrote :

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

Changed in maas:
status: Triaged → Confirmed
status: Confirmed → Triaged
Changed in maas:
status: Triaged → Confirmed
Revision history for this message
Adam Collard (adam-collard) wrote :

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

Changed in maas:
status: Confirmed → Invalid
Revision history for this message
Dimitri John Ledkov (xnox) wrote :

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

Revision history for this message
A Shah (ashphx) wrote :

Is there any status updates on this ?

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.