shadowtofu1h ago

Linux Kernel Mailing List: Deprecate Legacy IP

https://discuss.tchncs.de/post/57652606

Linux Kernel Mailing List: Deprecate Legacy IP - tchncs

A kernel patch series titled “Deprecate Legacy IP” was submitted by David Woodhouse: >RFC1883, the IPv6 standard, was published in the final decade of the 1900s. That’s closer in time to the Apollo 11 moon landing than it was to today. > > Even our esteemed Maddog has worked with computers for longer in the IPv6 era, than he ever did before it. > > Yet Linux still can’t even be built with only IPv6 support and without support for Legacy IP. This long overdue patch series fixes that, and immediately marks Legacy IP for deprecation. > > It also cleans up a few tautological “INET && IPV6” and “INET || IPV6” checks, since IPV6 (and now LEGACY_IP) cannot be selected without the overall CONFIG_INET option. > > For now, we only add a warning when a process listens on a Legacy IP socket (since you can listen on IPv6 and still accept connections which have come through a timewarp from the 20th century. Adding warnings for making outbound connections or accepting on Legacy IP can come later. > > > I would be happy if “Legacy IP” ceased to be the “industry standard” > > and IPv6 be the default, even if I had to beat IPv6 into the head of > > every single network administrator’s head with a shovel.’ said Jon > > ‘maddog’ Hall, ancient supporter of Free and Open Source Software. Also see this follow-up post [https://lore.kernel.org/lkml/[email protected]/]: > 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.

GripNews3h ago
🌗 Linux 新補丁推動 IPv6 純協議運作，並新增停用「傳統」IPv4 選項
➤ 邁向單一協議網路：Linux 核心網路架構的現代化轉型
✤ https://www.phoronix.com/news/Linux-IPv6-IPv4-Legacy-Knobs
資深 Linux 開發者 David Woodhouse 近期提交了一系列核心補丁，旨在推動將 IPv4 標記為「傳統協議」（Legacy IP），並允許編譯僅支援 IPv6 的 Linux 核心。儘管這項發布選在愚人節當日且帶有部分戲謔成分，但作者明確指出，其技術核心是為了改善核心架構，實現 CONFIG_INET 與網路協議堆疊的模組化分離，讓開發者未來能根據需求靈活選擇僅編譯 IPv4 或 IPv6，以優化特定環境下的網路配置。
+ 雖然 IPv4 離徹底消失還很遠，但在嵌入式或特定雲端環境中，能夠剔除掉冗餘的協議堆疊確實能有效縮小核心體積。
+ 稱呼 IPv4 為「Legacy IP」聽起來既諷刺又現實，這反映了核心開發社羣對於網路架構現代化的
#Linux 核心開發 #IPv6 #IPv4 網路協議 #系統架構
New Patches Allow Building Linux IPv6-Only, Option To Deprecate "Legacy" IPv4

Longtime Linux developer David Woodhouse sent out a patch series today to 'deprecate legacy IP' support within the Linux kernel

N-gated Hacker News3h ago
Ah, nothing screams "forward-thinking tech" like cutting-edge patches to ditch "legacy" IPv4 in favor of shiny #IPv6. 🦖✨ Because, who needs a robust, globally functional internet protocol when you can gamble on an IPv6-only utopia? 😅 #LivingOnTheEdge
https://www.phoronix.com/news/Linux-IPv6-IPv4-Legacy-Knobs #forwardthinkingtech #legacyprotocol #internetinnovation #techtrends #HackerNews #ngated
New Patches Allow Building Linux IPv6-Only, Option To Deprecate "Legacy" IPv4

Longtime Linux developer David Woodhouse sent out a patch series today to 'deprecate legacy IP' support within the Linux kernel

Hacker News3h ago

New Patches Allow Building Linux IPv6-Only, Option to Deprecate "Legacy" IPv4

https://www.phoronix.com/news/Linux-IPv6-IPv4-Legacy-Knobs

#HackerNews #Linux #Patches #IPv6 #IPv4 #Networking #Technology

New Patches Allow Building Linux IPv6-Only, Option To Deprecate "Legacy" IPv4

Longtime Linux developer David Woodhouse sent out a patch series today to 'deprecate legacy IP' support within the Linux kernel

kravietz 🦇7h ago

A few random thoughts from my yesterday’s #Akkoma instance failure:

  • Elixir libraries used by #Pleroma and #Akkoma suck at #IPv6 - this manifests by rather puzzling error messages like “I can’t resolve your Postgres server name” but it’s because it only resolves to AAAA, same for egress HTTP proxy
  • Postgres library can be made to work by rather ugly workarounds which don’t always work across version upgrades, and for HTTP proxy I had to set up a local IPv4-only Squid proxy exclusively for Akkoma to be able to reach the Internet
  • Fediverse instances in general massively increase load of the local DNS resolver because the whole point of federation is continuous updates sent to thousands of other instances, each using a different domain name in hundreds of the new TLDs
  • especially the latter impacts #DNSSEC validation and caching - nothing wrong with Fediverse here, you just need to be aware of that as a scaling problem
  • if you’re not aware, you can mistakenly blame the latter on the former, when “things stop working” as they did yesterday - Fediverse was only one of the impacted services but mostly visible for me

The primary solution was to spread DNS resolution load on two Unbound instances which I already had on the edge firewalls, except one of them was slacking as a redundancy instance. The other was to enable RFC 8767 serving of stale responses in Unbound.

Thomas Schäfer8h ago

Amazon CloudFront now supports BYOIP for IPv6 through VPC IPAM integration
Posted on: Mar 31, 2026

https://aws.amazon.com/about-aws/whats-new/2026/03/cloudfront-byoip-ipv6-vpc-ipam/

#ipv6 #aws

Amazon CloudFront now supports BYOIP for IPv6 through VPC IPAM integration

Discover more about what's new at AWS with Amazon CloudFront now supports BYOIP for IPv6 through VPC IPAM integration

Amazon Web Services, Inc.
Show threadvoided warranty12h ago

they think they found the issue.

here is their reply:

"The Problem: In many Qualcomm-based (QCA) drivers, the Multicast Snooping (MCS) module is programmed to ignore "well-known" or "permanent" multicast addresses (reserved by IANA) for snooping purposes. It floods them to all ports to ensure compatibility with network protocols that rely on these addresses. Like the one that you are choosing here is just the permanent multicast address "ff05::1234".

The Consequence: Because the system doesn't "snoop" these addresses, it never learns which specific client wants the traffic. Without this "MDB" entry, the Access Point cannot perform Multicast-to-Unicast (M2U) conversion, which is essential for stable video/data streaming over Wi-Fi.

The Solution: Moving to the ff3x::/16 range (often used for SSM - Source-Specific Multicast) or other non-permanent ranges allows the MCS to intercept the join requests and create the necessary entries for optimization."

I then tried ff35::1234 and it did not work #IPv6 #multicast #cursed

Show threadJason Tubnor 🇦🇺18h ago
@ironicbadger and still no #IPv6
Show threadThomas Schäfer22h ago

in case you want check some examples by yourself:

here is the extracted list

https://tschaefer.dynv6.net/1212hosts.txt

#ipv6

Show threadThomas Schäfer22h ago

https://commoncrawl.github.io/ipv6-analysis/

From the list of the 1212 I took some examples.

https://www.fcc.gov/
https://www.ups.com/

They work for me with the browser firefox.

Only wget/curl doesn't work.
🤨

#akamai

#ipv6

IPv6 Adoption Across the Top 100,000 Web Hosts

A measurement study of IPv6 adoption among the 100,000 most-linked web hosts using the Common Crawl Web Graph. 38.1% have AAAA records; 36.9% are reachable over IPv6.

Common Crawl