From: Ben Lentz <BLentz@channing-bete.com>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: Netfilter Development Mailinglist <netfilter-devel@vger.kernel.org>
Subject: Re: conntrack accounting
Date: Sat, 05 Jan 2008 13:52:03 -0500 [thread overview]
Message-ID: <477FD1D3.8000708@channing-bete.com> (raw)
In-Reply-To: <477FB3E8.9080609@netfilter.org>
> I just implemented buffer logging that guarantees that fflush is called
> if the buffer is full. Have a look at LogFileBufferSize. This must
> improve performance under very busy firewall. Does syslog have any
> similar setting?
>
That's good question, I'm not really sure what buffering is available in
the various syslog implementations.
> The logging format must be discussed before the release. It would be
> fairly easy to dump the connection logging info in XML instead of plain
> text and I'm not sure if current format is fine.
In my opinion, the existing plain text log format is fine. I have an
existing tool that's used to parse out the existing plain text iptables
syslog data, and I plan on adapting it to support the similar format
produced by conntrackd. If there are changes that could be made to make
the formats similar, that might be nice (so the "family" netfilter
softwares log uniformly (?)). XML would be nice, but I won't use it at
this time.
prev parent reply other threads:[~2008-01-05 18:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-30 2:39 conntrack accounting Ben Lentz
2008-01-03 15:54 ` Pablo Neira Ayuso
2008-01-03 18:12 ` Ben Lentz
2008-01-04 3:25 ` Ben Lentz
2008-01-04 21:35 ` Ben Lentz
2008-01-05 12:39 ` Pablo Neira Ayuso
[not found] ` <477DA84A.3030304@channing-bete.com>
[not found] ` <477EAEF0.4000300@channing-bete.com>
2008-01-05 12:45 ` Pablo Neira Ayuso
2008-01-05 14:22 ` Ben Lentz
2008-01-05 14:36 ` Pablo Neira Ayuso
2008-01-05 16:24 ` Jan Engelhardt
2008-01-05 16:44 ` Pablo Neira Ayuso
2008-01-05 18:52 ` Ben Lentz [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=477FD1D3.8000708@channing-bete.com \
--to=blentz@channing-bete.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 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.