subnetpool can create the cidr like 0.0.0.0/0

Bug #1483099 reported by zhaobo
6
This bug affects 1 person
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-94fc-4d43-bfcb-1098524092cd |
| ip_version | 4 |
| max_prefixlen | 32 |
| min_prefixlen | 8 |
| name | test3 |
| prefixes | 0.0.0.0/0 |
| shared | False |
| tenant_id | 2b47a754532a48a9a553964eb435cf0f |
+-------------------+--------------------------------------+

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-ec29-4221-9298-ce00ae276be4 |
| ip_version | 4 |
| ipv6_address_mode | |
| ipv6_ra_mode | |
| name | |
| network_id | 507aeb92-9b30-46ab-b2aa-da2ad13517e3 |
| subnetpool_id | b1bc9e6f-94fc-4d43-bfcb-1098524092cd |
| tenant_id | 2b47a754532a48a9a553964eb435cf0f |
+-------------------+----------------------------------------------+

So the subnetpool should not allow this special type of cidrs to be created.

zhaobo (zhaobo6)
Changed in neutron:
assignee: nobody → zhaobo (zhaobo6)
Revision history for this message
Ryan Tidwell (ryan-tidwell) wrote :

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.

Changed in neutron:
assignee: zhaobo (zhaobo6) → Ryan Tidwell (ryan-tidwell)
status: New → In Progress
Revision history for this message
Armando Migliaccio (armando-migliaccio) wrote :

This bug is > 240 days without activity. We are unsetting assignee and milestone and setting status to Incomplete in order to allow its expiry in 60 days.

If the bug is still valid, then update the bug status.

Changed in neutron:
assignee: Ryan Tidwell (ryan-tidwell) → nobody
status: In Progress → Incomplete
Changed in neutron:
assignee: nobody → ramesram (ramesh.rayapureddi)
Revision history for this message
Rodolfo Alonso (rodolfo-alonso-hernandez) wrote :

Bug closed due to lack of activity, please feel free to reopen if needed.

Changed in neutron:
status: Incomplete → Won't Fix
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.