From: Ken-ichirou MATSUZAWA <chamaken@gmail.com>
To: Akshat Kakkar <akshat.1984@gmail.com>
Cc: netfilter@vger.kernel.org
Subject: Re: nflog : We are losing events. Increasing buffer size to 1736704
Date: Wed, 16 Sep 2015 13:48:21 +0900 [thread overview]
Message-ID: <20150916044821.GA29321@gmail.com> (raw)
Hi,
On Wed, Sep 9, 2015 at 6:54 PM, Akshat Kakkar <akshat.1984@gmail.com> wrote:
> It doesnt get increased more than 1736704.
> Even if I set 1736704 as the default buffer size, then also I get the
> same message
> We are losing events. Increasing buffer size to 1736704
>
> Why is that so? What makes the buffer size having ceiling at 1736704
> (= 212KBytes)
It would be better to show your ulogd.conf, someone might be able to
help you more easily. I guess... set netlink_socket_buffer_maxsize
in ulogd.conf adequately and also check /proc/sys/net/core/rmem_max.
Thanks,
next reply other threads:[~2015-09-16 4:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-16 4:48 Ken-ichirou MATSUZAWA [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-09-09 13:24 nflog : We are losing events. Increasing buffer size to 1736704 Akshat Kakkar
2015-09-15 5:24 ` Akshat Kakkar
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=20150916044821.GA29321@gmail.com \
--to=chamaken@gmail.com \
--cc=akshat.1984@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).