|Charles Reid 3f35c8b7ad update with working south seattle wifi config||2 weeks ago|
|.gitignore||3 weeks ago|
|LICENSE||3 weeks ago|
|README.md||2 weeks ago|
|auto-reconnect.sh||2 weeks ago|
|check_for_wifi_on_boot.sh||2 weeks ago|
|confusing.md||3 weeks ago|
|securenet.cfg||2 weeks ago|
|southseattle.cfg||2 weeks ago|
|unencrypted.cfg||2 weeks ago|
Scripts to help Raspberry Pis join wifi networks.
Should just be able to add the following lines to
... auto wlan0 allow-hotplug wlan0 iface wlan0 inet dhcp wpa-ssid NetName wpa-psk NetPassword
This will allow the Pi to connect to the wifi network automatically (on boot). This can be manually added to the Pi for whichever network it is going to join. Or...
/etc/network/interfaces file can include the contents of other files.
From the contents of the interfaces manpage:
Lines beginning with "source" are used to include stanzas from other files, so configuration can be split into many files. The word "source" is followed by the path of file to be sourced. Shell wildcards can be used. (See wordexp(3) for details.)
So we can include or remove various wifi configurations by including or removing a configuration file.
For example, for an open network like South Seattle,
we add the following line to
southseattle.cfg contains the WPA ssid
for the South Seattle wifi netowrk,
auto wlan0 allow-hotplug wlan0 iface wlan0 inet dhcp wpa-ssid NetName #wpa-psk
Alternatively, for an encrypted network,
dropbear.cfg contains the WPA ssid and key
for the dropbear wireless router:
auto wlan0 allow-hotplug wlan0 iface wlan0 inet dhcp wpa-ssid dropbear wpa-psk abcdefg123