All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: Patrick McHardy <kaber@trash.net>, netfilter-devel@vger.kernel.org
Subject: Re: flow start_time
Date: Wed, 06 May 2009 13:26:07 +0200	[thread overview]
Message-ID: <4A0173CF.6080505@netfilter.org> (raw)
In-Reply-To: <4A016F74.6050601@msgid.tls.msk.ru>

Michael Tokarev wrote:
> Patrick McHardy wrote:
>> How are you going to log the data of a connection thats removed
>> from the conntrack tables without using netlink? If you're using
>> netlink, you can generate a time stamp when you receive a NEW
>> event.
> 
> In case either "new" or "remove" event is missing now, that connection
> can't be logged properly, because we don't see some part of the
> info in either of the two cases.
> 
> For nowadays tools, in case we've seen "new" but not "remove" event,
> that connection will be in our hash table sorta forever (ok, till
> restart).  Which is, I think, worse than not logging it at all (it
> will not be logged anyway).
> 
> Basically, I don't see such a case (lost "remove" event) as valid.

I have a couple of patches here that I'm still working on it here to
avoid "remove" event loss. It should be ready for review once the
nf-next-2.6 tree is open.

To know when a flow starts and avoid the problem of "new" event loss. I
think that we can still add a conntrack extension to store the start
time. I think that's enough, right?

-- 
"Los honestos son inadaptados sociales" -- Les Luthiers

  reply	other threads:[~2009-05-06 11:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-23 15:32 flow start_time Michael Tokarev
2009-05-05 13:58 ` Patrick McHardy
2009-05-06 11:07   ` Michael Tokarev
2009-05-06 11:26     ` Pablo Neira Ayuso [this message]
2009-05-06 11:47       ` Michael Tokarev

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=4A0173CF.6080505@netfilter.org \
    --to=pablo@netfilter.org \
    --cc=kaber@trash.net \
    --cc=mjt@tls.msk.ru \
    --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 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.