From: nexor@fnet.pl
To: netfilter@lists.netfilter.org
Subject: Re: Connections and connlimit problem,
Date: Mon, 5 Apr 2004 11:47:06 +0200 [thread overview]
Message-ID: <1278290250.20040405114706@fnet.pl> (raw)
In-Reply-To: <813267234.20040405102323@fnet.pl>
Hello nexor,
Monday, April 5, 2004, 10:23:23 AM, you wrote:
nfp> Hello,
nfp> it's my first post here - so welcome everyone!
nfp> I'm using Debian with kernel 2.4.6. I realized that I have a lot lines
nfp> in ip_conntrack like that:
nfp> tcp 6 431925 ESTABLISHED src=213.155.172.138
nfp> dst=217.17.41.88 sport=1057 dport=8074
nfp> src=217.17.41.88 dst=213.155.172.138 sport=8074 dport=1057 [ASSURED] use=1
nfp> I guess that 431925 (third values) is a timer - means how long this
nfp> connection will be tracked. Value of 431925 (in secs) means about 5
nfp> days... Those connections stay in ip_conntrack even after user reboot or
nfp> shutdown his computer.
nfp> I use connlimit and would like to not allow more than 20 connections
nfp> at once - here is my problem. After few days my ip_conntrack is full
nfp> of connections like that. Users can't make new connections, because
nfp> they have those 'dead' connections and connlimit prevent them from
nfp> making new.
nfp> Sorry for my poor English, I'm waiting for some advices.
I've found that:
cat /proc/sys/net/ipv4/netfilter/ip_conntrack_tcp_timeout_established
returns value:
432000
Isn't that too much ?
--
Best regards,
nexor mailto:nexor@fnet.pl
next prev parent reply other threads:[~2004-04-05 9:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-05 8:23 Connections and connlimit problem, nexor
2004-04-05 9:47 ` nexor [this message]
2004-04-06 3:10 ` Kiran Kumar
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=1278290250.20040405114706@fnet.pl \
--to=nexor@fnet.pl \
--cc=netfilter@lists.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 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.