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, netfilter-devel@vger.kernel.org,
Andy Zhou <azhou@nicira.com>
Subject: Re: [PATCHv5 net-next 05/10] openvswitch: Add conntrack action
Date: Tue, 25 Aug 2015 20:25:27 +0200 [thread overview]
Message-ID: <20150825182527.GJ3707@pox.localdomain> (raw)
In-Reply-To: <1440462740-23358-6-git-send-email-joestringer@nicira.com>
On 08/24/15 at 05:32pm, Joe Stringer wrote:
> Expose the kernel connection tracker via OVS. Userspace components can
> make use of the CT action to populate the connection state (ct_state)
> field for a flow. This state can be subsequently matched.
>
> Exposed connection states are OVS_CS_F_*:
> - NEW (0x01) - Beginning of a new connection.
> - ESTABLISHED (0x02) - Part of an existing connection.
> - RELATED (0x04) - Related to an established connection.
> - INVALID (0x20) - Could not track the connection for this packet.
> - REPLY_DIR (0x40) - This packet is in the reply direction for the flow.
> - TRACKED (0x80) - This packet has been sent through conntrack.
>
> When the CT action is executed by itself, it will send the packet
> through the connection tracker and populate the ct_state field with one
> or more of the connection state flags above. The CT action will always
> set the TRACKED bit.
>
> When the COMMIT flag is passed to the conntrack action, this specifies
> that information about the connection should be stored. This allows
> subsequent packets for the same (or related) connections to be
> correlated with this connection. Sending subsequent packets for the
> connection through conntrack allows the connection tracker to consider
> the packets as ESTABLISHED, RELATED, and/or REPLY_DIR.
>
> The CT action may optionally take a zone to track the flow within. This
> allows connections with the same 5-tuple to be kept logically separate
> from connections in other zones. If the zone is specified, then the
> "ct_zone" match field will be subsequently populated with the zone id.
>
> 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>
Acked-by: Thomas Graf <tgraf@suug.ch>
next prev parent reply other threads:[~2015-08-25 18:25 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-25 0:32 [PATCHv5 net-next 00/10] OVS conntrack support Joe Stringer
2015-08-25 0:32 ` [PATCHv5 net-next 01/10] openvswitch: Serialize acts with original netlink len Joe Stringer
2015-08-25 18:23 ` Thomas Graf
2015-08-25 0:32 ` [PATCHv5 net-next 02/10] openvswitch: Move MASKED* macros to datapath.h Joe Stringer
2015-08-25 0:32 ` [PATCHv5 net-next 03/10] ipv6: Export nf_ct_frag6_gather() Joe Stringer
2015-08-25 19:15 ` Pravin Shelar
2015-08-25 0:32 ` [PATCHv5 net-next 04/10] dst: Add __skb_dst_copy() variation Joe Stringer
2015-08-25 18:23 ` Thomas Graf
2015-08-25 0:32 ` [PATCHv5 net-next 05/10] openvswitch: Add conntrack action Joe Stringer
2015-08-25 18:25 ` Thomas Graf [this message]
2015-08-25 19:22 ` Pravin Shelar
2015-08-25 0:32 ` [PATCHv5 net-next 06/10] openvswitch: Allow matching on conntrack mark Joe Stringer
2015-08-25 18:27 ` Thomas Graf
2015-08-25 20:34 ` Pravin Shelar
2015-08-25 0:32 ` [PATCHv5 net-next 07/10] netfilter: Always export nf_connlabels_replace() Joe Stringer
2015-08-25 0:32 ` [PATCHv5 net-next 08/10] netfilter: connlabels: Export setting connlabel length Joe Stringer
2015-08-25 0:32 ` [PATCHv5 net-next 09/10] openvswitch: Allow matching on conntrack label Joe Stringer
2015-08-25 18:29 ` Thomas Graf
2015-08-25 20:44 ` Pravin Shelar
2015-08-25 0:32 ` [PATCHv5 net-next 10/10] openvswitch: Allow attaching helpers to ct action Joe Stringer
2015-08-25 18:33 ` Thomas Graf
2015-08-25 20:10 ` Joe Stringer
2015-08-25 20:46 ` 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=20150825182527.GJ3707@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=netfilter-devel@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).