Re: how do I stop connected routes from being injected?

From: Vladimir Shchutski (vshchutski@xxxxxxxxx)
Date: Wed Feb 21 2001 - 02:43:27 GMT-3


   
Do NOT use "distribute-list x out connected".
Use "distribute-list x out" or "distribute-list x out
int x x ".

When you have "distribute-list x out connected" you
control redistribution of connected networks into
EIGRP.

router eigrp 100
  network 10.0.0.0
  redistribute connected
  distribute-list 1 out connected
access-list 1 deny 192.168.1.0 0.0.0.255
access-list 1 permit any

When you use "distribute-list x out" you filter
networks advertised to downstream routers via EIGRP.

router eigrp 100
  network 10.0.0.0
  distribute-list 1 out
access-list 1 deny 10.1.1.0 0.0.0.255
access-list 1 permit any

Regards,
Vladimir.

--- "Hebert, Cory J (cory.hebert@wcom.com)"
<cory.hebert-eds@eds.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:55 GMT-3