subnetpool can create the cidr like 0.0.0.0/0
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Won't Fix
|
Undecided
|
ramesram |
Bug Description
neutron version : 2.6.0
I create subnetpool like:
neutron subnetpool-create --pool-prefix 6.6.66.6/24 --pool-prefix 99.9.9.9/30 --pool-prefix 8.9.8.8/20 --pool-prefix 0.0.0.0/0 --pool-prefix 0.0.0.0/16 test3
Created a new subnetpool:
+------
| Field | Value |
+------
| default_prefixlen | 8 |
| default_quota | |
| id | b1bc9e6f-
| ip_version | 4 |
| max_prefixlen | 32 |
| min_prefixlen | 8 |
| name | test3 |
| prefixes | 0.0.0.0/0 |
| shared | False |
| tenant_id | 2b47a754532a48a
+------
And then I create a subnet to network with this subnetpool like:
neutron subnet-create kl --subnetpool test3
Created a new subnet:
+------
| Field | Value |
+------
| allocation_pools | {"start": "0.0.0.2", "end": "0.255.255.254"} |
| cidr | 0.0.0.0/8 |
| dns_nameservers | |
| enable_dhcp | True |
| gateway_ip | 0.0.0.1 |
| host_routes | |
| id | 17b680d2-
| ip_version | 4 |
| ipv6_address_mode | |
| ipv6_ra_mode | |
| name | |
| network_id | 507aeb92-
| subnetpool_id | b1bc9e6f-
| tenant_id | 2b47a754532a48a
+------
So the subnetpool should not allow this special type of cidrs to be created.
Changed in neutron: | |
assignee: | nobody → zhaobo (zhaobo6) |
Changed in neutron: | |
assignee: | nobody → ramesram (ramesh.rayapureddi) |
Looks like we need to double-check the prefixes we allow into a s subnet pool more carefully. RFC 1700 says use of 0.0.0.0/8 is not supported. There's probably some IPv6 prefixes I'm not aware of that we might want to disallow allocation from.