From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mr Dash Four Subject: Re: [PATCH 0/3] ipset: change 'iface' part in hash:net,iface set Date: Sun, 08 Jul 2012 20:11:02 +0100 Message-ID: <4FF9DB46.5000302@googlemail.com> References: <4FF736FE.8030109@googlemail.com> <4FF74868.3070303@googlemail.com> <4FF74D5C.6060909@googlemail.com> <4FF752F0.3010007@googlemail.com> <4FF765E7.6020809@googlemail.com> <4FF9852C.7080201@googlemail.com> <4FF9D97D.7040309@googlemail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Netfilter Core Team , Pablo Neira Ayuso , Patrick McHardy To: Jozsef Kadlecsik Return-path: Received: from mail-wg0-f44.google.com ([74.125.82.44]:33258 "EHLO mail-wg0-f44.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751893Ab2GHTLM (ORCPT ); Sun, 8 Jul 2012 15:11:12 -0400 Received: by wgbdr13 with SMTP id dr13so10783813wgb.1 for ; Sun, 08 Jul 2012 12:11:11 -0700 (PDT) In-Reply-To: Sender: netfilter-devel-owner@vger.kernel.org List-ID: > Because that's too subtle, error prone and hard to catch if not used > really intentionally. If I use 'src,dst' instead of 'src,src' would you consider this "error prone", "hard to catch" or not? > Because that's illogical. Please explain - what do you see as "illogical"? > Because there are a couple > of ways to avoid it. > Avoid what exactly? Using 'in' or 'out' in list:set types?