A network administrator configures a Cisco IOS router to restrict access to a financial database server () from the HR subnet (). All other traffic between subnets must be permitted. The administrator applies the following access list in the inbound direction on interface GigabitEthernet0/0:
text
ip access-list extended FILTER_HR
deny ip 192.168.10.0 0.0.0.255 host 192.168.50.100
After applying this ACL, users report that all traffic targeting any server in the network is being dropped, including traffic from non-HR subnets. Which configuration change will resolve the issue and permit intended traffic?
- Append the statement `permit ip any any` to the end of the `FILTER_HR` access list.Cevap
- BModify the deny statement to use a wildcard mask of `0.0.255.255` instead of `0.0.0.255`.
- CRe-apply the ACL to interface GigabitEthernet0/0 in the outbound direction using `ip access-group FILTER_HR out`.
- DChange the protocol from `ip` to `tcp` and append `eq 80` to restrict only Web traffic.
Cevap
Appending the statement `permit ip any any` to the end of the `FILTER_HR` access list resolves the issue by explicitly permitting all traffic that does not match the deny rule.
Every IPv4 ACL in Cisco IOS ends with an invisible, mandatory `deny ip any any` statement. When an ACL contains only `deny` statements, any packet that does not match those deny statements reaches the bottom of the list and is dropped. Appending `permit ip any any` allows all other IP traffic to pass through as intended.
Adım Adım Çözüm
Anahtar Kavram
Access Control List Sequential Processing and the Implicit Deny Any Clause