[2.1 IPv6] IPv6 commissioning needs to aggregate /128 CIDRs from DHCP addresses
Bug #1625847 reported by
LaMont Jones
This bug report is a duplicate of:
Bug #1639288: [2.1] IPv6 autoconf addresses should not show up on the interface.
Edit
Remove
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Triaged
|
Critical
|
LaMont Jones |
Bug Description
DHCPv6 delivers /128 IPs to the client, which are not used for on-link decisions. As such, the client is on the subnet that maas assigned addresses from the dynamic range of, and maas should not create a /128 subnet when processing the commissioning report, but rather recognize that it's an IP from the dynamic range of the given network and attach it accordingly.
Changed in maas: | |
assignee: | nobody → LaMont Jones (lamont) |
summary: |
- IPv6 commissioning needs to aggregate /128 networks + IPv6 commissioning needs to aggregate /128 CIDRs from DHCP addresses |
Changed in maas: | |
status: | New → Confirmed |
importance: | Undecided → Critical |
milestone: | none → 2.1.0 |
Changed in maas: | |
status: | Confirmed → Triaged |
summary: |
- IPv6 commissioning needs to aggregate /128 CIDRs from DHCP addresses + [2.1 IPv6] IPv6 commissioning needs to aggregate /128 CIDRs from DHCP + addresses |
Changed in maas: | |
milestone: | 2.1.0 → 2.1.1 |
Changed in maas: | |
milestone: | 2.1.1 → 2.1.2 |
Changed in maas: | |
milestone: | 2.1.2 → 2.1.3 |
description: | updated |
To post a comment you must log in.
MAAS should not presume a prefix length based on an observed IPv6 address - full stop. To do this the correct way we should run something like radvdump before bringing up each interface so we can observe the advertised RAs after each interface sends its ICMPv6 router solicitation. (and/or look at something like `ip -6 route` to determine the on-link prefixes.)