Content deleted Content added
Reverted 1 edit by 223.229.169.35 (talk): Blog spam |
review complete: rm broken and commercial |
||
Line 41:
RPF is often interpreted as reverse-path ''filtering'', particularly when it comes to unicast routing. This is an understandable alternate interpretation of the acronym in that when RPF is used with unicast routing as in RFC 3704, traffic is either permitted or denied based upon the RPF check passing or failing. The thought being that traffic is denied if it fails the RPF check and is therefore filtered. While uRPF is used as an ingress ''filtering'' mechanism, it is affected by reverse-path ''forwarding''.
Reverse path filters are typically used to disable asymmetric routing where an IP application has a different incoming and outgoing routing path. Its intent is to prevent a packet entering one interface from leaving via the other interfaces. Reverse-path Filtering is a feature of the [[Linux Kernel]].<ref name="professional Linux-1">{{citation |url=https://www.theurbanpenguin.com/rp_filter-and-lpic-3-linux-security/ |title=rp_filter and LPIC-3 Linux Security |access-date=2020-12-30}}</ref
== See also ==
Line 53:
== External links ==
* {{cite IETF |RFC=2827 |title=Network Ingress Filtering: Defeating Denial of Service Attacks which employ IP Source Address Spoofing}}
* {{cite IETF |RFC=3704 |title=Ingress Filtering for Multihomed Networks}}
* [http://www.cisco.com/web/about/security/intelligence/unicast-rpf.html Cisco - Understanding uRPF]
* [https://web.archive.org/web/20120110091436/http://blog.ipexpert.com/2010/12/13/multicast-reverse-path-forwarding-rpf/ Multicast Reverse Forwarding (RPF)]
| |||