Let’s get an IPv4 default route into EIGRP. There are a few methods to do it. I hate most of them, though. I think it will be obvious which one I like. LOL
I wanted to do some analysis of the EIGRP topology table last night, so I fired up a small lab. I was especially interested in how external routes appear there and compare to internal entries. Like all good scientific endeavors, the whole thing got derailed when I made a realization.
Here’s one that I use every day at work. We have multiple customers coming into the same router, and, as luck would have it, they all use 192.168.1.0/24 (OK…not really but it might happen). That means we have to separate them into their own routing instance, or virtual router, so pass traffic to their firewall. Think VRF lite on a Cisco router. Let’s conflagrate.
I was studying via Google+ Hangout the other day with CJ and Rob, and one of the topics that came up was the idea of OSPFv2 advertising all loopbacks as 32-bit no matter what the configured mask is. I rarely use loopbacks outside of a lab and had no idea, so I set up a quick lab to see for myself. Sure enough! That’s exactly what I saw.
You can use route tags in redistribution scenarios to filter and/or manipulate routes.
Route reflectors remove the requirement of having a full mesh iBGP network.
You can configure an EIGRP router to filter routes from being advertised or from being accepted.
Are you sensing a theme lately? Since we covered the basics of the main IGPs (I’m an enterprise guy, so no IS-IS comments, please.), I thought I’d try to describe the basics of advertising IPv6 routes over BGP. Yet again, we’re not going to do any route manipulation or change any of the 948284928 BGP attributes. We’re just trying to get routes exchanged.
A few hours ago, the last of the IPv4 addresses were allocated by IANA. Now’s the time to learn more about IPv6! Yesterday, I posted about EIGRP for IPv6, so I think I’ll continue the trend by introducing OSPFv3, which is the IPv6 implementation of OSPF
EIGRP allows you to tag external routes. That is, any route redistributed into EIGRP can be tagged with a numeric descriptor from 0 to 4294967295.