From: Alexey Mikhailov <karma@galois.botik.ru>
To: netfilter@vger.kernel.org
Cc: netfilter-devel@vger.kernel.org
Subject: Conntrack flow expirations
Date: Wed, 24 Sep 2008 10:38:57 +0400 [thread overview]
Message-ID: <877i929hfi.fsf@galois.botik.ru> (raw)
Hello!
I'm working on some accounting application based on connection tracking
subsytem. Basically, i just gather information from expired flows. But
there's problem, any TCP flow can live for 4 or 5 days for example, and
I need to get more or less real-time processing. So I want to have some
expiration mechanism. I need to:
a) I don't want flows to live more than 30 minutes
b) If flow is inactive for 15 secs I want to get it expired as well
So here comes my question, how do I specify expiration time-out for
long lived flows? I have found
net.ipv4.netfilter.ip_conntrack_tcp_timeout_established = 5 DAYS
If I will change it to 30 MINS will it make trick? But there're
other protocols like UDP: how can I specify active timeout for
it? Another question, if it will affect underlying packet
converstation (i want it to remain undisturbed)? And last
question is how do I specify inactive timeout? I'm not sure that
it's possible but I can write it. And if so, can you please advice
me how I better done it: nf_ct_extend.. for example.
So many questions in so little message but I really looking forward
for your support.
Thank you in advance,
-- Alexey
P.S.: I'm not subscribed to list so please CC me your replies.
next reply other threads:[~2008-09-24 6:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-24 6:38 Alexey Mikhailov [this message]
2008-09-24 8:17 ` Conntrack flow expirations Philip Craig
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=877i929hfi.fsf@galois.botik.ru \
--to=karma@galois.botik.ru \
--cc=netfilter-devel@vger.kernel.org \
--cc=netfilter@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