Is it sufficient split-horizon rule to prevent RIP loops?
Per the split-horizon rule, don’t send an update back on the interface it was received on What is the challenge here? In addition to bandwidth usage and system resources consumption, […]
July 15, 2019 RIP: do not split it then… and unleach the power of the “network” command
In RIP domain routers R1 and R2 exchange information about loopback 0 and 1 networks Router RIP command “network 0.0.0.0” hints routers to add all ip enabled interfaces to the […]
July 15, 2019 Static routing metric
Both R1 and R3 advertise 13.13.13.13/32 network into RIP domain R3 is configured to offset all network updates via interface fa1/0 by 10
July 11, 2019 Adertised RIP learnt routes
In the topology Router R3 receives 1.1.1.1/32 route information from R2
July 8, 2019 RIP maximum equal cost paths feature
In this lab, we check how maximum equal paths feature works in RIP In this lab R2 advertises 2.2.2.2/32 subnetwork to R1 via RIP. R1 processed three equal paths through […]
July 8, 2019 
Understand RIP Routing Timers All in One Shot!
Cisco’s RIP implementation defines 4 times tight to one periodic update interval and 3 states: invalid, hold-down and flush. The misleading information is that they are referred to as “timers” […]
March 9, 2017