Show HN: We Implemented the IPv8 Internet-Draft in Linux, Libc, and BGP

Hacker News Top Products

Summary

The team at goonhost.rocks implemented the IPv8 Internet-Draft across the Linux kernel, Musl libc, iproute2, FRRouting, and a Go zone server, then deployed it on a 10-node multi-AS testbed with 112k+ routes. It works in isolated lab conditions but breaks in real-world scenarios.

No content available
Original Article
View Cached Full Text

Cached at: 08/14/26, 03:29 PM

# GoonHost — Unmatched VPS Slop & Dedicated Goy KVM Servers Source: [https://goonhost.rocks/blog/implementing-ipv8-internet-draft](https://goonhost.rocks/blog/implementing-ipv8-internet-draft) ## Show HN: We implemented the IPv8 Internet\-Draft in the Linux Kernel, Musl Libc, and BGP ## The Hook: Why We Built This A few weeks ago, an Internet\-Draft titled**[Internet Protocol Version 8 \(IPv8\) — draft\-thain\-ipv8\-02](https://www.ietf.org/archive/id/draft-thain-ipv8-02.html)**caught our eye\. The draft makes some extraordinary claims: - **Zero Address Exhaustion**: Every ASN holder automatically receives**4,294,967,296 host addresses**\($2^\{32\}$\)\. - **100% Backward Compatibility**: "IPv4 is a proper subset of IPv8\.\.\. There is no flag day and no forced migration\." - **Total Network Management**: Every packet is validated against DNS8 and WHOIS8; all elements are authorized via OAuth2 JWT tokens; and all core services \(DHCP, DNS, NTP, Syslog, WHOIS, NAT, ACLs\) are bundled into a single**"Zone Server"**\. Most network engineers would laugh this off as an April Fools RFC written by an enterprise architect on buzzword overdrive\. But instead of just arguing on mailing lists, the team at**`goonhost\.rocks`**decided to actually**build the entire specification from scratch**and test what happens when you deploy it across a distributed multi\-AS network\. --- ## What We Built \(Open Source Repositories\) We implemented the complete IPv8 stack from ring\-0 kernel code up to user\-space applications: 1. **Linux Kernel 6\.6 \([GitLab Repo](https://gitlab.turborigby.xyz/goonhost-experiments/linux)\)**:- Implemented native`AF\_INET8`\(address family 46\) supporting`SOCK\_STREAM`\(TCP8\),`SOCK\_DGRAM`\(UDP8\), and`SOCK\_RAW`\(RAW8\)\. - 28\-byte IPv8 header parsing, 64\-bit routing table lookups, and sysctl boundary drop rules \(`filter\_internal\_zones`,`filter\_rine`,`filter\_interior\_links`\)\. 2. **Musl Libc \([GitLab Repo](https://gitlab.turborigby.xyz/goonhost-experiments/musl)\)**:- Added`sockaddr\_in8`,`inet\_pton8`,`inet\_ntop8`,`getaddrinfo\(\)`, and`getnameinfo\(\)`for`64496\.10\.0\.0\.1`format addresses\. 3. **iproute2 \([GitLab Repo](https://gitlab.turborigby.xyz/goonhost-experiments/iproute2)\)**:- Native`ip \-8 route`and`ip \-8 addr`management commands\. 4. **FRRouting \(FRR\) \([GitLab Repo](https://gitlab.turborigby.xyz/goonhost-experiments/frrouting)\)**:- BGP8 daemon with Multi\-Protocol Extensions \(AFI/SAFI\) for peering and exchanging IPv8 routes\. 5. **IPv8 Zone Server Platform in Go \([GitLab Repo](https://gitlab.turborigby.xyz/goonhost-experiments/zoneserver)\)**:- Implemented all 10 RFC sub\-protocols: DHCP8 \(options 224–230\), DNS8 \(TYPE\_A8 88\), SNTP Stratum\-1, NetLog8 \(UDP 514 telemetry\), OAuth8 JWT server, WHOIS8 TCP 43/REST, ACL8, and XLATE8 stateful NAT\. 6. **Nginx & cURL \([Nginx Repo](https://gitlab.turborigby.xyz/goonhost-experiments/nginx)\|[cURL Repo](https://gitlab.turborigby.xyz/goonhost-experiments/curl)\)**:- Serving and requesting HTTP over 64\-bit IPv8 endpoints \(`http://64497\.20\.0\.0\.254:80/`\)\. 7. **10\-Node QEMU Multi\-AS Testbed**:- 4 Autonomous Systems \(**AS 64496, AS 64497, AS 64498, AS 64499**\) connected across multicast WAN/LAN segments, loaded with**112,000\+ active FIB routes**and continuous client traffic generation \(`trafficgen8`\)\. --- ## The Results: The Good, The Bad, and The Catastrophic ### The Good \(In a Lab Environment\) In an isolated sandbox, the protocol works surprisingly smoothly: - `curl \-i http://64497\.20\.0\.0\.254/`returns`HTTP/1\.1 200 OK`from Nginx across an inter\-AS WAN mesh\. - `dhcp8c`boots on an unconfigured interface, receives a dual\-gateway lease \(`\.254`Even /`\.253`Odd\), and syncs its clock via NTP8 in**2\.27 ms**\. - The Linux kernel`fib\_trie`handled**112,117 active routes**with sub\-millisecond lookup latency under continuous traffic\. --- ### The Bad: Why It Breaks in the Real World #### 1\. Path MTU \(PMTUD\) & Silent MSS Blackholing IPv8 addresses add 4 bytes to source and 4 bytes to destination, expanding the IP header from 20 to**28 bytes**\. - On a standard 1500\-byte MTU Ethernet link, standard IPv4 TCP packets \(1460\-byte payload \+ 20\-byte TCP \+ 28\-byte IPv8 =**1508 bytes**\) exceed the MTU\. - Because thousands of legacy middleboxes drop oversized packets without sending ICMP`Fragmentation Needed`messages, TLS handshakes and large file transfers hang indefinitely\. - **Fix**: Every router and host on earth must enforce**TCP MSS Clamping to 1452 bytes**\(or 1432 for 8to4 tunnels\)\. #### 2\. Multi\-Homing & Asymmetric uRPF \(BCP 38\) Drops In IPv8, your IP address is hard\-coded to your primary ASN \(`64496\.10\.0\.1`\)\. If you multihome with two upstream transit providers \(Provider A and Provider B\) and send outbound packets via Provider B: - Provider B’s ingress filters \(strict uRPF / BCP 38\) check if Provider B is the shortest path to AS 64496\. - Since Provider A is the primary route,**Provider B silently drops all your outbound traffic**as spoofed packets\. #### 3\. Legacy Switch ASICs Punt to CPU Slow\-Path Fixed\-function switch chips \(Broadcom Tomahawk/Trident, Cisco Silicon One\) in modern data centers have TCAM microcode hardwired for 32\-bit IPv4 \(`0x0800`\) and 128\-bit IPv6 \(`0x86DD`\)\. They do not know what EtherType`0x88B8`is\. - Packets cannot be switched at line rate \(400Gbps/800Gbps\) in hardware\. - Switches punt IPv8 frames to the control\-plane CPU exception queue, causing massive packet loss and throughput dropping from 400Gbps to <10Gbps\. #### 4\. The Monolithic Zone Server DDoS Target Putting DHCP, DNS, NTP, Syslog, OAuth2 auth, and NAT into one "Zone Server" gateway creates the ultimate single point of failure\. A simple UDP reflection attack against port 8080 or port 53 simultaneously knocks out time synchronization, dynamic addressing, token verification, and Internet egress for the entire company\. --- ### The Catastrophic: Economic Collapse for RIRs and Tier\-1 Upstreams #### 1\. RIRs \(ARIN, RIPE, APNIC\) Go Financially Bankrupt - RIRs are non\-profits funded by tiered annual fees based on the volume of IP space held\. - Under IPv8, registering a**single 32\-bit ASN**\($100–$500/yr\) gives you**4\.3 billion routable IP addresses**\. - Address volume is decoupled from fees, collapsing RIR operational revenues by**75% to 90%**\. - The multi\-billion dollar secondary IPv4 transfer market \($40–$55 per IP\) is wiped out overnight\. #### 2\. The Speculative "Run on 32\-bit ASNs" Because 1 ASN = 4\.3 Billion IPs, domain squatters and spammers will rush to hoard thousands of 32\-bit ASNs, depleting the global ASN registry within years\. #### 3\. Tier\-1 Transit Margin Destruction & Core TCAM Explosion - **DFZ Route Explosion**: Today's global BGP table has ~1\.15M routes\. In IPv8, with 115,000\+ ASNs announcing Tier\-1 and Tier\-2 subnets, the Default\-Free Zone expands to**3,000,000 to 5,000,000\+ active routes**, forcing billions of dollars in linecard replacements across global backbones\. - **RINE Peering Revenue Loss**: IPv8's RINE mandate \(`100\.0\.0\.0/8`\) forces zero\-cost regional peering, depriving Tier\-1 transit providers \(Lumen, Arelion, NTT\) of their high\-margin transit commit revenue that funds transoceanic subsea cables\. --- ## Read the Full Whitepaper We compiled our full data, test methodology, and protocol dissection into a comprehensive research paper: Let us know what you think in the comments\! —`goonhost\.rocks`Research Team [Back to all articles](https://goonhost.rocks/blog)

Similar Articles

Hacking the Go compiler to efficiently map IPv4 to IPv6

Lobsters Hottest

Vincent Bernat explores how to efficiently map IPv4 addresses to IPv6 in Go's netip.Addr, comparing a standard library addition, an unsafe helper, and hacking the Go compiler to optimize the netip.AddrFrom16(ip.As16()) pattern that maintainers prefer.

RFC8950: Announce IPv4 with an IPv6 next-hop

Hacker News Top

作者介绍了 RFC8950,该标准允许在 IPv6 网络上以 IPv6 下一跳通告 IPv4 路由(无需隧道),使骨干网可以仅运行 IPv6 而将 IPv4 作为边缘可选功能,并给出了基于 FRR 和 Containerlab 的实验演示。

Research carried out using NetBSD

Hacker News Top

This NetBSD gallery page highlights various academic and industrial research projects utilizing the operating system, including NASA's satellite TCP experiments, the KAME IPv6/IPsec project, and high-speed networking demonstrations.

IPv6 delegation, an unusually subtle failure mode

Lobsters Hottest

A blogger debugs a subtle failure on a custom x64 Linux router where restarting pppd causes new IPv6 prefix delegations while stale addresses with lingering preferred lifetimes remain, breaking IPv6 connectivity to sites like Google. The post traces the issue through networkd, NetworkManager, and the ISP delegation stack.

A Farewell to ARPs: IPv4 Service on IPv6-Only Networks

Lobsters Hottest

This article presents an IETF draft proposal to eliminate ARP and IPv4 subnets on IPv6-only networks, allowing IPv4 to run as a pure /32 service over IPv6 infrastructure without translation or tunnelling, addressing operational pain points like ARP storms and IPv4 address scarcity.