<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0">
    <channel>
        <title>Ipv6 - Tag - MickoD://</title>
        <link>https://mickod.ie/tags/ipv6/</link>
        <description>Ipv6 - 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/ipv6/" 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>
<item>
    <title>Back to the HOMELAN</title>
    <link>https://mickod.ie/posts/2018-11-09-back-to-the-homelan/</link>
    <pubDate>Fri, 09 Nov 2018 15:32:03 &#43;0100</pubDate>
    <author>mick@mickod.ie (Mick O&#39;Donovan)</author>
    <guid>https://mickod.ie/posts/2018-11-09-back-to-the-homelan/</guid>
    <description><![CDATA[<p>This week I spent a tone of time working on my HOMELAN with a couple of goals in mind.</p>
<ul>
<li>I needed to road-test my employer&rsquo;s <a href="https://www.globalservices.bt.com/en/solutions/products/agile-connect" target="_blank" rel="noopener noreffer ">&ldquo;Agile Connect&rdquo;</a> SD-WAN product which is based on <a href="http://www.nuagenetworks.net/products/virtualized-network-services/" target="_blank" rel="noopener noreffer ">Nokia Nuage Network&rsquo;s VNS SD-WAN offering</a> and had to carve off a new VLAN to plug the <a href="https://onestore.nokia.com/asset/201441" target="_blank" rel="noopener noreffer ">NSG-E</a> into.</li>
</ul>
<p>and</p>
<ul>
<li>I wanted to ensure my HOMELAN was completely v6-ified once again following several months using Google Wifi without my hosts having native v6.</li>
</ul>
<h2 id="connecting-my-nsg">Connecting my NSG</h2>
<p>There are a couple of us in BT Ireland that have been given the task of road-testing the NSGs and indeed our service wrap for this technology which has a product name of <a href="https://www.globalservices.bt.com/en/solutions/products/agile-connect" target="_blank" rel="noopener noreffer ">&ldquo;Agile Connect&rdquo;</a>. The intention is that we have active familiarity with the technology when we are doing customer engagement and can demonstrate our orchestration and reporting portal with ease and comfort.</p>]]></description>
</item>
</channel>
</rss>
