Lab 9-3: RIPv2 via GateD
All UNIX gateways are running GateD now to demonstrate its RIP capabilities. The GateD Interactive Interface (GII), as shown in Example 9-9, provides the RIP information on callisto.
Example 9-9. GateD RIPv2 Configuration and Output on Callisto
[root@callisto:~#] cat /etc/gated.cfg rip on{ interface eth0 eth1 ripin ripout version 2 multicast; }; [root@callisto:~#] telnet localhost 616 Trying 127.0.0.1... Connected to localhost (127.0.0.1). Escape character is '^]'. Password? 100 Gated Interactive Interface. Version gated-public-3_6 GateD-callisto> show interface 100 #ind name address mtu flags 100 #1 lo 127.0.0.1 16436/16372 Up Loopback 100 #2 eth0 192.168.14.1 1500/1436 Up Broadcast Multicast 100 #3 eth1 192.168.1.1 1500/1436 Up Broadcast Multicast 100 #3 eth1 192.168.45.253 1500/1436 Up Broadcast Multicast GateD-callisto> show timer 100 Name Task Last Next Intrvl Jitter flags 100 AGE IF 00:00s 00:57s 00:00s 00:00s <OneShot> 100 Flash RIP 00:01s 00:00s 00:00s 00:00s <Inactive> 100 Update RIP 00:03s 00:27s 00:30s 00:00s <> 100 Age RIP 00:00s 00:35s 00:00s 00:00s <OneShot> 100 IfCheck KRT 00:08s 00:07s 00:15s 00:00s <> 100 Timeout KRT 00:00s 00:00s 00:00s 00:00s <OneShot Inactive> 100 Age Redirect 00:00s 00:52s 00:00s 00:00s <OneShot> 100 Startup SMUX 01:00s 00:00s 01:00s 00:00s <> GateD-callisto> show rip summary 100 Gateway LastHeard Flags 100 192.168.14.1 0 100 192.168.1.1 0 100 192.168.45.253 0 100 192.168.1.254 1334 A 100 192.168.45.254 909 A 100 192.168.14.254 1339 A 100 RIP summary, 6 gateways. 100 Flags: 100 S This is a source gateway 100 T This is a trusted gateway 100 A We have accepted a packet from this gateway 100 R We have rejected a packet from this gateway 100 Q We have received a RIP query packet from this gateway 100 F This gateway failed authentication GateD-callisto> show rip routes 0/0 100 Proto Route/Mask NextHop Tag 100 RIP 0.0.0.0/0 192.168.14.254 0 100 RIP 192.168.2/24 192.168.1.254 0 100 RIP 192.168.7/24 192.168.14.254 0 100 RIP 192.168.13/29 192.168.14.254 0 100 RIP 192.168.17/29 192.168.14.254 0 100 RIP 192.168.44.1/32 192.168.1.254 0 100 RIP 192.168.80/24 192.168.1.254 0 100 RIP 192.168.201.2/32 192.168.14.254 0 100 RIP 111.11.117/24 192.168.1.254 0 GateD-callisto> show ip walkdown 0/0 100 RIP 0.0.0.0/0 192.168.14.254 IGP (Id 1) 100 Sta 127/8 127.0.0.1 IGP (Id 1) 100 Dir 127.0.0.1/32 127.0.0.1 IGP (Id 1) 100 Dir 192.168.1/24 192.168.1.1 IGP (Id 1) 100 RIP 192.168.2/24 192.168.1.254 IGP (Id 1) 100 RIP 192.168.7/24 192.168.14.254 IGP (Id 1) 100 RIP 192.168.13/29 192.168.14.254 IGP (Id 1) 100 Dir 192.168.14/24 192.168.14.1 IGP (Id 1) 100 RIP 192.168.17/29 192.168.14.254 IGP (Id 1) 100 RIP 192.168.44.1/32 192.168.1.254 IGP (Id 1) 100 Dir 192.168.45/24 192.168.45.253 IGP (Id 1) 100 RIP 192.168.80/24 192.168.1.254 IGP (Id 1) 100 RIP 192.168.201.2/32 192.168.14.254 IGP (Id 1) 100 RIP 111.11.117/24 192.168.1.254 IGP (Id 1) GateD-callisto> show ip route 192.168.7.0/24 100 Route 192.168.7 - 255.255.255 entries 1 Announced 1 Depth 0 <> 100 Proto Next Hop Source Gwt Preference/2 Metric/2 100 * RIP 192.168.14.254 192.168.14.254 100/0 2/0
Exercise 9-1: RIPv2 over Frame Relay Topologies
If you are blessed with a WAN network interface card (NIC) that supports Frame Relay, try to configure RIPv2 for a Frame Relay WAN network using the neighbor feature discussed in Lab 9-2.
Exercise 9-2: RIPv2 Metric Manipulation and Redistribution Control
Use the offset-list command in the RIP router section to manipulate the metric for incoming/outgoing updates. In addition, use the distribute-list command in combination with the default-metric command to add granularity to the redistribution of routing updates, and default-information originate to inject default routes. Remember that the passive-interface command results in the respective interface not sending any updates except to RIP neighbors specified with the neighbor command. This does not affect the processing of received updates.
