This post refers to the issue of traffic-filter not working. Please find out below the solution to this issue.
The customer tried to apply it on the scenario below:
vlanif and port :[~SWITCH-A]display current-configuration interface Vlanif 109 interface Vlanif109
ip address XXX.XXX.XXX.XXX 255.255.255.254
traffic-filter acl 3000 inbound
traffic-filter acl 3000 outbound
#
return
[~SWITCH-A]disp
[~SWITCH-A]display acl 3000
Advanced ACL 3000, 2 rules
ACL's step is 5
rule 5 deny udp destination YYY.YYY.YYY destination-port eq dns (0 times matched)
rule 10 deny icmp destination XXXX.XXXX.XXXX 0 (0 times matched)
The IP from interface vlanif109 and ACL 3000 is the same, noted with XXX...
Solution
If the match IP is the device host IP, the traffic-filter will not take effect because the packets arrived will be sent straight to the CPU.
This will not work because the IP that the customer is trying to deny by ACL is exactly the host IP and therefore the traffic-filter will not take effect.
It doesn’t really matter from where the customer is pinging, the important fact is that if the match IP is the source or dest IP of the ping - the traffic-filter will not take effect.
An alternative for what you need would be the auto-defend protocol.
