We use it globally for our Cisco LWAPPs, but not per scope. The ISC server is a bit ticky about using class declarations. I worried with it (not pertaining to LWAPPS) several years ago. The manner of declaring and using them is not intuitive.
Could you show us relevant areas of your dhcpd.conf (obfuscated if necessary)? Might bring back an unfond memory of the struggle. -----Original Message----- From: The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:[email protected]] On Behalf Of Ken Connell Sent: Thursday, June 02, 2011 7:42 AM To: [email protected] Subject: [WIRELESS-LAN] option 43 for finding master controller Is any one using this on a per-scope basis with an ISC DHCP server ? We're an Aruba shop an currently find our masters via dns, but are also exploring giving the master controller address via DHCP option 43. We currently have this working on a limited basis and have it defined in a particular scope, but have found that its seems to be working as a global option. So, and AP that gets DHCP from this server via a different subnet and therefore a different scope that does not have the subclass details for the master controller defined, in the end still gets the IP address as defined in a different scope..... I wondering if this is just how it works ? or can a define different master controllers on a per-scope basis ? Ken Connell Intermediate Network Engineer Computer & Communication Services Ryerson University 350 Victoria St RM AB50 Toronto, Ont M5B 2K3 416-979-5000 x6709 ********** Participation and subscription information for this EDUCAUSE Constituent Group discussion list can be found at http://www.educause.edu/groups/. ********** Participation and subscription information for this EDUCAUSE Constituent Group discussion list can be found at http://www.educause.edu/groups/.
