Revision as of 15:16, 9 April 2019 edit Kvng (talk \| contribs) Extended confirmed users, New page reviewers 116,086 edits promote a sentence to lead. multicast clarifications. combine short related paragraphs. rm unpromising empty section. rm distant See also entry. ← Previous edit		Revision as of 13:05, 10 April 2019 edit undo Arjayay (talk \| contribs) Autopatrolled, Extended confirmed users, Page movers, Pending changes reviewers, Rollbackers 678,607 edits Duplicate word removed Next edit →
Line 7: Multicast RPF, typically denoted simply as RPF, is used in conjunction with a multicast routing protocol such as [[Multicast Source Discovery Protocol\|MSDP]], [[Sparse multicast\|PIM-SM]] and [[Dense multicast\|PIM-DM]] to ensure loop-free forwarding of multicast packets. In multicast routing, the decision to forward traffic is based upon source address and not on destination address as in unicast routing. It does this by utilizing either a dedicated multicast routing table or alternatively the router's unicast routing table. When a multicast packet enters a router's interface, the router looks up the list of networks that are reachable via that interface i.e., it checks ~~the~~ the paths by which the packet could have arrived. If the router finds a matching routing entry for the source IP address of the multicast packet, the RPF check passes and the packet is forwarded to all other interfaces that are participating in that multicast group. If the RPF check fails, the packet is be dropped. As a result, the forwarding of the packet is decided based upon the reverse path of the packet rather than the forward path. By only forwarding packets that come into the interface that also holds the routing entry for the source of the packet, loops are prevented. This is critically important in redundant multicast topologies. Because the same multicast packet could reach the same router via multiple interfaces, RPF checking is integral in the decision to forward packets or not. If the router forwarded all packets that come in interface A to interface B and it also forwarded all packets coming in interface B to interface A and both interfaces receive the same packet, this will create a classic [[routing loop]] where packets will be forwarded in both directions until their IP [[Time to live\|TTL]]s expire. Even considering TTL expiry, all types of routing loops are best avoided as they involve at least temporary network degradation.

Reverse-path forwarding: Difference between revisions