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
For both OSPF and EIGRP routers to become neighbors, their interface’s primary IP address must be on the same subnet. That statement is true. There is a subtle difference between the two, though.
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.
Corrections – I invite them.
You can configure an EIGRP router to filter routes from being advertised or from being accepted.
Per the standard rules, please correct anything that’s wrong.
One of EIGRP’s big features is the ability to use unequal cost paths for load balancing. This is done with the variance command.
I’m not going to go all out like Jeremy over at Packetlife.net has, but I’m going to start to discuss a few IPv6 topics. In time (like in September when APNIC runs out of IPv4 addresses), I’m sure I’ll ramp up the IPv6 talk, but let’s start easy and get EIGRP for IPv6 up and running.
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.
What’s this? More IGP redistribution? Yes. Yes, it is.
Since I didn’t do too well on the test, here are some more notes on IGP redistribution.