All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: yihung.wei@gmail.com
Cc: netdev@vger.kernel.org, pshelar@ovn.org, pablo@netfilter.org
Subject: Re: [PATCH net-next v4 2/2] openvswitch: Add timeout support to ct action
Date: Thu, 28 Mar 2019 16:53:51 -0700 (PDT)	[thread overview]
Message-ID: <20190328.165351.1065732694970405396.davem@davemloft.net> (raw)
In-Reply-To: <1553625074-20756-2-git-send-email-yihung.wei@gmail.com>

From: Yi-Hung Wei <yihung.wei@gmail.com>
Date: Tue, 26 Mar 2019 11:31:14 -0700

> Add support for fine-grain timeout support to conntrack action.
> The new OVS_CT_ATTR_TIMEOUT attribute of the conntrack action
> specifies a timeout to be associated with this connection.
> If no timeout is specified, it acts as is, that is the default
> timeout for the connection will be automatically applied.
> 
> Example usage:
> $ nfct timeout add timeout_1 inet tcp syn_sent 100 established 200
> $ ovs-ofctl add-flow br0 in_port=1,ip,tcp,action=ct(commit,timeout=timeout_1)
> 
> CC: Pravin Shelar <pshelar@ovn.org>
> CC: Pablo Neira Ayuso <pablo@netfilter.org>
> Signed-off-by: Yi-Hung Wei <yihung.wei@gmail.com>
> ---
> v1-> v2: Utilize nf_ct_set_timeout().
> v2-> v4: No change in this patch, the build issue is resolved by patch 1.

Applied.

  parent reply	other threads:[~2019-03-28 23:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-26 18:31 [PATCH net-next v4 1/2] netfilter: Export nf_ct_{set,destroy}_timeout() Yi-Hung Wei
2019-03-26 18:31 ` [PATCH net-next v4 2/2] openvswitch: Add timeout support to ct action Yi-Hung Wei
2019-03-27 18:24   ` Pravin Shelar
2019-03-28 23:53   ` David Miller [this message]
2019-03-27 18:24 ` [PATCH net-next v4 1/2] netfilter: Export nf_ct_{set,destroy}_timeout() Pravin Shelar
2019-03-28 23:53 ` David Miller

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=20190328.165351.1065732694970405396.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=netdev@vger.kernel.org \
    --cc=pablo@netfilter.org \
    --cc=pshelar@ovn.org \
    --cc=yihung.wei@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.