Juniper firewalls support a concept called virtual routers. Each VR is its own independent router, with its own routing table and configuration.

By default, the Juniper firewalls come predefined with a Trust-VR and an Untrust-VR, which, though you can edit their properties, you cannot delete.

You can create a custom VR which can have the same capabilities as a predefined one. This is often useful to help segment your internal routing domain so routes are not leaked to other routers.

In addition to destination-based routing, Juniper firewalls support source-based routing, source interface based routing, and multicast.

Static routes allow you to manually define routes within a VR.

You may redistribute static routes into other routing protocols, but not vice versa.

RIP is a distance vector routing protocol which shares routing information between its neighbors to help build the network topology table.

There are currently two IPv4 RIP versions: Version 1 and Version 2. The main difference between v1 and v2 is that v2 supports subnet masks and authentication.

RIP uses a metric called hops to determine the cost of a route. A hop is viewed as a router which the traffic must pass through. If there are three routers that the traffic must pass through, then you would have a route cost of three hops. The maximum number of hops RIP will support is 15.

RIP is susceptible to routing loops, and uses mechanisms such as count to infinity, split horizon,...