<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Networking on Budiman JoJo</title>
    <link>https://budimanjojo.com/categories/networking/</link>
    <description>Recent content in Networking on Budiman JoJo</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Thu, 06 Mar 2025 12:20:51 +0700</lastBuildDate>
    <atom:link href="https://budimanjojo.com/categories/networking/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>The Pain and Peculiarity of NixOS Networking with systemd-networkd</title>
      <link>https://budimanjojo.com/2025/03/06/systemd-networkd-nixos-pain/</link>
      <pubDate>Thu, 06 Mar 2025 12:20:51 +0700</pubDate>
      <guid>https://budimanjojo.com/2025/03/06/systemd-networkd-nixos-pain/</guid>
      <description>&lt;p&gt;Setting up networking on NixOS with &lt;code&gt;systemd-networkd&lt;/code&gt; should, in theory, be a straightforward and declarative process.&#xA;Just define your network configurations in Nix, let &lt;code&gt;systemd-networkd&lt;/code&gt; handle the interfaces, and enjoy a seamless, reproducible setup.&#xA;But reality hits differently.&#xA;My journey with &lt;code&gt;systemd-networkd&lt;/code&gt; on NixOS has been a mix of frustration, debugging marathons, and the occasional victory that feels more like luck than mastery.&#xA;In this article, I&amp;rsquo;ll go over some of the quirks I&amp;rsquo;ve encountered, the pitfalls that made me question my sanity, and the workarounds that (sometimes) saved the day.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
