01-28-2016 06:29 PM - edited 03-12-2019 12:12 AM
what is the best practice for implementing the anti spoofing in inside or outside? what would be cause if we implemented?
01-28-2016 06:52 PM
You may check the link from the post
https://supportforums.cisco.com/discussion/10436756/asa-spoofing
http://www.cisco.com/c/en/us/support/docs/ip/access-lists/13608-21.html#anc104
--For ACL's they have to be applied from outside to inside denying RFC1918.
--IP Source guard, DAI and other features need to be applied on the inside.
--For uRPF and ACL logging (ACL log keyword), they require special CPU processing and are process switched by the CPU.
HTH
Syed
01-28-2016 06:55 PM
Can you give us a hint what kind of device you have?
01-28-2016 07:56 PM
ASA 5500 Firewall
01-28-2016 08:02 PM
I usually enable it on all interfaces with:
ip verify reverse-path interface <interface>
02-08-2016 07:02 PM
what would be the impact in our network infrastracture if we run this command?
ip verify reverse-path interface <interface>
02-08-2016 07:05 PM
It will drop traffic coming in from that interface that does not have an IP address coming from that subnet, or that would be routed via that subnet.
02-08-2016 07:22 PM
is there any effect in resources like memory and cpu utilization?. is their any documents?
02-08-2016 07:29 PM
The impact is pretty much unmeasurable. I always use it.
Here is the manual entry for it:
02-08-2016 07:38 PM
Hi John,
Enabling this feature should not cause any cpu/memory usage hike. However, per Cisco doc, it may drop legitimate traffic.I never noticed any -ve impact thoughssues though. Check the below link...
http://www.cisco.com/c/en/us/about/security-center/unicast-reverse-path-forwarding.html
hth
MS
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide