OK, so we have an existing Wireless network on our corporate LAN consisting of three Cisco 1100 WAPs working in conjunction with Microsoft IAS server. Works great. The problem is these AP's are spread around the building allowing coverage for the entire building. We have a staff room where we occasionally have large training events for up o 30 people. The staff room is covered by one AP only and 30 wireless clients will overwhelms the 100MB connection to the LAN for this AP. So, I need to add a couple more AP's in this room. The idea was to get a few inexpensive WAPs and set up two new training wireless networks that we can turn on during these training events and then store in a closet when not training. I ordered two Cisco WAP610N Wireless Access Points only to discover they only work in conjunction with a Linksys router. There is no Web GUI to configure them. you plug them into a Linksys router and then configure them form the Web Gui of the router (at least that is my impression from speaking to support who were clueless as expected).
Anyway, these will not work for us so I'm looking at other more advanced and more expensive Access points that I can configure. The issue is DHCP relay. It seems you can either allow the WAP to get an IP from DHCP or you can assign a static IP. The issue I have is how do the Wireless clients obtain an IP. My impression is most of the WAPs do not relay DHCP and they also do not act as a DHCP server. If I assign a static IP to the WAP then connect a wireless client how will they obtain an IP address? Do I need a Wireless router instead that I can plug into the LAN and assign a static IP then configure it to pass out DHCP addresses in a different subnet to the wireless clients? The router will then route between the LAN and the new Wireless subnet?
The current AP's do relay DHCP but they are expensive and they are all using the same SSID. If I just add another 1100 in this staff room I then run into the issue of splitting the wireless clients between the two APs in the same room with the same SSID. I know this is wordy explanation of the issue and I've probably left out some key information but it should start the conversation at least.