All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Gerd v. Egidy" <lists@egidy.de>
To: netfilter-devel@lists.netfilter.org
Subject: Re: condition for 2.6.16
Date: Fri, 21 Apr 2006 02:48:14 +0200	[thread overview]
Message-ID: <200604210248.14819.lists@egidy.de> (raw)
In-Reply-To: <200604210126.11294.max@nucleus.it>

On Friday 21 April 2006 01:26, Massimiliano Hofer wrote:
> On Friday 21 April 2006 12:47 am, Patrick McHardy wrote:
> > It was discussed at the netfilter workshops, summaries are available at
> > workshop.netfilter.org.
>
> I did a cursory check of the site, but I only found a 5 or 6 lines summary
> for every conference. Google doesn't help either.
> May you direct me to a more comprehensive report, please?

There is no big discussion about condition online but one line at 
http://workshop.netfilter.org/2004/ :

6.2. Decisions about individual patches
...
condition  Stays in POM, because it's ugly and ruleset updates are faster 
these days 

I don't know more than that because I didn't attend that netfilter workshop.

I already had a discussion about the future of condition with Harald back in 
2004 and he basically said the same as Patrick now:

http://thread.gmane.org/gmane.comp.security.firewalls.netfilter.devel/5694

I think something like condition is needed as temporary solution until the 
proposed fast and reliable way to change rules is available. I very much 
appreciate your work on porting it to 2.6, I already had planned doing that 
in the nex two or three month.

Kind regards,

Gerd

  parent reply	other threads:[~2006-04-21  0:48 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-20 17:19 condition for 2.6.16 Massimiliano Hofer
2006-04-20 18:49 ` Patrick McHardy
2006-04-20 19:39   ` Massimiliano Hofer
2006-04-20 19:44     ` Martijn Lievaart
2006-04-20 22:47     ` Patrick McHardy
2006-04-20 23:26       ` Massimiliano Hofer
2006-04-21  0:41         ` Gerd v. Egidy
2006-04-21  0:48         ` Gerd v. Egidy [this message]
2006-04-21  9:29           ` Amin Azez
2006-04-23 13:47   ` Simon Lodal
2006-04-28  7:12     ` Patrick McHardy
2006-04-28 10:46       ` Massimiliano Hofer
2006-04-28 11:06         ` Patrick McHardy
2006-04-28 12:44           ` Massimiliano Hofer
2006-04-28 12:58             ` Jozsef Kadlecsik
2006-04-28 13:07               ` Patrick McHardy
2006-04-28 15:18                 ` KOVACS Krisztian
2006-04-28 15:34                   ` Patrick McHardy
2006-04-29  0:53                     ` Massimiliano Hofer
2006-04-29  2:56                       ` Patrick McHardy
2006-04-29 15:36                         ` Massimiliano Hofer
2006-04-28 13:18               ` Massimiliano Hofer
2006-04-28 13:09             ` Patrick McHardy
2006-04-28 13:26               ` Massimiliano Hofer

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=200604210248.14819.lists@egidy.de \
    --to=lists@egidy.de \
    --cc=netfilter-devel@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 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.