<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Netconf on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/netconf/</link>
    <description>Recent content in Netconf on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 08 May 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/netconf/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>netopeer2 vs OpenDaylight NETCONF vs Tail-f ConfD: Self-Hosted NETCONF/YANG Network Configuration Guide 2026</title>
      <link>https://www.pistack.xyz/posts/2026-05-18-netopeer2-vs-opendaylight-vs-confd-netconf-yang-guide/</link>
      <pubDate>Fri, 08 May 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-05-18-netopeer2-vs-opendaylight-vs-confd-netconf-yang-guide/</guid>
      <description>&lt;p&gt;Network configuration management has evolved from manual CLI sessions to programmatic, model-driven automation. &lt;strong&gt;NETCONF&lt;/strong&gt; (Network Configuration Protocol, RFC 6241) and &lt;strong&gt;YANG&lt;/strong&gt; (data modeling language, RFC 6020) form the industry standard for programmatic network device management. This guide compares three open-source NETCONF server implementations: &lt;strong&gt;netopeer2&lt;/strong&gt;, &lt;strong&gt;OpenDaylight NETCONF&lt;/strong&gt;, and &lt;strong&gt;Tail-f ConfD&lt;/strong&gt;.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
