Hi Jason/Group,
I am searching for some clarification with regards to some of the elements of the CPU ACL in the for mentioned task. * I understand that as the controller relays DHCP traffic, that that DHCP requests need to be allowed in but what is the reason for the DNS entry. I am trying to see why this would be required as I can only see a reason for a client to do a DNS query, is there a reason for the WLC to do a DNS query? Is this something to do with Web Auth and intercepting the DNS request? (probably just answered my own question J) * There are different directions defined (some inbound only and some any), as the CPU ACL only works inbound to the CPU, what is the reason for this? (if any) * Does the ACL have an effect on LWAPP control traffic. ( as according to this guide it does not)http://www.cisco.com/en/US/products/ps6366/products_tech_note09186a0 080a7c988.shtml#console) * Finally, please could you expand on why there is a statement for the WLC allowing all traffic to itself, and is this always required?? Many Thanks Phil
_______________________________________________ For more information regarding industry leading CCIE Lab training, please visit www.ipexpert.com
