<?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>Gre on TTL Expired</title>
    <link>https://ttl-expired.net/tags/gre/</link>
    <description>Recent content in Gre on TTL Expired</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 15 Apr 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://ttl-expired.net/tags/gre/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>IP Tunnels for JNCIS-SP</title>
      <link>https://ttl-expired.net/docs/tunnels/</link>
      <pubDate>Wed, 15 Apr 2026 00:00:00 +0000</pubDate>
      <guid>https://ttl-expired.net/docs/tunnels/</guid>
      <description>&lt;h2 id=&#34;ip-tunnels&#34;&gt;IP Tunnels&lt;/h2&gt;
&lt;p&gt;Tunnels encapsulate one protocol inside another, creating a virtual point-to-point link across a network that wouldn&amp;rsquo;t otherwise carry that traffic. The encapsulating network is called the &lt;strong&gt;underlay&lt;/strong&gt;; the encapsulated traffic and the logical topology it creates is called the &lt;strong&gt;overlay&lt;/strong&gt;. Both GRE and IP-IP are &lt;strong&gt;stateless&lt;/strong&gt; — they hold no session state and provide no encryption or reliability guarantees.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Common use cases:&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Carry IPv6 traffic across an IPv4-only core (6in4)&lt;/li&gt;
&lt;li&gt;Carry IPv4 traffic across an IPv6-only core (4in6)&lt;/li&gt;
&lt;li&gt;Extend IGP adjacencies across a WAN that doesn&amp;rsquo;t support multicast&lt;/li&gt;
&lt;li&gt;Tunnel MPLS across a non-MPLS network&lt;/li&gt;
&lt;li&gt;Bridge Layer 2 domains across a routed network&lt;/li&gt;
&lt;/ul&gt;
&lt;hr&gt;
&lt;h3 id=&#34;tunnel-concepts&#34;&gt;Tunnel Concepts&lt;/h3&gt;
&lt;p&gt;&lt;strong&gt;Underlay vs Overlay:&lt;/strong&gt;&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
