新的补丁允许构建仅支持IPv6的Linux系统,并可以选择弃用“遗留”IPv4。
New patches allow building Linux IPv6-only

原始链接: https://www.phoronix.com/news/Linux-IPv6-IPv4-Legacy-Knobs

Linux 内核开发者 David Woodhouse 提出了一系列补丁,旨在可能地启用仅 IPv6 的内核构建并逐步淘汰 IPv4 支持,但带有四月愚人节的意味。这些补丁引入了一个 `CONFIG_LEGACY_IP` 选项,允许开发者在内核编译期间切换 IPv4 功能。 目前,该补丁集主要在进程使用较旧的 IPv4 套接字时发出警告,将 IPv4 标记为“遗留”,以便将来可能移除。Woodhouse 澄清了他提出该建议的认真意图,倡导更清晰地分离 IPv4 和 IPv6 配置,以及构建仅支持一种协议的内核的可能性。 虽然完全弃用并非立即发生,但这些更改代表着朝着更简化和面向未来的内核迈出的一步,尤其对于优先采用 IPv6 的环境有益。这些补丁可在内核邮件列表中进行审查和讨论。

## Linux IPv6 专用补丁引发讨论 针对 Linux 内核提出的新补丁将允许构建仅支持 IPv6 的系统,从而在 Hacker News 上引发了热烈的讨论。虽然部分被当作玩笑提出,但这一想法点燃了关于互联网协议未来的争论。 许多评论者表达了对 IPv6 采用缓慢以及对地址隐私等功能的支持的沮丧。一些人提倡激励 IPv6 的使用,甚至建议对“传统 IP”(IPv4)施加延迟惩罚。然而,另一些人强烈反对强制过渡,理由是担心与现有基础设施的兼容性以及破坏已建立网络的可能性。 一个关键的争论点是 NAT(网络地址转换)在安全性和隐私方面被认为具有的优势,尽管它存在已知的缺点。人们也对 IPv6 配置的复杂性以及某些软件和服务中缺乏广泛支持表示担忧。最终,这场讨论凸显了对现代、可寻址互联网的渴望与维护与现有 IPv4 生态系统兼容性的实际情况之间的持续紧张关系。
相关文章

原文
Longtime Linux developer David Woodhouse sent out a patch series today to "deprecate legacy IP" support within the Linux kernel. While some of his commentary his April 1st-esque, he does acknowledge much of this work has merit. Ultimately it can allow for building a Linux kernel with IPv6-only support and working on allowing "legacy" IPv4 support to be disabled as part of the kernel build.

The set of six patches add a CONFIG_LEGACY_IP option to allow toggling IPv4 support for the kernel build. At the moment with the patches, there will just be a warning if a process listens on a legacy IP socket. It also "marks Legacy IP for deprecation" though in reality this part of the patch series is more akin for April Fools' Day.

Legacy IP option


The patches from David Woodhouse, an Amazon/AWS engineer, can be found on the kernel mailing list.

With the hatred for the April 1st Day, Woodhouse did clarify in a follow-up post with his clear intentions:

"Yeah. The date notwithstanding, I do actually think we should do most of this for real.

Maybe we don't get away with the actual deprecation and the warnings on use *just* yet, and *maybe* we won't even get away with calling the config option CONFIG_LEGACY_IP, although I would genuinely like to see us moving consistently towards saying "Legacy IP" instead of "IPv4" everywhere.

But we *should* clean up the separation of CONFIG_INET and CONFIG_IPV[64] and make it possible to build with either protocol alone."


So we'll see ultimately what comes out of this patch series but there is merit for allowing IPv4-only or IPv6-only kernel builds especially in more forward-looking environments.
联系我们 contact @ memedata.com