All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pablo Neira Ayuso <pablo@netfilter.org>
To: James <vger_tracker@trackivity.com>
Cc: netfilter@vger.kernel.org
Subject: Re: set ipv4_addr interval timeout?
Date: Mon, 16 Jan 2017 17:28:56 +0100	[thread overview]
Message-ID: <20170116162856.GA2479@salvia> (raw)
In-Reply-To: <186719b4-eedb-80aa-232c-11f07e4ebcc8@trackivity.com>

On Fri, Jan 06, 2017 at 08:18:11PM -0500, James wrote:
> http://git.netfilter.org/nftables/tree/src/parser_bison.y#n1171 (and especially #n1206 and #n1213)
> 
> would seem to indicate that the following should work... *is* it supposed to work?
> 
> uname -a
> Linux pc 4.8.0-32-generic #34-Ubuntu SMP Tue Dec 13 14:30:43 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
> nft --version
> nftables v0.7 (Scrooge McDuck)
> nft flush ruleset
> nft list ruleset
> nft add table inet firewall
> nft add set inet firewall v4timeoutintervals { type ipv4_addr\; flags interval\; timeout 1h\; }
> <cmdline>:1:1-89: Error: Could not process rule: Operation not supported
> add set inet firewall v4timeoutintervals { type ipv4_addr; flags interval; timeout 1h; }
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> 
> Either interval or timeout alone works but interval and timeout together don't.
> 
> Basically, it seems that you can't use timeouts for subnets.

Yes.

Combination of intervals and timeouts is not yet implemented. Please,
file a bug at netfilter's bugzilla so we can keep track of this
enhancement request:

        https://bugzilla.netfilter.org/

Thanks!

      reply	other threads:[~2017-01-16 16:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-07  1:18 set ipv4_addr interval timeout? James
2017-01-16 16:28 ` Pablo Neira Ayuso [this message]

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=20170116162856.GA2479@salvia \
    --to=pablo@netfilter.org \
    --cc=netfilter@vger.kernel.org \
    --cc=vger_tracker@trackivity.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.