Home / Network / Routing / Is It Sufficient RIP Split-Horizon Rule To Prevent Routing Loops?

Is It Sufficient RIP Split-Horizon Rule To Prevent Routing Loops?

RIP will loop indefinately…

As conclusion

To achieve this loop we’ve deactivated the split horizon rule, changed the update next hop so that R2 accept it, and the admin distance of the static route. In another condition, in a more complex network there would be no need to change the next hop of admin distance because routes are also learnt dynamically (not static or connected). The idea was to show that split horizon rule is working using CLI commands (show and debug) and on-wire packets capture.

Pages: 1 2 3 4

Tagged:

Leave a Reply

802.11 (4) application (2) architecture (4) asm (4) automatisation (2) cagd (3) chd (2) checkpoint (2) cisco (6) command (5) cost (6) coverage (5) debug (10) distance (6) dtls (2) dynamic rrm (5) firewall (2) fortinet (2) gns3 (2) ieee (4) igmp (5) igp (8) interference (2) internet (3) ip (2) logique (2) loop (5) mac (3) machine learning (3) model (2) mpls (3) mroute (4) multicast (5) nat (2) ndp (2) network (3) next-hop (5) nurbs (3) osi (6) pat (2) pim (4) poisoning (6) policy (2) projet (2) qos (2) radio (5) rib (5) rip (5) route (6) router (6) routing (15) rpf (4) rrm (10) security (3) security gateway (2) show (5) simulation (2) snr (2) solution (2) split-horizon (5) ssl (2) ssm (4) static (6) stp (2) summarization (5) tcp (2) travail (2) udp (2) vpn (3) vrf (3) wifi (11) windows (2) wireshark (2) wlan (7) wlc (5)

October 2025
M T W T F S S
 12345
6789101112
13141516171819
20212223242526
2728293031  
Table of Contents
Copied!