<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Neighbor on Aaron&#39;s Worthless Words</title>
    <link>https://efb97021.aww-3cz.pages.dev/tags/neighbor/</link>
    <description>Recent content in Neighbor on Aaron&#39;s Worthless Words</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Fri, 27 Jun 2014 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://efb97021.aww-3cz.pages.dev/tags/neighbor/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>EIGRP and OSPF - Are We Connected?</title>
      <link>https://efb97021.aww-3cz.pages.dev/posts/2014/06/eigrp-and-ospf-are-we-connected/</link>
      <pubDate>Fri, 27 Jun 2014 00:00:00 +0000</pubDate>
      <guid>https://efb97021.aww-3cz.pages.dev/posts/2014/06/eigrp-and-ospf-are-we-connected/</guid>
      <description>&lt;p&gt;For both OSPF and EIGRP routers to become neighbors, their interface&amp;rsquo;s primary IP address must be on the same subnet. That statement is true. There is a difference in the definition of &amp;ldquo;same subnet&amp;rdquo;, though.&lt;/p&gt;&#xA;&lt;p&gt;In OSPF, both routers have to be configured to be on the same subnet with the same mask or else they won&amp;rsquo;t neighbor up.  When an hello packet is sent, the subnet mask is sent embedded in there.  The router does a quick look to be sure the subnets are defined the same way on both ends.  If everything doesn&amp;rsquo;t match, they don&amp;rsquo;t neighbor. Here&amp;rsquo;s a &lt;a href=&#34;http://www.wireshark.org/&#34;&gt;Wireshark&lt;/a&gt; screenshot to show you the OSPF hello.  &lt;em&gt;Note: See edit below.&lt;/em&gt;&lt;/p&gt;</description>
    </item>
    <item>
      <title>Routing IPv6 with BGP - The Basics</title>
      <link>https://efb97021.aww-3cz.pages.dev/posts/2011/02/routing-ipv6-with-bgp-the-basics/</link>
      <pubDate>Thu, 10 Feb 2011 00:00:00 +0000</pubDate>
      <guid>https://efb97021.aww-3cz.pages.dev/posts/2011/02/routing-ipv6-with-bgp-the-basics/</guid>
      <description>&lt;p&gt;Are you sensing a theme lately?  Since we covered the basics of the main IGPs (I&amp;rsquo;m an enterprise guy, so no IS-IS comments, please.), I thought I&amp;rsquo;d try to describe the basics of advertising IPv6 routes over BGP.  Yet again, we&amp;rsquo;re not going to do any route manipulation or change any of the 948284928 BGP attributes.  We&amp;rsquo;re just trying to get routes exchanged.&lt;/p&gt;&#xA;&lt;h3 id=&#34;configuration&#34;&gt;Configuration&lt;/h3&gt;&#xA;&lt;p&gt;There&amp;rsquo;s no new version of BGP for IPv6 here.  It&amp;rsquo;s the standard BGP version 4 that we&amp;rsquo;ve all been using for years, but we&amp;rsquo;re going to take advantage of the multiprotocol support (MPBGP, &lt;a href=&#34;http://tools.ietf.org/html/rfc2858&#34;&gt;RFC 2858&lt;/a&gt; &lt;a href=&#34;http://tools.ietf.org/html/rfc4760&#34;&gt;RFC 4760&lt;/a&gt;).  We&amp;rsquo;ll get to the differences in a second, but the first thing to do is to set up the BGP process as normal.  &lt;/p&gt;</description>
    </item>
    <item>
      <title>ROUTE Notes - OSPF Neighbor Relationships</title>
      <link>https://efb97021.aww-3cz.pages.dev/posts/2010/06/route-notes-ospf-neighbor-relationships/</link>
      <pubDate>Fri, 18 Jun 2010 00:00:00 +0000</pubDate>
      <guid>https://efb97021.aww-3cz.pages.dev/posts/2010/06/route-notes-ospf-neighbor-relationships/</guid>
      <description>&lt;p&gt;Feel free to correct.&lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;Study Questions&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;What are the definitions of the hello and dead intervals?&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;The hello intervals is how often a router sends hello messages.  The dead interval is how long to wait before considering a neighbor dead from lack of hello messages; this is 4x the hello interval by default.&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;How do you keep OSPF from trying to detect neighbors on an interface?&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;Don’t configure a &lt;em&gt;network&lt;/em&gt; statement for that interface Make that interface passive&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
