All of lore.kernel.org
 help / color / mirror / Atom feed
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:21:39 +0200	[thread overview]
Message-ID: <20030615182139.GF2103@lbsd.net> (raw)
In-Reply-To: <3EECB5F4.7010004@trash.net>

[-- Attachment #1: Type: text/plain, Size: 1012 bytes --]

> Probably not much, but did you make sure you also increased
> /proc/sys/net/core/rmem_max ? If you don't mind your statistics
> beeing wrong (better than high drop rates imho) you could
> modify ip_queue so it nf_reinjects packets which could not
> be sent instead of returning a error to nf_queue.

This is very strange, i'm sure i'm doing something wrong.

I have rmem_max set to 272144, i use setsockopt to set the
options for the socket, namely SO_RCVBUF, this i set to 1048576.

The socket i create with  socket(PF_NETLINK,SOCK_RAW,NETLINK_FIREWALL).

(this is basicallly all in libipq, i've not changed more than the
rcvbuf).

now the strange thing is, when receiving data, i get IPQ_ERR_TIMEOUT's,
this being basically impossible imho because of the high packet rate.

after these timeouts, i get no data at all... data hits the queue, but
my small proggie doesn't get any (using a 1/4 timeout), funny enough i
don't get IPQ_ERR_TIMEOUTS... *shrug*... any help would be very much
appreciated!


-Nigel


[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2003-06-15 18:21 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
2003-06-15 18:07     ` Patrick McHardy
2003-06-15 18:21       ` Nigel Kukard [this message]
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=20030615182139.GF2103@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.