All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Tassilo Schütz" <tschuetz@avodaq.com>
To: netfilter-devel@lists.samba.org
Subject: problem with libipq and userprocess and 'clean' exit
Date: Thu, 13 Jun 2002 12:19:08 +0200	[thread overview]
Message-ID: <3D08719C.7020204@avodaq.com> (raw)

Hello list,

I have a userprocess using libipq. It stores packets comming in through 
traget -j QUEUE,
delay them for a while, and send them out via verdict NF_ACCEPT. That 
works fine.
But when I quit the process normaly (use ipq_destroy_handle()) and not 
all packets have
been send out again, I see sometimes in /proc/net/ip_queue, that the 
values are not set back.
It is the same, when the userprocess starts, calls irq_read() and before 
a packet arrives, I quit
the process normaly. In /proc/net/ip_queue you can see that Peer pid, 
Peer copy mode and
Peer copy range are not set back.

I would like to know, if I have to do anything else, before quit my 
userprocess? Is there
maybe a flush_queue() call or term_queue() call? I thought about, 
because of Queue flushing
and Queue terminate in /proc/net/ip_queue.

Looking through the source of ip_queue.c I found some similar calls and 
a comment :
 * Packets arrive here from netfilter for queuing to userspace. *
 * All of them must be fed back via nf_reinject() or Alexey will kill 
Rusty. *

Can someone give me a guidance how to quit my process without the above 
effets :-)  ?

Thanks in advance

Tassilo

             reply	other threads:[~2002-06-13 10:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-13 10:19 Tassilo Schütz [this message]
2002-06-13 11:50 ` problem with libipq and userprocess and 'clean' exit James Morris
2002-06-13 11:56   ` Henrik Nordstrom
2002-06-13 13:07     ` James Morris
2002-06-14 13:40   ` Tassilo Schütz

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=3D08719C.7020204@avodaq.com \
    --to=tschuetz@avodaq.com \
    --cc=netfilter-devel@lists.samba.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.