<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Networking on The Ginger Sysadmin Blog</title>
		<link>https://gingersysadmin.com/tags/networking/</link>
		<description>Recent content in Networking on The Ginger Sysadmin Blog</description>
		<generator>Hugo</generator>
		<language>en-us</language>
		
		
		
		
			<lastBuildDate>Tue, 01 Sep 2026 15:18:07 -0500</lastBuildDate>
		
			<atom:link href="https://gingersysadmin.com/tags/networking/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Docker Networking</title>
				<link>https://gingersysadmin.com/posts/docker-networks/</link>
				<pubDate>Tue, 01 Sep 2026 15:18:07 -0500</pubDate>
				<guid>https://gingersysadmin.com/posts/docker-networks/</guid>
				<description>&lt;h1 id=&#34;tools&#34;&gt;Tools&lt;/h1&gt;&#xA;&lt;p&gt;The &lt;a href=&#34;https://github.com/nicolaka/netshoot&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;netshoot&lt;/a&gt; Docker image is very helpful as it includes all the networking tools you might need to test with. I recently used it to mess around with the setup of docker ipvlan networking.&lt;/p&gt;&#xA;&lt;pre tabindex=&#34;0&#34;&gt;&lt;code&gt;services:&#xA;  netshoot:&#xA;    image: nicolaka/netshoot&#xA;    command: sleep infinity&#xA;    tty: true&#xA;    stdin_open: true&#xA;    container_name: netshoot&#xA;    environment:&#xA;      - DEBIAN_FRONTEND=noninteractive&#xA;&lt;/code&gt;&lt;/pre&gt;&lt;h1 id=&#34;docker-ipvlan-networks&#34;&gt;Docker ipvlan Networks&lt;/h1&gt;&#xA;&lt;p&gt;Docker ipvlans allow each container to have a unique IP address on a specified network. This removes the need for port mapping, etc. It also allows for some flexibility with firewalls as you can create container specific firewall rules at the network edge instead of mucking around with iptables on the container host.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
