netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Kevin Cernekee <cernekee@chromium.org>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: Snooping expected connections in a user CT helper
Date: Fri, 9 Sep 2016 12:47:55 +0200	[thread overview]
Message-ID: <20160909104755.GA9943@salvia> (raw)
In-Reply-To: <20160908221824.GA28289@salvia>

On Fri, Sep 09, 2016 at 12:18:24AM +0200, Pablo Neira Ayuso wrote:
[...]
> > > 2) The timeout is not extended when there is activity on the
> > > expectation.  It would be good if it was extended any time there is
> > > new activity, in order to support long-lived subscriptions.
> 
> Actually, I thought permanent expectation has no timeout, but looking
> at the code it seems they do. I think it makes sense to refresh it or
> to keep it fixed, given that this depends on the master, it will just
> go away once the master is not there anymore.

Revisiting this: Actually, you are in control of the expectation time
too, so you can set a larger one given this is bound by the master
conntrack if you don't want to cook a patch to update this.

The question here is what are the reasonable timeouts to set, I guess
you can extract this from this application protocol behaviour or any
standard that document it.

      reply	other threads:[~2016-09-09 10:47 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-17  4:51 Snooping expected connections in a user CT helper Kevin Cernekee
2016-08-18  1:12 ` Pablo Neira Ayuso
2016-08-23  3:34   ` Kevin Cernekee
2016-08-23 15:36     ` Pablo Neira Ayuso
2016-09-01 23:47       ` Kevin Cernekee
2016-09-08 22:02         ` Kevin Cernekee
2016-09-08 22:18           ` Pablo Neira Ayuso
2016-09-09 10:47             ` 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=20160909104755.GA9943@salvia \
    --to=pablo@netfilter.org \
    --cc=cernekee@chromium.org \
    --cc=netfilter-devel@vger.kernel.org \
    /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).