RIPv2

RIPv2 is modelled as a deterministic distance-vector routing protocol for IPv4 training scenarios. It is intentionally small and transparent: the important outcome is which hop-count routes appear in the RIB.

Support level

Area	Level	Notes
RIPv2 route solving	Behaviour model	Computes routes across configured RIP domains.
Hop-count metric	Supported	Lower hop count wins; infinity is treated as unreachable.
Network statements	Supported	Cisco-style network selection.
Passive interfaces	Supported	Suppresses updates on selected interfaces.
Packet timing	Partial	Timers are deterministic simulation events, not wall-clock protocol noise.

Standards coverage

Standard	Coverage	Notes
RFC 2453	Behaviour model	RIPv2 hop-count routing and route advertisement concepts.

Feature matrix

Feature	Status	Notes
router rip	Supported	Enables RIP process.
version 2	Supported	RIPv2 config surface.
network <network>	Supported	Interface participation.
passive-interface	Supported	Stops sending updates from the interface.
no auto-summary	Config model	Accepted for config fidelity.
Route installation	Supported	RIP routes enter the IPv4 RIB with protocol distance.

Vendor command matrix

Command	IOS-style	Junos-style	VyOS-style	Notes
router rip	Supported	n/a	Partial	Canonical RIP process.
version 2	Supported	n/a	Partial	RIPv2 mode.
network 10.0.0.0	Supported	n/a	Supported	Interface selection.
show ip route rip	Supported	Partial	Partial	RIP-learned routes.

Behaviour notes

The model avoids probabilistic update races. Given the same topology, the same RIP routes and hop counts appear every run.

Examples

Canonical example

configure terminal
router rip
 version 2
 no auto-summary
 network 10.0.0.0
end
show ip route rip

Vendor styles

IOS-style

router rip
 version 2
 no auto-summary
 network 10.0.0.0

Junos-style

set protocols rip group CORE neighbor ge-0/0/0.0
set protocols rip group CORE export CONNECTED

VyOS-style

set protocols rip network 10.0.0.0/8
set protocols rip interface eth0

Known limits

Triggered update races, authentication, route poisoning packet fidelity, and per-vendor timer quirks are not modelled in depth.