From mboxrd@z Thu Jan 1 00:00:00 1970 From: Martijn Lievaart Subject: Re: condition for 2.6.16 Date: Thu, 20 Apr 2006 21:44:24 +0200 Message-ID: <4447E498.7060006@rtij.nl> References: <200604201919.19246.max@nucleus.it> <4447D7AA.1010602@trash.net> <200604202139.02931.max@nucleus.it> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: netfilter-devel@lists.netfilter.org, Patrick McHardy Return-path: To: Massimiliano Hofer In-Reply-To: <200604202139.02931.max@nucleus.it> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: netfilter-devel-bounces@lists.netfilter.org Errors-To: netfilter-devel-bounces@lists.netfilter.org List-Id: netfilter-devel.vger.kernel.org Massimiliano Hofer wrote: >On Thursday 20 April 2006 8:49 pm, Patrick McHardy wrote: > > >>We have already decided that the condition match will not be merged >>because the same thing can easily be done by adding/removing rules >>from userspace. >> >> > >Sorry, I missed that discussion. >Is it still possible to include it in the external patches? > >Anyway I think condition allows for a much more elegant solution in cases >where adding and removing rules would lead to a messy and unpredictable >sequence of overlapping rules, not to mention races between different >modifications. >Just my humble opinion. > > I concur. The condition match is much more elegant then dynamically messing with the rules. M4