Scripts to help Raspberry Pis join wifi networks.
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Charles Reid b07de297ec updating MIT license. 7 years ago
.gitignore keep from accidentally committing passphrases 8 years ago
LICENSE updating MIT license. 7 years ago
README.md adding /etc/network/interfaces config files for encrypted and unencrypted wifi networks. 8 years ago
auto-reconnect.sh add bit more detail. 8 years ago
check_for_wifi_on_boot.sh check for wifi on boot 8 years ago
confusing.md there are a dozen ways, apparently, to connect to wifi in Linux, all or most of them broken. 8 years ago
securenet.cfg adding /etc/network/interfaces config files for encrypted and unencrypted wifi networks. 8 years ago
southseattle.cfg update with working south seattle wifi config 8 years ago
unencrypted.cfg adding /etc/network/interfaces config files for encrypted and unencrypted wifi networks. 8 years ago

README.md

pi-join-wifi

Scripts to help Raspberry Pis join wifi networks.

Joining Encrypted Wifi Networks

Simplest Possible Method

Should just be able to add the following lines to /etc/network/interfaces:

...

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...

Scripted Method

The /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 /etc/network/interfaces:

source /etc/network/interfaces.d/southseattle.cfg

where 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,

source /etc/network/interfaces.d/dropbear.cfg

where 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