From: Ivan (ivan@iip.net)
Date: Fri Nov 24 2006 - 16:10:11 ART
The "<no> default-information originate {in|out}" command in EIGRP is
not intended to influence EIGRP behavior in regard to the 0.0.0.0/0
default route. Instead, it is used to allow or deny the acceptance of
routes flagged as candidate defaults due to the use of "ip
default-network" configuration.
On Friday 24 November 2006 18:06, cadet wrote:
> HI Group !
> I do not clear understand default routing originating in EIGRP.
>
>
> 1. If I correct understand there some methods generate default route from
> one EIGRP-peer to other EIGRP-peer:
>
> a) for all EIGRP-peers
>
> ip route 0.0.0.0 0.0.0.0 x.x.x.x (next hop to the internet)
> router eigrp 100
> redistribute static
>
> b) for specific EIGRP-peers
>
> (config-if)#ip summary-address eigrp 100 0.0.0.0 0.0.0.0
>
> May be there are any other methods ?
>
> _____________________________________
>
> 2. Who may correctly explain me why default-information {allowed {in |
> out} | in | out [acl-number | acl-name]} work ?
>
> For example I have R1->R6
>
> R1
> interface FastEthernet0/0
>
> ip summary-address eigrp 10 0.0.0.0 0.0.0.0 5
>
> R6
> router eigrp 10
> network 14.14.6.6 0.0.0.0
> network 14.14.20.6 0.0.0.0
> no default-information in
> no auto-summary
> eigrp router-id 14.14.6.6
>
>
> BUT
> r6#sh ip route eigrp
> D* 0.0.0.0/0 [90/30720] via 14.14.20.1, 00:11:35, FastEthernet0/0
>
> ____________________________________________
>
> Regards
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
-- Ivan
This archive was generated by hypermail 2.1.4 : Fri Dec 01 2006 - 08:05:48 ART