I have seen a few posts about this issue but no solution that I could find. I am seeing Mac OS, iOS, Android, Windows clients all getting an a 169.x.x.x address after roughly a week of the APs being on and then I will have to reboot the controller to fix the failed DHCP issue. Wired clients do not have this issue. Any help to point me in the right direction would be great.
------------------------------
Chad Sparrow
------------------------------