From: Erick B. (erickbe@xxxxxxxxx)
Date: Tue Jan 23 2001 - 15:51:09 GMT-3
I think the default-network has to be a EIGRP learned
route in the routing table for it to become active
(same with IGRP). Since 10.0.0.0 is directly connected
the EIGRP route is not making it into the main routing
table thus not becoming the default gateway.
Put a loopback address on the router and announce that
and make it your default-network. The remote router
will see that route in its table and should have a
default route. Please correct me if I'm wrong.
Erick
--- Chuck Larrieu <chuck@cl.cncdsl.com> wrote:
> The "*" indicates the candidate default route.
> I.e. 10.0.0.0 is noted in
> the table as the candidate default. Since there are
> two directly connected
> networks which match that default, ( the /32 and the
> /24 ) may I suggest you
> do an extended ping, using the option for "report"
> to actually look and see
> what happens?
>
> Chuck
>
> -----Original Message-----
> From: nobody@groupstudy.com
> [mailto:nobody@groupstudy.com] On Behalf Of
> Patrick Bikar
> Sent: Tuesday, January 23, 2001 11:07 AM
> To: ccielab@groupstudy.com
> Subject: default routes for (E)IGRP
>
> Hi all !
>
> I can't get default routes to be advertised in my
> eigrp domain. Here is the
> config of the router that is suppose to originate
> the default : could anyone
> tell me what is wrong ?
>
> First, the config :
> router eigrp 5
> network 10.0.0.0
> network 172.20.0.0
> no auto-summary
> !
> ip classless
> ip default-network 10.0.0.0
>
> and then :
> r3#sh ip route
> Codes: C - connected, S - static, I - IGRP, R - RIP,
> M - mobile, B - BGP
> D - EIGRP, EX - EIGRP external, O - OSPF, IA
> - OSPF inter area
> N1 - OSPF NSSA external type 1, N2 - OSPF
> NSSA external type 2
> E1 - OSPF external type 1, E2 - OSPF external
> type 2, E - EGP
> i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS
> level-2, ia - IS-IS inter
> area
> * - candidate default, U - per-user static
> route, o - ODR
> P - periodic downloaded static route
>
> Gateway of last resort is not set
>
> 172.20.0.0/16 is variably subnetted, 15
> subnets, 6 masks
> D 172.20.1.160/27 [90/1930240] via
> 172.20.1.139, 00:11:29,
> Serial0/0.555
> D 172.20.1.144/28 [90/2554112] via
> 172.20.1.139, 00:11:30,
> Serial0/0.555
> C 172.20.1.136/29 is directly connected,
> Serial0/0.555
> D 172.20.1.128/25 is a summary, 00:11:30,
> Null0
> D 172.20.1.249/32 [90/2554112] via
> 172.20.1.139, 00:11:30,
> Serial0/0.555
> D 172.20.1.250/32 [90/409600] via 172.20.1.67,
> 00:11:30, Ethernet0/0
> C 172.20.1.243/32 is directly connected,
> Loopback0
> D 172.20.1.242/32 [90/2554112] via
> 172.20.1.139, 00:11:30,
> Serial0/0.555
> D 172.20.1.245/32 [90/2042112] via
> 172.20.1.139, 00:11:30,
> Serial0/0.555
> D 172.20.1.247/32 [90/2058240] via
> 172.20.1.139, 00:11:30,
> Serial0/0.555
> D 172.20.1.192/27 [90/1955840] via
> 172.20.1.139, 00:11:30,
> Serial0/0.555
> D 172.20.1.32/27 [90/409600] via 172.20.1.67,
> 00:11:30, Ethernet0/0
> D 172.20.1.16/28 [90/409600] via 172.20.1.67,
> 00:11:31, Ethernet0/0
> D 172.20.1.0/25 is a summary, 00:11:31, Null0
> C 172.20.1.64/26 is directly connected,
> Ethernet0/0
> * 10.0.0.0/8 is variably subnetted, 2 subnets, 2
> masks
> C 10.0.0.2/32 is directly connected, Serial0/1
> C 10.0.0.0/24 is directly connected, Serial0/1
>
> Please help !
> Thanks, Patrick.
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:27:41 GMT-3