From: Andrew (arousch@xxxxxxxx)
Date: Tue Feb 20 2001 - 15:55:05 GMT-3
Post your configuration and maybe some route info.
At 12:42 PM 2/20/01 -0600, Hebert, Cory J (cory.hebert@wcom.com) wrote:
>Thanks for the help guys. But, I guess I should have mentioned that I
>already have passive-interfaces defined, and that still does not help. I
>thought that 'distriblute-list x out conneected' would have done it, but
>that didn't help either.
>
>Cory
>
>
>-----Original Message-----
>From: Amyn Naran [mailto:amyn_naran@yahoo.com]
>Sent: Tuesday, February 20, 2001 12:14 PM
>To: Pablo Thoma; Hebert, Cory J (cory.hebert@wcom.com)
>Subject: Re: how do I stop connected routes from being injected?
>
>
>
>remember the intent of the passive intf - to NOT advertise but listen.
>
>--- Pablo Thoma <pthoma@employees.org> wrote:
> > try
> >
> > passive-interface
> >
> > for those that you wish not to be included.
> >
> > Cheers,
> >
> > Pablo
> >
> > "Hebert, Cory J (cory.hebert@wcom.com)" wrote:
> >
> > > Hi all,
> > >
> > > I have simple question for you guys. I have a router running
> > eigrp, and all
> > > interfaces on the router have subnets of the same major classful
> > network.
> > > Well, obviously, I put the classful network statement under eigrp.
> > Well, as
> > > soon as eigrp sees that it has an interface belonging to the same
> > classful
> > > network defined under the eigrp process, it injects the connected
> > route into
> > > the process.
> > >
> > > I've tried 'no redistribute connected', 'distribute-list x out
> > connected',
> > > nothing works. Can someone help me to stop this connected route
> > from being
> > > injected into eigrp, so that the downstream router doesn't learn
> > it?
> > >
> > > Thanks!
> > >
> > > Cory
> > >
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:28:54 GMT-3