Re: [RFC net-next 3/4] openvswitch: Add conntrack action.

On 14 February 2015 at 00:13, Joe Stringer [off-list ref] wrote:

From: Justin Pettit <redacted>

Expose the kernel connection tracker to OVS. Userspace components can
make use of the "conntrack()" action, followed by "recirculate", to
populate the conntracking state in the OVS flow key, and subsequently
match on that state.

IP fragment handling is yet to be addressed, for the time being we pass
fragments through to conntrack directly, which I expect will result in
the connection being identified as "invalid".

Zone support added by Thomas Graf [off-list ref]

Signed-off-by: Justin Pettit <redacted>
Signed-off-by: Joe Stringer <redacted>
---
This is mostly a tidyup and port across to net-next from the previous
version of this patch. Newly added is ability to match on zones, adding
support for matching connections that cannot be identified ("invalid"),
and more testing in the userspace component which is available here:

https://www.github.com/justinpettit/openvswitch conntrack

That is,  https://www.github.com/justinpettit/ovs conntrack