From: Kristian Evensen <kristian.evensen@gmail.com>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [PATCH RFC nf_conntrack_tcp] Export ip_ct_tcp_state variables to userspace
Date: Tue, 17 Dec 2013 15:50:59 +0100 [thread overview]
Message-ID: <CAKfDRXgS7HQNcSo24f8hp3rPDeRPxWMn6e00Gtn9A8bj3c_Zzg@mail.gmail.com> (raw)
In-Reply-To: <20131217143059.GA13342@localhost>
On Tue, Dec 17, 2013 at 3:30 PM, Pablo Neira Ayuso <pablo@netfilter.org> wrote:
> I still don't see how that information can be useful to be included in
> that output as it changes very fast and by polling you will only get
> stale snapshots of what it's actually happening in the TCP tracking
> subsystem.
Yes, this tool would be most useful for somewhat long-living TCP
connections. One idea I had was to correlate the development of max
ack/end with number of TCP bytes sent/received over a single link.
Little development in the sequence numbers, but large amounts of data
transferred could be used as an indication of a problematic link.
However, the more I think about it, this will be a very complicated
and unreliable solution, at least when scaled up.
Thanks for your help, back to the drawing board for me :)
-Kristian
prev parent reply other threads:[~2013-12-17 14:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-14 16:46 [PATCH RFC nf_conntrack_tcp] Export ip_ct_tcp_state variables to userspace Kristian Evensen
2013-12-17 13:16 ` Pablo Neira Ayuso
2013-12-17 14:22 ` Kristian Evensen
2013-12-17 14:30 ` Pablo Neira Ayuso
2013-12-17 14:50 ` Kristian Evensen [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=CAKfDRXgS7HQNcSo24f8hp3rPDeRPxWMn6e00Gtn9A8bj3c_Zzg@mail.gmail.com \
--to=kristian.evensen@gmail.com \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.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).