Non-EUI64 fixed IPs should be rejected for IPv6 SLAAC
Bug #1369767 reported by
Dane LeBlanc
This bug report is a duplicate of:
Bug #1330826: Neutron network:dhcp port is not assigned EUI64 IPv6 address for SLAAC subnet.
Edit
Remove
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| neutron |
In Progress
|
Undecided
|
Dane LeBlanc | ||
Bug Description
When a port is created on a subnet that is configured for IPv6 SLAAC, that port's IP address will be automatically generated (to a pre-determined value) using the EUI64 address algorithm, based on the subnet's IPv6 prefix and the port's MAC address. Therefore, any port create requests that include a fixed IPv6 address that does not match the expected IPv6 EUI64 address should be rejected.
| Changed in neutron: | |
| assignee: | nobody → Dane LeBlanc (leblancd) |
| summary: |
- Fixed IPs that do not match EUI64 should be rejected for IPv6 SLAAC - subnets + Non-EUI64 fixed IPs should be rejected for IPv6 SLAAC |
Revision history for this message
| Xu Han Peng (xuhanp) wrote | #1 |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix proposed to neutron (master) | #2 |
| Changed in neutron: | |
| status: | New → In Progress |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Change abandoned on neutron (master) | #3 |
To post a comment you must log in.
I think this patch already cover the fix for this problem: https:/
This patch checks if fixed IP address is specified for a IPv6 subnet with address mode slaac or dhcpv6-stateless
during creating or updating a port. If yes, raise InvalidInput error to stop the port creation or update.