<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Donavan Fritz</title>
    <link>/</link>
    <description>Recent content on Donavan Fritz</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 12 Sep 2021 00:00:00 +0000</lastBuildDate>
    <atom:link href="/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>This Site is Still IPv6 Only</title>
      <link>/this-site-is-still-ipv6-only/</link>
      <pubDate>Sun, 12 Sep 2021 00:00:00 +0000</pubDate>
      <guid>/this-site-is-still-ipv6-only/</guid>
      <description>&lt;p&gt;This site is still IPv6 only.&#xA;One drawback from my &lt;a href=&#34;/this-site-is-ipv6-only/&#34;&gt;original attempt&lt;/a&gt; at doing IPv4-less was the failure mode.&#xA;IPv4 users did not understand the problem.&#xA;It would be indistinguishable if this site was actually &lt;em&gt;down&lt;/em&gt;, or if the user did not support IPv6.&lt;/p&gt;&#xA;&lt;p&gt;For example, using curl we see a &lt;code&gt;Could not resolve host&lt;/code&gt; error.&#xA;This error can give the impression that this site is offline, vs incorrect IP protocol version.&lt;/p&gt;</description>
    </item>
    <item>
      <title>This Site is IPv6 Only</title>
      <link>/this-site-is-ipv6-only/</link>
      <pubDate>Mon, 06 Sep 2021 00:00:00 +0000</pubDate>
      <guid>/this-site-is-ipv6-only/</guid>
      <description>&lt;p&gt;This site is now IPv6 only.&#xA;I have been thinking about this for a long time, and I decided to just do it.&#xA;A records have been removed, and only AAAA exists for reaching this site. See Below:&lt;/p&gt;&#xA;&lt;div class=&#34;highlight&#34;&gt;&lt;pre tabindex=&#34;0&#34; style=&#34;color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;-webkit-text-size-adjust:none;&#34;&gt;&lt;code class=&#34;language-bash&#34; data-lang=&#34;bash&#34;&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;user@machine$ host fritz.dev&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;fritz.dev has IPv6 address 2620:79:e000:fb01::206&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;fritz.dev has IPv6 address 2620:79:e000:fa00::206&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;fritz.dev mail is handled by &lt;span style=&#34;color:#ae81ff&#34;&gt;10&lt;/span&gt; mail01.fritzlab.net.&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;fritz.dev mail is handled by &lt;span style=&#34;color:#ae81ff&#34;&gt;20&lt;/span&gt; mail02.fritzlab.net.&#xA;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;But.&#xA;I&amp;rsquo;m not a complete psychopath.&#xA;Legacy IPv4 compatibility is available at &lt;a href=&#34;https://ipv4.fritz.dev&#34;&gt;ipv4.fritz.dev&lt;/a&gt; (it&amp;rsquo;s actually dual-stacked).&lt;/p&gt;</description>
    </item>
    <item>
      <title>IP Prefixes on EC2</title>
      <link>/ip-prefixes-on-ec2/</link>
      <pubDate>Fri, 23 Jul 2021 00:00:00 +0000</pubDate>
      <guid>/ip-prefixes-on-ec2/</guid>
      <description>&lt;h2 id=&#34;what-are-ip-prefixes&#34;&gt;What are IP Prefixes?&lt;/h2&gt;&#xA;&lt;p&gt;Yesterday, &lt;a href=&#34;https://aws.amazon.com/about-aws/whats-new/2021/07/amazon-virtual-private-cloud-vpc-customers-can-assign-ip-prefixes-ec2-instances/&#34;&gt;AWS released IP Prefixes for EC2&lt;/a&gt;.&#xA;IP prefixes are a contiguous, summarizable, blocks of IPv6 and/or IPv4 addresses.&#xA;These prefixes are assigned to a single Elastic Network Interface (ENI) in a VPC (which is typically attached to an EC2 instance).&#xA;In the most basic sense, it&amp;rsquo;s this:&lt;/p&gt;&#xA;&lt;p&gt;&lt;img src=&#34;/img/prefix-1.png#center&#34; alt=&#34;ip prefix logical&#34;&gt;&lt;/p&gt;&#xA;&lt;h3 id=&#34;why-do-i-want-this&#34;&gt;Why do I want this?&lt;/h3&gt;&#xA;&lt;p&gt;It comes down to efficiency, simplicity, and scalability for container platforms.&#xA;Let&amp;rsquo;s break this down-&lt;/p&gt;</description>
    </item>
    <item>
      <title>Notes for Running Tinc on an EdgeRouter (EdgeMAX)</title>
      <link>/notes-for-running-tinc-on-an-edgerouter-edgemax/</link>
      <pubDate>Sun, 19 Apr 2020 00:00:00 +0000</pubDate>
      <guid>/notes-for-running-tinc-on-an-edgerouter-edgemax/</guid>
      <description>&lt;h2 id=&#34;introduction&#34;&gt;Introduction&lt;/h2&gt;&#xA;&lt;p&gt;I have been running &lt;a href=&#34;https://www.tinc-vpn.org/&#34;&gt;tinc&lt;/a&gt; on a Ubiquiti EdgeRouters for about five years.&#xA;Tinc has been great for creating dynamic multipoint VPN tunnels between EdgeRouters for the purposes of extending private IPv4 address connectivity.&#xA;The problem space and setup is straightforward.&#xA;I am writing this post for the following reasons:&lt;/p&gt;&#xA;&lt;p&gt;1- Most of the time this is a &amp;ldquo;set it and forget it&amp;rdquo; type setup, however, from time to time it requires some maintenance.&#xA;The time in between the periods where I need to edit this setup (troubleshoot, add a new node ..etc) is quite long.&#xA;I intend this document to be used as a reference for my future self.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Just Start</title>
      <link>/just-start/</link>
      <pubDate>Sat, 04 Apr 2020 00:00:00 +0000</pubDate>
      <guid>/just-start/</guid>
      <description>&lt;p&gt;This is my first blog post and a step towards my 2020 goal.&#xA;Every year I set a few personal goals, this year one of my goals was to start a personal website/blog.&#xA;I have wanted to create a personal blog for many years, but always struggled to get started.&lt;/p&gt;&#xA;&lt;p&gt;Generally I always find myself aiming for perfection.&#xA;This is especially challenging when trying to create a personal blog that will be viewed as a reflection of who I am.&#xA;There are countless ways I&amp;rsquo;ve tried to nitpick the perfect design and perfect content slate.&#xA;However, perfection is a form of procrastination; and I should bias towards action.&lt;/p&gt;</description>
    </item>
    <item>
      <title>About Me</title>
      <link>/about/</link>
      <pubDate>Fri, 03 Apr 2020 00:00:00 +0000</pubDate>
      <guid>/about/</guid>
      <description>&lt;figure class=&#34;me&#34;&gt;&lt;img src=&#34;/img/me.jpg&#34; width=&#34;250&#34;&gt;&#xA;&lt;/figure&gt;&#xA;&#xA;&lt;p&gt;My name is Donavan Fritz.&#xA;While I am currently employed at Netflix, the words, thoughts and opinions on this site are my own and do not reflect any past, current, or future employer.&lt;/p&gt;&#xA;&lt;p&gt;I have an amazing wife (pictured with me on the right); and I am a father of two young children.&#xA;I live in work in the San Francisco Bay Area, however, I was born and raised in rural Wisconsin.&#xA;When I&amp;rsquo;m not working I enjoy watching Netflix (ironically), getting outside and spending time with my family, and playing around with technology (like building this site).&lt;/p&gt;</description>
    </item>
    <item>
      <title>IPv6 is Required</title>
      <link>/redirect/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/redirect/</guid>
      <description>&lt;p&gt;This site requires IPv6.&#xA;Please contact your network administrator and ensure you are not restricted to using legacy IPv4 only.&#xA;If you are not redirected in thirty seconds, &lt;a href=&#34;https://ipv6.fritz.dev&#34;&gt;click here&lt;/a&gt;.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
