<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Ipv6 on Aperture Zone</title>
    <link>https://aperturezone.com/tags/ipv6/</link>
    <description>Recent content in Ipv6 on Aperture Zone</description>
    <image>
      <url>https://aperturezone.com/logo.webp</url>
      <link>https://aperturezone.com/logo.webp</link>
    </image>
    <generator>Hugo -- gohugo.io</generator>
    <language>fr-fr</language>
    <lastBuildDate>Fri, 01 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://aperturezone.com/tags/ipv6/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>GPO - Killing IPv6 once and for all</title>
      <link>https://aperturezone.com/gpo/no-ipv6/</link>
      <pubDate>Fri, 01 May 2026 00:00:00 +0000</pubDate>
      
      <guid>https://aperturezone.com/gpo/no-ipv6/</guid>
      <description>&lt;p&gt;I’m not against IPv6; it’s just that on a LAN that doesn’t need it, it’s pointless—it’s a box that’s checked by default in the network card settings that nobody asked for.&lt;/p&gt;
&lt;p&gt;We have a LAN. It runs on IPv4. It’s always run on IPv4. It will run on IPv4 until we change our infrastructure or the sun’s heat engulfs the Earth, whichever comes first.&lt;/p&gt;
&lt;p&gt;And yet, every time we check a network adapter on a Windows machine, we see this:&lt;/p&gt;</description>
    </item>
    
  </channel>
</rss>
