RIP Default Route Redistribution

Default route / Gateway of last resort digunakan untuk mengarahkan paket yang bertujuan ke network yang tidak ada di routing tabel. biasanya digunakan bersama nat agar user lokal dapat mengakses ke jaringan internet.
ada 3 cara untuk mendistribusikan default route ke dalam RIP , Default-information-origiante, redistribute static default route, dan ip default-network.

skenario lab ini R1 terhubung ke jaringan internet.
baca disini cara menghubungkan gns3 ke internet.
kemudian konfigurasikan dynamic nat Overload pada R1.
Saat mengkonfigurasikan ip nat pada router mungkin anda akan mengalami error memory seperti yang saya alami, lihat disini untuk solusinya.
konfigurasikan ip domain-lookup dan ip name-server 8.8.8.8 pada semua router.


1. Default-information originate

secara otomatis default-information originate akan mengadvertise semua default route ke dalam RIP.

R1(config-router)#do show run | begin rip        
router rip
 version 2
 network 12.0.0.0
 network 13.0.0.0
 no auto-summary
!

tambahkan subcommand default-information originate pada konfigurasi router rip

R1(config)#router rip
R1(config-router)#default-information originate

cek di routing tabel R2 dan R3, secara otomatis default route akan di kirimkan ke semua router rip

R2#show ip route
Gateway of last resort is 12.12.12.1 to network 0.0.0.0

     23.0.0.0/8 is variably subnetted, 2 subnets, 2 masks
C       23.23.23.0/24 is directly connected, FastEthernet0/1
R       23.0.0.0/8 [120/2] via 12.12.12.1, 00:00:18, FastEthernet0/0
     12.0.0.0/24 is subnetted, 1 subnets
C       12.12.12.0 is directly connected, FastEthernet0/0
     13.0.0.0/24 is subnetted, 1 subnets
R       13.13.13.0 [120/1] via 12.12.12.1, 00:00:18, FastEthernet0/0
R*   0.0.0.0/0 [120/1] via 12.12.12.1, 00:00:11, FastEthernet0/0


R3#show ip route
Gateway of last resort is 13.13.13.1 to network 0.0.0.0

     23.0.0.0/24 is subnetted, 1 subnets
C       23.23.23.0 is directly connected, FastEthernet0/1
     12.0.0.0/24 is subnetted, 1 subnets
R       12.12.12.0 [120/1] via 13.13.13.1, 00:00:08, FastEthernet0/0
     13.0.0.0/24 is subnetted, 1 subnets
C       13.13.13.0 is directly connected, FastEthernet0/0
R*   0.0.0.0/0 [120/1] via 13.13.13.1, 00:00:08, FastEthernet0/0

R2(config)#do ping google.com   

Translating "google.com"...domain server (8.8.8.8) [OK]

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 173.194.126.33, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 116/136/152 ms

R3#ping google.com

Translating "google.com"...domain server (8.8.8.8) [OK]

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 173.194.126.32, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 160/178/200 ms

2. Redistribute Static

default route konfigurasinya menggunakan routing static dengan destination address dan masknya diset 0.0.0.0 yang artinya routing dengan network tujuan manapun dengan netmask berapapun. konfigurasi default route menggunakan static default route ini secara otomatis hanya mengatur gateway of last resort Router tersebut saja. oleh karena itu perlu di redistribute ke dalam RIP agar bisa diadvertise ke semua router rip.

R1(config-router)#no default-information originate

lihat  routing tabel R2, R3 dan pastikan default route sudah tidak ada

R2#show ip route
Gateway of last resort is not set

     23.0.0.0/24 is subnetted, 1 subnets
C       23.23.23.0 is directly connected, FastEthernet0/1
     12.0.0.0/24 is subnetted, 1 subnets
C       12.12.12.0 is directly connected, FastEthernet0/0
     13.0.0.0/24 is subnetted, 1 subnets
R       13.13.13.0 [120/1] via 23.23.23.3, 00:00:19, FastEthernet0/1
                   [120/1] via 12.12.12.1, 00:00:11, FastEthernet0/0

R3#show ip route
Gateway of last resort is not set

     23.0.0.0/24 is subnetted, 1 subnets
C       23.23.23.0 is directly connected, FastEthernet0/1
     12.0.0.0/24 is subnetted, 1 subnets
R       12.12.12.0 [120/1] via 23.23.23.2, 00:00:13, FastEthernet0/1
                   [120/1] via 13.13.13.1, 00:00:09, FastEthernet0/0
     13.0.0.0/24 is subnetted, 1 subnets
C       13.13.13.0 is directly connected, FastEthernet0/0

pertama perlu dikonfigurasikan dulu default routenya pada R1. kemudian redistribute ke RIP.

R1(config)#ip route 0.0.0.0 0.0.0.0 192.168.42.129 
R1(config-router)#redistribute static

R2#show ip route
Gateway of last resort is 12.12.12.1 to network 0.0.0.0

     23.0.0.0/24 is subnetted, 1 subnets
C       23.23.23.0 is directly connected, FastEthernet0/1
     12.0.0.0/24 is subnetted, 1 subnets
C       12.12.12.0 is directly connected, FastEthernet0/0
     13.0.0.0/24 is subnetted, 1 subnets
R       13.13.13.0 [120/1] via 23.23.23.3, 00:00:21, FastEthernet0/1
                   [120/1] via 12.12.12.1, 00:00:15, FastEthernet0/0
R*   0.0.0.0/0 [120/1] via 12.12.12.1, 00:00:15, FastEthernet0/0

R3#show ip route
Gateway of last resort is 13.13.13.1 to network 0.0.0.0

     23.0.0.0/24 is subnetted, 1 subnets
C       23.23.23.0 is directly connected, FastEthernet0/1
     12.0.0.0/24 is subnetted, 1 subnets
R       12.12.12.0 [120/1] via 23.23.23.2, 00:00:02, FastEthernet0/1
                   [120/1] via 13.13.13.1, 00:00:01, FastEthernet0/0
     13.0.0.0/24 is subnetted, 1 subnets
C       13.13.13.0 is directly connected, FastEthernet0/0
R*   0.0.0.0/0 [120/1] via 13.13.13.1, 00:00:01, FastEthernet0/0

R2#ping sfprimary.com

Translating "sfprimary.com"...domain server (8.8.8.8) [OK]

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.31.186.20, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 300/313/360 ms

R3#ping sfprimary.com

Translating "sfprimary.com"...domain server (8.8.8.8) [OK]

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.31.186.20, timeout is 2 seconds:
.!!!!
Success rate is 80 percent (4/5), round-trip min/avg/max = 288/493/1084 ms

3. ip default-network

jika ip default-gateway digunakan di router yang ip routingnya didisabled. ip default-network digunakan pada router yang aktif melakukan routing seperti R1 dan secara otomatis gateway yang dikonfigurasikan akan di advertise ke RIP. network yang dikonfigurasikan sebagai gateway of last resort di ip default-network haruslah classful network.
pertama hapus dulu default routing dan redistribute static pada R1.

R1(config)#ip default-network 192.168.42.0

R2#show ip route
Gateway of last resort is 12.12.12.1 to network 0.0.0.0

     23.0.0.0/24 is subnetted, 1 subnets
C       23.23.23.0 is directly connected, FastEthernet0/1
     12.0.0.0/24 is subnetted, 1 subnets
C       12.12.12.0 is directly connected, FastEthernet0/0
     13.0.0.0/24 is subnetted, 1 subnets
R       13.13.13.0 [120/1] via 23.23.23.3, 00:00:18, FastEthernet0/1
                   [120/1] via 12.12.12.1, 00:00:07, FastEthernet0/0
R*   0.0.0.0/0 [120/1] via 12.12.12.1, 00:00:07, FastEthernet0/0


R3#show ip route
Gateway of last resort is 13.13.13.1 to network 0.0.0.0

     23.0.0.0/24 is subnetted, 1 subnets
C       23.23.23.0 is directly connected, FastEthernet0/1
     12.0.0.0/24 is subnetted, 1 subnets
R       12.12.12.0 [120/1] via 23.23.23.2, 00:00:16, FastEthernet0/1
                   [120/1] via 13.13.13.1, 00:00:14, FastEthernet0/0
     13.0.0.0/24 is subnetted, 1 subnets
C       13.13.13.0 is directly connected, FastEthernet0/0
R*   0.0.0.0/0 [120/1] via 13.13.13.1, 00:00:14, FastEthernet0/0

Read more

RIP Route Filtering

untuk memfilter route pada RIP ada beberapa cara yang bisa digunakan, pertama menggunakan Distribute List, kedua menggunakan Administrative Distance dan Terakhir menggunakan Offset List

Pertama konfig semua Interface pada R1, R2, dan R3.
kemudian konfigurasikan RIP

R1,R2,R3(config-if)#router rip
R1,R2,R3(config-router)#v 2
R1,R2,R3(config-router)#network 0.0.0.0
R1,R2,R3(config-router)#no auto-summary

kemudian pastikan routing tabelnya lengkap.


1. Distribute List

digunakan untuk memfilter route mana yang akan diadvertise dan yang akan diproses oleh router, bisa diterapkan jalur inbound dan outbound.
distribute list bisa digunakan dengan access-list maupun prefix-list.

Access-list                                                                                                               
R1 dalam routing tabelnya tentu memiliki semua route dari R3.

 R1#show ip route rip
     20.0.0.0/16 is subnetted, 4 subnets
R       20.4.0.0 [120/2] via 12.12.12.2, 00:00:11, FastEthernet0/0
R       20.1.0.0 [120/2] via 12.12.12.2, 00:00:11, FastEthernet0/0
R       20.2.0.0 [120/2] via 12.12.12.2, 00:00:11, FastEthernet0/0
R       20.3.0.0 [120/2] via 12.12.12.2, 00:00:11, 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:11, FastEthernet0/0

Sekarang filter pada R2 menggunakan access-list agar yang masuk ke R3 adalah route yang oktet ke-2 nya genap.

biar commandnya cukup satu baris, permit saja oktet genapnya
R2(config)#access-list 1 permit 20.0.0.0 0.254.255.255
distribute-list bisa dikonfigurasikan saat masuk interface maupun keluar, karena yang perlu diblok adalah yang masuk R3 maka dikonfigurasikan di f0/0 arah out.
R2(config)#router rip
R2(config-router)#distribute-list 1 out f0/0 

 R1#show ip route rip
     20.0.0.0/16 is subnetted, 2 subnets
R       20.4.0.0 [120/2] via 12.12.12.2, 00:00:12, FastEthernet0/0
R       20.2.0.0 [120/2] via 12.12.12.2, 00:00:12, FastEthernet0/0

Prefix-list                                                                                                                     
Prefix list merupakan route filter yang digunakan untuk memfilter route berdasarkan panjang prefix. berbeda dengan access-list, prefix-list tidak bisa digunakan untuk memfilter route genap/ganjil saja. namun prefix list digunakan untuk memilih route yang berurutan dari prefix sekian sampai prefix sekian yang bisa kita tentukan.
contohnya :

Router(config)#ip prefix-list contoh1 permit 123.0.0.0/8 ge 24 le 32
prefix list akan mencocokan route dengan 8 bit / oktet pertama 123.x.x.x dengan subnet mask 255.255.255.0 sampai 255.255.255.255

R3 pasti memiliki semua route dari R1

R3#show ip route rip
     1.0.0.0/32 is subnetted, 1 subnets
R       1.1.1.1 [120/2] via 23.23.23.2, 00:00:05, FastEthernet0/0
     10.0.0.0/16 is subnetted, 2 subnets
R       10.2.0.0 [120/2] via 23.23.23.2, 00:00:05, FastEthernet0/0
R       10.1.0.0 [120/2] via 23.23.23.2, 00:00:05, FastEthernet0/0
     11.0.0.0/16 is subnetted, 2 subnets
R       11.2.0.0 [120/2] via 23.23.23.2, 00:00:05, FastEthernet0/0
R       11.1.0.0 [120/2] via 23.23.23.2, 00:00:05, FastEthernet0/0
     12.0.0.0/24 is subnetted, 1 subnets
R       12.12.12.0 [120/1] via 23.23.23.2, 00:00:05, FastEthernet0/0

Blok ruote 10.x.0.0/16 dan 11.x.0.0/16 dari R1 pada R2 agar nantinya route tersebut hilang dari routing tabel R3.

prefix list dieksekusi berdasarkan nomor sequence-nya. seq 5 melakukan fungsi seperti access list permit ip any any.
R2(config)#ip prefix-list blokr1 seq 1 deny 10.0.0.0/8 le 16
R2(config)#ip prefix-list blokr1 seq 2 deny 11.0.0.0/8 le 16
R2(config)#ip prefix-list blokr1 seq 5 permit 0.0.0.0/0 le 32 
R2(config-router)#distribute-list prefix blokr1 out f0/1

R3#show ip route 10.0.0.0 longer-prefixes | begin Gate  
Gateway of last resort is not set

R3#show ip route 11.0.0.0 longer-prefixes | begin Gate
Gateway of last resort is not set

R3#show ip route rip                                 
     1.0.0.0/32 is subnetted, 1 subnets
R       1.1.1.1 [120/2] via 23.23.23.2, 00:00:02, FastEthernet0/0
     12.0.0.0/24 is subnetted, 1 subnets
R       12.12.12.0 [120/1] via 23.23.23.2, 00:00:02, FastEthernet0/0

2. Administrative Distance

sebuah route bisa difilter dengan cara administrative distance nya dimanipulasi menjadi sangat besar.

R2#show ip route 1.1.1.1
Routing entry for 1.1.1.1/32
  Known via "rip", distance 120, metric 1
  Redistributing via rip
  Last update from 12.12.12.1 on FastEthernet0/0, 00:00:05 ago
  Routing Descriptor Blocks:
  * 12.12.12.1, from 12.12.12.1, 00:00:05 ago, via FastEthernet0/0
      Route metric is 1, traffic share count is 1

dengan membuat nilai AD menjadi 255 kita akan buat agar route tersebut dibuang di routing tabel R2

R2(config-router)#distance 255 0.0.0.0 255.255.255.255 2
R2#show ip route 1.1.1.1
% Network not in table

3. Offset List

dengan offset list ini metric dari sebuah route bisa dimanipulasi, jika pada rip maka sebuah route bisa dibuang dari routing tabel dengan hop countnya dibuat menjadi 16 inaccessible. Offset list hanya bisa digunakan pada distance vektor routing protokol, RIP dan EIGRP. RIP hanya bertukar informasi routing dengan directly connected router, namun darimana tetangganya mendapatkan route tersebut router tersebut tidak tahu oleh karena itu RIP sering disebut "routing by rumour"

R1#show ip route 20.2.0 metric, of a.1
Routing entry for 20.2.0.0/16
  Known via "rip", distance 120, metric 2
  Redistributing via rip
  Last update from 12.12.12.2 on FastEthernet0/0, 00:00:22 ago
  Routing Descriptor Blocks:
  * 12.12.12.2, from 12.12.12.2, 00:00:22 ago, via FastEthernet0/0
      Route metric is 2, traffic share count is 1

offset list dikonfigurasikan inbound, untuk memfilter route yang router terima.
R1(config-router)#offset-list 3 in 16 f0/0

Read more

RIP Split Horizon di Frame Relay

Split Horizon merupakan fitur distance vektor routing protokol yaitu RIP dan EIGRP yang digunakan untuk mencegah terjadinya routing loop dengan tidak memperbolehkan sebuah route diadvertise ke interface route tersebut berasal.
Split Horizon menjadi masalah pada jaringan frame relay khususnya frame relay hub and spoke yang menggunakan sub-interface, karena pada serial physical interface ip split horizon defaultnya adalah disabled sementara pada sub-interface enabled.

R2(config)#interface s1/0
R2(config-if)#encapsulation frame-relay
R2(config-if)#ip add 10.10.10.2 255.255.255.0
R2(config-if)#frame-relay map ip 10.10.10.1 201 broadcast
R2(config-if)#frame-relay map ip 10.10.10.3 201         
R2(config-if)#no shut
R2(config-if)#interface lo0
R2(config-if)#ip add 2.2.2.2 255.255.255.255
R2(config-if)#router rip
R2(config-router)#v 2
R2(config-router)#network 0.0.0.0
R2(config-router)#no auto-summary


R3(config)#interface s1/0
R3(config-if)#encapsulation frame-relay 
R3(config-if)#ip add 10.10.10.3 255.255.255.0
R3(config-if)#frame-relay map ip 10.10.10.1 301 broadcast
R3(config-if)#frame-relay map ip 10.10.10.2 301
R3(config-if)#no shut
R3(config-if)#interface lo0
R3(config-if)#ip add 3.3.3.3 255.255.255.255
R3(config-if)#router rip
R3(config-router)#v 2
R3(config-router)#network 0.0.0.0
R3(config-router)#no auto-summary

R1(config)#interface s1/0
R1(config-if)#encapsulation frame-relay
R1(config-if)#no shut   
R1(config)#interface s1/0.1 multipoint
R1(config-subif)#ip add 10.10.10.1 255.255.255.0
R1(config-subif)#frame-relay map ip 10.10.10.2 102 broadcast
R1(config-subif)#frame-relay map ip 10.10.10.3 103 broadcast 
R1(config)#router rip
R1(config-router)#v 2     
R1(config-router)#network 0.0.0.0
R1(config-router)#no auto-summary

pada routing tabel R2 hanya ada RIP dari loopback R1
R2#show ip route

R    1.0.0.0/8 [120/1] via 10.10.10.1, 00:00:25, Serial1/0
     2.0.0.0/32 is subnetted, 1 subnets
C       2.2.2.2 is directly connected, Loopback0
     10.0.0.0/24 is subnetted, 1 subnets
C       10.10.10.0 is directly connected, Serial1/0

informasi routing di R1 lengkap, namun R1 tidak akan mengirimkan update dari R2 ke R3 melalui s1/0.1 maupun sebaliknya.
R1#show ip route

     1.0.0.0/8 is variably subnetted, 2 subnets, 2 masks
C       1.1.1.1/32 is directly connected, Loopback0
R       1.0.0.0/8 [120/1] via 10.10.10.3, 00:00:23, Serial1/0.1
                  [120/1] via 10.10.10.2, 00:00:07, Serial1/0.1
R    2.0.0.0/8 [120/1] via 10.10.10.2, 00:00:07, Serial1/0.1
R    3.0.0.0/8 [120/1] via 10.10.10.3, 00:00:23, Serial1/0.1
     10.0.0.0/24 is subnetted, 1 subnets
C       10.10.10.0 is directly connected, Serial1/0.1

R1#show ip interface s1/0.1
Serial1/0.1 is up, line protocol is up
  Internet address is 10.10.10.1/24
  Broadcast address is 255.255.255.255
  Address determined by setup command
  MTU is 1500 bytes
  Helper address is not set
  Directed broadcast forwarding is disabled
  Multicast reserved groups joined: 224.0.0.9
  Outgoing access list is not set
  Inbound  access list is not set
  Proxy ARP is enabled
  Local Proxy ARP is disabled
  Security level is default
  Split horizon is enabled
  ICMP redirects are always sent
  ICMP unreachables are always sent
  ICMP mask replies are never sent
  IP fast switching is enabled
  IP fast switching on the same interface is enabled
  IP Flow switching is disabled
  IP CEF switching is enabled
  IP CEF Fast switching turbo vector
  IP multicast fast switching is enabled
 --More--  

R1(config)#interface s1/0.1
R1(config-subif)#no ip split-horizon  

cek ladi di routing tabel R2 dan R3. Pastikan bisa ping ke loopback masing-masing.

R2#show ip route

     1.0.0.0/32 is subnetted, 1 subnets
R       1.1.1.1 [120/1] via 10.10.10.1, 00:00:27, Serial1/0
     2.0.0.0/32 is subnetted, 1 subnets
C       2.2.2.2 is directly connected, Loopback0
     3.0.0.0/32 is subnetted, 1 subnets
R       3.3.3.3 [120/2] via 10.10.10.3, 00:00:27, Serial1/0
     10.0.0.0/24 is subnetted, 1 subnets
C       10.10.10.0 is directly connected, Serial1/0

R2#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 = 8/24/44 ms

Read more

RIP Authentication

RIP memiliki dua mode authentikasi untuk routing updatenya, clear text dan MD5. perbedaanya adalah mode clear text Router tidak menyembunyikan passwordnya sedangkan MD5 Router mengirimkan message diggest keyed sehingga apabila dijaringan ada yang mencapture trafik maka password tidak akan terlihat.

pertama buat key chain , key id dan key string di kedua sisi harus sama, begitu juga dengan mode authentikasinya. kemudian apply key chain ke interface.

R1(config)#key chain sfprimary
R1(config-keychain)#key 1
R1(config-keychain-key)#key-string cisco
R1(config)#interface f0/0
R1(config-if)#ip add 12.12.12.1 255.255.255.0
R1(config-if)#ip rip authentication mode text
R1(config-if)#ip rip authentication key-chain sfprimary
R1(config-if)#no shut
R1(config-if)#interface lo0
R1(config-if)#ip add 1.1.1.1 255.255.255.255
R1(config-keychain-key)#router rip
R1(config-router)#v 2           
R1(config-router)#network 0.0.0.0

R2(config)#key chain sfprimary
R2(config-keychain)#key 1
R2(config-keychain-key)#key-string cisco
R2(config)#interface f0/0
R2(config-if)#ip add 12.12.12.2 255.255.255.0
R2(config-if)#ip rip authentication mode text
R2(config-if)#ip rip authentication key-chain sfprimary
R2(config-if)#no shut
link ke R3 menggunakan autentikasi MD5
R2(config-if)#interface f0/1
R2(config-if)#ip add 23.23.23.2 255.255.255.0
R2(config-if)#ip rip authentication mode md5
R2(config-if)#ip rip authentication key-chain sfprimary
R2(config-if)#no shut
R2(config-if)#interface lo0
R2(config-if)#ip add 2.2.2.2 255.255.255.255
R2(config-if)#router rip
R2(config-router)#v 2
R2(config-router)#network 0.0.0.0 


R3 menggunakan key id berbeda, sebenarnya key id bisa saja berbeda. namun aturanya key id yang lebih kecil tidak dapat menerima update dari key id yang lebih besar sementara key id yang besar bisa menerima update dari id kecil
R3(config)#key chain sfprimary
R3(config-keychain)#key 2
R3(config-keychain-key)#key-string cisco
R3(config-keychain-key)#interface f0/0
R3(config-if)#ip add 23.23.23.3 255.255.255.0
R3(config-if)#ip rip authentication mode md5
R3(config-if)#ip rip authentication key-chain sfprimary
R3(config-if)#no shut    
R3(config-if)#interface lo0
R3(config-if)#ip add 3.3.3.3 255.255.255.255
R3(config-if)#router rip
R3(config-router)#v 2
R3(config-router)#network 0.0.0.0

Gunakan command show ip protocol untuk melihat pada interface mana saja key chain di aplikasikan dan key chainya.

 R2#show ip protocol
Routing Protocol is "rip"
    Sending updates every 30 seconds, next due in 26 seconds
  Invalid after 180 seconds, hold down 180, flushed after 240
  Redistributing: rip
  Default version control: send version 2, receive version 2
    Interface             Send  Recv  Triggered RIP  Key-chain
    FastEthernet0/0       2     2           sfprimary      
    FastEthernet0/1       2     2          sfprimary      
    Loopback0             2     2                                   
 

R2#debug ip rip
RIP protocol debugging is on
R2#
*Mar  1 00:47:41.335: RIP: sending v2 update to 224.0.0.9 via FastEthernet0/0 (12.12.12.2)
*Mar  1 00:47:41.335: RIP: build update entries
*Mar  1 00:47:41.335:     2.0.0.0/8 via 0.0.0.0, metric 1, tag 0
*Mar  1 00:47:41.339:     23.0.0.0/8 via 0.0.0.0, metric 1, tag 0
*Mar  1 00:47:45.391: RIP: sending v2 update to 224.0.0.9 via Loopback0 (2.2.2.2)
*Mar  1 00:47:45.391: RIP: build update entries
*Mar  1 00:47:45.391:     1.0.0.0/8 via 0.0.0.0, metric 1, tag 0
*Mar  1 00:47:45.391:     12.0.0.0/8 via 0.0.0.0, metric 1, tag 0
*Mar  1 00:47:45.391:     23.0.0.0/8 via 0.0.0.0, metric 1, tag 0
*Mar  1 00:47:50.523: RIP: received packet with text authentication cisco
*Mar  1 00:47:50.523: RIP: received v2 update from 12.12.12.1 on FastEthernet0/0
*Mar  1 00:47:50.527:      1.0.0.0/8 via 0.0.0.0 in 1 hops
*Mar  1 00:47:50.563: RIP: sending v2 update to 224.0.0.9 via FastEthernet0/1 (23.23.23.2)
*Mar  1 00:47:50.563: RIP: build update entries
*Mar  1 00:47:50.563:     1.0.0.0/8 via 0.0.0.0, metric 1, tag 0
*Mar  1 00:47:50.567:     2.0.0.0/8 via 0.0.0.0, metric 1, tag 0
*Mar  1 00:47:50.567:     12.0.0.0/8 via 0.0.0.0, metric 1, tag 0
*Mar  1 00:47:54.671: RIP: received packet with MD5 authentication
R2 memiliki key id 1 sedangkan R3 Memiliki key id 2, jadi R2 tidak akan mengabaikan route yang diterima dari R3
*Mar  1 00:47:54.671: RIP: ignored v2 packet from 23.23.23.3 (invalid authentication)

R3#debug ip rip
RIP protocol debugging is on
R3#
*Mar  1 00:51:10.147: RIP: sending v2 update to 224.0.0.9 via FastEthernet0/0 (23.23.23.3)
*Mar  1 00:51:10.147: RIP: build update entries
*Mar  1 00:51:10.151:     3.0.0.0/8 via 0.0.0.0, metric 1, tag 0
*Mar  1 00:51:29.007: RIP: sending v2 update to 224.0.0.9 via Loopback0 (3.3.3.3)
*Mar  1 00:51:29.007: RIP: build update entries
*Mar  1 00:51:29.007:     1.0.0.0/8 via 0.0.0.0, metric 1, tag 0
*Mar  1 00:51:29.011:     2.0.0.0/8 via 0.0.0.0, metric 1, tag 0
*Mar  1 00:51:29.011:     12.0.0.0/8 via 0.0.0.0, metric 1, tag 0
*Mar  1 00:51:29.011:     23.0.0.0/8 via 0.0.0.0, metric 1, tag 0
*Mar  1 00:51:29.019: RIP: ignored v2 packet from 3.3.3.3 (sourced from one of our addresses)
*Mar  1 00:51:30.259: RIP: received packet with MD5 authentication
*Mar  1 00:51:30.259: RIP: received v2 update from 23.23.23.2 on FastEthernet0/0
 

Read more

RIP Unicast Update

Secara Default Rip v1 mengirimkan routing update secara broadcast (255.255.255.255) dan Rip v2 mengirimkan update ke 224.0.0.9. RIP bisa dikonfigurasikan untuk melakukan update secara unicast, digunakan pada jaringan seperti frame-relay.
 

R1, R2, R3 ketiganya merupakan router RIP. skenarionya disini R1 akan update unicast ke R2 dan R2 update unicast ke R3.

R1(config)#interface f0/0            
R1(config-if)#ip add 12.12.12.1 255.255.255.0
R1(config-if)#no shut
R1(config-if)#router rip
R1(config-router)#v 2
R1(config-router)#network 0.0.0.0
harus dikonfig manual neighbornya
R1(config-router)#neighbor 12.12.12.2

R2(config)#interface f0/0
R2(config-if)#ip add 12.12.12.2 255.255.255.0
R2(config-if)#no shut
R2(config-if)#router rip
R2(config-router)#v 2
R2(config-router)#network 0.0.0.0
R2(config-router)#neighbor 12.12.12.1

dilihat pada debug ip rip, update yang dikrimkan malah masih tetap menggunakan multicast walaupun unicastnya sudah bisa. untuk itu perlu dikonfigurasikan passive-interface pada rip configuration
R1#debug ip rip
*Mar  1 00:08:41.367: %SYS-5-CONFIG_I: Configured from console by console
RIP protocol debugging is on
R1#
*Mar  1 00:08:59.427: RIP: sending v2 update to 224.0.0.9 via FastEthernet0/0 (12.12.12.1)
*Mar  1 00:08:59.427: RIP: build update entries - suppressing null update
*Mar  1 00:08:59.427: RIP: sending v2 update to 12.12.12.2 via FastEthernet0/0 (12.12.12.1)

passive interface pada rip digunakan agar interface tidak mengirimkan update, tetapi masih bisa menerima update.
R1(config-router)#passive-interface f0/0  
R2(config-router)#passive-interface f0/0  

R1(config-router)#
*Mar  1 00:13:37.767: RIP: sending v2 update to 12.12.12.2 via FastEthernet0/0 (12.12.12.1)
*Mar  1 00:13:37.767: RIP: build update entries - suppressing null update

Selanjutnya R2 ke R4 dikonfig untuk update secara unicast tetapi melalui Router non-RIP.

R2(config)#interface f0/1
R2(config-if)#ip add 23.23.23.2 255.255.255.0
R2(config-if)#no shut
R2(config-if)#router rip
tambahkan ip unicast R4 dengan command neighbor, kemudian buat statik routing agar packet bisa tersampaikan dari R2 Ke R4.
R2(config-router)#neighbor 34.34.34.4
R2(config-router)#passive-interface f0/1
R2(config-router)#ex
R2(config)#ip route 34.34.34.0 255.255.255.0 f0/1

R4(config)#interface f0/0
R4(config-if)#ip add 34.34.34.4 255.255.255.0
R4(config-if)#no shut
R4(config-if)#ip route 23.23.23.0 255.255.255.0 f0/0
R4(config)#router rip
R4(config-router)#v 2
R4(config-router)#network 0.0.0.0
R4(config-router)#neighbor 23.23.23.2
R4(config-router)#passive-interface f0/0

Router R4 sudah mengirimkan update secara unicast, tapi route dari R2 belum akan ada di routing tabel milik R4 karena debug dibawah ini menunjukan bahwa R4 menolak update dari R2.
hal ini terjadi karena RIP tidak akan pernah menerima update dari source yang tidak memiliki subnet yang sama. untuk mengatasi itu kita disable validasi update sourcenya.
R4#debug ip rip
RIP protocol debugging is on
R4#
*Mar  1 00:24:24.159: RIP: sending v2 update to 23.23.23.2 via FastEthernet0/0 (34.34.34.4)
*Mar  1 00:24:24.159: RIP: build update entries - suppressing null update
*Mar  1 00:24:48.211: RIP: ignored v2 update from bad source 23.23.23.2 on FastEthernet0/0

R2(config-router)#no validate-update-source
R4(config-router)#no validate-update-source

sekarang pada routing tabel R4 akan masuk  route yang bersumber dari R2

R4(config-router)#do show ip route

     34.0.0.0/24 is subnetted, 1 subnets
C       34.34.34.0 is directly connected, FastEthernet0/0
     23.0.0.0/24 is subnetted, 1 subnets
S       23.23.23.0 is directly connected, FastEthernet0/0
R    12.0.0.0/8 [120/1] via 23.23.23.2, 00:00:01

 

Read more

RIP Pindah Jalur - Offset list

RIP menggunakan hop count sebagai nilai metricnya, semakin rendah nilai hop count maka jalur itu akan dipilih menjadi jalur terbaiknya.
pada lab ini kita akan mempelajari bagaimana untuk merubah jalur pada RIP. langsung saja topologi yang digunakan  :

secara default R1 menuju R2 akan melalui jalur serial karena memiliki hop count yang lebih sedikit, namun bagaimana jika dari R1 ping ke Loopback R2 melewati jalur yang lebih jauh yaitu R1-R3-R2.

Konfigurasi R1

R1(config)#int f0/0
R1(config-if)#ip add 13.13.13.1 255.255.255.0
R1(config-if)#no shut
R1(config-if)#int s0/0
R1(config-if)#ip add 12.12.12.1 255.255.255.0
R1(config-if)#no shut
R1(config-if)#int lo0
R1(config-if)#ip add 1.1.1.1 255.255.255.255
R1(config-if)#router rip
R1(config-router)#version 2
R1(config-router)#network 0.0.0.0
R1(config-router)#no auto-summary

Konfigurasi R2

R2(config)#int f0/0
R2(config-if)#ip add 23.23.23.2 255.255.255.0
R2(config-if)#no shut
R2(config-if)#int s0/0
R2(config-if)#ip add 12.12.12.2 255.255.255.0
R2(config-if)#no shut
R2(config-if)#int lo0
R2(config-if)#ip add 2.2.2.2 255.255.255.255
R2(config-if)#router rip
R2(config-router)#version 2
R2(config-router)#network 0.0.0.0
R2(config-router)#no auto-summary

Konfigurasi R3

R3(config)#int f0/0
R3(config-if)#ip add 13.13.13.3 255.255.255.0
R3(config-if)#no shut
R3(config-if)#int f0/1
R3(config-if)#ip add 23.23.23.3 255.255.255.0
R3(config-if)#no shut
R3(config-if)#int lo0
R3(config-if)#ip add 3.3.3.3 255.255.255.255
R3(config-if)#router rip
R3(config-router)#version 2
R3(config-router)#network 0.0.0.0
R3(config-router)#no auto-summary

sampai disini pastikan R1 dapat ping ke IP Loopback R2.

R1(config-router)#do ping 2.2.2.2

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 2.2.2.2, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 4/4/8 ms
R1(config-router)#do traceroute 2.2.2.2

Type escape sequence to abort.
Tracing the route to 2.2.2.2

  1 12.12.12.2 4 msec 4 msec * 

dari hasil traceroute terlihat jalur yang dipilih adalah jalur terpendek, sekarang kita manipulasi hop countya dengan offset List, seolah-olah Hop count s0/0 lebih besar.
Offset list ini bisa kita konfigurasikan baik disisi R1 maupun R2.
Konfigurasi R1

R1(config)#router rip
R1(config-router)#offset-list 0 in 5 s0/0
R1(config-router)#do clear ip route *

sekarang coba kita cek lagi dengan traceroute jalur mana yang dipilih

R1(config-router)#do traceroute 2.2.2.2

Type escape sequence to abort.
Tracing the route to 2.2.2.2

  1 13.13.13.3 8 msec 8 msec 8 msec
  2 23.23.23.2 8 msec 8 msec * 

kita bisa juga mengkonfigurasikan Offset-list pada R2, pertama kita hapus dulu konfigurasi offset-list pada R1

R1(config-router)#no offset-list 0 in 5 s0/0

R2(config-router)#offset-list 0 out 5 s0/0
R2(config-router)#do clear ip route *

R1(config-router)#do traceroute 2.2.2.2    

Type escape sequence to abort.
Tracing the route to 2.2.2.2

  1 13.13.13.3 4 msec 8 msec 8 msec
  2 23.23.23.2 8 msec 8 msec *

Read more

RIP Convergence Timers

RIP Timer secara default sebagai berikut :

• Update 30s, Router Rip melakukan update secara periodik dalam waktu 30s
• Invalid 180s, sebuah route akan invalid / dinyatakan inaccessible dan diadvertise unreachable apabila selama 180s router tidak menerima update mengenai route tersebut. namun route tetap ada pada routing tabel.
• Holdown 180s, apabila nilai matric sebuah route berubah maka router tidak akan menerima update dari router lain selama waktu holddown ini
• Flush 240s, apabila selama 240s router tetap tidak mendapatkan update mengenai sebuah route maka route tersebut akan benar-benar dihapus dari routing tabel.

pada lab ini kita akan mempelajari mengubah timer basic pada RIP
topologi yang digunakan :

kita akan rubah default update time pada R1 ke R2 menjadi 10s sedangkan R2 ke R3 tetap ke defaultnya yaitu 30s.

Konfigurasi R1

R1(config)#int f0/0
R1(config-if)#ip add 12.12.12.1 255.255.255.0
R1(config-if)#no shut
R1(config-if)#int lo0

R1(config-if)#ip add 1.1.1.1 255.255.255.255
R1(config-if)#router rip
R1(config-router)#version 2
R1(config-router)#network 0.0.0.0
R1(config-router)#no auto-summary

Konfigurasi R2

R2(config)#int f0/0
R2(config-if)#ip add 12.12.12.2 255.255.255.0
R2(config-if)#no shut
R2(config-if)#int f0/1
R2(config-if)#ip add 23.23.23.2 255.255.255.0
R2(config-if)#no shut
R2(config-if)#int lo0
R2(config-if)#ip add 2.2.2.2 255.255.255.255
R2(config-if)#router rip
R2(config-router)#version 2
R2(config-router)#network 0.0.0.0
R2(config-router)#no auto-summary

Konfigurasi R3

R3(config)#int f0/0
R3(config-if)#ip add 23.23.23.3 255.255.255.0
R3(config-if)#no shut
R3(config-if)#int lo0
R3(config-if)#ip add 3.3.3.3 255.255.255.255
R3(config-if)#router rip
R3(config-router)#version 2
R3(config-router)#network 0.0.0.0
R3(config-router)#no auto-summary

pastikan terlebih dahulu dengan ping ke IP Loopback masing-masing router berhasil.

kemudian kita akan rubah basic timernya menggunakan perintah "timer basic

<update><invalid><hold><flush>"

R1(config-router)#timer basic ?
  <0-4294967295>  Interval between updates

R1(config-router)#timer basic 10 ?
  <1-4294967295>  Invalid

R1(config-router)#timer basic 10 180 ?
  <0-4294967295>  Holddown

R1(config-router)#timer basic 10 180 180 ?
  <1-4294967295>  Flush

R1(config-router)#timer basic 10 180 180 240

R2(config-router)#timer basic 10 180 180 240

sampai disini apabila update time nya berbeda maka akan menimbulkan masalah neighboring, R3 update time nya masih default yaitu 30s, untuk itu perlu kita spesifikasikan R2-R3 

R2(config-router)#int f0/1
R2(config-if)#ip rip advertise 30

kita bisa menggunakan command "show ip protocol" untuk melihat apakah konfigurasi sudah berhasil

R1(config-router)#do show ip protocol
Routing Protocol is "rip"
  Outgoing update filter list for all interfaces is not set
  Incoming update filter list for all interfaces is not set
  Sending updates every 10 seconds, next due in 6 seconds
  Invalid after 180 seconds, hold down 180, flushed after 240

R2(config-if)#do show ip protocol
Routing Protocol is "rip"
  Outgoing update filter list for all interfaces is not set
  Incoming update filter list for all interfaces is not set
  Sending updates every 10 seconds, next due in 8 seconds
  Invalid after 180 seconds, hold down 180, flushed after 240

terlihat untuk update time R1 dan R2 sudah berubah menjadi 10s, bagaimana dengan R3

R3#show ip protocol
Routing Protocol is "rip"
  Outgoing update filter list for all interfaces is not set
  Incoming update filter list for all interfaces is not set
  Sending updates every 30 seconds, next due in 26 seconds
  Invalid after 180 seconds, hold down 180, flushed after 240

update timenya masih default yaitu 30s. 

sekarang  test ping ke ip loopback router

R1(config-router)#do ping 2.2.2.2

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 2.2.2.2, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 4/6/8 ms
R1(config-router)#do 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 = 8/18/52 ms

Read more

RIP Summary Address

Kita akan mempelajari Summary Address pada Routing RIP, Peringkasan routing tabel berpengaruh terhadap penggunaan memory dan processor Router sehingga kinerja router akan lebih ringan. 

Topologi yang digunakan :

Konfigurasi R1

R1(config)#int f0/0
R1(config-if)#ip add 12.12.12.1 255.255.255.0
R1(config-if)#no shut
R1(config-if)#int lo0
R1(config-if)#ip add 1.1.1.1 255.255.
R1(config-if)#ip add 12.12.12.1 255.255.255.255.255

selanjutnya kita buat ip loopback yang banyak untuk pengetesan

R1(config-if)#interface lo1
R1(config-if)#ip add 10.0.0.1 255.255.255.255
R1(config-if)#interface lo2
R1(config-if)#ip add 10.0.1.1 255.255.255.255
R1(config-if)#interface lo3
R1(config-if)#ip add 10.0.2.1 255.255.255.255
R1(config-if)#interface lo4
R1(config-if)#ip add 10.0.4.1 255.255.255.255
R1(config-if)#interface lo5
R1(config-if)#ip add 10.0.5.1 255.255.255.255
R1(config-if)#int lo6
R1(config-if)#ip add 10.0.6.1 255.255.255.255
R1(config-if)#int lo7
R1(config-if)#ip add 10.0.7.1 255.255.255.255
R1(config-if)#int lo8
R1(config-if)#ip add 10.0.8.1 255.255.255.255
R1(config-if)#int lo9
R1(config-if)#ip add 10.0.9.1 255.255.255.255
R1(config-if)#int lo10
R1(config-if)#ip add 10.0.10.1 255.255.255.255
R1(config-if)#int lo20
R1(config-if)#ip add 20.0.0.1 255.255.255.255
R1(config-if)#int lo21
R1(config-if)#ip add 20.0.1.1 255.255.255.255
R1(config-if)#int lo22
R1(config-if)#ip add 20.0.2.1 255.255.255.255
R1(config-if)#int lo23
R1(config-if)#int lo30
R1(config-if)#ip add 30.0.0.1 255.255.255.255
R1(config-if)#int lo31
R1(config-if)#ip add 30.0.1.1 255.255.255.255
R1(config-if)#int lo32
R1(config-if)#ip add 30.0.2.1 255.255.255.255

Aktifkan Routing RIP

R1(config-if)#router rip
R1(config-router)#version 2
R1(config-router)#network 1.0.0.0
R1(config-router)#network 12.0.0.0
R1(config-router)#network 10.0.0.0
R1(config-router)#network 20.0.0.0
R1(config-router)#network 30.0.0.0
R1(config-router)#no auto-summary

Konfigurasi R2

R2(config)#int f0/0

R2(config-if)#ip add 12.12.12.2 255.255.255.0

R2(config-if)#no shut

R2(config-if)#int f0/1

R2(config-if)#ip add 23.23.23.2 255.255.255.0

R2(config-if)#no shut

R2(config-if)#int lo0

R2(config-if)#ip add 2.2.2.2 255.255.255.255

R2(config-if)#router rip

R2(config-router)#version 2

R2(config-router)#network 12.0.0.0

R2(config-router)#network 2.0.0.0

R2(config-router)#network 23.0.0.0

R2(config-router)#no auto-summary

Konfigurasi R3

R3(config)#interface f0/0

R3(config-if)#ip add 23.23.23.3 255.255.255.0

R3(config-if)#no shut

R3(config-if)#int lo

R3(config-if)#ip add 3.3.3.3 255.255.255.255

R3(config-if)#router rip

R3(config-router)#version 2

R3(config-router)#network 23.0.0.0

R3(config-router)#network 3.0.0.0

R3(config-router)#no auto-summary

sekarang kita coba lihat routing tabel pada R3

R3(config-router)#do sh ip route

Gateway of last resort is not set

1.0.0.0/32 is subnetted, 1 subnets

R 1.1.1.1 [120/2] via 23.23.23.2, 00:00:10, FastEthernet0/0

2.0.0.0/32 is subnetted, 1 subnets

R 2.2.2.2 [120/1] via 23.23.23.2, 00:00:10, FastEthernet0/0

3.0.0.0/32 is subnetted, 1 subnets

C 3.3.3.3 is directly connected, Loopback0

20.0.0.0/32 is subnetted, 3 subnets

R 20.0.1.1 [120/2] via 23.23.23.2, 00:00:10, FastEthernet0/0

R 20.0.0.1 [120/2] via 23.23.23.2, 00:00:10, FastEthernet0/0

R 20.0.2.1 [120/2] via 23.23.23.2, 00:00:10, FastEthernet0/0

23.0.0.0/24 is subnetted, 1 subnets

C 23.23.23.0 is directly connected, FastEthernet0/0

10.0.0.0/32 is subnetted, 10 subnets

R 10.0.10.1 [120/2] via 23.23.23.2, 00:00:12, FastEthernet0/0

R 10.0.9.1 [120/2] via 23.23.23.2, 00:00:13, FastEthernet0/0

R 10.0.8.1 [120/2] via 23.23.23.2, 00:00:13, FastEthernet0/0

R 10.0.2.1 [120/2] via 23.23.23.2, 00:00:13, FastEthernet0/0

R 10.0.1.1 [120/2] via 23.23.23.2, 00:00:13, FastEthernet0/0

R 10.0.0.1 [120/2] via 23.23.23.2, 00:00:13, FastEthernet0/0

R 10.0.7.1 [120/2] via 23.23.23.2, 00:00:13, FastEthernet0/0

R 10.0.6.1 [120/2] via 23.23.23.2, 00:00:13, FastEthernet0/0

R 10.0.5.1 [120/2] via 23.23.23.2, 00:00:13, FastEthernet0/0

R 10.0.4.1 [120/2] via 23.23.23.2, 00:00:13, FastEthernet0/0

12.0.0.0/24 is subnetted, 1 subnets

R 12.12.12.0 [120/1] via 23.23.23.2, 00:00:13, FastEthernet0/0

30.0.0.0/32 is subnetted, 3 subnets

R 30.0.2.1 [120/2] via 23.23.23.2, 00:00:13, FastEthernet0/0

R 30.0.1.1 [120/2] via 23.23.23.2, 00:00:13, FastEthernet0/0

R 30.0.0.1 [120/2] via 23.23.23.2, 00:00:13, FastEthernet0/0

Terlihat banyak sekali network yang ada, sekarang kita coba ringkas untuk meringankan kerja router

Konfigurasi pada R1

R1(config)#int f0/0

R1(config-if)#ip summary-address rip 10.0.0.0 255.0.0.0

R1(config-if)#ip summary-address rip 20.0.0.0 255.0.0.0

R1(config-if)#ip summary-address rip 30.0.0.0 255.0.0.0

sekarang coba cek lagi routing tabel pada R3

R3#clear ip route *

R3#show ip route

Gateway of last resort is not set

1.0.0.0/32 is subnetted, 1 subnets

R 1.1.1.1 [120/2] via 23.23.23.2, 00:00:03, FastEthernet0/0

2.0.0.0/32 is subnetted, 1 subnets

R 2.2.2.2 [120/1] via 23.23.23.2, 00:00:03, FastEthernet0/0

3.0.0.0/32 is subnetted, 1 subnets

C 3.3.3.3 is directly connected, Loopback0

R 20.0.0.0/8 [120/2] via 23.23.23.2, 00:00:03, FastEthernet0/0

23.0.0.0/24 is subnetted, 1 subnets

C 23.23.23.0 is directly connected, FastEthernet0/0

R 10.0.0.0/8 [120/2] via 23.23.23.2, 00:00:03, FastEthernet0/0

12.0.0.0/24 is subnetted, 1 subnets

R 12.12.12.0 [120/1] via 23.23.23.2, 00:00:03, FastEthernet0/0

R 30.0.0.0/8 [120/2] via 23.23.23.2, 00:00:03, FastEthernet0/0

Read more