From: Franck JONCOURT <franck.mail@dthconnex.com>
To: netfilter@vger.kernel.org
Subject: Re: Stopping ip_conntrack_max from resetting
Date: Tue, 25 Mar 2008 20:33:45 +0100 [thread overview]
Message-ID: <be74a7029007782ed97a12bfcd070e49@localhost> (raw)
In-Reply-To: <alpine.LNX.1.10.0803250258490.9368@fbirervta.pbzchgretzou.qr>
On Tue, 25 Mar 2008 02:59:12 +0100 (CET), Jan Engelhardt
<jengelh@computergmbh.de> wrote:
>
> On Monday 2008-03-24 15:09, Richard Andrews wrote:
>> Hello,
Hi,
>> We have a system running iptables, of which due to the incoming
>> traffic we've had to increase ip_conntrack_max via sysctl.
>> However, when restarting the service during any maintenance the
>> value we pass during sysctl.conf is reset to the default 65536.
>> Which then we are forced to run "sysctl -p" to reload our custom
>> value. Is there a way to stop the iptables service from rewriting
>> ip_conntrack_max when issued a restart/reload?
>
> That seems to be a bug of your distribution, because on mine,
> sysctl.conf is read and applied on boot.
Running Debian Sid, I can get the same behaviour. This is not
a bug, just a matter of boot sequence.
If you load sysctl configuration before your module is loaded
(should be nf_conntrack_ipv4, not quite sure), the entry
net.ipv4.netfilter.ip_conntrack_max does not exist yet, so it
is not possible to set it to its value.
To get it work, I just added it to my module list, in order to
load it at boot time before my sysctl configuration.
---
Franck Joncourt
http://www.debian.org/ - http://smhteam.info/wiki/
prev parent reply other threads:[~2008-03-25 19:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-24 14:09 Stopping ip_conntrack_max from resetting Richard Andrews
2008-03-25 1:59 ` Jan Engelhardt
2008-03-25 19:33 ` Franck JONCOURT [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=be74a7029007782ed97a12bfcd070e49@localhost \
--to=franck.mail@dthconnex.com \
--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