<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Iproute2 on Lloyd Rochester's Geek Blog</title><link>https://lloydroc.github.io/tags/iproute2/</link><description>Recent content in Iproute2 on Lloyd Rochester's Geek Blog</description><generator>Hugo</generator><language>en</language><copyright>Copyright © 2025, Lloyd Rochester.</copyright><lastBuildDate>Tue, 04 Feb 2020 07:40:31 +0000</lastBuildDate><atom:link href="https://lloydroc.github.io/tags/iproute2/index.xml" rel="self" type="application/rss+xml"/><item><title>Creating IP Tunnels in Linux with iproute2</title><link>https://lloydroc.github.io/post/unix/iproute2_create_tunnel/</link><pubDate>Tue, 04 Feb 2020 07:40:31 +0000</pubDate><guid>https://lloydroc.github.io/post/unix/iproute2_create_tunnel/</guid><description>&lt;h1 id="hahahugoshortcode90s0hbhb">Creating IP Tunnels in Linux with iproute2&lt;/h1>
&lt;p>In this post we&amp;rsquo;ll use &lt;em>iproute2&lt;/em> to create tunnels between two unix hosts. This will be the simplest form of an &lt;em>IP-in-IP&lt;/em> tunnel.&lt;/p>
&lt;h2 id="how-the-tunnels-will-work">How the Tunnels will work&lt;/h2>
&lt;p>In this example we have two Unix hosts with IP addresses &lt;em>10.255.254.96&lt;/em> and &lt;em>10.255.254.196&lt;/em> on a &lt;em>10.255.254.0/24&lt;/em> network and a gateway address of &lt;em>10.255.254.2&lt;/em>. These two hosts are on the same network. For this tunnel example we are going to add &lt;em>dummy&lt;/em> interfaces to each of our hosts and assign addresses &lt;em>192.168.2.111&lt;/em> and &lt;em>192.168.2.222&lt;/em> addresses to each of them respectively. Once the tunnels are up we will be able to send a ping from the first tunnel to the second tunnel as if the hosts are on the same network. This is known as encapsulation, since inside an IPv4 packet with a source of &lt;em>10.255.254.96&lt;/em> and destination of &lt;em>10.255.254.196&lt;/em> we have another IPv4 packet encapsulated inside with a source of &lt;em>192.168.2.111&lt;/em> and destination of &lt;em>192.168.2.222&lt;/em>.&lt;/p></description></item></channel></rss>