I've got HREAP working well, in that when an AP loses conenctivity with the WLC the AP continues to push out a LAN over radio and clients are authenticated back onto a radius server that the AP can see when disconnected.
I have one burning question: When an AP in HREAP power-cycles (and still cannot see the WLC), does it lose its HREAP config? I'll be really, really annoyed if it does.
This is what I'm seeing at the moment. A newly rebooted LAP just seems to spend its time saying
7 -rwx 7192 Mar 1 2002 00:00:31 +00:00 private-multiple-fs
The top one is a reap.cfg file, which when I do a 'more' command contain some basic information about the WLAN that is supposed to be being pushed out by the radio, but for some reason the LAP is ignoring this and spending time trying to get to a WLC that it can never reach - as i've created a fake WAN failure between the LAP and WLC.
I have tested this in my lab and was able to reconnect and pull an IP after a AP in H-REAP standalone mode after a reboot of the AP. It will take a few minutes after the AP reboots before it will kick over to standalone mode. It will try to join a controller first. After it fails it will revert back to standalone mode and the WLAN will be available.