<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Iptables on Michele Bologna</title>
    <link>https://www.michelebologna.net/tags/iptables/</link>
    <description>Recent content in Iptables on Michele Bologna</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Mon, 06 Aug 2018 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.michelebologna.net/tags/iptables/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Preventing Docker from manipulating iptables rules</title>
      <link>https://www.michelebologna.net/2018/preventing-docker-from-manipulating-iptables-rules/</link>
      <pubDate>Mon, 06 Aug 2018 00:00:00 +0000</pubDate>
      <guid>https://www.michelebologna.net/2018/preventing-docker-from-manipulating-iptables-rules/</guid>
      <description>&lt;p&gt;By default, &lt;a href=&#34;https://docs.docker.com/network/iptables/#add-iptables-policies-before-dockers-rules&#34;  class=&#34;external-link&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;Docker manipulates iptables rules&lt;/a&gt; to provide network isolation:&lt;/p&gt;&#xA;&lt;pre tabindex=&#34;0&#34;&gt;&lt;code&gt;Chain FORWARD (policy DROP)&#xA;target prot opt source destination&#xA;DOCKER all -- 0.0.0.0/0 0.0.0.0/0&#xA;&#xA;[...]&#xA;&#xA;Chain DOCKER (1 references)&#xA;target prot opt source destination&#xA;&lt;/code&gt;&lt;/pre&gt;&lt;p&gt;I don&amp;rsquo;t mind having my iptables rules for forwarding manipulated, but there is a caveat: when you expose a container (with &lt;code&gt;-p&lt;/code&gt;), then the port will be exposed to every network interface (which means the whole Internet too). Let&amp;rsquo;s make an example:&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
