From: Merrill, James D. (AIT) (jm8752@xxxxxxx)
Date: Thu Feb 22 2001 - 14:14:02 GMT-3
I believe the DISTRIBUTE-LIST 1 OUT should be used since you want to limit
out bound network advertisements. The DISTRIBUTE-LIST 1 IN filters inbound
networks.
James D. Merrill
Systems Engineer
SBC DataComm
-----Original Message-----
From: Dan [mailto:dp595@optonline.net]
Sent: Thursday, February 22, 2001 10:39 AM
To: Rick Burts; Pablo Thoma
Cc: Hebert, Cory J (cory.hebert@wcom.com);
ccielab@groupstudy.com
Subject: Re: how do I stop connected routes from
being injected?
Yes, you are correct Rick. I believe I asked this question
in an earlier
post (see below):
(from 2/17)...
Ok so to further expand on that, let's say I have the config
below:
interface Ethernet0/0
ip address 192.168.1.17 255.255.255.248
inteface Ethernet0/1
ip address 192.168.1.33 255.255.255.248
If I only want to advertise Ethernet0/0 via EIGRP, but not
Ethernet0/1.
I must filter within the EIGRP process to stop 192.168.1.32
/29 from being
advertised?
EIGRP 1
network 192.168.1.0
distribute-list 1 in
access-list 1 permit 192.168.1.16
Is this correct? Wildcard masks are much easier.
Dan Pontrelli
Customer Installation Engineer - Verio NYC
CCNP, MCSE, CNA
Dan Pontrelli
Customer Installation Engineer - Verio NYC
CCNP, MCSE, CNA
----- Original Message -----
From: "Rick Burts" <burts@mentortech.com>
To: "Pablo Thoma" <pthoma@employees.org>
Cc: "Hebert, Cory J (cory.hebert@wcom.com)"
<cory.hebert-eds@eds.com>;
<ccielab@groupstudy.com>
Sent: Tuesday, February 20, 2001 1:08 PM
Subject: Re: how do I stop connected routes from being
injected?
> Passive Interface for EIGRP has a bit of an unusual
behavior.
> For most of the interior routing protocols passive
interface indicates
> not to send advertisements but to continue to listen for
advertisements.
> With EIGRP use of passive interface will prevent sending
of Hello
> messages and therefore will prevent formation of neighbor
relationships
> with any other router on that subnet.
>
> However use of passive interface has no effect on
advertising that subnet
> on active interfaces. The point of the original post was
that he did not
> want the subnet advertised. Passive interface will not
achieve that.
> I do not see a solution other than use of mask on the
network statement
> (a feature in some releases of 12.0) or a distribute list.
>
> Rick
>
> Rick Burts, CCSI CCIE 4615 burts@mentortech.com
> Mentor Technologies 240-568-6500 ext
6652
> 133 National Business Parkway 240-568-6515 fax
> Annapolis Junction, Md 20701
>
> Chesapeake Network Solutions has now become Mentor
Technologies.
> Mentor Technologies is a certified Cisco Training Partner
and also
> a Cisco Professional Services partner.
> We offer most of the Cisco training courses.
> We also offer training in Checkpoint Firewall software and
> Fore Systems (now Marconi) and MicroMuse.
> We also provide network consulting services including
> design, management, and problem solving.
> We have 22 CCIEs on our staff.
> We offer the breakthrough VLAB remote access technology
for
> access to pratice configuration on real equipment.
>
> On Tue, 20 Feb 2001, Pablo Thoma 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:57 GMT-3