Previously, the ipset_manager would pass in 0.0.0.0/0 or ::/0 if
these addresses were inputted as allowed address pairs. This causes
ipset to raise an error as it does not work with zero prefix sizes.
To solve this problem we use two ipset rules to represent this:
Ipv4: 0.0.0.0/1 and 128.0.0.1/1
IPv6: ::/1' and '8000::/1
All of this logic is handled via _sanitize_addresses() in the ipset_manager
which is called to convert the input.
Reviewed: https:/ /review. openstack. org/194697 /git.openstack. org/cgit/ openstack/ neutron/ commit/ ?id=9ff6138c47c 95034ba845e9448 ddffd147b51f38
Committed: https:/
Submitter: Jenkins
Branch: stable/kilo
commit 9ff6138c47c9503 4ba845e9448ddff d147b51f38
Author: Aaron Rosen <email address hidden>
Date: Wed Jun 3 16:19:39 2015 -0700
Provide work around for 0.0.0.0/0 ::/0 for ipset
Previously, the ipset_manager would pass in 0.0.0.0/0 or ::/0 if
these addresses were inputted as allowed address pairs. This causes
ipset to raise an error as it does not work with zero prefix sizes.
To solve this problem we use two ipset rules to represent this:
Ipv4: 0.0.0.0/1 and 128.0.0.1/1
IPv6: ::/1' and '8000::/1
All of this logic is handled via _sanitize_ addresses( ) in the ipset_manager
which is called to convert the input.
Conflicts: agent/linux/ ipset_manager. py tests/unit/ agent/linux/ test_ipset_ manager. py
neutron/
neutron/
Change-Id: I8c6a08e0cf3b5b 5386fe03af9f217 4c666b8ac75
Closes-bug: 1461054