From: Christian Riechmann <riechmann@fgan.de>
To: netfilter-devel@lists.netfilter.org
Subject: "No buffer space available" upon ipq_read
Date: Thu, 29 Jul 2004 12:44:49 +0200 [thread overview]
Message-ID: <20040729104449.GA2202@rie.rie.priv> (raw)
Hello,
I am sure some one can give me a short answer to the following problem:
Sometimes - for the moment I would say "randomly" - during a relative
long run upon an ipq_read request I get the error
"Failed to receive netlink message: No buffer space available"
My questions are:
Which buffer is meant ?
and
Which are some reasons for this error situation ?
I use iptables- 1.2.9 and I am pretty sure, that all packets read into
user space are verdicted. The user space program does not expand its used
memory the more it runs.
Thanks in advance for some pointers.
Christian
--
Christian Riechmann E-Mail: riechmann@fgan.de
c/o FGAN/FKIE Tel: (+49) 228/9435 345,378
Neuenahrer Strasse 20 Fax: (+49) 228/9435 685
D-53343 Wachtberg, Germany
next reply other threads:[~2004-07-29 10:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-29 10:44 Christian Riechmann [this message]
2004-07-29 12:08 ` "No buffer space available" upon ipq_read Pablo Neira
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=20040729104449.GA2202@rie.rie.priv \
--to=riechmann@fgan.de \
--cc=netfilter-devel@lists.netfilter.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.