Configuring RIP on SonicWall through Command Line
Description
Routing Information Protocol (RIP) is a distance-vector routing protocol. RIP sends the complete routing table out to all active interfaces every 30 seconds. RIP only uses hop count (the number of routers) to determine the best way to a remote network.
Note: RIP v1 is a classful routing protocol but RIP v2 is a classless routing protocol.
RIP uses broadcast User Datagram Protocol (UDP) data packets to exchange routing information. Routing information updates are sent every 30 seconds, which is termed advertising. If a router does not receive an update from another router for 180 seconds or more, it marks the routes served by the non updating router as being unusable. If there is still no update after 240 seconds, the router removes all routing table entries for the non updating router.
The metric that RIP uses to rate the value of different routes is hop count. The hop count is the number of routers that can be traversed in a route. A directly connected network has a metric of zero; an unreachable network has a metric of 16. This small range of metrics makes RIP an unsuitable routing protocol for large networks.
Resolution
Configuration of RIP on the Sonicwall:
Command line procedure to configure RIP on sonicwall
| SONICWALL Â Â A | SONICWALL Â Â B |
| admin> configure config# routing  config-routing)# rip  config-routing)# router rip version 2 network 172.27.60.0/24 network 192.168.60.0/24  | admin> configure config# routing  config-routing)# rip  config-routing)# router rip version 2 network 172.27.60.0/24 network 192.168.60.0/24  |
VERIFICATION:
>show routing rip
 interface X0
 ip rip send version 2
 ip rip receive version 2
!
interface X1
 ip rip send version 2
 ip rip receive version 2
!
interface X2
!
interface lo0
!
router rip
 network 172.27.60.0/24
 network 192.168.60.0/24
!
end
 RIP ROUTES ON SONICWALL:
| SONICWALL Â Â A | SONICWALL Â Â B |
| config# show routing nsm database ARS NSM>show ip route database Codes: K - kernel, C - connected, S - static, R - RIP, B - BGP       O - OSPF, IA - OSPF inter area       N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2       E1 - OSPF external type 1, E2 - OSPF external type 2       i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, ia - IS-IS inter area       > - selected route, * - FIB route, p - stale info  C   *> 127.0.0.0/8 is directly connected, lo0 C   *> 172.27.60.0/23 is directly connected, X0 C   *> 192.168.60.0/23 is directly connected, X1 R   *> 192.168.60.0/24 [120/2] via 172.27.60.88, X0, 00:31:28 | config# show routing nsm database ARS NSM>show ip route database Codes: K - kernel, C - connected, S - static, R - RIP, B - BGP       O - OSPF, IA - OSPF inter area       N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2       E1 - OSPF external type 1, E2 - OSPF external type 2       i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, ia - IS-IS inter area       > - selected route, * - FIB route, p - stale info  C   *> 127.0.0.0/8 is directly connected, lo0 C   *> 172.27.60.0/23 is directly connected, X0 C   *> 192.168.60.0/23 is directly connected, X1 R   *> 192.168.60.0/24 [120/2] via 172.27.60.81, X0, 00:37:00 |
The rip routes are getting populated on the other sonicwall and the rip routes are advertised to the other Sonicwall.