<?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>Iptables on Gnali</title>
    <link>https://www.gnali.org/en/tags/iptables/</link>
    <description>Recent content in Iptables on Gnali</description>
    <image>
      <title>Gnali</title>
      <url>https://www.gnali.org/imgs/img_6169.jpeg</url>
      <link>https://www.gnali.org/imgs/img_6169.jpeg</link>
    </image>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Tue, 28 Jul 2026 16:00:00 +0200</lastBuildDate>
    <atom:link href="https://www.gnali.org/en/tags/iptables/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Forward traffic between two libvirt NAT bridges (RHEL 9 and RHEL 10)</title>
      <link>https://www.gnali.org/en/posts/libvirt-bridge-forward-nftables/</link>
      <pubDate>Tue, 28 Jul 2026 16:00:00 +0200</pubDate>
      <guid>https://www.gnali.org/en/posts/libvirt-bridge-forward-nftables/</guid>
      <description>&lt;p&gt;Allowing one libvirt VM network to reach another is not a classic &lt;code&gt;firewall-cmd --direct&lt;/code&gt; problem anymore. Libvirt&amp;rsquo;s own NAT firewall rejects NEW traffic between bridges. The layout differs by RHEL version — and so do the tools.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
