Received: by 2002:a25:4158:0:0:0:0:0 with SMTP id o85csp1950474yba; Thu, 25 Apr 2019 08:17:50 -0700 (PDT) X-Google-Smtp-Source: APXvYqwsf9iEtNU14KcuJw4BmiLJLaXwuglfzKeDxxpB9TiflBLMBOdCQtpAFGVUK4jtAyX+ZnFx X-Received: by 2002:a62:e215:: with SMTP id a21mr41343208pfi.30.1556205470689; Thu, 25 Apr 2019 08:17:50 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1556205470; cv=none; d=google.com; s=arc-20160816; b=dI7DYTng4fdjHJctOj2A5P1CID3SMFJbpgPc4dj7HuStR81ssIgYMXN6CtxqDqm7fn oqxalL1LEt9+yvPMzdx7YwAj8nAf7vBjnzLdPS7GD02j2/i0KKzgEvbhqr2XMCzk0KsS 3S8celszPWdu4fbtlTVuOOdejiSJxaHT+azjiM8AlT+ngNotq7YUtlanW0IaDhlvNu0/ omzvEwb8vaXI2c3PhXibvo4+23eTVUkrM1Jy5cSPrUaSHmOcW6kmK8oUj80PLDbaVaPT Yw45m7LCMoki9rSCdI1i94kjILZR+M31OllC4wjMT6al9UxcMuo5oxHf0p6K3WHlOT4X PKFw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:message-id:date:subject:to :from:user-agent; bh=yQg3ohXghka/urRfkkcnIys22ql+Fw/d5bx39ynTv0I=; b=h26D0IMODOMD4ZWGSHnziO9MGMU7CwB1tdAr1NkmUhfECQc3hDLpcjjcutvxyuyRWI eoocpXkjtz79seWSnRFgawLSdTDIovicJLTPJ4I3rIzptCDsoz7p/heHd/Hpkzliyi5j nkfXC56/Km8xJMNBwh6S1Gj+T96XGxwmcx7FeCbdGQzcqJAypMK9jk3Dm9cvP+B1l6VN elRtBo0w2MouwHG3doj8qvJ5P9DXyHQOQJNAzPu1kiE4+KCsqaBr2WMZfOC43nlT9h8X g8mN90JC8utv0v+4kGfxymll1L1/tU6TMq5LtORrbaZlo5Ujbm+yF1xiGusBJVg0u3rb P45g== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id x24si5388830plr.207.2019.04.25.08.17.34; Thu, 25 Apr 2019 08:17:50 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728714AbfDYJkE (ORCPT + 99 others); Thu, 25 Apr 2019 05:40:04 -0400 Received: from mx.ungleich.ch ([185.203.112.16]:39638 "EHLO smtp.ungleich.ch" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727536AbfDYJkD (ORCPT ); Thu, 25 Apr 2019 05:40:03 -0400 X-Greylist: delayed 442 seconds by postgrey-1.27 at vger.kernel.org; Thu, 25 Apr 2019 05:40:02 EDT Received: from nico.schottelius.org (localhost [IPv6:::1]) by smtp.ungleich.ch (Postfix) with ESMTP id 133882358E for ; Thu, 25 Apr 2019 11:32:39 +0200 (CEST) Received: by nico.schottelius.org (Postfix, from userid 1000) id 0611D1A0100C; Thu, 25 Apr 2019 11:32:39 +0200 (CEST) User-agent: mu4e 1.0; emacs 26.1 From: Nico Schottelius To: linux-kernel@vger.kernel.org Subject: How to turn off IPv4 without disabling IPv6 Date: Thu, 25 Apr 2019 11:32:38 +0200 Message-ID: <87pnpaqvk9.fsf@line.ungleich.ch> MIME-Version: 1.0 Content-Type: text/plain Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Good morning kernel hackers, we are a small company in Switzerland running some IPv6 only networks. The systems in the IPv6 only networks do not need any IPv4 support anymore and thus for switches/routers we turned the support off. Today we tried to turn off IPv4 in the Linux kernel at compile time. But it seems that as soon as we turn off CONFIG_INET, CONFIG_IPV6 is automatically turned off as well. While you can argue that "turning off IPv4 is not necessary", this is not our point. As IPv4 resources have depleted almost everywhere in the world a move to IPv6 is inevitable, especially if you are a small organisation offering Internet services. Being a (new) small organisation you are already disadvantaged in terms of IPv4 resources that you can afford, so our objective is to make the life in the IPv6 world as easy as possible. If we can build operating systems that don't run IPv4 anymore, operators have at least a certain degree of complexity less and can start fresh into adventures, without having to care about iptables, about IPv4 routing, etc. Coming back to my original question: is there a way or how would we turn off IPv4 support in the Linux kernel? So far the only operating system that is reported to be able to run without IPv4 is FreeBSD [0], but I hope we can add more in the near future. Best, Nico [0] https://ungleich.ch/en-us/cms/blog/2019/01/09/die-ipv4-die/ -- Your Swiss, Open Source and IPv6 Virtual Machine. Now on www.datacenterlight.ch.