netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ralf <rm@amitrader.com>
To: netfilter-devel@vger.kernel.org
Subject: userspace packetfiltering problems
Date: Tue, 17 Feb 2009 21:14:27 +0100	[thread overview]
Message-ID: <gnf5r6$a7u$1@ger.gmane.org> (raw)

The majority of the public linux servers are VPS systems.
Most are based on openVZ/Virtuozzo.

In this environment the VPS admin has IMHO unfortunately 
no possibility to use modprobe or insmod to load iptable modules.

Therefore it is impossible to write 3rd party software 
which needs packet filtering capability (QUEUE/NFQUEUE).

The iptables/netfilter developers should think about this problem
and give the VPS users the capability to load userspace modules
by themselves, and not let them beg at their hosters
as this mostly nearly never works.

Can anybody give me an advice for a packet filtering library
that works in userspace on all linux systems, without the need
for any kernel modules etc.?
I tried libipq, but it gives an error because a kernel module
(ip_queue) is not loaded, and the hoster denies to load that damn module.
Is that not worser than Microsoft's monopoly practices???
It is happening with Open Source! Isn't that a crime?


                 reply	other threads:[~2009-02-17 20:14 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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='gnf5r6$a7u$1@ger.gmane.org' \
    --to=rm@amitrader.com \
    --cc=netfilter-devel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).