From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from shards.monkeyblade.net ([184.105.139.130]:60336 "EHLO shards.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752970AbeBSPbl (ORCPT ); Mon, 19 Feb 2018 10:31:41 -0500 Date: Mon, 19 Feb 2018 10:31:39 -0500 (EST) Message-Id: <20180219.103139.2230101523652161323.davem@davemloft.net> To: laforge@gnumonks.org Cc: fw@strlen.de, daniel@iogearbox.net, netdev@vger.kernel.org, netfilter-devel@vger.kernel.org, alexei.starovoitov@gmail.com Subject: Re: [PATCH RFC 0/4] net: add bpfilter From: David Miller In-Reply-To: <20180219152746.GH5490@nataraja> References: <20180219145935.GE6333@breakpoint.cc> <20180219.101335.8419642951000951.davem@davemloft.net> <20180219152746.GH5490@nataraja> Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: netdev-owner@vger.kernel.org List-ID: From: Harald Welte Date: Mon, 19 Feb 2018 16:27:46 +0100 > On Mon, Feb 19, 2018 at 10:13:35AM -0500, David Miller wrote: > >> Florian, first of all, the whole "change the iptables binary" idea is >> a non-starter. For the many reasons I have described in the various >> postings I have made today. >> >> It is entirely impractical. > > Why is it practical to replace your kernel but not practical to replace > a small userspace tool running on top of it? The container is just userspace components. Those are really baked in and are never changing. The hosting element, on the other hand, can upgrade the kernel in that scenerio no problem. This is how cloud hosting environments work.