From: Erick B. (erickbe@xxxxxxxxx)
Date: Mon Nov 12 2001 - 01:02:31 GMT-3
Thats another option, also a default-route.
It all depends... if you're not sure ask the proctor.
--- dhuskey <dhuskey@xnet.com> wrote:
> could you use policy routing?
> kind of a static.
> is policy based routing considered the same as a
> static?
>
> > -----Original Message-----
> > From: nobody@groupstudy.com
> >
> > Erick,
> >
> > None of these options would be acceptable in the
> lab. There must be a way
> > for the two routers to have a 200.0.0.0/24 route
> pointing to each other. I
> > think this is a common problem that you could see
> in a lab. Since each
> > router is bound to have a loopback interface with
> a /32 address
> > but part of
> > the same /24 network. When you add IGRP into the
> picture and you have this
> > scenario, how are you going to reach that lonely
> loopback in that IGRP
> > network?? I guess the obvious solution is to use a
> /32 static
> > route pointing
> > to that loopback, but static routes are often
> frowned upon in lab exams
> > eventhough they are often used in real world
> scenarios.
> >
> > Thanks
> >
> > Albert
> >
> > -----Original Message-----
> > From: nobody@groupstudy.com
> >
> > Albert,
> >
> > You could use a routing protocol that understands
> VLSM
> > like EIGRP, OSPF, etc. With the addressing you're
> > using for the loopbacks on both routers that
> causes a
> > problem with a classful routing protocol. Both
> > loopbacks 200.x.x.x/32 will be summarized down to
> a
> > /24 when advertised across the 150.x.x.x/24 serial
> > link between the routers.
> >
> > Another solution short of changing the addressing,
> > would be not to advertise the loopbacks and use
> static
> > host routes on both sides.
> >
> > You could also get creative with NAT.
> >
> > HTH, Erick
> >
> > --- Albert Lu <albert_ccie@yahoo.com> wrote:
> > > Erick,
> > >
> > > So how would R4 be able to advertise to R2 it's
> > > loopback address and R2
> > > advertise it's loopback address to R4 if they
> are
> > > going to advertise it as a
> > > 200.0.0.0/24 route to each other?
This archive was generated by hypermail 2.1.4 : Fri Jun 21 2002 - 06:45:13 GMT-3