From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mr Dash Four Subject: Re: [PATCH v2 3/3] ipset: change 'iface' part in hash:net,iface set Date: Sun, 15 Jul 2012 23:48:48 +0100 Message-ID: <500348D0.8030005@googlemail.com> References: <1341872622-5015-2-git-send-email-mr.dash.four@googlemail.com> <4FFCBDB8.9080101@googlemail.com> <4FFF6EF2.6010108@googlemail.com> <5000293F.4030901@googlemail.com> <50002F3F.5020408@googlemail.com> <5001678C.6000505@googlemail.com> <5002AF68.9070204@googlemail.com> <5002F0AF.4000502@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-f42.google.com ([74.125.82.42]:52741 "EHLO mail-wg0-f42.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750955Ab2GOWs6 (ORCPT ); Sun, 15 Jul 2012 18:48:58 -0400 Received: by wgbfm10 with SMTP id fm10so1942475wgb.1 for ; Sun, 15 Jul 2012 15:48:57 -0700 (PDT) In-Reply-To: Sender: netfilter-devel-owner@vger.kernel.org List-ID: > Because this or that way, someone would scratch his/her head. For example > if the rule contains "in/out" and the list:set is a mixed one, contains > both hash:net,iface and other types of sets. They'll ask: "What the heck > is "in/out" for say hash:ip type of set?" I've just read that again, so decided to clarify (a bit like you :-) ) what was meant in my previous email: I am discussing the issue of in/out <-> src/dst *only* for list:set type sets and *only* for the second dimension parameter of that set - everything else is "as is" and as we agreed before, OK?