Jakub Libosvar d6bfd091b9 ovs-fw: Clear conntrack information before egress pipeline ... In case where Neutron logical port is placed directly to hypervisor, hypervisor does a conntrack lookup before packets reach OVS integration bridge. This patch introduces a rule with high priority that is placed at the beginning of the egress pipeline. This rule removes conntrack information from all packets if conntrack information is present. Then packets continue in the egress pipeline. That means all packets in egress pipeline are not tracked and ovs firewall can do a lookup in correct zone. As for ingress pipeline, it distinguishes between tracked - which are packets coming from egress pipeline, and not tracked, which are inbound packets coming not from a local port. Change-Id: Ia4f524adce2b5ee6d98d3921cfb03d56ad6d0813 Closes-bug: #1747082 (cherry picked from commit 3327db80be)		2018-03-21 11:00:50 +00:00
..
source	ovs-fw: Clear conntrack information before egress pipeline	2018-03-21 11:00:50 +00:00
Makefile	Merge from launchpad quantum/diablo branch:	2011-09-23 20:17:44 -07:00