From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Clemens Eisserer <linuxhippy@gmail.com>
Cc: netfilter@vger.kernel.org
Subject: Re: Howto get ulog-prefix with ulogd-1.24 + sqlite3 backend?
Date: Mon, 11 Apr 2011 16:57:39 +0200 [thread overview]
Message-ID: <4DA316E3.5050309@netfilter.org> (raw)
In-Reply-To: <BANLkTingf+1nKHejX9XHcyep0DOHA__ghw@mail.gmail.com>
On 09/04/11 14:13, Clemens Eisserer wrote:
> Hi,
>
> We try to use ulog for traffic accounting in an university project.
>
> First we tried ulogd-2.0beta4 + pgsql backend, but even under moderate
> load the database couldn't keep pace with the amount of requests.
> I thought about using ulog2 with sqlite, however in TODO theres an
> entry about making ulogd2 compatible with squlite, so I guessed sqlite
> is not yet supported with ulogd2?
The support for sqlite3 was recently added in the git tree. Get a git
snapshot. I have tested it here. I'd appreciate if you let me know how
it goes.
> Then we switched back to ulog-1.24 + squlite3, which works perfectly.
> It can handle 100mbit/s torrent traffic at about ~50% CPU load.
> However in sqlite's ulog table, the ulog-prefix is not stored. Is
> there any way to get it stored - to be able to track which rule caused
> the log enrty?
You mean the log prefix? The ulogd2 version includes it for sqlite3.
> Also, conntrack is supported in ulogd2. Is this also true for
> ulogd1.2? I couldn't find specific docs about that.
No ulogd1.2 does not support conntrack, only packet-based logging.
next prev parent reply other threads:[~2011-04-11 14:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-09 12:13 Howto get ulog-prefix with ulogd-1.24 + sqlite3 backend? Clemens Eisserer
2011-04-09 12:17 ` Jan Engelhardt
2011-04-10 10:29 ` Eric Leblond
2011-04-11 14:57 ` Pablo Neira Ayuso [this message]
2011-04-14 1:17 ` Peter Phaal
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=4DA316E3.5050309@netfilter.org \
--to=pablo@netfilter.org \
--cc=linuxhippy@gmail.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;
as well as URLs for NNTP newsgroup(s).