I have a client that is running IPV4 on their network and not IPV6, but of course IPV6 is enabled on all the windows boxes. They had an issue today where they had tons of IPV6 router advertisements flooding through their VPLS cloud all sourced from a MAC address that could not be located on their network. I did a packet capture and saw that all IPV6 router advertises to the multicast address were from the same source MAC. From reading various articles this appears to be an IPV6 Router Advertisement Spoofing/Flooding. I have seen ways of mitigating the attack via windows but is there a way to do this on Cisco via a central point. Seeing the client is not using IPV6, I guess I could use an IPV6 access list to deny all IPV6 traffic and apply it to all 40 VPLS routers. Anyone come across this and have a better way of mitigating this? Thanks in advance, Mike ... View more

I have two remote sites connected to the main office via Site-to-Site VPNs. The tunnels are up and working fine. The only thing I can not figure out is how to send traffic generated by the ASA through the tunnel. For instance I am trying to get the ASA's at the remote sites to send syslog and SNMP to the servers at the main office, but I have had no luck. I assume it is a routing issue but I can't seem to find the answer. Sylog and snmp traffic generated by devices on the LAN pass through the tunnel to the main office but not traffic generated on the ASA. When I debug the ASA I can see that when it is attempting to send traffic (SYSlog,SNMP) generated by the ASA routing fails. Routing failed to locate next hop for udp from NP Identity Ifc:192.168.20.1/514 to inside:172.20.5.55/514 192.168.20.1 is the inside interface of the ASA. How to I get traffic that starts on the ASA to route through the VPN tunnel? ... View more