neutron/neutron/api/rpc/handlers
LIU Yulong bd6203b2c7 [Security] fix allowed-address-pair 0.0.0.0/0 issue
When add allowed-address-pair 0.0.0.0/0 to one port, it will
unexpectedly open all others' protocol under same security
group. IPv6 has the same problem.

The root cause is the openflow rules calculation of the
security group, it will unexpectedly allow all IP(4&6)
traffic to get through.

For openvswitch openflow firewall, this patch adds a source
mac address match for the allowed-address-pair which has
prefix lenght 0, that means all ethernet packets from this
mac will be accepted. It exactly will meet the request of
accepting any IP address from the configured VM.

Test result shows that the remote security group and
allowed address pair works:
1. Port has 0.0.0.0/0 allowed-address-pair clould send any
   IP (src) packet out.
2. Port has x.x.x.x/y allowed-address-pair could be accepted
   for those VMs under same security group.
3. Ports under same network can reach each other (remote
   security group).
4. Protocol port number could be accessed only when there
   has related rule.

Conflicts:
    neutron/tests/unit/agent/linux/openvswitch_firewall/test_rules.py

Closes-bug: #1867119
Change-Id: I2e3aa7c400d7bb17cc117b65faaa160b41013dde
(cherry picked from commit 00298fe6e8)
2020-07-31 13:31:18 +02:00
..
__init__.py RPC additions to support DVR 2014-07-17 11:45:45 -07:00
dhcp_rpc.py Optimize the code that fixes the race condition of DHCP agent. 2019-06-11 09:44:32 +08:00
dvr_rpc.py Revert "DVR: Inter Tenant Traffic between networks not possible with shared net" 2018-08-28 23:41:29 +00:00
l3_rpc.py Adding LOG statements to debug 1838449 2020-05-13 21:34:53 +00:00
metadata_rpc.py Wrong path of rpc_api.rst in class docstring 2017-10-11 23:57:06 +05:30
resources_rpc.py Don't assume RPC push object has an ID 2017-09-18 22:39:44 +00:00
securitygroups_rpc.py [Security] fix allowed-address-pair 0.0.0.0/0 issue 2020-07-31 13:31:18 +02:00