From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Thomas Jacob <jacob@internet24.de>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: ulogd2/NFLOG: nfnetlink_log: error creating log nlmsg
Date: Sat, 06 Jun 2009 08:57:04 +0200 [thread overview]
Message-ID: <4A2A1340.2090301@netfilter.org> (raw)
In-Reply-To: <1244210460.9510.4.camel@enterprise.ims-firmen.de>
Thomas Jacob wrote:
> On Fri, 2009-05-22 at 14:12 +0200, Thomas Jacob wrote:
>> On Thu, May 21, 2009 at 07:24:58PM +0200, Pablo Neira Ayuso wrote:
>>> Thomas Jacob wrote:
>>>> Bug? Feature? If it's the latter, how can I prevent this from
>>>> happening?
>>> Does this patch helps? It seems that we're missing to add the size of
>>> the hardware address since 2.6.27.
>> Thanks for the quick reply and the patch. Unfortunately I haven't found a way
>> to reproduce this problem in a lab environment yet, so I can't confirm
>> whether or not it does anything. Originally the issue
>> occurred when hot-replacing an older system with one that
>> runs NFLOG/ulogd2 and the versions listed, thereby generating lots
>> of invalid packets probably (which should have been logged) as well
>> as some intentional drops (Packet rate at the time maybe was 30kpps).
>
> Just to let you know, I still haven't been able to reproduce the
> problem in the lab, but the errors went away in the production
> environment after applying your patch, so presumably it did the trick.
> Also, the lines in question are clearly missing anyway.
Thanks for the info. I think that it should be related with the patch.
I'll try make some tests by hot-replacing the daemon in my testbed to
see if I catch anything.
--
"Los honestos son inadaptados sociales" -- Les Luthiers
prev parent reply other threads:[~2009-06-06 6:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-20 18:05 ulogd2/NFLOG: nfnetlink_log: error creating log nlmsg Thomas Jacob
2009-05-21 17:24 ` Pablo Neira Ayuso
2009-05-22 12:12 ` Thomas Jacob
2009-06-05 14:01 ` Thomas Jacob
2009-06-06 6:57 ` 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=4A2A1340.2090301@netfilter.org \
--to=pablo@netfilter.org \
--cc=jacob@internet24.de \
--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.