Well I've figured it out! Since no one else has answered (or possibly the mods are just really slow at approving messages) I was determined to get this working. After scouring across various guides, I realized where I was lacking understanding. I ended up just keeping with busybox instead of Apache. You can replicate this with the default image that comes on the board.
Here are the steps to get a locally hosted web page going on your Connect Core SBC Board:
1.) Create a softAP access point
a.) Modify your wpa_suppplicant config file in /etc/wpa_supplicant.conf
# SoftAP mode (WPA-PSK/AES)
ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=0
fast_reauth=1
update_config=1
ap_scan=2
network={
ssid="AES-AP" #this is what you will see on the devices you want to connect
mode=2
frequency=2412
key_mgmt=WPA-PSK
proto=RSN
pairwise=CCMP
psk="aes_dev_ap" #enter in passphrase of choice
}
b.) Generate your WPA key for your devices to use by using 'wpa_passphrase' on your CCiMX6UL
root@ccimx6ulsbc:~# wpa_passphrase AES-AP aes_dev_ap
c.) Kill wpa_supplicant if its currently running
root@ccimx6ulsbc:~# killall wpa_supplicant
d.) Run the wpa_supplicant daemon again with the following parameters:
root@ccimx6ulsbc:~# wpa_supplicant -i wlan0 -D nl80211 -c /etc/wpa_supplicant.conf -B
e.) Check and make sure the daemon is running:
root@ccimx6ulsbc:~# ps | grep wpa_supplicant
2.) bind an IP address to your wlan interface (in this case wlan0):
root@ccimx6ulsbc:~# ifconfig wlan0 192.168.40.1 netmask 255.255.255.0 broadcast 192.168.40.255 up
3.) Now we must enable dhcp on this network interface so that devices that connect get an IP assigned
a.) Create a configuration file for the dhcp daemon to use:
root@ccimx6ulsbc:~# vi /etc/dhcp/udhcp.conf
start 192.168.40.1 #range start for IP assigning addresses
end 192.168.40.200 #range end
interface wlan0 #specify our wireless interface
option subnet 255.255.255.0
option router 192.168.40.1
option lease 43200
option dns 192.168.40.1
option domain local
:wq
b.) Create a lease file for the dhcp daemon (the daemon will complain if it doesn't exist):
root@ccimx6ulsbc:~# touch /var/lib/misc/udhcpd.leases
c.) Start the daemon with our configuration file(use -S to post messages to syslog):
root@ccimx6ulsbc:~# /usr/sbin/udhcpd -S /etc/dhcp/dhcpd.conf
d.) Make sure the daemon is running:
root@ccimx6ulsbc:~# ps | grep udhcpd
(optional)
4.) By default the httpd daemon seems to bind to all interfaces, but if you want to bind it to a specific address or interface you can end the server by killing the process (find the process PID using 'ps' and then kill it using 'kill -9 <pid>') and restart the httpd daemon by running:
root@ccimx6ulsbc:~# /usr/sbin/httpd -p 192.168.40.1:80 -h /srv/www
At this point, after connecting your device to your connect core board (using the key we generated in 1.b) you should be able to see your web page by entering the IP address of your wlan0 interface into your browser!
Now my only remaining task is determining why my yocto configuration did not yield an image that had the wlan0 interfaces. I will explore this next!