From: Nigel Kukard <nkukard@lbsd.net>
To: Patrick McHardy <kaber@trash.net>
Cc: netfilter-devel@lists.netfilter.org
Subject: Re: ip_queue & QUEUE target
Date: Sun, 15 Jun 2003 20:00:31 +0200 [thread overview]
Message-ID: <20030615180031.GE2103@lbsd.net> (raw)
In-Reply-To: <3EECA7B2.5090300@trash.net>
[-- Attachment #1: Type: text/plain, Size: 476 bytes --]
>
> netlink sockets provide unreliable communication. your problem is
> probably the sockets receive queue overflowing. ip_queue then
> returns a negative error code to nf_queue which drops the packet.
well i'm pumping through about 5,000 pkt/s, doing a few Mb/s. What would
the best thing be to use? or how could i remedy this problem?
i set the rcv buffer to a few Mb, and also the ipq_maxlen to 8196... is
there anything else i can do?
Regards
Nigel
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-06-15 18:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-15 15:53 ip_queue & QUEUE target Nigel Kukard
2003-06-15 17:06 ` Patrick McHardy
2003-06-15 18:00 ` Nigel Kukard [this message]
2003-06-15 18:07 ` Patrick McHardy
2003-06-15 18:21 ` Nigel Kukard
2003-06-15 18:35 ` Nigel Kukard
2003-06-15 18:50 ` Martin Josefsson
2003-06-15 18:53 ` Patrick McHardy
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=20030615180031.GE2103@lbsd.net \
--to=nkukard@lbsd.net \
--cc=kaber@trash.net \
--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.