From: miken (miken@sisna.com)
Date: Fri Sep 26 2003 - 20:00:45 GMT-3
Another possibility to consider:
1. You don't have access to the bb router
2. You are not allowed to send/distribute any routes to the bb router
3. All routers must have the routes from bb in their routing tables
4. All routers must be able to ping the bb router
Acceptable filtering solutions have already been furnished. But in addition,
you could also PAT you pod networks to the bb directly connected address.
The bb will then see the source as a directly connected network and be able
to route back. The bb doesn't need a default route.
Thanks,
Mike N.
----- Original Message -----
From: "William Lijewski" <ccie8642@hotmail.com>
To: <kaiseranwar@sbcglobal.net>; <ccielab@groupstudy.com>
Sent: Thursday, September 25, 2003 4:27 PM
Subject: Re: routes to backbones
> Tony is right also, a simple passive interface for RIP would do the trick.
> It will allow the RIP to accept the routes in, but it won't send any
routes
> out. Passive interface wouldn't work for the rest of the routing
protocols
> though.
>
> If they specifically tell you to block all of the routes going to the
> backbone, then there isn't any way that you will be able to ping the
routes
> (again unless they put a default route on the backbone). There isn't much
> you can do about that since you won't have access to the backbone router.
> If they don't specify anything about blocking all or some of the routes, I
> would make sure that you redistribute into the backbone router so you can
> ping the backbone routes from anywhere in your network.
>
> Bill Lijewski
> CCIE #8642
> Network Learning Inc
> 5 Day R&S CCIE Bootcamp Instructor
>
>
> >From: "Kaiser Anwar" <kaiseranwar@sbcglobal.net>
> >To: "William Lijewski" <ccie8642@hotmail.com>,<ccielab@groupstudy.com>
> >Subject: Re: routes to backbones
> >Date: Thu, 25 Sep 2003 17:13:13 -0500
> >
> >This is another of my concern that if not told in the lab do we
> >redistribute
> >lab routes to bb so it has a path back.
> >this way when you do pinging you could be sure that not only you see bb
> >routes that you also have a best path.
> >this way you can ping end to end.so what is it you just to what you are
> >told
> >and make sure that it works.
> >
> >
> >Thanks In advance for reply
> >Kaiser Anwar
> >
> >
> >----- Original Message -----
> >From: "William Lijewski" <ccie8642@hotmail.com>
> >To: <kaiseranwar@sbcglobal.net>; <ccielab@groupstudy.com>
> >Sent: Thursday, September 25, 2003 5:02 PM
> >Subject: Re: routes to backbones
> >
> >
> > > If you want to block routes, you don't want to apply an access-list to
> >an
> > > interface. The access-list on the interface will block traffic, not
> >routing
> > > updates. You would want to use the distribute-list outbound to the
> >backbone
> > > router. For RIP and EIGRP it would always be a distribute-list, and
you
> > > should always be specific as to which interface you are blocking the
> >routing
> > > updates:
> > >
> > > distribute-list 1 out ethernet 0
> > >
> > > If you are blocking BGP routes there are a couple of ways you can do
it:
> > > distribute-list, prefix-list, or filter-list depending on the
> >requirements.
> > > Again all of these should be a specific as possible with their
> >application -
> > > they should all go on neighbor statements.
> > >
> > > You router that is directly attached to the Backbone router will still
> >be
> > > able to ping it since its ping by default will be sourced from its
> >outgoing
> > > (connected to the Backbone) interface. The Backbone router will know
> >how
> >to
> > > get back to it. Unless there is a default route on the Backbone
router
> >no
> > > other router would be able to ping it since the Backbone router
wouldn't
> > > have a return path (the directly connected router would not be able to
> >ping
> > > it either if you changed the source address of the ping).
> > >
> > > Bill Lijewski
> > > CCIE #8642
> > > Network Learning Inc
> > > 5 Day R&S CCIE Bootcamp Instructor
> > >
> > >
> > > >From: "Kaiser Anwar" <kaiseranwar@sbcglobal.net>
> > > >Reply-To: "Kaiser Anwar" <kaiseranwar@sbcglobal.net>
> > > >To: <ccielab@groupstudy.com>
> > > >Subject: routes to backbones
> > > >Date: Thu, 25 Sep 2003 16:48:41 -0500
> > > >
> > > >Hi,
> > > > just came up with this, if I am told that I am not supposed to
> >send
> > > >any
> > > >routes to backbone.
> > > > what would be the best way to accomplish this.create an standard
> > > >access
> > > >list and apply to the bb interface or
> > > > match it with distribute list and apply it in the routing process
> >for
> > > >rip
> > > >or for bgp on neighbor. just little confused.
> > > > in either of the case if an access list is applied. would I still
be
> > > >able to
> > > >ping BB routes. or may there is a proper way to do it.
> > > >
> > > >
> > > >Thanks
> > > >Kaiser Anwar
> > > >
> > > >***Get your CCIE and a FREE vacation: Shop.GroupStudy.com***
> > >
>_______________________________________________________________________
> > > >Please help support GroupStudy by purchasing your study materials
from:
> > > >shop.groupstudy.com
> > > >
> > > >Subscription information may be found at:
> > > >http://www.groupstudy.com/list/CCIELab.html
> > >
> > > _________________________________________________________________
> > > Instant message during games with MSN Messenger 6.0. Download it now
> >FREE!
> > > http://msnmessenger-download.com
> > >
> > > ***Get your CCIE and a FREE vacation: Shop.GroupStudy.com***
> > >
This archive was generated by hypermail 2.1.4 : Wed Oct 01 2003 - 07:24:38 GMT-3