EDIT: Oh no, the following just ends up in a new static IP: The one that it got the last time pulling one from the DHCP! This is rude!
OMG - so why there is no documention how to set an AP back to DHCP??
First step is done:
- enable DHCP-Server on controller (done)
- connect to managed AP via BLE (done)
- reboot AP (done)
- interrupt boot procedure (done)
- "DHCP" (done)
- "save" (done)
- "boot" (done)
- pray (done)
Now all APs are back from static IP to DHCP again.
No, they are not: they just have a new static IP from the DHCP-range which will surely end up in "duplicate IP address" failures as long as I do not exclude all these IPs from DHCP now.
It is a hard job to find out the correct way:
- BluConsole on iOS crashes sometimes,
- Very often one can connect to AP but no login screen will appear and soon you will be disconnected. Only way I could find out to get really access: Boot AP via controller and be very (!) fast
- CLI on APBoot differs from "normal" CLI on AP, could not find a good and human readable documentation of CLI syntax
- it is documented how to set static IP - but did not found how to go back to DHCP!
- The apboot command "dhcp" is not well described. From the description one could think that it will pull an IP just for the moment and show it on the console...)
So good luck to anyone else in this situation - above is the solution