DHCP is handled by the WLC itself (proxy or no proxy.) So, CPU ACLs need to allow it. ACLs applied to interfaces and WLANs don't need to allow it specifically.
Jason Boyers - CCIE #26024 (Wireless) Technical Instructor - IPexpert [email protected] Office: +1 (810) 326-1444 For *Free* CCIE Training, please visit: http://bit.ly/vLecture For Technical Support, please E-Mail: [email protected] For Live Assistance, please visit: www.ipexpert.com/chat Community: http://www.ipexpert.com/communities eFax: +1 (810) 454-0130 IPexpert is the Global leader in training for the Cisco CCIE lab exam, having helped over 1,600 students earn their CCIE. We are the premier provider of Classroom Training, Self-Study Workbooks, Video on Demand, Audio Tools, and Online Hardware Rental for CCIE Routing & Switching, Voice, Security, Service Provider, and Wireless education with locations throughout the United States, Europe, and Australia. Please visit us at: www.ipexpert.com/communities along with our sister companies: www.proctorlabs.com www.platinumsolutionsgroup.com and www.platinumplacementservices.com On Feb 12, 2011, at 11:28 AM, Ralph Olsen <[email protected]> wrote: > I just did a test with ACL's being assigned to the user on login by > aaa-override and ACS'server. > > I did a test access-list allowing DHCP, ICMP and SSH to default > gateway. The access-list gets pushed ok, but when looking at the > counters it hits me that there are no matches for the DHCP rules. > > Moved the access-list to the interface and still no hits... DHCP works > fine by the way :) > > Is DHCP always allowed in access-lists in the WLC? (I'm not running > 4.2 at the moment.) > > /Ralph > _______________________________________________ > For more information regarding industry leading CCIE Lab training, please > visit www.ipexpert.com _______________________________________________ For more information regarding industry leading CCIE Lab training, please visit www.ipexpert.com
