From: Carlos G Mendioroz (tron@huapi.ba.ar)
Date: Tue Jul 31 2007 - 07:58:57 ART
I don't know if I'm adding to the confusion, but...
if this is for a lab requirement, I would pay attention to the details.
It is true that a connected PREFIX can not be overruled, but 151.10.1.2
is not a prefix, it's an IP address.
So ? Well, you can play with the interface MASK and make the real (i.e.
defined by design) external while another mask defines the connected
network.
-Carlos
CCIE 19999 @ 30/07/2007 20:18 -0300 dixit:
> Alex,
>
>
>
> That's what I thought, but just wanted a confirmation.
>
>
>
> Thanks,
>
>
>
> Shine
>
>
>
> _____
>
> From: Alexey Tolstenok [mailto:alextols@gmail.com]
> Sent: Tuesday, 31 July 2007 7:33 AM
> To: CCIE 19999
> Cc: ccielab@groupstudy.com
> Subject: Re: Connected interface appear as External
>
>
>
> INo, since you cannot make the AD of EIGRP route (when disabling eigrp
> split-horizon on neighbor) lower than "connected" AD = 0 or increase AD of
> "connected"
>
> 2007/7/31, CCIE 19999 < ccie@iprimus.com.au>:
>
> Hi Folks,
>
>
>
> Is there a way actually you can make a connected prefix appear as external?
>
> For example, 151.10.1.2 is a connected interface on R1 and the routing
> protocol is EIGRP.
>
> I am wondering if it is possible to make the prefix appear as D EX in router
>
> R1 instead of as Connected.
>
>
>
> TIA,
>
> Shine
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
>
>
>
>
-- Carlos G Mendioroz <tron@huapi.ba.ar> LW7 EQI Argentina
This archive was generated by hypermail 2.1.4 : Sat Aug 18 2007 - 08:17:42 ART