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=-5.2 required=3.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS, USER_AGENT_SANE_1 autolearn=no 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 E976BC4338F for ; Tue, 27 Jul 2021 23:02:36 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id CC2C160EB2 for ; Tue, 27 Jul 2021 23:02:36 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232556AbhG0XCg (ORCPT ); Tue, 27 Jul 2021 19:02:36 -0400 Received: from mail.netfilter.org ([217.70.188.207]:37010 "EHLO mail.netfilter.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232198AbhG0XCg (ORCPT ); Tue, 27 Jul 2021 19:02:36 -0400 Received: from netfilter.org (bl11-146-165.dsl.telepac.pt [85.244.146.165]) by mail.netfilter.org (Postfix) with ESMTPSA id 112606429D; Wed, 28 Jul 2021 01:02:03 +0200 (CEST) Date: Wed, 28 Jul 2021 01:02:30 +0200 From: Pablo Neira Ayuso To: Alex Forster Cc: Kyle Bowman , kernel-team , Jozsef Kadlecsik , Florian Westphal , "David S. Miller" , Jakub Kicinski , netfilter-devel@vger.kernel.org, coreteam@netfilter.org, linux-kernel@vger.kernel.org, Network Development Subject: Re: [PATCH] netfilter: xt_NFLOG: allow 128 character log prefixes Message-ID: <20210727230230.GA30104@salvia> References: <20210727190001.914-1-kbowman@cloudflare.com> <20210727195459.GA15181@salvia> <20210727211029.GA17432@salvia> <20210727212730.GA20772@salvia> <20210727215240.GA25043@salvia> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.1 (2018-07-13) Precedence: bulk List-ID: X-Mailing-List: netfilter-devel@vger.kernel.org On Tue, Jul 27, 2021 at 05:45:09PM -0500, Alex Forster wrote: > > Yes, you can update iptables-nft to use nft_log instead of xt_LOG, > > that requires no kernel upgrades and it will work with older kernels. > > I've always been under the impression that mixing xtables and nftables > was impossible. Forgive me, but I just want to clarify one more time: > you're saying we should be able to modify iptables-nft such that the > following rule will use xt_bpf to match a packet and then nft_log to > log it, rather than xt_log as it does today? You could actually use *any* of the existing extensions to match a packet, the matching side is completely irrelevant to this picture. As I said, userspace iptables-nft can be updated to use nft_log instead of xt_LOG. > iptables-nft -A test-chain -d 11.22.33.44/32 -m bpf --bytecode > "1,6 0 0 65536" -j NFLOG --nflog-prefix > "0123456789012345678901234567890123456789012345678901234567890123456789" > > We had some unexplained performance loss when we were evaluating > switching to iptables-nft, but if this sort of mixing is possible then > it is certainly worth reevaluating.