<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Vr on Aaron&#39;s Worthless Words</title>
    <link>https://38a8db03.aww-3cz.pages.dev/tags/vr/</link>
    <description>Recent content in Vr on Aaron&#39;s Worthless Words</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Sat, 02 Mar 2013 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://38a8db03.aww-3cz.pages.dev/tags/vr/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Junos - Logical Tunnel Interfaces with Virtual Routers</title>
      <link>https://38a8db03.aww-3cz.pages.dev/posts/2013/03/junos-logical-tunnel-interfaces-with-virtual-routers/</link>
      <pubDate>Sat, 02 Mar 2013 00:00:00 +0000</pubDate>
      <guid>https://38a8db03.aww-3cz.pages.dev/posts/2013/03/junos-logical-tunnel-interfaces-with-virtual-routers/</guid>
      <description>&lt;p&gt;There are a few ways to leak routes in and out of virtual routers in Junos. On the list is a cool feature called the logical tunnel interface.&lt;/p&gt;&#xA;&lt;p&gt;So, what am I talking about?  One way to separate traffic on a router is to use virtual routers (VRs) so that you wind up with multiple routing tables on the same router.  This separate traffic, but you will usually (read: always) have a demand to get traffic from one VR to another.  There are a few different way to do that (see rib-group, instance-import, next-table, et al.), but one really cool way to do it is through logical tunnel interfaces.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
