From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Eric Leblond <eric@inl.fr>, Anton <anton.vazir@gmail.com>,
netfilter-devel@vger.kernel.org,
Pablo Neira Ayuso <pablo@netfilter.org>
Subject: Re: NFLOG - missing packets?
Date: Mon, 12 May 2008 13:53:56 +0200 [thread overview]
Message-ID: <48282FD4.4070806@netfilter.org> (raw)
In-Reply-To: <20080511161837.GJ11778@ice-age>
Eric Leblond wrote:
> Hello,
>
> On Saturday, 2008 May 10 at 17:50:37 +0500, Anton wrote:
>> Something wrong quite definitelly,
>> in 700Mb of the data it logs only 43Mb
>
> I've done some test on my system and I've got similar results. Sole
> difference is the ratio between logged packets and unlogged packets.
>
> I've downloaded a 48Mo at a rate of 348.28K/s and I have the following
> result :
> Iptables : 33625 packets, 50383786 bits
> Ulogd2 : 33272 packets 49856076 bits
>
> As usual, size does not matter. The problem is due to some packets not
> being loggued. It recall me results of Pablo's conntrackd benchmark.
> After a given rate, the netlink subsystem is not able to transmit
> messages.
>
> IMHO, the main issue is that the lost (or the overrun) does not seem to be logged
> somewhere.
I'm finishing a patchset to improve this and other aspects of ulogd.
I'll post them to the ML soon.
--
"Los honestos son inadaptados sociales" -- Les Luthiers
prev parent reply other threads:[~2008-05-12 11:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-10 11:57 NFLOG - missing packets? Anton
2008-05-10 12:50 ` Anton
2008-05-11 16:18 ` Eric Leblond
2008-05-12 7:24 ` Anton
2008-05-14 17:49 ` Pablo Neira Ayuso
2008-05-14 17:53 ` Patrick McHardy
2008-05-15 5:42 ` Anton
2008-05-14 23:01 ` Eric Leblond
2008-05-12 9:19 ` Anton
2008-05-12 11:53 ` Pablo Neira Ayuso [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=48282FD4.4070806@netfilter.org \
--to=pablo@netfilter.org \
--cc=anton.vazir@gmail.com \
--cc=eric@inl.fr \
--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 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.