From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.2 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,USER_AGENT_MUTT autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 541C4C48BD6 for ; Wed, 26 Jun 2019 12:27:21 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 2B9F9204FD for ; Wed, 26 Jun 2019 12:27:21 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726329AbfFZM1U (ORCPT ); Wed, 26 Jun 2019 08:27:20 -0400 Received: from orbyte.nwl.cc ([151.80.46.58]:56082 "EHLO orbyte.nwl.cc" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726104AbfFZM1U (ORCPT ); Wed, 26 Jun 2019 08:27:20 -0400 Received: from n0-1 by orbyte.nwl.cc with local (Exim 4.91) (envelope-from ) id 1hg71B-0005hn-PC; Wed, 26 Jun 2019 14:27:17 +0200 Date: Wed, 26 Jun 2019 14:27:17 +0200 From: Phil Sutter To: Pablo Neira Ayuso Cc: Florian Westphal , netfilter-devel@vger.kernel.org Subject: Re: Use of oifname in input chains Message-ID: <20190626122717.GF9218@orbyte.nwl.cc> Mail-Followup-To: Phil Sutter , Pablo Neira Ayuso , Florian Westphal , netfilter-devel@vger.kernel.org References: <20190625122954.GC9218@orbyte.nwl.cc> <20190625194321.e2siqh7jfhldwzgw@salvia> <20190626103230.b7eqh2i3ibpkfv52@breakpoint.cc> <20190626103746.ag26jczoq7ggkh5b@salvia> <20190626104254.cfhkfpagequp6kuv@breakpoint.cc> <20190626104740.vw7xzrkoqd2lwzqh@salvia> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190626104740.vw7xzrkoqd2lwzqh@salvia> User-Agent: Mutt/1.10.1 (2018-07-13) Sender: netfilter-devel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: netfilter-devel@vger.kernel.org Hi, On Wed, Jun 26, 2019 at 12:47:40PM +0200, Pablo Neira Ayuso wrote: [...] > OK, you think there may be people using oifname from the C chain, but > how so? To skip rules that are specific to the output path? My idea for how to use it was this: | table ip t { | chain in { | type filter hook input priority 0; policy accept; | jump common | } | | chain out { | type filter hook output priority 0; policy accept; | jump common | } | | chain common { | iifname "eth0" tcp dport ssh counter packets 101 bytes 10149 accept | oifname "eth0" tcp sport ssh counter packets 65 bytes 8233 accept | counter packets 0 bytes 0 drop | } | } > Anyway, I'm fine with leaving things as is, I don't need this. Just in > case you pass by here in the future, the tracking infrastructure > should allow for this. OK, cool. Thanks for clarifying upstream PoV. :) Cheers, Phil