<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Ipv6 on Support Tools</title><link>https://support.tools/tags/ipv6/</link><description>Recent content in Ipv6 on Support Tools</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Tue, 27 Oct 2026 00:00:00 -0500</lastBuildDate><atom:link href="https://support.tools/tags/ipv6/index.xml" rel="self" type="application/rss+xml"/><item><title>Configuring IPv4 and IPv6 Preferences in Linux: A Comprehensive Guide</title><link>https://support.tools/configuring-ipv4-ipv6-preferences/</link><pubDate>Sun, 15 Feb 2026 09:00:00 -0600</pubDate><guid>https://support.tools/configuring-ipv4-ipv6-preferences/</guid><description>&lt;p&gt;Master the art of configuring IPv4 and IPv6 preferences in Linux systems to optimize network performance and reliability.&lt;/p&gt;</description></item><item><title>Running K3s in an IPv6-Only Environment with Cilium</title><link>https://support.tools/k3s-ipv6-cilium/</link><pubDate>Sun, 01 Jun 2025 00:00:00 -0500</pubDate><guid>https://support.tools/k3s-ipv6-cilium/</guid><description>&lt;p&gt;Most guides for Kubernetes focus on IPv4 by default, but IPv6 is no longer a second-class citizen. In this post, I walk through configuring a &lt;strong&gt;K3s cluster using only IPv6&lt;/strong&gt;, with &lt;strong&gt;Cilium&lt;/strong&gt; as the CNI, and &lt;strong&gt;BGP&lt;/strong&gt; to announce addresses to my router. This setup runs entirely on a public IPv6 prefix—no dual-stack, no IPv4 fallback.&lt;/p&gt;</description></item><item><title>Enterprise IPv6 Deployment and Dual-Stack Transition: Complete Guide to Production IPv6 Implementation and Network Migration</title><link>https://support.tools/ipv6-enterprise-deployment-dual-stack-transition-guide/</link><pubDate>Tue, 22 Apr 2025 10:00:00 -0500</pubDate><guid>https://support.tools/ipv6-enterprise-deployment-dual-stack-transition-guide/</guid><description>&lt;p&gt;IPv6 deployment in enterprise environments requires comprehensive planning, strategic implementation approaches, and sophisticated transition mechanisms to ensure business continuity while modernizing network infrastructure. This guide covers enterprise IPv6 architecture design, dual-stack implementation strategies, migration methodologies, and production-grade deployment frameworks for large-scale organizational networks.&lt;/p&gt;</description></item><item><title>NAT64 and DNS64 on Linux: Tayga and BIND 9 Configuration</title><link>https://support.tools/nat64-dns64-ipv6-transition-enterprise-guide/</link><pubDate>Tue, 15 Apr 2025 10:00:00 -0500</pubDate><guid>https://support.tools/nat64-dns64-ipv6-transition-enterprise-guide/</guid><description>&lt;p&gt;NAT64 lets IPv6-only clients reach IPv4-only servers: DNS64 synthesizes an AAAA record inside a NAT64 prefix such as &lt;code&gt;64:ff9b::/96&lt;/code&gt;, and a NAT64 gateway translates packets sent to that prefix into IPv4. This page gives a working Tayga gateway and BIND 9 resolver first, then the high-availability, monitoring and prefix planning material for larger networks.&lt;/p&gt;</description></item><item><title>Force apt to Use IPv4 (Acquire::ForceIPv4) and Prefer IPv4</title><link>https://support.tools/configure-ipv4-ipv6-preference/</link><pubDate>Sun, 30 Mar 2025 09:00:00 -0600</pubDate><guid>https://support.tools/configure-ipv4-ipv6-preference/</guid><description>&lt;p&gt;A comprehensive guide to managing IPv4 and IPv6 preferences in Linux systems, helping you optimize network connectivity and resolve common issues.&lt;/p&gt;</description></item><item><title>Adventures in IPv6 Part 2</title><link>https://support.tools/ipv6-adventures-part-2/</link><pubDate>Sun, 08 Dec 2024 12:00:00 -0500</pubDate><guid>https://support.tools/ipv6-adventures-part-2/</guid><description>&lt;p&gt;As the world inches toward IPv6, my quest to run this blog on IPv6-only infrastructure continues. While progress has been made, challenges abound—from SMTP configurations to Nodemailer quirks and Docker networking.&lt;/p&gt;</description></item><item><title>IPv6 Is A Disaster (but we can fix it)</title><link>https://support.tools/ipv6-adventures-part-1/</link><pubDate>Wed, 04 Dec 2024 12:00:00 -0500</pubDate><guid>https://support.tools/ipv6-adventures-part-1/</guid><description>&lt;p&gt;With IPv4 costs rising and availability shrinking, the shift to IPv6 seems inevitable. But as this blog reveals, transitioning to IPv6 is fraught with challenges and broken dependencies. Here&amp;rsquo;s an exploration of what works, what doesn&amp;rsquo;t, and how to bridge the gap.&lt;/p&gt;</description></item></channel></rss>