It wouldn’t get an IP address from the network DHCP server until I ran set management dhcp-status up on the serial line console.
Then I used the web interface to enable the embedded DHCP server, set the wireless security settings, set the country settings (this will reboot the AP) and the NTP server. In the DHCP server settings leave the DNS and WINS server addresses to the default 0.0.0.0, the clients will use the AP.
On the serial or SSH console the set and get commands followed by TAB reveal most available options. save-running may be necessary to make sure changes are saved between reboots.
This always takes me ages to remember and the graphical interfaces never seem to work. I still haven’t got it quite right but here are some hints.
- Don’t forget to start bluetooth with
sudo /etc/init.d/bluetooth start.
hcitool dev gives you the address of your device.hcitool scan gives a list of nearby devices with their addresses.rfcomm connect 2 00:12:34:56:78:9A. The number after connect seems to determine the name of the file which will be created in /dev/, in this case it will be /dev/rfcomm2. I always end up using a new number because the old device files remain and won’t let rfcomm connect again.- I didn’t need to use
sudo hcitool cc 00:12:34:56:78:9A or sudo hcitool auth 00:12:34:56:78:9A.
