<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>NetworkManager on Support Tools</title><link>https://support.tools/tags/networkmanager/</link><description>Recent content in NetworkManager on Support Tools</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Fri, 20 Nov 2026 09:00:00 -0600</lastBuildDate><atom:link href="https://support.tools/tags/networkmanager/index.xml" rel="self" type="application/rss+xml"/><item><title>Cilium BPF Compile Fails with 'macro redefined': How NetworkManager Disabled IPv6 on cilium_host</title><link>https://support.tools/cilium-bpf-macro-redefined-node-config-h-networkmanager-cilium-host-ipv6/</link><pubDate>Fri, 20 Nov 2026 09:00:00 -0600</pubDate><guid>https://support.tools/cilium-bpf-macro-redefined-node-config-h-networkmanager-cilium-host-ipv6/</guid><description>&lt;p&gt;One Kubernetes node stopped giving pods a network. Every other node in the cluster was fine. New pods on the bad node sat in &lt;code&gt;ContainerCreating&lt;/code&gt; until the CNI ADD call timed out, and the Cilium agent log on that node was a wall of clang errors:&lt;/p&gt;&#10;&lt;div class="code-block" data-copy-label="Copy text code, block 1"&gt;&#10; &lt;div class="code-block-header" data-pagefind-ignore&gt;&lt;span class="code-block-lang"&gt;text&lt;/span&gt;&lt;/div&gt;&#10; &lt;div class="highlight"&gt;&lt;pre tabindex="0" class="chroma"&gt;&lt;code class="language-text" data-lang="text"&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;error: &amp;#39;MONITOR_AGGREGATION&amp;#39; macro redefined [-Werror,-Wmacro-redefined]&#10;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;error: &amp;#39;ENABLE_ARP_RESPONDER&amp;#39; macro redefined [-Werror,-Wmacro-redefined]&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&#10;&lt;/div&gt;&#10;&lt;p&gt;Those lines look like a Cilium bug, a clang version mismatch, or a kernel header problem. They are none of those. The BPF compiler was doing exactly what it was told, against a header file that should have been generated a minute earlier and never was. The real failure was much further up the log: &lt;strong&gt;NetworkManager&lt;/strong&gt; had applied a catch-all connection profile to the &lt;code&gt;cilium_host&lt;/code&gt; interface and turned IPv6 off on it, which made Cilium&amp;rsquo;s datapath initialization fail with &lt;code&gt;permission denied&lt;/code&gt;. This post walks through how that chain works, how to confirm it in under five minutes, and the three changes that fix it permanently.&lt;/p&gt;</description></item></channel></rss>