DHCP Client will not work on a WLAN 4402

Question

Wireless Scenario
I am attempting to create a wireless network using a 4402 WLAN Controller and 1200 series LWAPP access points.
The WLAN Controller has the following interface settings:
Management Interface 10.71.50.9
Ap-Manager Intereface 10.71.50.8
Virtual Interface 1.1.1.1
VLAN 451 10.29.64.27
I have two access points that both pulled a DHCP Address and recognize the WLAN Controller.
Access Point 1 10.29.64.20
Access Point 2 10.29.64.21
I have configured the WLAN Controller to use the Cisco ACS Server for Authentication. I am using LEAP at present, but intend to go with certificate based authentication at a later date. The ssid I am using is ybor-wirenew. The client gets authenticated and associated but does not get an IP Address from DHCP.
I have tried the internal DHCP server on the controller, and although the wireless client gets a 10.29.64.x address it will not communicate with the default gateway or the rest of the network.
The only thing that works is creating a scope on the 10.71.50.x network. The client then gets an address and functions normally.
I need this to work across subnets. Is there something that I am missing???

Answer 1

The problem is with your AP's and wireless clients being in the same subnet/vlan. I learned the hard way the thw WLC's expect the AP's to appear like any other client device on your wired network. Once they are associated with the WLC, your wireless clients are dropped into a different VLAN/subnet. An example config would be:
Management - 10.0.1.2 VLAN 1
AP-Manager - 10.0.1.3 VLAN 1
AP - 10.0.2.2 VLAN 2
Wireless Clients - 10.0.3.x VLAN 3
There are other known issues with crossing address space and the service port on the WLC.