<?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>Cni on Michael Johnson</title>
    <link>https://ahze.net/tags/cni/</link>
    <description>Recent content in Cni on Michael Johnson</description>
    <image>
      <title>Michael Johnson</title>
      <url>https://ahze.net/images/profile.jpg</url>
      <link>https://ahze.net/images/profile.jpg</link>
    </image>
    <generator>Hugo -- 0.167.0</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 09 Aug 2026 15:00:00 -0400</lastBuildDate>
    <atom:link href="https://ahze.net/tags/cni/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Deep Dive: FreeBSD Podman Networking, Custom CNI, and Resource Accounting</title>
      <link>https://ahze.net/posts/freebsd-podman-networking/</link>
      <pubDate>Sun, 09 Aug 2026 15:00:00 -0400</pubDate>
      <guid>https://ahze.net/posts/freebsd-podman-networking/</guid>
      <description>&lt;p&gt;When running native OCI containers on FreeBSD with Podman and &lt;code&gt;ocijail&lt;/code&gt;, networking is one of the most interesting—and sometimes confusing—parts of the setup. Because Podman translates container commands into FreeBSD &lt;code&gt;jail(2)&lt;/code&gt; system calls, container interfaces aren&amp;rsquo;t just Linux veth pairs inside network namespaces; they leverage FreeBSD&amp;rsquo;s &lt;strong&gt;VNET (Virtual Network Stack)&lt;/strong&gt;, &lt;code&gt;epair(4)&lt;/code&gt; interface pairs, and standard CNI plugins.&lt;/p&gt;
&lt;p&gt;Here is a practical deep dive into how Podman container networking works on FreeBSD, how to build custom CNI bridge networks for VLANs, how to fix &lt;code&gt;podman stats&lt;/code&gt; metric collection with RACCT, and how to structure multi-container Compose setups.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
