<?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>Firewalld on Gnali</title>
    <link>https://www.gnali.org/tags/firewalld/</link>
    <description>Recent content in Firewalld on Gnali</description>
    <image>
      <title>Gnali</title>
      <url>https://www.gnali.org/%3Clink%20or%20path%20of%20image%20for%20opengraph,%20twitter-cards%3E</url>
      <link>https://www.gnali.org/%3Clink%20or%20path%20of%20image%20for%20opengraph,%20twitter-cards%3E</link>
    </image>
    <generator>Hugo</generator>
    <language>fr</language>
    <lastBuildDate>Tue, 28 Jul 2026 16:00:00 +0200</lastBuildDate>
    <atom:link href="https://www.gnali.org/tags/firewalld/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Faire communiquer deux bridges NAT libvirt (firewalld nftables)</title>
      <link>https://www.gnali.org/posts/libvirt-bridge-forward-nftables/</link>
      <pubDate>Tue, 28 Jul 2026 16:00:00 +0200</pubDate>
      <guid>https://www.gnali.org/posts/libvirt-bridge-forward-nftables/</guid>
      <description>&lt;p&gt;Sous RHEL avec le backend &lt;strong&gt;nftables&lt;/strong&gt; de firewalld, autoriser un réseau libvirt à joindre un autre n&amp;rsquo;est plus une affaire de &lt;code&gt;firewall-cmd --direct&lt;/code&gt;. Libvirt installe sa propre table &lt;code&gt;ip libvirt_network&lt;/code&gt;, et c&amp;rsquo;est elle qui refuse le trafic NEW entre bridges.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
