From: Patrick McHardy <kaber@trash.net>
To: Guillaume Leccese <guillaume.leccese@oxalide.com>
Cc: netfilter-devel@vger.kernel.org, netfilter@vger.kernel.org
Subject: Re: iptables logging to syslog: performance problem
Date: Tue, 23 Oct 2007 18:18:23 +0200 [thread overview]
Message-ID: <471E1ECF.3030300@trash.net> (raw)
In-Reply-To: <471E1A16.5060404@oxalide.com>
Guillaume Leccese wrote:
> Patrick McHardy a écrit :
>>> On a 2.6.19.1 kernel box (nfct patch from Julian
>>> http://www.ssi.bg/~ja/nfct/) we have a strange performance problem.
>>>
>>> When a scan occur on a /24 network handled by the firewall (on a
>>> filtered
>>> port) packets dropping produces a syslog output. During the logging
>>> process,
>>> the traffic is at a frozen state (2 seconds to 30 seconds, depending
>>> of the
>>> number of ports scanned).
>>>
>>> [...]
>>> When output to syslog is not effective, there is no performance
>>> decrease.
>>>
>>> More details about the configuration:
>>>
>>> - Linux 2.6.19.1, module activate, iptables not in module
>>> - e1000, tygon 3 and sundance drivers in module
>>> - bonding device in module
>>> - 2x e1000, driver v7.6.9 stable, in bonding
>>> - Keepalived 1.1.12-1, Debian apt version
>>
>> Are you using serial console?
>>
>
> Hi Patrick,
>
> Do you ask me if the serial console is compiled in the kernel or if
> I'm using serial console for remote control ?
Whether you use serial console for logging.
>
> 1/ yes, see the .config in attachment
>
> 2/ no, we use ssh
In case you're not using the serial console for logging, can you
reproduce it without Julian's patches?
next prev parent reply other threads:[~2007-10-23 16:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-23 15:12 iptables logging to syslog: performance problem Guillaume Leccese
2007-10-23 15:49 ` Patrick McHardy
2007-10-23 15:58 ` Guillaume Leccese
2007-10-23 16:05 ` Jan Engelhardt
2007-10-23 16:18 ` Patrick McHardy [this message]
2007-10-23 16:41 ` Guillaume Leccese
2007-10-23 16:45 ` Patrick McHardy
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=471E1ECF.3030300@trash.net \
--to=kaber@trash.net \
--cc=guillaume.leccese@oxalide.com \
--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