Day 2 - RIP Filtering - Administrative Distance

Untuk pembahasan filtering routing pada RIP, selanjutnya kita akan bahas bagaimana cara konfigurasi filtering menggunakan Administrative Distance.

Lab 7 - RIP - Filtering - Administrative Distance

Topologi yang digunakan :

 

Skenario pada lab kali ini sbb :
- All router akan advertise IP Loopback masing - masing ke RIP
- R1 akan melakukan filter terhadap IP Loopback R3 menggunakan AD


Konfigurasi R1 :

interface Loopback0
 ip address 1.1.1.1 255.255.255.255
!
interface FastEthernet0/0
 ip address 12.12.12.1 255.255.255.0
!
router rip
 version 2
 network 1.0.0.0
 network 12.0.0.0
 no auto-summary

Konfigurasi R2 :

interface Loopback0
 ip address 2.2.2.2 255.255.255.255
!
interface FastEthernet0/0
 ip address 12.12.12.2 255.255.255.0
!
interface FastEthernet0/1
 ip address 23.23.23.2 255.255.255.0
!
router rip
 version 2
 network 2.0.0.0
 network 12.0.0.0
 network 23.0.0.0
 no auto-summary

Konfigurasi R3 :

interface Loopback0
 ip address 3.3.3.3 255.255.255.255
!
interface FastEthernet0/0
 ip address 23.23.23.3 255.255.255.0
!
router rip
 version 2
 network 3.0.0.0
 network 23.0.0.0
 no auto-summary

Kondisi routing table R1 sebelum filtering administratice distance di konfigurasikan.

R1#sh ip route

Gateway of last resort is not set

     1.0.0.0/32 is subnetted, 1 subnets
C       1.1.1.1 is directly connected, Loopback0
     2.0.0.0/32 is subnetted, 1 subnets
R       2.2.2.2 [120/1] via 12.12.12.2, 00:00:12, FastEthernet0/0
     3.0.0.0/32 is subnetted, 1 subnets
R       3.3.3.3 [120/2] via 12.12.12.2, 00:00:12, FastEthernet0/0
     23.0.0.0/24 is subnetted, 1 subnets
R       23.23.23.0 [120/1] via 12.12.12.2, 00:00:12, FastEthernet0/0
     12.0.0.0/24 is subnetted, 1 subnets
C       12.12.12.0 is directly connected, FastEthernet0/0

R1#sh ip route 3.3.3.3
Routing entry for 3.3.3.3/32
  Known via "rip", distance 120, metric 2
  Redistributing via rip
  Last update from 12.12.12.2 on FastEthernet0/0, 00:00:11 ago
  Routing Descriptor Blocks:
  * 12.12.12.2, from 12.12.12.2, 00:00:11 ago, via FastEthernet0/0
      Route metric is 2, traffic share count is 1

R1#ping 3.3.3.3
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 3.3.3.3, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 16/36/52 ms


Kemudian kita coba konfigurasi AD di R1 agar IP 3.3.3.3 tidak bisa diakses dari R1 :


R1(config)#access-list 1 permit host 3.3.3.3
R1(config)#router rip
R1(config-router)#distance 255 0.0.0.0 255.255.255.255 1
R1(config-router)#exit
R1(config)#do clear ip route *


Kita cek lagi di routing table R1 untuk IP 3.3.3.3 :

R1(config)#do sh ip route 3.3.3.3
% Network not in table

R1(config)#do sh ip route

Gateway of last resort is not set

     1.0.0.0/32 is subnetted, 1 subnets
C       1.1.1.1 is directly connected, Loopback0
     2.0.0.0/32 is subnetted, 1 subnets
R       2.2.2.2 [120/1] via 12.12.12.2, 00:00:01, FastEthernet0/0
     23.0.0.0/24 is subnetted, 1 subnets
R       23.23.23.0 [120/1] via 12.12.12.2, 00:00:01, FastEthernet0/0
     12.0.0.0/24 is subnetted, 1 subnets
C       12.12.12.0 is directly connected, FastEthernet0/0

Terlihat bahwa untuk IP 3.3.3.3 sudah hilang dari routing table R1, dan konfigurasi filtering menggunakan AD sudah berhasil :)