← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1356926] [NEW] ipv6 subnet reserves 2 addresses in allocation pool

 

Public bug reported:

consider this table:

125::/125      | {"start": "125::1", "end": "125::6"}      |
126::/126      | {"start": "126::1", "end": "126::2"}      |
127::/127      |                                                                    |
128::/128      |                                                                    |

all those  subnets created with 
neutron subnet-create --ip_version 6 --disable-dhcp --no-gateway NETWORK CIDR

You see that ::0 and the largest address in CIDR are reserved.
This is similar to ipv4 where we have network address and broadcast address, while
according to http://www.iana.org/assignments/ipv6-interface-ids/ipv6-interface-ids.xhtml there should be no this reservation for ipv6.
Situation for prefixes 127 and 128 even worse, no addresses at all.

** Affects: neutron
     Importance: Undecided
         Status: New


** Tags: ipv6

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1356926

Title:
  ipv6 subnet reserves 2 addresses in allocation pool

Status in OpenStack Neutron (virtual network service):
  New

Bug description:
  consider this table:

  125::/125      | {"start": "125::1", "end": "125::6"}      |
  126::/126      | {"start": "126::1", "end": "126::2"}      |
  127::/127      |                                                                    |
  128::/128      |                                                                    |

  all those  subnets created with 
  neutron subnet-create --ip_version 6 --disable-dhcp --no-gateway NETWORK CIDR

  You see that ::0 and the largest address in CIDR are reserved.
  This is similar to ipv4 where we have network address and broadcast address, while
  according to http://www.iana.org/assignments/ipv6-interface-ids/ipv6-interface-ids.xhtml there should be no this reservation for ipv6.
  Situation for prefixes 127 and 128 even worse, no addresses at all.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1356926/+subscriptions


Follow ups

References