From: Sylvie Colin <sylvie.colin@aql.fr>
To: netfilter@lists.netfilter.org
Subject: ipq_read() error
Date: Thu, 20 Nov 2003 15:15:52 +0100 [thread overview]
Message-ID: <3FBCCC98.2070002@aql.fr> (raw)
Hi all,
I am using libipq in a C++ program to intercept packets destined to a
particular host at the Forward hook : the rule "iptables -A FORWARD -j
QUEUE -d <IPdest>" is installed.
The program waits on multiple file descriptors using select() and, when
input data gets available on the IPQ netlink socket, it gets the IP
packet using ipq_read() and sets the verdict to NF_DROP. It works well
except that sometimes ipq_read returns with the error IPQ_ERR_RECV
"Failed to receive netlink message" and errno 105-ENOBUFS "no buffer
space available". I've tried to change the kernel parameter
net.ipv4.ip_queue_maxlen but it seems to have no effect: the entry
/proc/net/ip_queue always shows a queue max length of 1024.
Environment: kernel 2.4.20, iptables[-devel]-1.2.6a
Could anyone explain me the reason of this error? Are any packets
dropped when the error occurs? How can I solve it?
Thanks for help,
Sylvie
**************************************************************************************************
The contents of this email and any attachments are confidential.
It is intended for the named recipient(s) only.
If you have received this email in error please notify the system manager or the
sender immediately and do not disclose the contents to anyone or make copies.
** eSafe scanned this email for viruses, vandals and malicious content **
**************************************************************************************************
next reply other threads:[~2003-11-20 14:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-20 14:15 Sylvie Colin [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-10-27 10:08 ipq_read error Peter.Muller
2005-10-27 11:58 ` Eric Leblond
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=3FBCCC98.2070002@aql.fr \
--to=sylvie.colin@aql.fr \
--cc=netfilter@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox