From: Thomas Graf <tgraf@suug.ch>
To: Joe Stringer <joestringer@nicira.com>
Cc: netdev@vger.kernel.org, pshelar@nicira.com,
linux-kernel@vger.kernel.org, pablo@netfilter.org,
fwestpha@redhat.com, hannes@redhat.com, jpettit@nicira.com,
jesse@nicira.com, Andy Zhou <azhou@nicira.com>
Subject: Re: [PATCHv4 net-next 05/10] openvswitch: Add conntrack action
Date: Thu, 20 Aug 2015 18:21:48 +0200 [thread overview]
Message-ID: <20150820162148.GA5599@pox.localdomain> (raw)
In-Reply-To: <1439941188-19293-6-git-send-email-joestringer@nicira.com>
On 08/18/15 at 04:39pm, Joe Stringer wrote:
> Expose the kernel connection tracker via OVS. Userspace components can
> make use of the "ct()" action, followed by "recirculate", to populate
> the conntracking state in the OVS flow key, and subsequently match on
> that state.
>
> Example ODP flows allowing traffic from 1->2, only replies from 2->1:
> in_port=1,tcp,action=ct(commit,zone=1),2
> in_port=2,ct_state=-trk,tcp,action=ct(zone=1),recirc(1)
> recirc_id=1,in_port=2,ct_state=+trk+est-new,tcp,action=1
>
> IP fragments are handled by transparently assembling them as part of the
> ct action. The maximum received unit (MRU) size is tracked so that
> refragmentation can occur during output.
>
> IP frag handling contributed by Andy Zhou.
>
> Signed-off-by: Joe Stringer <joestringer@nicira.com>
> Signed-off-by: Justin Pettit <jpettit@nicira.com>
> Signed-off-by: Andy Zhou <azhou@nicira.com>
OVS bits look great.
Acked-by: Thomas Graf <tgraf@suug.ch>
next prev parent reply other threads:[~2015-08-20 16:21 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-18 23:39 [PATCHv4 net-next 00/10] OVS conntrack support Joe Stringer
2015-08-18 23:39 ` [PATCHv4 net-next 01/10] openvswitch: Serialize acts with original netlink len Joe Stringer
2015-08-18 23:39 ` [PATCHv4 net-next 02/10] openvswitch: Move MASKED* macros to datapath.h Joe Stringer
2015-08-18 23:39 ` [PATCHv4 net-next 03/10] ipv6: Export nf_ct_frag6_gather() Joe Stringer
2015-08-18 23:39 ` [PATCHv4 net-next 04/10] dst: Add __skb_dst_copy() variation Joe Stringer
2015-08-18 23:39 ` [PATCHv4 net-next 05/10] openvswitch: Add conntrack action Joe Stringer
2015-08-19 20:30 ` Pravin Shelar
2015-08-20 16:21 ` Thomas Graf [this message]
2015-08-18 23:39 ` [PATCHv4 net-next 06/10] openvswitch: Allow matching on conntrack mark Joe Stringer
2015-08-19 20:47 ` Pravin Shelar
2015-08-21 0:41 ` Joe Stringer
2015-08-18 23:39 ` [PATCHv4 net-next 07/10] netfilter: Always export nf_connlabels_replace() Joe Stringer
2015-08-19 20:47 ` Pravin Shelar
2015-08-20 16:22 ` Thomas Graf
2015-08-18 23:39 ` [PATCHv4 net-next 08/10] netfilter: connlabels: Export setting connlabel length Joe Stringer
2015-08-19 20:48 ` Pravin Shelar
2015-08-20 16:23 ` Thomas Graf
2015-08-18 23:39 ` [PATCHv4 net-next 09/10] openvswitch: Allow matching on conntrack label Joe Stringer
2015-08-19 21:24 ` Pravin Shelar
2015-08-19 23:04 ` Joe Stringer
2015-08-20 15:45 ` Pravin Shelar
2015-08-20 19:13 ` Joe Stringer
2015-08-20 21:01 ` Pravin Shelar
2015-08-21 0:40 ` Joe Stringer
2015-08-18 23:39 ` [PATCHv4 net-next 10/10] openvswitch: Allow attaching helpers to ct action Joe Stringer
2015-08-19 22:57 ` Pravin Shelar
2015-08-21 0:47 ` Joe Stringer
2015-08-21 17:39 ` Pravin Shelar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150820162148.GA5599@pox.localdomain \
--to=tgraf@suug.ch \
--cc=azhou@nicira.com \
--cc=fwestpha@redhat.com \
--cc=hannes@redhat.com \
--cc=jesse@nicira.com \
--cc=joestringer@nicira.com \
--cc=jpettit@nicira.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pablo@netfilter.org \
--cc=pshelar@nicira.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).