<?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 Wirez</title><link>https://wirez.top/tags/ipv6/</link><description>Recent content in Ipv6 on Wirez</description><generator>Hugo</generator><language>en</language><lastBuildDate>Thu, 09 Apr 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://wirez.top/tags/ipv6/index.xml" rel="self" type="application/rss+xml"/><item><title>Akvorado IPv6 Visibility: See SOHO Traffic Clearly</title><link>https://wirez.top/posts/akvorado-ipv6-visibility-see-soho-traffic-clearly/</link><pubDate>Thu, 09 Apr 2026 00:00:00 +0000</pubDate><guid>https://wirez.top/posts/akvorado-ipv6-visibility-see-soho-traffic-clearly/</guid><description>&lt;meta charset="utf-8">
&lt;!-- wp:paragraph {"className":"std-text"} -->
&lt;!-- /wp:paragraph -->
&lt;!-- wp:paragraph {"className":"std-text"} -->
&lt;p class="std-text">Deploying Akvorado on modest hardware like a 6-core Ryzen NUC eliminates blind spots in &lt;strong>IPv6-first networks&lt;/strong> instantly. This guide argues that open-source flow analysis via &lt;strong>Akvorado&lt;/strong> is now essential for SOHO administrators to visualize traffic without enterprise overhead. Readers will learn how &lt;strong>NetFlow enrichment&lt;/strong> leverages &lt;strong>SNMP queries&lt;/strong> to map interface indices, the mechanics of &lt;strong>packet sampling&lt;/strong> intervals, and a streamlined &lt;strong>Docker Compose&lt;/strong> deployment strategy.&lt;/p></description></item><item><title>IPv6 loops explained: Stop packet amplification now</title><link>https://wirez.top/posts/ipv6-loops-explained-stop-packet-amplification-now/</link><pubDate>Thu, 26 Mar 2026 00:00:00 +0000</pubDate><guid>https://wirez.top/posts/ipv6-loops-explained-stop-packet-amplification-now/</guid><description>&lt;meta charset="utf-8">
&lt;!-- wp:paragraph {"className":"std-text"} -->
&lt;!-- /wp:paragraph -->
&lt;!-- wp:paragraph {"className":"std-text"} -->
&lt;p class="std-text">Routing loops can exponentially amplify traffic when routers duplicate packets, a flaw prevalent in 34% of assigned &lt;a href="https://datatracker.ietf.org/doc/html/rfc8200" target="_blank" rel="noopener noreferrer">IPv6&lt;/a> blocks.&lt;/p>
&lt;!-- /wp:paragraph -->
&lt;!-- wp:paragraph {"className":"std-text"} -->
&lt;p class="std-text">The core thesis is clear: the sparse population of &lt;strong>IPv6 address space&lt;/strong> combined with misconfigured &lt;strong>provider-aggregatable&lt;/strong> assignments creates a fertile ground for &lt;strong>packet amplification&lt;/strong> that network operators are lazily ignoring. While cloud-native workloads drive adoption, the underlying routing hygiene has not kept pace, leaving infrastructure vulnerable to self-inflicted &lt;strong>DDoS attacks&lt;/strong>. Research indicates that despite the simplicity of the fix, the community fails to prioritize these dangerous misconfigurations, allowing unnecessary load to congest links and destabilize the global internet.&lt;/p></description></item><item><title>IPv6 physical labs reshape APNIC training for 2026</title><link>https://wirez.top/posts/ipv6-physical-labs-reshape-apnic-training-for-2026/</link><pubDate>Wed, 18 Mar 2026 00:00:00 +0000</pubDate><guid>https://wirez.top/posts/ipv6-physical-labs-reshape-apnic-training-for-2026/</guid><description>&lt;meta charset="utf-8">
&lt;!-- wp:paragraph {"className":"std-text"} -->
&lt;!-- /wp:paragraph -->
&lt;!-- wp:paragraph {"className":"std-text"} -->
&lt;p class="std-text">With 50% &lt;a href="https://datatracker.ietf.org/doc/html/rfc8200" target="_blank" rel="noopener noreferrer">IPv6&lt;/a> capability already reached in the Asia Pacific by April 2025, the region&amp;#039;s network operators can no longer treat next-generation protocols as optional experiments. The refreshed &lt;strong>IPv6 Deployment Workshop&lt;/strong> at APRICOT 2026 demonstrates that shifting from dual-stack to &lt;strong>IPv6-mostly&lt;/strong> architectures requires entirely new operational tooling and curriculum designs.&lt;/p></description></item><item><title>IPv6 native traffic: How to push past 80% at home</title><link>https://wirez.top/posts/ipv6-native-traffic-how-to-push-past-80-at-home/</link><pubDate>Mon, 16 Mar 2026 00:00:00 +0000</pubDate><guid>https://wirez.top/posts/ipv6-native-traffic-how-to-push-past-80-at-home/</guid><description>&lt;meta charset="utf-8">
&lt;!-- wp:paragraph {"className":"std-text"} -->
&lt;!-- /wp:paragraph -->
&lt;!-- wp:paragraph {"className":"std-text"} -->
&lt;p class="std-text">With &lt;strong>Debian ISO downloads&lt;/strong> forcing native connectivity, home networks can push &lt;strong>IPv6 traffic&lt;/strong> above &lt;strong>80%&lt;/strong> as proven by &lt;strong>Terry Sweester&lt;/strong>.&lt;/p></description></item><item><title>IPv6 data shows DNS issues are gone</title><link>https://wirez.top/posts/ipv6-data-shows-dns-issues-are-gone/</link><pubDate>Thu, 05 Mar 2026 00:00:00 +0000</pubDate><guid>https://wirez.top/posts/ipv6-data-shows-dns-issues-are-gone/</guid><description>&lt;meta charset="utf-8">
&lt;!-- wp:paragraph {"className":"std-text"} -->
&lt;!-- /wp:paragraph -->
&lt;!-- wp:paragraph {"className":"std-text"} -->
&lt;p class="std-text">Geoff Huston&amp;#039;s advertising-based experiments reveal that the negative impact of &lt;a href="https://en.wikipedia.org/wiki/Domain_Name_System" target="_blank" rel="noopener noreferrer">DNS&lt;/a> resolution via &lt;a href="https://datatracker.ietf.org/doc/html/rfc8200" target="_blank" rel="noopener noreferrer">IPv6&lt;/a> is now negligible. &lt;a href="https://blog.apnic.net/2020/06/23/measuring-ipv6/" target="_blank" rel="noopener noreferrer">&lt;a href="https://www.apnic.net/" target="_blank" rel="noopener noreferrer">APNIC&lt;/a>&amp;#039;s measuring ipv6&lt;/a> This data drives the core thesis: the internet has shifted from asking if IPv6 breaks DNS to confirming it is ready for widespread, normative deployment as a &lt;strong>Best Current Practice&lt;/strong>.&lt;/p></description></item><item><title>IPv6 DNS fails 40%: Why dual-stack is essential</title><link>https://wirez.top/posts/ipv6-dns-fails-40-why-dual-stack-is-essential/</link><pubDate>Mon, 02 Mar 2026 00:00:00 +0000</pubDate><guid>https://wirez.top/posts/ipv6-dns-fails-40-why-dual-stack-is-essential/</guid><description>&lt;meta charset="utf-8">
&lt;!-- wp:paragraph {"className":"std-text"} -->
&lt;!-- /wp:paragraph -->
&lt;!-- wp:paragraph {"className":"std-text"} -->
&lt;p class="std-text">A staggering 40% failure rate plagues large &lt;a href="https://en.wikipedia.org/wiki/Domain_Name_System" target="_blank" rel="noopener noreferrer">DNS&lt;/a> responses over &lt;a href="https://datatracker.ietf.org/doc/html/rfc8200" target="_blank" rel="noopener noreferrer">IPv6&lt;/a> when packet fragmentation is required, exposing critical gaps in current infrastructure.&lt;/p></description></item><item><title>APNIC IPv6 /32 vs /36: Why I Back the Larger Block</title><link>https://wirez.top/posts/apnic-ipv6-32-vs-36-why-i-back-the-larger-block/</link><pubDate>Tue, 24 Feb 2026 00:00:00 +0000</pubDate><guid>https://wirez.top/posts/apnic-ipv6-32-vs-36-why-i-back-the-larger-block/</guid><description>&lt;meta charset="utf-8">
&lt;!-- wp:paragraph {"className":"std-text"} -->
&lt;!-- /wp:paragraph -->
&lt;!-- wp:paragraph {"className":"std-text"} -->
&lt;p class="std-text">&lt;a href="https://www.apnic.net/" target="_blank" rel="noopener noreferrer">APNIC&lt;/a> serves over four billion people, yet debates persist on reducing minimum &lt;strong>IPv6 address&lt;/strong> blocks to a /36. &lt;a href="https://blog.apnic.net/2026/01/20/ip-addresses-through-2025/" target="_blank" rel="noopener noreferrer">APNIC&amp;#039;s ip addresses through 2025&lt;/a>&lt;/p></description></item><item><title>IPv6 infrastructure: Master the 24-hour RIPE course</title><link>https://wirez.top/posts/ipv6-infrastructure-master-the-24-hour-ripe-course/</link><pubDate>Tue, 10 Feb 2026 00:00:00 +0000</pubDate><guid>https://wirez.top/posts/ipv6-infrastructure-master-the-24-hour-ripe-course/</guid><description>&lt;meta charset="utf-8">
&lt;!-- wp:paragraph {"className":"std-text"} -->
&lt;!-- /wp:paragraph -->
&lt;!-- wp:paragraph {"className":"std-text"} -->
&lt;p class="std-text">The &lt;a href="https://www.ripe.net/" target="_blank" rel="noopener noreferrer">RIPE NCC&lt;/a>&amp;#039;s new 24-hour course addresses the critical gap in &lt;strong>IPv6 infrastructure&lt;/strong> design for modern networks. &lt;a href="https://www.ripe.net/publications/ipv6-info-centre/training-and-materials/" target="_blank" rel="noopener noreferrer">RIPE&amp;#039;s training and materials&lt;/a>&lt;/p></description></item></channel></rss>