From: Sven Schuster <schuster.sven@gmx.de>
To: "Jee J.Z." <jz105@york.ac.uk>
Cc: netfilter@lists.netfilter.org
Subject: Re: whether there are any packets in the ip_queue
Date: Tue, 20 Apr 2004 10:46:26 +0200 [thread overview]
Message-ID: <20040420084626.GB25017@zion.homelinux.com> (raw)
In-Reply-To: <004a01c4266c$b2d7d830$68892090@grouse>
[-- Attachment #1: Type: text/plain, Size: 1151 bytes --]
On Tue, Apr 20, 2004 at 01:16:17AM +0100, Jee J.Z. told us:
> Hi all,
>
> I am using libipq for userspace programming on netfilter. I am having
> problems to determine whether there are any packets in the ip_queue before I
> call the function ipq_read(). I just don't wish to call ipq_read() when
> there is no packet in the ip_queue, because I need my program to do other
> things rather than waiting for a packet arriving (after calling ipq_read(),
> the program will stop and wait for some time or until a packet coming from
> the kernel). Are there anybody on the list who has any idea about this?
Why don't you just call ipq_read with a negative timeout value?? When
there's no packet available it will return immediately with a return
code of 0. (see "man ipq_read")
HTH
Sven
>
> BTW, may I ask whether this is the proper list to ask about netfilter/libipq
> programming, since it seems few people on the list talking about this kind
> of questions?
>
--
Linux zion 2.6.6-rc1 #1 Sat Apr 17 11:50:12 CEST 2004 i686 athlon i386 GNU/Linux
10:44:31 up 2 days, 17:42, 1 user, load average: 0.00, 0.01, 0.00
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2004-04-20 8:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-20 0:16 whether there are any packets in the ip_queue Jee J.Z.
2004-04-20 8:46 ` Sven Schuster [this message]
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=20040420084626.GB25017@zion.homelinux.com \
--to=schuster.sven@gmx.de \
--cc=jz105@york.ac.uk \
--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