All of lore.kernel.org
 help / color / mirror / Atom feed
From: "He Ke" <heke@uestc.edu.cn>
To: netfilter-devel@lists.netfilter.org
Subject: a libipq problem(FAQ cannot help)
Date: Fri, 27 Aug 2004 18:01:08 +0800	[thread overview]
Message-ID: <293600868.26725@uestc.edu.cn> (raw)

i've now got a serious problem on the libipq programming.I wrote an application
which gets 
packets from iptables's QUEUE target(ip_queue&ip6_queue),and then deals with
them(drop,accept,...).
It works well with normal amout of packets,but when packets comes above 10M/s,it
dies soon,and show
 "Failed to received netlink message: No buffer space available".
   I've checked the FAQ,it says "you can tune their receive buffer sizes via
 /proc/sys/net/core, sysctl, or use the SO_RCVBUF socket option on the file
 descriptor".I tried them both , but it doesn't work,my application still die
soon
 when it meets packets above 10M/s.
   I tuned
  /proc/sys/net/core/rmem_default
  /proc/sys/net/core/rmem_max
 up to 1048576 .
   I modified the ipq_create_handle function in the libipq.c file, added the
 following sentence:
 	char maxbuf[1048576];
 	if(setsockopt(h->fd,SOL_SOCKET,SO_RCVBUF,&maxbuf,sizeof(maxbuf))==-1)
 		{
 		ipq_errno=IPQ_ERR_RECVBUF;
 		free(h);
 		return NULL;
 		}
 Am I right?
 If what i've done is what the FAQ says,why doesn't it work?
 the software snort_inline who uses this technique has the same problem,i've
 checked it.
 Would you please tell me how can i deal with this problem ?
 I'll be very appreaciate!

             reply	other threads:[~2004-08-27 10:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-27 10:01 He Ke [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-08-28  8:46 a libipq problem(FAQ cannot help) He Ke
2004-08-29  4:13 ` Pablo Neira
2004-08-27 10:01 He Ke

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=293600868.26725@uestc.edu.cn \
    --to=heke@uestc.edu.cn \
    --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.