The Unicast RPF feature reduces problems that are caused by the introduction of malformed or forged (spoofed) IPv4 or IPv6 source addresses into a network by discarding IPv4 or IPv6 packets that lack a verifiable IP source address. For example, a number of common types of Denial-of-Service (DoS) attacks, including Smurf and Tribal Flood Network (TFN) attacks, can take advantage of forged or rapidly changing source IPv4 or IPv6 addresses to allow attackers to thwart efforts to locate or filter the attacks. Unicast RPF deflects attacks by forwarding only the packets that have source addresses that are valid and consistent with the IP routing table.

When you enable Unicast RPF on an interface, the switch examines all ingress packets received on that interface to ensure that the source address and source interface appear in the routing table and match the interface on which the packet was received. This examination of source addresses relies on the Forwarding Information Base (FIB).

Note	Unicast RPF is an ingress function and is applied only on the ingress interface of a switch at the upstream end of a connection.

Unicast RPF verifies that any packet received at a switch interface arrives on the best return path (return route) to the source of the packet by doing a reverse lookup in the FIB. If the packet was received from one of the best reverse path routes, the packet is forwarded as normal. If there is no reverse path route on the same interface from which the packet was received, the source address might have been modified by the attacker. If Unicast RPF does not find a reverse path for the packet, the packet is dropped.

Note

With Unicast RPF, all equal-cost “best” return paths are considered valid, which means that Unicast RPF works where multiple return paths exist, if each path is equal to the others in terms of the routing cost (number of hops, weights, and so on) and as long as the route is in the FIB. Unicast RPF also functions where Enhanced Interior Gateway Routing Protocol (EIGRP) variants are being used and unequal candidate paths back to the source IP address exist.

Unicast RPF has the following configuration guidelines and limitations:

• The following platforms support uRPF:

  • Cisco Nexus 3100 platform switches in N3K mode.

  • Cisco Nexus 3132Q-V, 31108PC-V, and 31108TC-V switches.

  • Cisco Nexus 3164Q, 31128PQ, 3232C, and 3264Q switches and Cisco Nexus 3100 platform switches in N9K mode.

• For Cisco Nexus 3164Q switches, Unicast RPF is supported only with the non-hierarchical routing mode.

• You must apply Unicast RPF at the interface downstream from the larger portion of the network, preferably at the edges of your network.

• The further downstream that you apply Unicast RPF, the finer the granularity you have in mitigating address spoofing and in identifying the sources of spoofed addresses. For example, applying Unicast RPF on an aggregation device helps to mitigate attacks from many downstream networks or clients and is simple to administer, but it does not help identify the source of the attack. Applying Unicast RPF at the network access server helps limit the scope of the attack and trace the source of the attack; however, deploying Unicast RPF across many sites does add to the administration cost of operating the network.

• The more entities that deploy Unicast RPF across Internet, intranet, and extranet resources means that the better the chances of mitigating large-scale network disruptions throughout the Internet community, and the better the chances are of tracing the source of an attack.

• Unicast RPF will not inspect IP packets that are encapsulated in tunnels, such as generic routing encapsulation (GRE) tunnels. You must configure Unicast RPF at a home gateway so that Unicast RPF processes network traffic only after the tunneling and encryption layers have been stripped off the packets.

• You can use Unicast RPF in any “single-homed” environment where there is only one access point out of the network or one upstream connection. Networks that have one access point provide symmetric routing, which means that the interface where a packet enters the network is also the best return path to the source of the IP packet.

• Do not use Unicast RPF on interfaces that are internal to the network. Internal interfaces are likely to have routing asymmetry, which means that multiple routes to the source of a packet exist. You should configure Unicast RPF only where there is natural or configured symmetry. Do not configure strict Unicast RPF.

• Unicast RPF allows packets with 0.0.0.0 source and 255.255.255.255 destination to pass so that the Bootstrap Protocol (BOOTP) and the Dynamic Host Configuration Protocol (DHCP) can operate correctly.

• If the route to the source IP is Equal Cost Multi Path route with more than 8 members, the Unicast RPF check performed on the ingress interface cannot be of the strict mode and by default, will be of loose mode.

Note	If you are familiar with the Cisco IOS CLI, be aware that the Cisco NX-OS commands for this feature might differ from the Cisco IOS commands that you would use.

This table lists the default settings for Unicast RPF parameters.

The following example shows how to configure loose Unicast RPF for IPv4 packets:

interface Ethernet2/3
ip address 172.23.231.240/23
ip verify unicast source reachable-via any allow-default

The following example shows how to configure loose Unicast RPF for IPv6 packets:

interface Ethernet2/3
ipv6 address 2001:0DB8:c18:1::3/64
ipv6 verify unicast source reachable-via any allow-default

The following example shows how to configure strict Unicast RPF for IPv4 packets:

interface Ethernet2/2
ip address 172.23.231.240/23
ip verify unicast source reachable-via rx

The following example shows how to configure strict Unicast RPF for IPv6 packets:

interface Ethernet2/2
ipv6 address 2001:0DB8:c18:1::3/64
ipv6 verify unicast source reachable-via rx

To display Unicast RPF configuration information, perform one of the following tasks: