<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>SDN on DevOpsTales</title>
    <link>https://devopstales.github.io/tags/sdn/</link>
    <description>Recent content in SDN on DevOpsTales</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-US</language>
    <lastBuildDate>Mon, 21 Sep 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://devopstales.github.io/tags/sdn/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Fixing Proxmox SDN: missing &#39;source /etc/network/interfaces.d/sdn&#39; directive</title>
      <link>https://devopstales.github.io/virtualization/proxmox-sdn-missing-source-directive/</link>
      <pubDate>Mon, 21 Sep 2026 00:00:00 +0000</pubDate>
      
      <guid>https://devopstales.github.io/virtualization/proxmox-sdn-missing-source-directive/</guid>
      <description>If you have ever applied a Proxmox VE Software-Defined Network configuration and seen this warning pop up in the task view, you are not alone:
WARN: missing &#39;source /etc/network/interfaces.d/sdn&#39; directive for SDN support! Created symlink /etc/systemd/system/multi-user.target.wants/dnsmasq@testzone.service -&gt; /lib/systemd/system/dnsmasq@.service. TASK WARNINGS: 1 It looks harmless, and in most cases it is. But if you want SDN-generated networks to actually come up on the node, that one line is the difference between a pending configuration and a running one. This post explains where the warning comes from in the Proxmox source code, why the fix is a single source directive, and how to verify the whole pipeline works afterwards.
</description>
      <enclosure url="https://devopstales.github.io/img/proxmox.webp" length="11936" type="image/png" />
    </item>
    
  </channel>
</rss>
