Belajar Konfigurasi Route Tables dan Implementasinya
Tabel routing adalah jantung dari routing di jaringan komputer. Artikel ini akan membahas secara mendalam tentang konfigurasi route tables, berbagai jenis rute, dan implementasinya dalam skenario nyata menggunakan MikroTik.
Apa Itu Routing Table?
Routing Table adalah database yang disimpan di router yang berisi informasi tentang jaringan yang dapat dijangkau dan bagaimana mencapainya. Setiap entry dalam routing table disebut route.
Analogi Sederhana:
Routing table seperti peta jalan untuk router:
- Destinasi: Alamat tujuan yang ingin dicapai
- Gateway/Next Hop: "Persimpangan" berikutnya
- Interface: "Jalan" yang harus diambil
- Metric: "Jarak" atau "biaya" rute
- Administrative Distance: "Kepercayaan" pada sumber rute
Struktur Routing Table
Format Entry Routing Table:
DESTINATION | GATEWAY | INTERFACE | DISTANCE | METRIC 192.168.1.0/24 192.168.88.1 ether2 1 0 10.0.0.0/8 10.0.0.1 ether1 1 10 0.0.0.0/0 203.0.113.1 ether1 1 1 Keterangan: • Destination: Network tujuan • Gateway: Alamat router berikutnya • Interface: Port keluar di router lokal • Distance: Administrative Distance • Metric: Cost rute (semakin kecil semakin baik)
Routing Table di MikroTik:
[admin@MikroTik] > ip route print Flags: X - disabled, A - active, D - dynamic, C - connect, S - static, r - rip, b - bgp, o - ospf, m - mme, B - blackhole, U - unreachable, P - prohibit DST-ADDRESS PREF-SRC GATEWAY DISTANCE ADC 192.168.88.0/24 192.168.88.1 bridge-local 0 A S 0.0.0.0/0 10.0.0.1 1 A S 10.10.10.0/24 10.0.0.2 1 ADo 192.168.1.0/24 10.0.0.3 110 # Flags penting: A - Active (rute aktif digunakan) D - Dynamic (dipelajari dari protokol routing) C - Connected (network langsung terhubung) S - Static (konfigurasi manual) o - OSPF (dipelajari dari OSPF)
Jenis-Jenis Route
| Jenis Route | Deskripsi | Cara Pembentukan | Contoh |
|---|---|---|---|
| Connected Route | Network yang langsung terhubung ke interface router | Otomatis ketika IP address di-set | 192.168.1.0/24 di interface ether2 |
| Static Route | Route yang dikonfigurasi manual oleh administrator | Konfigurasi manual via CLI/GUI | Route ke network cabang |
| Default Route | Route untuk semua traffic yang tidak ada rute spesifiknya | Static route ke 0.0.0.0/0 | Route ke internet |
| Dynamic Route | Route yang dipelajari dari protokol routing | OSPF, RIP, BGP | Route antar kantor cabang |
| Host Route | Route ke host spesifik (/32) | Static atau dynamic | Route ke server tertentu |
| Null Route | Route yang membuang paket (blackhole) | Konfigurasi manual | Block malicious traffic |
Administrative Distance dan Metric
Administrative Distance (AD)
Administrative Distance adalah nilai yang menentukan kepercayaan terhadap sumber route. Semakin rendah AD, semakin dipercaya route tersebut. Jika ada multiple routes ke network yang sama, route dengan AD terendah yang akan dipilih.
| Sumber Route | Default AD (MikroTik) | Default AD (Cisco) | Keterangan |
|---|---|---|---|
| Connected | 0 | 0 | Paling dipercaya |
| Static Route | 1 | 1 | Manual configuration |
| EBGP | 20 | 20 | External BGP |
| OSPF | 110 | 110 | Link state protocol |
| RIP | 120 | 120 | Distance vector |
| IBGP | 200 | 200 | Internal BGP |
| Unreachable | 255 | 255 | Tidak digunakan |
Routing Metric
Metric adalah nilai yang digunakan untuk membandingkan rute dari sumber yang sama (AD sama). Semakin rendah metric, semakin baik rute tersebut. Metric dihitung berbeda untuk setiap protokol routing.
# Contoh: Multiple static routes dengan metric berbeda [admin@MikroTik] > ip route add dst-address=192.168.2.0/24 gateway=10.0.0.2 distance=1 scope=30 target-scope=10 [admin@MikroTik] > ip route add dst-address=192.168.2.0/24 gateway=10.0.0.3 distance=1 scope=40 target-scope=10 # Router akan memilih route dengan scope terendah (30) sebagai primary # Route dengan scope 40 akan menjadi backup # Cek route status [admin@MikroTik] > ip route print where dst-address=192.168.2.0/24
Konfigurasi Static Route di MikroTik
1. Basic Static Route
Via Winbox/Webfig:
- Buka menu IP → Routes
- Klik tab Routes
- Klik + (Add New)
- Isi:
- Dst. Address: 192.168.2.0/24
- Gateway: 10.0.0.2
- Distance: 1
- Scope: 30
- Target Scope: 10
- Comment: Route to Branch Office
- Apply → OK
Via CLI:
# Basic static route [admin@MikroTik] > ip route add dst-address=192.168.2.0/24 gateway=10.0.0.2 # Static route dengan semua parameter [admin@MikroTik] > ip route add dst-address=192.168.3.0/24 gateway=10.0.0.3 distance=1 scope=30 target-scope=10 check-gateway=ping routing-mark=main comment="Route to Data Center" # Default route (ke internet) [admin@MikroTik] > ip route add dst-address=0.0.0.0/0 gateway=203.0.113.1 check-gateway=ping # Route melalui interface (tanpa gateway) [admin@MikroTik] > ip route add dst-address=192.168.4.0/24 gateway=pppoe-out1
2. Static Route dengan Backup/Redundancy
# Primary route dengan distance 1 [admin@MikroTik] > ip route add dst-address=192.168.5.0/24 gateway=10.0.0.5 distance=1 check-gateway=ping # Backup route dengan distance 2 [admin@MikroTik] > ip route add dst-address=192.168.5.0/24 gateway=10.0.0.6 distance=2 check-gateway=ping # ECMP (Equal Cost Multi-Path) Load Balancing [admin@MikroTik] > ip route add dst-address=192.168.6.0/24 gateway=10.0.0.7,10.0.0.8 # Cek route status [admin@MikroTik] > ip route print where dst-address=192.168.5.0/24 [admin@MikroTik] > ip route print status
3. Special Route Types
# Blackhole Route (membuang paket) [admin@MikroTik] > ip route add dst-address=10.10.10.0/24 type=blackhole comment="Block malicious network" # Unreachable Route (mengembalikan ICMP unreachable) [admin@MikroTik] > ip route add dst-address=10.20.20.0/24 type=unreachable comment="Network not accessible" # Prohibit Route (mengembalikan ICMP prohibited) [admin@MikroTik] > ip route add dst-address=10.30.30.0/24 type=prohibit comment="Administratively prohibited" # Host Route (/32 route) [admin@MikroTik] > ip route add dst-address=192.168.1.100/32 gateway=10.0.0.10 comment="Route to specific server"
Dynamic Routing Tables
1. OSPF Routes
# Konfigurasi OSPF [admin@MikroTik] > routing ospf instance set default router-id=1.1.1.1 redistribute-connected=as-type-2 [admin@MikroTik] > routing ospf area add name=backbone area-id=0.0.0.0 [admin@MikroTik] > routing ospf network add network=192.168.0.0/16 area=backbone # Lihat routes yang dipelajari dari OSPF [admin@MikroTik] > ip route print where dynamic [admin@MikroTik] > routing ospf route print # Detail OSPF route [admin@MikroTik] > routing ospf route print detail
2. BGP Routes
# Konfigurasi BGP [admin@MikroTik] > routing bgp instance set default as=65001 router-id=2.2.2.2 [admin@MikroTik] > routing bgp peer add name=ISP1 remote-address=203.0.113.1 remote-as=64512 [admin@MikroTik] > routing bgp network add network=192.168.0.0/22 # Lihat BGP routes [admin@MikroTik] > routing bgp advertisement print [admin@MikroTik] > ip route print where bgp
Route Filtering dan Manipulation
1. Route Filters
# Filter untuk mencegah route tertentu masuk [admin@MikroTik] > routing filter add chain=bgp-in dst-address=10.0.0.0/8 action=discard comment="Block RFC1918 from BGP" # Filter untuk OSPF [admin@MikroTik] > routing filter add chain=ospf-in dst-address=192.168.100.0/24 action=discard comment="Block specific network" # Filter dengan set action [admin@MikroTik] > routing filter add chain=ospf-out dst-address=192.168.0.0/16 action=accept set-ospf-metric=100 comment="Set metric for OSPF" # Lihat routing filters [admin@MikroTik] > routing filter print
2. Route Redistribution
# Redistribute connected routes ke OSPF [admin@MikroTik] > routing ospf instance set default redistribute-connected=as-type-2 # Redistribute static routes ke OSPF [admin@MikroTik] > routing ospf instance set default redistribute-static=as-type-2 # Redistribute OSPF ke BGP [admin@MikroTik] > routing bgp instance set default redistribute-ospf=yes # Redistribute dengan filter [admin@MikroTik] > routing filter add chain=bgp-out dst-address=0.0.0.0/0 action=discard comment="Don't redistribute default route"
Policy Based Routing (PBR)
Apa Itu Policy Based Routing?
Policy Based Routing (PBR) memungkinkan routing decisions berdasarkan criteria selain destination address, seperti source address, protocol, port, dll. PBR menggunakan routing marks dan routing tables.
Implementasi PBR di MikroTik:
# Step 1: Buat mangle rules untuk mark traffic # Mark traffic dari departemen IT ke routing-mark "route-it" [admin@MikroTik] > ip firewall mangle add chain=prerouting src-address=192.168.10.0/24 action=mark-routing new-routing-mark=route-it passthrough=no comment="IT Department Traffic" # Mark traffic dari departemen Sales ke routing-mark "route-sales" [admin@MikroTik] > ip firewall mangle add chain=prerouting src-address=192.168.20.0/24 action=mark-routing new-routing-mark=route-sales passthrough=no comment="Sales Department Traffic" # Mark HTTP/HTTPS traffic ke routing-mark "route-web" [admin@MikroTik] > ip firewall mangle add chain=prerouting protocol=tcp dst-port=80,443 action=mark-routing new-routing-mark=route-web passthrough=yes comment="Web Traffic" # Step 2: Buat routing tables untuk masing-masing routing mark # Route untuk IT Department (ISP1) [admin@MikroTik] > ip route add dst-address=0.0.0.0/0 gateway=203.0.113.1 routing-mark=route-it comment="IT Department Internet" # Route untuk Sales Department (ISP2) [admin@MikroTik] > ip route add dst-address=0.0.0.0/0 gateway=198.51.100.1 routing-mark=route-sales comment="Sales Department Internet" # Route khusus untuk web traffic (lewat VPN) [admin@MikroTik] > ip route add dst-address=0.0.0.0/0 gateway=10.0.0.100 routing-mark=route-web comment="Web traffic via VPN" # Step 3: NAT untuk masing-masing routing table [admin@MikroTik] > ip firewall nat add chain=srcnat out-interface=ether1 action=masquerade routing-mark=route-it [admin@MikroTik] > ip firewall nat add chain=srcnat out-interface=ether2 action=masquerade routing-mark=route-sales # Step 4: Cek routing marks [admin@MikroTik] > ip firewall mangle print where action=mark-routing [admin@MikroTik] > ip route print where routing-mark!=""
Routing Table Management Tools
1. Route Monitoring Script
/system script add name=monitor-routes source={ :local totalRoutes [/ip route print count-only] :local staticRoutes [/ip route print count-only where static] :local dynamicRoutes [/ip route print count-only where dynamic] :local connectedRoutes [/ip route print count-only where connected] :log info "=== ROUTING TABLE REPORT ===" :log info "Total Routes: $totalRoutes" :log info "Static Routes: $staticRoutes" :log info "Dynamic Routes: $dynamicRoutes" :log info "Connected Routes: $connectedRoutes" # Check for duplicate routes :local duplicates 0 :foreach route in=[/ip route find] do={ :local dstAddr [/ip route get $route dst-address] :local count [/ip route find dst-address=$dstAddr] :if ([:len $count] > 1) do={ :set duplicates ($duplicates + 1) :log warning "Duplicate route for $dstAddr" } } :log info "Duplicate routes found: $duplicates" # Check inactive routes :local inactiveRoutes [/ip route find inactive=yes] :if ([:len $inactiveRoutes] > 0) do={ :log warning "Inactive routes: $[:len $inactiveRoutes]" :foreach inactive in=$inactiveRoutes do={ :local dstAddr [/ip route get $inactive dst-address] :log warning "Inactive: $dstAddr" } } :log info "=== REPORT COMPLETED ===" }
2. Route Backup Script
/system script add name=backup-routes source={ :local date [/system clock get date] :local time [/system clock get time] :local filename "routes-backup-$date-$time.rsc" # Export hanya static routes /export file=$filename compact # Atau export semua routes /ip route export file=routes-export.rsc :log info "Routes backup created: $filename" # Kirim email notification (jika email di-setup) /tool e-mail send to="admin@company.com" subject="Route Table Backup" body="Route table backup completed at $time on $date" } # Schedule regular backup [admin@MikroTik] > /system scheduler add name=daily-route-backup interval=1d on-event="/system script run backup-routes"
Routing Table Optimization
1. Route Summarization
Route Summarization (supernetting) adalah teknik menggabungkan multiple network routes menjadi satu summary route untuk mengurangi ukuran routing table.
# Sebelum summarization (multiple routes) [admin@MikroTik] > ip route add dst-address=192.168.1.0/24 gateway=10.0.0.1 [admin@MikroTik] > ip route add dst-address=192.168.2.0/24 gateway=10.0.0.1 [admin@MikroTik] > ip route add dst-address=192.168.3.0/24 gateway=10.0.0.1 [admin@MikroTik] > ip route add dst-address=192.168.4.0/24 gateway=10.0.0.1 # Setelah summarization (satu summary route) [admin@MikroTik] > ip route add dst-address=192.168.0.0/22 gateway=10.0.0.1 comment="Summary route for 192.168.0-3.0/24" # Contoh: Summarize 10.0.0.0/24 sampai 10.0.3.0/24 [admin@MikroTik] > ip route add dst-address=10.0.0.0/22 gateway=10.0.0.254 comment="Summary: 10.0.0.0-10.0.3.0"
2. Route Aggregation di BGP
# Aggregated route di BGP [admin@MikroTik] > routing bgp instance set default as=65001 router-id=1.1.1.1 [admin@MikroTik] > routing bgp aggregate add prefix=192.168.0.0/22 # Atau advertise aggregate route [admin@MikroTik] > routing bgp network add network=192.168.0.0/22 summary-only=yes
Troubleshooting Routing Tables
| Problem | Symptoms | Diagnosis Commands | Solution |
|---|---|---|---|
| Route Missing | Cannot reach specific network | ip route printip route print detail | Add missing route, check gateway |
| Wrong Route Selected | Traffic takes wrong path | ip route print where dst-address=...traceroute | Adjust distance/scope, fix AD |
| Routing Loop | Traffic circulates, TTL exceeded | tool torchlog print | Check for circular references |
| Route Flapping | Route appears/disappears | log print where message~"route"ip route print status | Check interface stability, gateway |
| High CPU from Routing | Slow performance, high CPU | system resource printtool profile | Optimize routes, use summarization |
Troubleshooting Commands:
# Comprehensive routing troubleshooting [admin@MikroTik] > /ip route print [admin@MikroTik] > /ip route print detail [admin@MikroTik] > /ip route print status [admin@MikroTik] > /ip route print where inactive=yes # Check route for specific destination [admin@MikroTik] > /ip route print where dst-address=192.168.1.0/24 # Test route with traceroute [admin@MikroTik] > /tool traceroute 192.168.2.1 src-address=192.168.1.1 # Check routing protocols status [admin@MikroTik] > /routing ospf neighbor print [admin@MikroTik] > /routing bgp peer print # Monitor route changes [admin@MikroTik] > /log print where topics=route
Implementasi Routing Table dalam Skenario Nyata
Scenario 1: Multi-Office Network
ENTERPRISE NETWORK ROUTING TABLE DESIGN HEADQUARTERS (HQ) IP: 10.0.0.0/24 Gateway: 10.0.0.1/24 BRANCH OFFICE 1 (BR1) IP: 10.0.1.0/24 Gateway: 10.0.1.1/24 BRANCH OFFICE 2 (BR2) IP: 10.0.2.0/24 Gateway: 10.0.2.1/24 DATA CENTER (DC) IP: 10.0.3.0/24 Gateway: 10.0.3.1/24 Routing Table di HQ Router: DESTINATION GATEWAY INTERFACE TYPE 0.0.0.0/0 203.0.113.1 ether1 Static (Internet) 10.0.0.0/24 bridge-local - Connected 10.0.1.0/24 10.0.0.100 vpn-tunnel1 Static (via VPN) 10.0.2.0/24 10.0.0.200 vpn-tunnel2 Static (via VPN) 10.0.3.0/24 10.0.0.50 ether2 Static (Direct) 192.168.0.0/16 10.0.0.1 - OSPF (Internal)
Konfigurasi di MikroTik HQ:
# HQ Router Configuration # Connected routes (automatic) /ip address add address=10.0.0.1/24 interface=bridge-local /ip address add address=10.0.3.50/30 interface=ether2 # Static routes /ip route add dst-address=0.0.0.0/0 gateway=203.0.113.1 check-gateway=ping comment="Internet" /ip route add dst-address=10.0.1.0/24 gateway=10.0.0.100 distance=1 comment="Branch Office 1 via VPN" /ip route add dst-address=10.0.2.0/24 gateway=10.0.0.200 distance=1 comment="Branch Office 2 via VPN" /ip route add dst-address=10.0.3.0/24 gateway=10.0.3.1 distance=1 comment="Data Center" # Backup routes (jika ada multiple paths) /ip route add dst-address=10.0.1.0/24 gateway=10.0.0.101 distance=2 comment="BR1 Backup via ISP2" /ip route add dst-address=10.0.2.0/24 gateway=10.0.0.201 distance=2 comment="BR2 Backup via ISP2" # OSPF untuk internal routing (jika ada banyak internal networks) /routing ospf instance set default router-id=10.0.0.1 /routing ospf area add name=backbone area-id=0.0.0.0 /routing ospf network add network=10.0.0.0/8 area=backbone /routing ospf network add network=192.168.0.0/16 area=backbone
Scenario 2: Internet Service Provider (ISP)
# ISP Edge Router Configuration # Customer routes (static) /ip route add dst-address=203.0.113.0/29 gateway=ether1 comment="Customer A" /ip route add dst-address=198.51.100.0/28 gateway=ether2 comment="Customer B" /ip route add dst-address=192.0.2.0/24 gateway=pppoe-customerC comment="Customer C (PPPoE)" # BGP configuration untuk upstream providers /routing bgp instance set default as=64512 router-id=1.1.1.1 /routing bgp peer add name=upstream1 remote-address=100.64.0.1 remote-as=174 /routing bgp peer add name=upstream2 remote-address=100.64.0.2 remote-as=3356 # Advertise customer routes ke upstream /routing bgp network add network=203.0.113.0/24 /routing bgp network add network=198.51.100.0/24 /routing bgp network add network=192.0.2.0/24 # Route filtering untuk security /routing filter add chain=bgp-in dst-address=10.0.0.0/8 action=discard comment="Block RFC1918" /routing filter add chain=bgp-in dst-address=172.16.0.0/12 action=discard comment="Block RFC1918" /routing filter add chain=bgp-in dst-address=192.168.0.0/16 action=discard comment="Block RFC1918" # Default route dari upstream /ip route add dst-address=0.0.0.0/0 gateway=100.64.0.1 distance=1 comment="Default via Upstream1" /ip route add dst-address=0.0.0.0/0 gateway=100.64.0.2 distance=2 comment="Backup via Upstream2"
Best Practices Routing Table Management
✅ Routing Table Best Practices Checklist
- Document semua static routes dengan comments yang jelas
- Gunakan consistent naming convention untuk routing marks
- Implement route summarization untuk mengurangi table size
- Monitor routing table size dan growth
- Use route filtering untuk security dan stability
- Test failover scenarios secara berkala
- Backup routing configuration sebelum perubahan
- Use administrative distance dengan bijak
- Implement logging untuk routing changes
- Regularly review routing tables untuk optimization
- Use PBR untuk traffic engineering jika diperlukan
- Monitor route flaps dan instability
Advanced Routing Table Features
1. VRF (Virtual Routing and Forwarding)
VRF memungkinkan multiple routing tables dalam satu router, mengisolasi network traffic secara logis.
# VRF Configuration (MikroTik v7+ required) # Buat VRF instances /routing vrf add name=vrf-customerA /routing vrf add name=vrf-customerB # Assign interfaces ke VRF /interface vrf assign interface=ether1 vrf=vrf-customerA /interface vrf assign interface=ether2 vrf=vrf-customerB # Routes dalam masing-masing VRF /ip route vrf=vrf-customerA add dst-address=0.0.0.0/0 gateway=203.0.113.1 /ip route vrf=vrf-customerB add dst-address=0.0.0.0/0 gateway=198.51.100.1 # Cek routes per VRF /ip route print vrf=vrf-customerA /ip route print vrf=vrf-customerB
2. MPLS Layer 3 VPN
# MPLS VPN Route Distinguisher dan Route Target # (Advanced topic - requires MPLS configuration) /routing bgp vpn add name=vpn-customer1 rd=64512:100 import-route-targets=64512:100 export-route-targets=64512:100 /ip route vrf=vpn-customer1 add dst-address=10.0.0.0/24 gateway=10.0.0.1
Kesimpulan
Routing table adalah komponen fundamental dalam jaringan yang menentukan bagaimana traffic mengalir. Penguasaan routing table meliputi:
- Memahami berbagai jenis route (connected, static, dynamic)
- Menguasai administrative distance dan metric
- Mengimplementasikan route filtering dan manipulation
- Menggunakan policy based routing untuk traffic engineering
- Memonitor dan troubleshooting routing issues
- Mengoptimalkan routing tables dengan summarization
Key Takeaways:
- Routing table yang efisien = jaringan yang efisien
- Documentation dan comments sangat penting
- Regular monitoring prevents routing issues
- Security through route filtering dan validation
- Scalability through route summarization
Learning Path untuk Routing Table Mastery:
- Phase 1 (Basic): Static routes, default route, connected routes
- Phase 2 (Intermediate): Route filtering, PBR, backup routes
- Phase 3 (Advanced): Dynamic routing (OSPF, BGP), route redistribution
- Phase 4 (Expert): VRF, MPLS VPN, large-scale optimization
- Phase 5 (Master): Automation, monitoring, troubleshooting complex scenarios
🗺️ Routing Tables: Peta Jaringan Anda!
Kuasi routing tables, dan Anda kuasi aliran informasi dalam jaringan.
