From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Arturo Borrero Gonzalez <arturo.borrero.glez@gmail.com>
Cc: Netfilter Development Mailing list <netfilter-devel@vger.kernel.org>
Subject: Re: [conntrackd] allowing DisableExternalCache in alarm mode
Date: Tue, 1 Sep 2015 18:44:21 +0200 [thread overview]
Message-ID: <20150901164421.GA3320@salvia> (raw)
In-Reply-To: <CAOkSjBhxLk2beq70jZCTKtO8K09UcSj5jNh2H-9wvCzSL0XxeA@mail.gmail.com>
On Mon, Aug 31, 2015 at 09:55:23AM +0200, Arturo Borrero Gonzalez wrote:
> On 28 August 2015 at 18:49, Pablo Neira Ayuso <pablo@netfilter.org> wrote:
> >
> > Are these FTP data flows? I'm asking this because the master
> > connection (control flow) may be missing in the conntrack table, thus
> > the ENOENT error.
>
> Makes sense.
>
> Would you consider accepting the patch?
I think you can fix the problem that you're noticing by extending
timer_add().
Note that the general idea behind the alarm approach is to insert a
timer with a random time wait in unit from 0..M seconds.
A quick workaround to address this is that master conntracks are
placed in the time range from 0..N/2, then you place non-master
conntrack entries in the range from N/2+1 to M. Then, unless there is
packet loss, most likely the expected conntrack will find the master
one.
It should be just a few more extra lines away from this oneliner.
next prev parent reply other threads:[~2015-09-01 16:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-27 10:57 [conntrackd] allowing DisableExternalCache in alarm mode Arturo Borrero Gonzalez
2015-08-28 16:49 ` Pablo Neira Ayuso
2015-08-31 7:55 ` Arturo Borrero Gonzalez
2015-09-01 16:44 ` Pablo Neira Ayuso [this message]
2015-09-02 8:41 ` Arturo Borrero Gonzalez
2015-09-25 11:38 ` Arturo Borrero Gonzalez
2015-10-01 18:26 ` Pablo Neira Ayuso
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=20150901164421.GA3320@salvia \
--to=pablo@netfilter.org \
--cc=arturo.borrero.glez@gmail.com \
--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).