All of lore.kernel.org
 help / color / mirror / Atom feed
From: "U.Mutlu" <for-gmane@mutluit.com>
To: netfilter@vger.kernel.org
Subject: [nfqueue] nfqueue in virtualized environment (ie. on a VPS)
Date: Thu, 08 Dec 2011 21:09:49 +0100	[thread overview]
Message-ID: <jbr5is$u2g$1@dough.gmane.org> (raw)

I need to use, in a virtual environment (VPS), an app
that makes use of libnetfilter_queue (ie. the NFQUEUE target of iptables).
Running the same app on the host machine works fine,
but I need it to run also on VPSes.

Is nfqueue supposed to work in such virtual environments?
(IMO since iptables works fine on a VPS, then I think nfqueue should do too, isn't it?)

I wonder why it's not working on my setup.
Could someone please give me some hints & tips for diagnosing and solving this problem?
It would be much helpful if someone who has it working simply confirm that it works.

My environment: debian wheezy using openvz kernel from the debian repo:
# uname -a
Linux s7 2.6.32-5-openvz-amd64 #1 SMP Fri Sep 9 21:03:29 UTC 2011 x86_64 GNU/Linux

# iptables --version
iptables v1.4.12

Libs installed:
# dpkg -l | grep nfnet
    libnfnetlink-dev        1.0.0-1    Development files for libnfnetlink0
    libnfnetlink0           1.0.0-1    Netfilter netlink library
# dpkg -l | grep queue
    libnetfilter-queue-dev  0.0.17-1   Development files for libnetfilter-queue1
    libnetfilter-queue1     0.0.17-1   Netfilter netlink-queue library

NFQUEUE definition in iptables script:
  iptables -A INPUT -p all -j NFQUEUE --queue-num 4712

App output:
   opening library handle
   binding nfnetlink_queue as nf_queue handler for AF_INET
   error during nfq_bind_pf()


Thx


             reply	other threads:[~2011-12-08 20:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-08 20:09 U.Mutlu [this message]
2011-12-09 11:04 ` [nfqueue] nfqueue in virtualized environment (ie. on a VPS) U.Mutlu

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='jbr5is$u2g$1@dough.gmane.org' \
    --to=for-gmane@mutluit.com \
    --cc=netfilter@vger.kernel.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.