From mboxrd@z Thu Jan 1 00:00:00 1970 From: Florian Westphal Subject: Re: [RFC] connlimit for nftables and limiting ct count by zone Date: Wed, 1 Nov 2017 02:26:00 +0100 Message-ID: <20171101012600.GE7663@breakpoint.cc> References: <20171016144254.GA3728@breakpoint.cc> <20171030104018.GA6593@breakpoint.cc> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Florian Westphal , netfilter-devel@vger.kernel.org, YiHung Wei , Justin Pettit , Joe Stringer To: Yi-Hung Wei Return-path: Received: from Chamillionaire.breakpoint.cc ([146.0.238.67]:50110 "EHLO Chamillionaire.breakpoint.cc" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752175AbdKAB00 (ORCPT ); Tue, 31 Oct 2017 21:26:26 -0400 Content-Disposition: inline In-Reply-To: Sender: netfilter-devel-owner@vger.kernel.org List-ID: Yi-Hung Wei wrote: > > Really? So far my impression was that ovs does not wish > > to interact with nft in any way. > I was thinking about how to use nft to get and the ct limit and ct > count not by ovs tho. Say a nft user may want to know how many active > connections are there in a particular zone. They can do that with the conntrack tool ("conntrack -L --zone 42"), we can extend the filtering capabilties if needed.