I've been playing around with the broadcom wl module - the one in the repo is compiled to use the depreciated wext interface, but it can also be compiled to use the more recent cfg80211 interface.
Using the wext interface with an ap using wpa2 (aes) with no ssid broadcast - I can connect by issuing commands manually, but wifi.sh will only connect if the ssid is broadcast. I have to issue the udhcpc command twice due to a bug with the wl wext module, but wifi.sh will connect first time.
Using the cfg80211 interface with an ap using wpa2 (aes) with no ssid broadcast - I cannot connect by issuing commands manually and wifi.sh will only connect if the ssid is broadcast.
The manual commands I use are: $ sudo wpa_supplicant -B -i eth1 -c/etc/wpa_configure.conf
$ sudo udhcpc -b -i eth1 -x hostname:boxdell -p /var/run/udhcpc.eth1.pid
The commands wifi.sh uses are: # wpa_supplicant -i eth1 -c /etc/wpa_supplicant.conf -B
# udhcpc -n -i eth1
Using the cfg80211 interface, if I save the wifi.db created with ssid broadcast enabled and use it with "sudo wifi.sh -a" with ssid broadcast disabled, wifi.sh will not connect. If I use manual commands with the wpa_supplicant.conf created by wifi.sh, I cannot connect.
What I'd like to do is use the wl module in cfg80211 mode with either manual commands or wifi.sh with with ssid broadcast disabled - is there something I'm missing?