From: Bob Watson (watson.robert@gmail.com)
Date: Sun Dec 10 2006 - 12:13:03 ART
Looking at it all you need to do is some route filtering on r2 to deny
routing updates from the below or only permiting updates from r1. Easily
done with the distribute-list gateway command.
On 12/10/06, Tandou Mohamed <dtandou@yahoo.com> wrote:
>
> GS,
> need a clarifiaction on lab 36 if someone has done it
> RIP Configuration
> New routers will be joining the 136.10.12.0/24 subnet. R2 should not
> accept/retain any RIP routes from these new routers. However, R1 should
> accept the new routes.
>
> The following five additional new routers will be added on 136.10.12/24
> subnet:
> - 136.10.12.101
> - 136.10.12.102
> - 136.10.12.103
> - 136.10.12.165
> - 136.10.12.166
>
> Configure R2 with minimum number of commands
>
> The subnet 136.10.12/24 is the network between R1 and R2.
> How should i configure the above network? as secondary ip address or
> loopback ?
>
> Thanks,
>
> Mohamed
>
> __________________________________________________
> Do You Yahoo!?
> Tired of spam? Yahoo! Mail has the best spam protection around
> http://mail.yahoo.com
>
> ---------------------------------
> Everyone is raving about the all-new Yahoo! Mail beta.
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
This archive was generated by hypermail 2.1.4 : Tue Jan 02 2007 - 07:50:37 ART