WAP(config)#dot11 ssid Coolness Cisco-WAP(config-ssid)#authentication open Chapter 29: Wireless The authentication open command tells the WAP that no authentication is necessary to gain access to the wireless network. If we needed to have users authenticate to this WAP, we might use a shared key with the authentication shared command or even leap with the network eap command. Though WEP requires a shared key, which offers a rudimentary form of authentication, it is not strictly an authentication method. While open authentication sounds like a bad idea (and it is in the case of my single WAP), when you're using wireless LAN controllers, a guest VLAN would likely be set up with open access, and authentication would be performed by the controller. If you've ever stayed in a hotel where you were allowed to connect to the wireless LAN, and then pre- sented with an authentication website, you've used this type of setup. Now I need to configure a DHCP pool for the wireless clients to use. This pool will provide IP addresses to the clients when they connect, as well as DNS server and domain information. To make things interesting, I'm going to limit the range to the IP addresses 192.168.1.100 through 149. I wouldn't normally do this, because I prefer to allocate IP addresses on subnet boundaries, but this reflects some real installations I've seen. People tend not to think about subnet boundaries, after all. First, I need to exclude addresses from the range, specifically because I'm not using a range that fits within a subnet: Cisco-WAP(config)#ip dhcp excluded-address 192.168.1.1 192.168.1.109 Cisco-WAP(config)#ip dhcp excluded-address 192.168.1.150 192.168.1.255 Now that I've created the exclusions, I can create the pool. Since this is a wireless device and there can be more than one SSID, the pool is assigned to the SSID. Here, I enter the ip dhcp pool SSID command and then issue the shown commands, all of which should be obvious to anyone who has worked with DHCP: Cisco-WAP(config)#ip dhcp pool Coolness Cisco-WAP(dhc