PiBox

I found the problem. Hostapd 2.0 doesn't work if wpa_supplicant is running. So I killed wpa_supplicant and started hostapd and that got it running again. The question is whether or not it will accept connections. Based on this post for ArchLinux it seems it should. I just need a test for that. Probably testing to see if the PiBox ssid is visible and then trying to connect to it from my laptop.

1. when switching to AP the network restart doesn't kill wpa_supplicant
2. Start dhcpd fails because /var/lib/dhcp doesn't exist and the leases file needs to be created (/var/lib/dhcp/dhcpd.leases)
3. The static IP address from bui-network-config might not work with the address range in dhcpd.conf. The default IP address for the AP should be 192.168.3.1.

Do all this and the host goes into AP mode and starts serving up dhcp addresses.

Got it working tonight. The trick was to add the following to /etc/hostsapd.conf

auth_algs=1
wpa_pairwise=TKIP
macaddr_acl=0
ignore_broadcast_ssid=0
hw_mode=g

Not sure exactly which fixed the problem but I know changing auth_aug back to 2 (as it is now) causes it not to work. I'm pretty sure that was the issue since the other options don't seem that important.

Since bui-network-config writes this file from the code without a template file I'll have to fix the code (and/or make it use a template file).

Updated bui-network-config to write the defaults for these values. Tested on dev system. Need to verify on target.

Verified working on target.

Closing issue.