From: Geatti (geatti@xxxxxxxx)
Date: Wed Sep 13 2000 - 14:34:09 GMT-3
Your right there has been a lot of conflicting documentation on this. I
tried it briefly in my lab, below is the routing table, I redistributed a
static route of 0.0.0.0/0 to null 0. Kevin is right it does understand it.
10.0.0.0/24 is subnetted, 1 subnets
D EX 10.10.10.0 [170/2170112] via 138.5.20.4, 00:00:09, Serial0.2
138.5.0.0/16 is variably subnetted, 5 subnets, 3 masks
C 138.5.10.0/29 is directly connected, Serial0.1
C 138.5.5.0/24 is directly connected, Loopback0
D 138.5.4.0/24 [90/2297856] via 138.5.20.4, 00:01:52, Serial0.2
C 138.5.20.0/28 is directly connected, Serial0.2
D 138.5.90.0/24 [90/2185984] via 138.5.20.4, 00:01:52, Serial0.2
D*EX 0.0.0.0/0 [170/2170112] via 138.5.20.4, 00:00:09, Serial0.2
\
\Laid to rest a last.
I must admit that I was under the impression that EIGRP was not able to do
this (due in part to the books that told me so)
Thanks Kevin.
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of
Kevin M. Woods
Sent: Wednesday, September 13, 2000 10:44 AM
To: ccielab@groupstudy.com
Subject: Re: EIGRp and default routes
I know some documentation out there on this topic is confusing, but once
again EIGRP does understand 0.0.0.0/0.
The default network capability is only there for backwards compatibility
with IGRP (e.g. a slow migration from IGRP to EIGRP).
Kevin
// EIGRP does not use the all zeros network to match all routes (0.0.0.0
// 0.0.0.0).
// EIGRP uses a NETWORK address as the pointer to a default route.
//
// Carl
// CCIE #5934
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 08:24:55 GMT-3