Skip to main content

Route This Way: (E)IGRP




IGRP information is...scant. It's made by Cisco, and they have since moved on to EIGRP.



  • EIGRP talks to its neighbors it knows via the neighbor table. Neighbors are directly connected.
  • The topology table stores routes it learns from its directly connected neighbors 
  • Hellos are sent every few seconds (Depending on Network capability) to make sure the neighbor is still there. A hold time is around 15 seconds. The router will drop the connection if the neighbor doesn't respond.
  • Routers get updates via multicast address 224.0.0.10





 New commands -

 🧠 no auto-summary - Back in RIP-land, I advertised the networks using the networks and not the individual IP addresses. ("Summarize at the boundary to the classful network.") You may not wish to do that in EIGRP.

🥏  router eigrp [AS#]
The AS is Autonomous System number. Essentially, "How many routers are under the same networking entity?" Imagine a Botnet, but legal, and helping the internet to run.

🐲 Wildcard masks
With RIP, we could put in the first part (Network, maybe the host) of an IP address and be fine. The router understood it. Now, we have to wildcard-inverse-mask.

Subnet mask of 255.255.255.0 (/24) would be 0.0.0.255. Imagine it as "What's left in this IP segment."

(/30) (255.255.255.252) Would be 0.0.0.3 (I think. The 1 and 2 bits at the end remain.)


Router A (I renamed them part of the way through this to better keep track)


Note the subnet wildcard bits.

Onto Router B - and the adjacency is made!


And Router C


show ip route


Look under 'variably subnetted' - see the [90/2681856]?

That is the administrative distance. Lower is better. 90 is EIGRP, 0 (or 1) would be static.

show ip eigrp neighbors


One on the left, and one on the right.


The bits I didn't remember I used resources for, one of which is this. The topology is all mine.

Comments

Popular posts from this blog

Connecting IoT Devices to a Registration Server (Packet Tracer, Cisco)

In Packet Tracer, a demo software made by Cisco Systems. It certainly has changed a lot since 2016. It's almost an Olympic feat to even get started with it now, but it does look snazzy. This is for the new CCNA, that integrates, among other things, IoT and Automation, which I've worked on here before. Instructions here . I don't know if this is an aspect of "Let's make sure people are paying attention and not simply following blindly", or an oversight - The instructions indicate a Meraki Server, when a regular one is the working option here. I have to enable the IoT service on this server. Also, we assign the server an IPv4 address from a DHCP pool instead of giving it a static one. For something that handles our IoT business, perhaps that's safer; Getting a new IPv4 address every week or so is a minimal step against an intruder, but it is a step. There are no devices associated with this new server; In an earlier lab (not shown), I attached them to 'H

Securing Terraform and You Part 1 -- rego, Tfsec, and Terrascan

9/20: The open source version of Terraform is now  OpenTofu     Sometimes, I write articles even when things don't work. It's about showing a learning process.  Using IaC means consistency, and one thing you don't want to do is have 5 open S3 buckets on AWS that anyone on the internet can reach.  That's where tools such as Terrascan and Tfsec come in, where we can make our own policies and rules to be checked against our code before we init.  As this was contract work, I can't show you the exact code used, but I can tell you that this blog post by Cesar Rodriguez of Cloud Security Musings was quite helpful, as well as this one by Chris Ayers . The issue is using Rego; I found a cool VS Code Extension; Terrascan Rego Editor , as well as several courses on Styra Academy; Policy Authoring and Policy Essentials . The big issue was figuring out how to tell Terrascan to follow a certain policy; I made it, put it in a directory, and ran the program while in that directory

Building, Breaking, and Building A CRM with Retool

 I like no- or low-code solutions to things. I've often wanted to simply push a button or move some GUI around and have the code implement itself.  I've thought about building something that's like a customer relationship management (CRM) system for keeping up with my network better than my little spreadsheet where I click links and then go like something. The general idea in this CRM Development is:  To have a GUI to add people to a NRM (Network Relationship Management).       Attach it to a database (MySQL is what I went with eventually using Amazon Relational Database service, but you can use PostGRES, and probably others).     Make sure components are connected to each other in the retool interface. This video is a good start. Watching the tutorial video, heard some SQL commands and went 'Oh no 😳" before going "Wait I know basic SQL", which is good, because you'll see.  When you get set up, there's a plethora of resources you can use -- Incl