Another RIPv2 LAB

Another RIPv2 LAB

Here is the following network scenario:

 R1 is advertising 4 networks: 192.168.10.x to 192.168.40.x, on each task I have configured different way to control and manipulate the routes using distance, offset-list and distribute-list.

First task was to advertise network 192.168.20.0/24 to R5 through R2 only, this has achieved through distribute-list configured on R5

An extended access-list has been configured:

access-list 100 permit ip host 10.0.25.2 192.168.20.0 0.0.0.0

access-list 100 deny   ip any host 192.168.20.0

access-list 100 permit ip any any

The first line point the source of the advertisement (10.0.25.2) and the route prefix (192.168.20.0/24), second line deny this network from any other source and the third line allow all other advertisements.

Then configure this ACL using distribute-list under router configuration:

Router rip

 distribute-list 100 in

The second task was to advertise network 192.168.30.0/24 through R3 to R5 using offset-list on R2 and R4.

Configure standard ACL which will recognize this network:

access-list 30 permit 192.168.30.0

And then, under the router configuration, configure offset-list, toward the interface to R5, which will rise up the metric (hop count in RIP) over 16 which is eventually unreachable:

offset-list 30 out 15 FastEthernet0/1

Third task was to allow R5 to accept network 192.168.10.0/24 from R3 and, in case of failure, from R4.

A standard ACL for recognize this network:

access-list 10 permit 192.168.10.0

And then configure distance under the router configuration:

distance 255 10.0.25.2 0.0.0.0 10

distance 150 10.0.45.4 0.0.0.0 10

Distance change the AD locally on R5, while the first line sets AD to network 192.168.10.0/24 received from R2 to 255 – which is unknown, the second sets the same from R4 to AD of 150 while R3 remain with RIP default AD of 120.