From: Massimiliano Hofer <max@nucleus.it>
To: netfilter@lists.netfilter.org
Subject: Re: Controlling an iptables-match from userspace
Date: Fri, 26 May 2006 00:00:55 +0200 [thread overview]
Message-ID: <200605260000.56259.max@nucleus.it> (raw)
In-Reply-To: <815d745e0605230800t4b4f58a3s76f160788025fa95@mail.gmail.com>
On Tuesday 23 May 2006 5:00 pm, Manfred Stock wrote:
> Thanks. That's close to what I'm looking for. Unfortunately, it does
> not seem to be maintained anymore - I could find the sources in
> netfilter's svn using google, but the last change was it's import into
> the new trunk directory 19 months ago... At least it compiles against
> 2.6.8 with only one warning, and seems to work. But I would very much
> prefer a solution which does not rely on /proc because I don't believe
> in it's future for this kind of stuff ;). Any ideas?
I recently became maintainer of the condition patch.
You can find a new version at
"http://www.nucleus.it/pom-repo/condition.tar.gz". From now on it will be
handled as an external repository.
I'm working on some other changes that should make it more acceptable,
althought I've been busy in the last couple of weeks.
Some considerations:
- adding a new system call or ioctl is more intrusive than a proc interface;
- a file interface doesn't require a special app.
You could argue about putting it in /sys or in the brand new configfs.
I'd like feedback about the best way to handle this.
--
Saluti,
Massimiliano Hofer
Nucleus
next prev parent reply other threads:[~2006-05-25 22:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-23 11:42 Controlling an iptables-match from userspace Manfred Stock
2006-05-23 12:04 ` Sven-Haegar Koch
2006-05-23 15:00 ` Manfred Stock
2006-05-25 22:00 ` Massimiliano Hofer [this message]
2006-05-26 2:17 ` STRING agrument Allan Parreno
2006-05-27 2:49 ` Eric Benton
2006-05-28 18:19 ` Controlling an iptables-match from userspace Manfred Stock
2006-05-28 23:36 ` Massimiliano Hofer
2006-05-30 7:36 ` Manfred Stock
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=200605260000.56259.max@nucleus.it \
--to=max@nucleus.it \
--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