netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Anton VG <anton.vazir@gmail.com>
To: netfilter-devel <netfilter-devel@vger.kernel.org>
Subject: Re: Ulogd2 beta3 +NFCT - unable to get working
Date: Wed, 24 Jun 2009 14:40:24 +0500	[thread overview]
Message-ID: <c4b050a10906240240m5d685ca8q80424978fb475caa@mail.gmail.com> (raw)
In-Reply-To: <c4b050a10906231656u53e20855ud5cf5833ca5db7cc@mail.gmail.com>

Hello!
Just my experience with ULOGD 2.0 beta 3. NFCT logging seems broken.
I've managed to get something working, i'm logging to a PGSQL DB.

When I do enable hash_enable=0 and
pollinterval=100 and"INSERT_CT"  - it starts logging connections, but
after a while, byte counters of already logged connections in DB was
zeroed.

If hash_enable=1 and -"INSERT_CT" - it logs some connections, and byte
counters always 0

if pollinterval is not manually defined - it does not log anything.

Libraries and netfilter all latest
Kernel 2.6.29.5
os Debian stable

my test bed is 3 PC's , one of which consists all the given stuff for
traffic accounting and i'm WGETtting files between 1 and 3rd PC's and
watching the result in

PC_1 <-- NFCT_PC_2 --> PC_3

stack=ct1:NFCT,ip2str1:IP2STR,pgsql1:PGSQL

[pgsql1]
db="ulog2"
host="192.168.1.148"
user="ulog2"
table="ulog2_ct"
pass="ulog2"
procedure="INSERT_CT"
#procedure="INSERT_OR_REPLACE_CT"

[ct1]
pollinterval=1
hash_enable=1

Anything I can do to help fixing this?

  reply	other threads:[~2009-06-24  9:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-23 23:56 Ulogd2 beta3 +NFCT - unable to get working Anton VG
2009-06-24  9:40 ` Anton VG [this message]
2009-06-24 18:02 ` Pablo Neira Ayuso
2009-06-24 18:06   ` Pablo Neira Ayuso
2009-06-24 20:54     ` Anton VG
2009-06-27 21:13       ` Pablo Neira Ayuso

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=c4b050a10906240240m5d685ca8q80424978fb475caa@mail.gmail.com \
    --to=anton.vazir@gmail.com \
    --cc=netfilter-devel@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).