Securing the local segment is both one of the toughest parts of networking to get right and also one of the most vulnerable portions of the network. Get it wrong and all of your users’ traffic could be sniffed by a malicious device. IPv6 client address configuration moves away from how DHCPv4 works but still carries the same vulnerabilities as before.

Before we go further, you must understand how the IPv6 autoconfiguration process works. An IPv6 clients can initiate the process in one of two ways, either by receiving a periodic ICMP Neighbor Discover Router Advertisement packet or by sending out an ICMP Neighbor Discover Router Solicitation packet which will be responded to by the aforementioned ICMP ND RA packet. This router advertisement packet will contain a couple of things but the two key pieces of information that we're worried about are the Source Address and Prefix Information. A misconfigured device could advertise its own link-local address as the source address to perform a man-in-the-middle attack, or incorrect prefix information to perform a denial-of-service attack. This attack is effective against networks running SLAAC and DHCPv6 because both rely on the ICMP ND RA packet to advertise the default gateway for a particular LAN segment.

To combat this vulnerability, Cisco has implemented a feature called RA Guard. To put it simply, RA Guard is configured on switches to block router advertisements from untrusted ports. This is used similarly to DHCP Snooping in IPv4 deployments. The process of implementing RA Guard it to create a policy and then apply it inbound on an interface.

To deploy RA Guard, you need to first create an RA Guard policy globally where you set the device type.

Next step in deployment is to attach this policy to an uplink interface.

On access-ports, we'll create a host RA Guard policy and attach it to the interfaces via the interface range command.

Use the "Show ipv6 nd ragaurd policy" command to verify that the policies are applied correctly.

And of course, if you have any other questions regarding the specifics of this feature, refer to Cisco’s documentation on RA Guard