<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0">
    <channel>
        <title>Wireguard - Tag - MickoD://</title>
        <link>https://mickod.ie/tags/wireguard/</link>
        <description>Wireguard - Tag - MickoD://</description>
        <generator>Hugo -- gohugo.io</generator><language>en-gb</language><managingEditor>mick@mickod.ie (Mick O&#39;Donovan)</managingEditor>
            <webMaster>mick@mickod.ie (Mick O&#39;Donovan)</webMaster><lastBuildDate>Sat, 19 Sep 2026 20:32:17 &#43;0100</lastBuildDate><atom:link href="https://mickod.ie/tags/wireguard/" rel="self" type="application/rss+xml" /><item>
    <title>Dealing with IPv4 literals via an IPv6 only WAN</title>
    <link>https://mickod.ie/posts/2026-09-16-ipv4-literals-testing-from-an-ipv6-only-network/</link>
    <pubDate>Sat, 19 Sep 2026 20:32:17 &#43;0100</pubDate>
    <author>mick@mickod.ie (Mick O&#39;Donovan)</author>
    <guid>https://mickod.ie/posts/2026-09-16-ipv4-literals-testing-from-an-ipv6-only-network/</guid>
    <description><![CDATA[<h1 id="building-a-464xlat-home-network-to-help-getting-to-ipv4-literals">Building a 464XLAT home network to help getting to IPv4 literals</h1>
<p>I&rsquo;ve spent more than a few years over the years in various web-based rabbit holes online researching examples of how to try and remove any remaining barriers to turning off IPv4 on my (or any other) WAN. There&rsquo;s plenty of resources out there but none that I found which completely explain the <strong>FULL</strong> end-to-end deployment. This blog post will set out to document that a little better for (mainly) future me to use as a reference but obviously for anyone that needs it to reference.</p>]]></description>
</item>
</channel>
</rss>
