From mboxrd@z Thu Jan 1 00:00:00 1970 From: Samuel Jean Subject: Re: ipt_time fixes (resend, sorry) Date: Thu, 20 Jan 2005 19:23:48 -0500 Message-ID: <41F04B94.3070902@cookinglinux.org> References: <20050114143722.GA10088@ti64.telemetry-investments.com> <57991.142.169.215.10.1105716756.squirrel@142.169.215.10> <41E7F2DA.608@info-link.net> <41E7F4B9.4080103@info-link.net> <41EFDDE2.8030901@info-link.net> <13851.142.169.215.10.1106246038.squirrel@142.169.215.10> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-2; format=flowed Content-Transfer-Encoding: 8bit Cc: netfilter-devel@lists.netfilter.org Return-path: To: Krzysztof Oledzki In-Reply-To: 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 Krzysztof Oledzki wrote: > I'm not sure if adding a negation-like-workaround to ipt_time (and > possible other matches like ipt_limit) is a good idea. Obviously, I would need to peek at the code to continue following this thread. However, my brain is already spinning on other codes. > My qestion is: > why we cannot simply negate all matches? I guess it would confuse the user when the match uses multiple options. Am confused just thinking about it :) But am also in the favor that all matches should accept and behave the right way with negation unless negation really doesn't make sense nor does anything usefull. Maybe I missed a match that really doesn't make sense with negation. (I surely did) > > > Best regards, > > Krzysztof Olędzki Cheers, Samuel